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
Currently, Marquez displays the parent jobs and their child jobs independently with no lineage connection. For exemple, a Airflow task initiated in an Airflow DAG is not visually linked in the UI to its parent, although the information is present in the ParentRunFacet.
Closes: #2484
Solution / Open Questions
This solution mainly serves as the trigger of a larger discussion towards full parent/child hierarchy handling in Marquez. Adding a Job to Job representation in the lineage could be a great step toward a retrieving a more complete picture of the data landscape in general.
For now, the proposed modifications only focuses on the backend API, adding the Job UUID along with the parent name to the job metadata returned.
This could be used by the Front End to display the parent node as a short-term solution.
If we want to go further, this work leads to implementation questions:
One-line summary:
Checklist
CHANGELOG.md(Depending on the change, this may not be necessary)..sqldatabase schema migration according to Flyway's naming convention (if relevant)