This repository was archived by the owner on Mar 4, 2020. It is now read-only.
'Recover' step in Data Import for failed objects. #33
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When migrating a DB with big amount of objects, it is possible that some objects won't be updated properly because of unpredictable reasons (e.g: http connection fails and etc.). We observed that it happens to 5-15 objects when there are ~ 500.000 objects in total to be migrated.
With this PR, we will have a recover step for that kind of objects. To identify those objects, we will query them by empty values in 'Title' field, since all objects in the source instance must have a 'Title'.