Conversation
Bug introduced due to change from data model get method to universal Job.get
…ry for multiple times
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
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.
Close #11
What is done in this MR
By using the
OpenLineageairflow service provider, DataCI is now able to track lineages among different versions of data and code (stage, pipeline)How to reproduce?
The following code is available at
tests/lineage/python_ops_pipeline.pyRun the pipeline using Airflow web UI

The lineage is tracked, write a simple code to query.
Here we track the 3-level dataset downstreams from the test dataset we just manually published.
Expected Result
Sorry for the bad visualization 😿
Copy this to any graphviz visualizer, you can see 3 levels of datasets (and their runs)

Roadmap