-
Notifications
You must be signed in to change notification settings - Fork 182
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
Store block offsets in disk data cache #611
Conversation
Signed-off-by: Alessandro Passaro <[email protected]>
Signed-off-by: Alessandro Passaro <[email protected]>
7da517b
to
b6214f5
Compare
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.
In the interest of stabilizing the format on disk, I'm inclined to merge as is.
I do like the idea we discussed of having some kind of guard type that wraps something and requires a certain set of metadata to be provided before allowing code access to the contents. Let's do this at a later point.
Signed-off-by: Alessandro Passaro <[email protected]>
Signed-off-by: Alessandro Passaro <[email protected]>
Description of change
Add the block offset to the header stored in each cache block. This allows for additional consistency checks when reading or writing to the cache, where the offset can be compared with the block index.
Does this change impact existing behavior?
It does change the on disk cache format, but it is still currently under the
caching
feature flag.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).