[MTG-1266] hotfix for migrations when the key encoding changes #386
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
kstepanovdev
approved these changes
Jan 27, 2025
StanChe
changed the title
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.
The previous rocks migration changed the structure of Change Log Items, as well as the key encoding, putting the tree before the index, and thus keeping all tree-related change logs together, rather than dispersed. But the migration was putting the data using the old encoding of the keys, thus rendering invalid keys and no data after the migration. This did not affect the newly added data, or the backfilled data, but the migration itself.
This change allows preserving the data by properly migrating it.