-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-30022 Refactor CacheConfig and HFileReaderImpl to use CacheAcce… #8279
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
taklwu
merged 1 commit into
apache:HBASE-30018
from
VladRodionov:HBASE-30022-hfile-reader-cache-access-service
May 28, 2026
Merged
Changes from all commits
Commits
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
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.
nit: I'm wondered if we should do this instead? basically, if we let the code follow throw the
non-null/ non-NoOpCacheAccessService, either it's still using any code logic to do no ops, or ifNoOpCacheAccessServicehas any bug or human error in the future, it may be easier to cause another issue.what do you think?
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.
Thanks. I think I would avoid the explicit
instanceof NoOpCacheAccessServicecheck here.CacheAccessServiceis intended to be the abstraction boundary, soHFileReaderImplshould not needto know which concrete service implementation it received. The disabled-cache behavior belongs in
NoOpCacheAccessService; itsgetBlock(...)returns null, so the current flow already exitswithout doing cache work.
If there is concern about future bugs in
NoOpCacheAccessService, I think the better protection isunit coverage for that implementation rather than adding implementation-specific checks in the read
path. This keeps the reader code independent of whether the service is block-cache-backed,
topology-backed, or no-op.