MODE-1961 Fixed the processing of mixins when nodes are imported from an XML file using IMPORT_UUID_COLLISION_REMOVE_EXISTING, multiple times. #865
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
XML file using IMPORT_UUID_COLLISION_REMOVE_EXISTING, multiple times. The problem was caused by the fact that the same NodeKey is reused, causing in effect the old persisted node(s) to be seen together with new nodes (which are supposed to be created by the import). Thefore, mixins would not be set on the new nodes because they appeared as "already existing".
|
Yeesh. Merging now. |
|
Merged into the 'master' branch and rebased into the '3.3.x' branch. |
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 problem was caused by the fact that the same
NodeKeyis reused, causing in effect the old persisted node(s) to be "seen" together with new nodes (which are supposed to be created by the import). Therefore, mixins would not be set on the new nodes because they appeared as "already existing".