Support for the PromoteAction strategy #389
No reviewers
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
RDGraph
RSAC
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: D-Net/dnet-hadoop#389
Loading…
Reference in New Issue
No description provided.
Delete Branch "promote_actions_join_type"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR introduces support for two strategies the workflow can use to promote the actionset contents in the graph.
So far the only strategy assumed to upsert each record against the corresponding entity table, merging with the records matched by OpenAIRE id and inserting those that do not match. This turned out to be introducing noisy or stable records often contained in the actionset, which pollute the graph and may cause failures along the graph processing pipeline.
The upsert strategy continues to be the default one, but this modification allows the workflow caller to speficy a different one, named
ENRICH
, which only updates the matching records, while discarding the non-matching ones.Hence, the oozie workflow definition now suppoerts a new optional parameter named
promoteActionStrategy
that can assume two valuesUPSERT
(default)ENRICH
@giambattista.bloisi @miriam.baglioni can you review these changes? Thanks!