As an adopter, I wish to avoid data loss during ingest

Description

A Site configurable merge strategy for ingested catalogs to avoid data loss

It should be site configurable whether to keep episode updates from OC system or overwrite existing catalogs during ingest from Capture Agent.

The difference in 5x vs 1.6x merge strategy is demonstrated in the difference in the log lines in the Ingest merge (the square bracket is my emphasis).

Current OC DEVELOP:

1 2 logger.info("Ignore [existing] scheduled element '{}', there is already an [inbound] ingested element with flavor '{}'", element, element.getFlavor());

"Old" OC/MH:

1 2 logger.info( "[Existing] Mediapackage {} already contains a catalog with flavor {}. Skipping the conflicting [inbound] ingested catalog", existingMediaPackage, catalogFlavor);

Steps to reproduce

None

Status

Assignee

Karen Dolan

Reporter

Karen Dolan

Criticality

None

Tags (folksonomy)

None

Components

Fix versions

Affects versions

5.0

Priority

Minor
Configure