Introduce series-based event discovery to limit processing to relevant events #1380
Conversation
This file contains hidden or 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
…t events, This PR introduces a new discovery method to ensure only events related to the current Stud.IP instance are processed. - Events without a series ID will still be processed, as there's no reliable way to determine their relevance. - Events with a series ID will be checked against the list of known series for the current instance. If the series is unknown, the event is skipped as unrelated.
ferishili
added
type:enhancement
type:bug
v:3
|
Discussion:
[UPDATE]: I found that taking the migration approach would impose significant constraints on Opencast for a certain period, which could potentially lead to unintended behavior. |
|
This pull request has conflicts ☹ |
- pass user series when uploading from workspace - add a checker/mapper to insert user series for those events without series based on perms "owner"
|
@tgloeggl; |
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 PR
(partialy)fixes #1372,This PR introduces a new discovery method to ensure only events related to the current Stud.IP instance are processed.
Events without a series ID will still be processed, as there's no reliable way to determine their relevance.
Events with a series ID will be checked against the list of known series for the current instance. If the series is unknown, the event is skipped as unrelated.
[UPDATE]: with latest changes new approaches have been added: