-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[rest] Make RESTTokenFileIO cache maximum size configurable #9528
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
Merged
JingsongLi
merged 2 commits into
apache:master
from
tonymtu:rest-token-file-io-cache-size
Sep 2, 2026
+33
−0
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P2] Do not accept a zero cache size with the current ownership model
The new test explicitly makes
0a supported value, but this cache owns its values: its removal listener closes every evictedFileIO. With a Caffeine maximum of zero,fileIO()creates an instance, puts it intoFILE_IO_CACHE, and it is immediately eligible for SIZE eviction/close even though the method then returns that same instance to the current operation. An application using the conventional0 = disable cachingsetting can therefore get a closed FileIO duringnewInputStream,newOutputStream, etc., reproducing the premature-close failure this change is intended to mitigate.Please either require
maximumSize > 0, or implement an explicit no-cache path whose FileIO lifetime extends through the operation instead of inserting it into this owning cache.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in ec3d312. The setter now requires maximumSize > 0, and the test covers the zero value.