Add important notes on HybridCache limitations and behavior #34224
Conversation
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
- Added a note indicating that removing cache entries by tag is still under development and is currently non-functional. - Clarified that cache invalidation by key or tags affects only the current node and secondary storage, but not other nodes' in-memory cache. Ask Copilot
tdykstra
reviewed
Dec 1, 2024
Contributor
tdykstra
left a comment
tdykstra
left a comment
There was a problem hiding this comment.
Thanks, @wilsonneto-dev, a couple suggestions for you to take, and then this is approved.
Co-authored-by: Tom Dykstra <[email protected]>
Co-authored-by: Tom Dykstra <[email protected]>
Author
Great! Sure thing; the suggestions have been accepted. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #34250
Added a note indicating that removing cache entries by tag is still under development and is currently non-functional.
Clarified that cache invalidation by key or tags affects only the current node and secondary storage, but not other nodes' in-memory cache.
Internal previews