Fix relation/indexing processing Data object collision #723
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.
processRelated
anddoIndex
may be executed for the same operation object,doIndex
mutates theData
of the operation which breaks the relation processing if the relation processing happens after the indexing.The effect of such a collision may be observed as printed errors like "Source field _id not found in document: ...", because
doIndex
removes the_id
field from theData
object as part of theprepareDataForIndexing
function butextractData
attempts to read it in case if thesrc-field="_id"
The fix separates copies of Data between relation processing and indexing, which eliminates the possibility of such a collision.