Fix bug that caused a single run event to create multiple jobs #2162
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.
Signed-off-by: Michael Collado [email protected]
Problem
As described in #2158 a single run may send multiple run events, where the start event contains a parent run and subsequent events do not. In that case, the subsequent jobs will create a new job without a parent, causing duplicate jobs with the same name.
Closes: #2158
Solution
During OpenLineage event handling, check to see if a run with the given id already exists. If it does, do not create a new job (or parent), but simply use the job that is already associated with the run.
Checklist
CHANGELOG.md
with details about your change under the "Unreleased" section (if relevant, depending on the change, this may not be necessary).sql
database schema migration according to Flyway's naming convention (if relevant)