Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with File Cache Persistence in Extensions Service #2520

Closed
tenthe opened this issue Mar 8, 2024 · 0 comments · Fixed by #2522
Closed

Issue with File Cache Persistence in Extensions Service #2520

tenthe opened this issue Mar 8, 2024 · 0 comments · Fixed by #2522
Labels
bug Something isn't working
Milestone

Comments

@tenthe
Copy link
Contributor

tenthe commented Mar 8, 2024

Body

  • Files are being cached within the extensions service as expected.
  • However, when a user deletes a file (such as a file stream adapter), it's correctly removed from the backend but remains in the extensions service cache.
  • Consequently, when a new file with the same name is uploaded, the extension service incorrectly uses the old cached file instead of the updated file.

This behavior is also the reason for the failing nightly e2e tests.

StreamPipes Committer

I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.

@bossenti bossenti added this to the 0.95.0 milestone Mar 8, 2024
@bossenti bossenti added the bug Something isn't working label Mar 8, 2024
tenthe added a commit that referenced this issue Mar 11, 2024
#2522)

* refactor(#2520): Add method to check file content in FileProtocolUtils

* refactor(#2520): Move code to hash file into module commons
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants