Fix problems with bad migration to 1.5 #792
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
The script to migrate from 1.4 to 1.5 did not correctly remove the old `register_node` function. This caused issues for the migration from 1.5 to 1.6, because we remove the old `replication_state` type there. The old `register_node` function still depended on this version of the `replication_state` type, so it's removal was blocked.
|
Fixes #784 |
DimCitus
approved these changes
Sep 2, 2021
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 script to migrate from 1.4 to 1.5 did not correctly remove the old
register_nodefunction. This caused issues for the migration from 1.5to 1.6, because we remove the old
replication_statetype there. Theold
register_nodefunction still depended on this version of thereplication_statetype, so it's removal was blocked.Fixes #784