Support for the PromoteAction strategy [master] #391

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 values

UPSERT (default)
ENRICH

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 values - `UPSERT` (default) - `ENRICH`

Labels Milestones

Support for the PromoteAction strategy [master] #391

Step 1:

Step 2: