storage: support bounded mutability - #350
Draft
Jordan Olshevski (jveski) wants to merge 3 commits into
Draft
Conversation
Jordan Olshevski (jveski)
force-pushed
the
mutability
branch
4 times, most recently
from
June 29, 2026 20:29
ce0c063 to
fd2d4a2
Compare
Jordan Olshevski (jveski)
force-pushed
the
mutability
branch
from
June 30, 2026 15:55
fa138b4 to
8703354
Compare
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
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.
Don't assume all values are immutable. Each key is cached for a TTL, after which the value pages may remain in cache, but the metadata will be redownloaded from the backend. If the metadata has changed, new pages will be downloaded. The goal is to guarantee that values will be no staler than a configured TTL.