Fix Scheduler Conflict Checks #3339
Merged
Conversation
This file contains 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
lkiesow
added a commit
to lkiesow/opencast
that referenced
this pull request
Jan 10, 2022
Capture agents often record to filenames containing metadata which allows us to identify an event by looking at a specific time in the schedule of a certain location (capture agent). If `created` and `spatial` metadata could be identified, this patch allows us to look up the schedule, using all available event data fram there if we had a unique match. Data taken from the schedule, overwriting inbox data are: - All metadata - Workflow definition - Workflow configuration Notes: - This patch fixes opencast#3240. - This is based on opencast#3327. - You want opencast#3339 for this.
lkiesow
added a commit
to lkiesow/opencast
that referenced
this pull request
Jan 10, 2022
Capture agents often record to filenames containing metadata which allows us to identify an event by looking at a specific time in the schedule of a certain location (capture agent). If `created` and `spatial` metadata could be identified, this patch allows us to look up the schedule, using all available event data fram there if we had a unique match. Data taken from the schedule, overwriting inbox data are: - All metadata - Workflow definition - Workflow configuration Notes: - This patch fixes opencast#3240. - This is based on opencast#3327. - You want opencast#3339 for this.
7 tasks
This patch fixes the scheduler's conflict checks which previously broke spectacularly if someone already ingested media to one of the found scheduled events. The scheduler woould then find the conflict but would fail to retrieve the media package since it wouldn't be the owner of that event in the asset manager any longer. That does not make a lot of sense for a conflict check where you just want to get the information.
lkiesow
force-pushed
the
scheduler-conflict-check
branch
from
cffee31
to
4ed5516
Compare
lkiesow
added a commit
to lkiesow/opencast
that referenced
this pull request
Jan 17, 2022
Capture agents often record to filenames containing metadata which allows us to identify an event by looking at a specific time in the schedule of a certain location (capture agent). If `created` and `spatial` metadata could be identified, this patch allows us to look up the schedule, using all available event data fram there if we had a unique match. Data taken from the schedule, overwriting inbox data are: - All metadata - Workflow definition - Workflow configuration Notes: - This patch fixes opencast#3240. - This is based on opencast#3327. - You want opencast#3339 for this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This patch fixes the scheduler's conflict checks which previously broke
spectacularly if someone already ingested media to one of the found
scheduled events.
The scheduler woould then find the conflict but would fail to retrieve
the media package since it wouldn't be the owner of that event in the
asset manager any longer. That does not make a lot of sense for a
conflict check where you just want to get the information.
Your pull request should…