This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
state database versioning #7401
Merged
Conversation
This file contains 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
…ersioning for the application level data. The intent is to have a more direct informative message when the expectations for in-memory layout of application data has changed due to explicit changes to the structure (as opposed to the implicit change detected by our chainbase level checks)
heifner
approved these changes
May 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Change Description
add support for a simple header in the state database which defines versioning for the application level data. The intent is to have a more direct informative message when the expectations for in-memory layout of application data has changed due to explicit changes to the structure(s). This is in contrast to the implicit changes to in-memory layout that we attempt to catch at the chainbase level by detecting compiler/OS/optimization differences.
For the first version of this, any existing un-versioned state database should be automatically upgraded. Future versions will inform users to upgrade via snapshots or replay when the version in the in-memory file is no longer compatible with the code.
Consensus Changes
API Changes
Documentation Additions