Add a caching strategy version number. #9409
Open
+14
−0
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
When a weight cache implementation persists data between runs, it needs to be informed when the caching strategy changes (for instance when caching is added to an operation). Note that implementations could already find out if caching for a specific operation has changed by checking caching fingerprints. This doesn't work when an operation that wasn't cached previously starts being cached. PiperOrigin-RevId: 859494304
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add a caching strategy version number.
When a weight cache implementation persists data between runs, it needs to be
informed when the caching strategy changes (for instance when caching is added
to an operation).
Note that implementations could already find out if caching for a specific
operation has changed by checking caching fingerprints. This doesn't work when
an operation that wasn't cached previously starts being cached.