Migrations: Add in progress data to migration #925
Merged
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
nodech
added
migrations
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 in progress arbitrary data storage to the migrations. Long running processes may be interrupted and may not have simple way to recover last state. This should allow those migrations to store metadata to the db.
Add version entry to the migration state. Repurpose unused 16 bits of flags into the version, that should allow conditional serialization of the migration state.
Create and pass the migration context to the migrations instead of just passing Results.
Migration context now contains state that will get committed after the migration is done, but also provides saveState for the data.
Add migration to the chain/wallet to increment migration state version.