operator migrate use path as Entry key #6043
Closed
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
use path as Entry key to prevent a situation where migration results with the inconsistent state on dst
|
|
|
This is actually seems like a Postgres storage backend bug, or at least quirk. As far as I can tell all of the other builtin storage backends populate the |
|
@kalafut yeah, I also thought this might be a PG issue, so I used this fix on a fork to unblock myself, and it worked. If I will have some more time I will try to investigate this from PG perspective too. |
|
FYI: #6044 |
|
Thanks for reporting the bug! |
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.
use path as Entry key to prevent a situation where migration results with the inconsistent state on dst