Gen new uuid
for etl_menus
ol events
#2519
Merged
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.
Problem
The OL quickstart produces an invalid lineage graph if Marquez was seeded using the
seed
cmd (see related PR OpenLineage/docs#183). That is, in the lineage graph below, the jobmy-job
should not contain the out edgepublic.menus
as an output dataset (linking the two subgraphs):Solution
Believe it or not, the invalid lineage graph is actually, valid! It's the result of a runID collision. That is, the OL events for
my-job
in the quickstart uses the runIDd46e465b-d358-4d32-83d4-df660ff614dd
, the same runIDd46e465b-d358-4d32-83d4-df660ff614dd
as jobetl_menus
inmetadata.json
. Therefore, the backend assumes the outputs have changed foretl_menus
. This PR generates a new runID4d3b8069-69b6-4708-ade0-3275112c9f04
foretl_menus
to render the expected lineage graph:Checklist
CHANGELOG.md
(Depending on the change, this may not be necessary)..sql
database schema migration according to Flyway's naming convention (if relevant)