Check for existence of related object in IngestedRelationshipsTransformer#14
Open
mike-jones wants to merge 6 commits intoredbox-mint:masterfrom
Open
Check for existence of related object in IngestedRelationshipsTransformer#14mike-jones wants to merge 6 commits intoredbox-mint:masterfrom
mike-jones wants to merge 6 commits intoredbox-mint:masterfrom
Conversation
…handled such that: - related object existence checking may be done (configurable with the "checkExistence" property) - forced updating of the relationships on a harvested record (configurable with the "forceUpdate" property)
ghost
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Added logic and configuration options to control the behaviour of the IngestedRelationshipsTransformer's handling of related objects.
Check for existence of the related object before creating the relationship. This logic is activated by using the boolean option "checkExistence" (which may exist within the relationship definition of the JSON config).
Forcibly update relationship metadata (at harvest time) - overriding the existing PROPERTY_FLAG check. This logic is activated by using the boolean option "forceUpdate" (which may exist directly under the "ingest-relations" section in the JSON config).