Inconsistent catalog update behaviour in Ingest/Upload

Steps to reproduce

Not sure if this is a bug or feature... It could be a feature if taking the episode.xml from the ingest package is a recovery mechanism after an ingest failure.

Situation:
The ingest "startover==true" takes the episode.xml in the inbound mediapackage. Otherwise (on initial ingest), the existing episode.xml from the scheduled MP is preserved.

Actual Results: Inconsistent ingest policy on updating existing episode DC catalog on initial and retry ingest.
Expected Results: Consistent behavior.

From startover true code:
// Get episode dublincore from scheduler event [only] if not [already] provided by the ingesting party

From startover false code:
// if the existing mediapackage contains a catalog of the same flavor, keep the server-side catalog, since it is more likely to be up-to-date

Related Tickets:

Activity

Show:
Former user
September 3, 2013, 2:06 PM

The ingested series overwrites existing series prior to these logs:
2013-08-29 00:19:34 INFO (IngestServiceImpl:877) - Mediapackage 9d9b3352-4d43-4668-b7cc-11a8cc75ec03 already contains a catalog with flavor dublincore/episode. Skipping the conflicting ingested catalog
2013-08-29 00:19:34 INFO (IngestServiceImpl:877) - Mediapackage 9d9b3352-4d43-4668-b7cc-11a8cc75ec03 already contains a catalog with flavor dublincore/series. Skipping the conflicting ingested catalog

Greg Logan
October 22, 2019, 8:03 PM

Out of date, and somewhat of known issue in terms of XML catalogs fighting.

Assignee

Unassigned

Reporter

Former user

Severity

Incorrectly Functioning Without Workaround

Tags (folksonomy)

Components

Affects versions

Priority

Minor
Configure