Data Lineage Catalog
Capture dataset stewardship and field mappings, import completed OpenLineage runs and trace a proposed change to downstream consumers and owners.
Application guideVerifying your session…
Using Data Lineage Catalog
Identify accountable downstream consumers of a dataset or specific field and inspect evidence for each dependency.
Field-level lineage · Ownership dictionary · Downstream impact
- Inputs and working data
- Namespaced datasets, steward and dictionary, sourced transformation edges, job/run references and selected upstream/downstream impact investigation.
- Working in the editor
- Steward register, field dictionary, manual job mapping, completed OpenLineage RunEvent import and path explorer.
- What can I produce?
- Path and owner evidence in a CSV and JSON investigation package plus an editable catalog.
- What are the limits?
- 200 datasets, 5,000 fields and 2,500 sourced mappings. Completed events with column-level mappings or dataset-level declarations. Dataset-wide indirect column facets require manual mappings.
- Example
- Import two completed jobs, trace an input field to a downstream report owner through both transforms and recover the catalog.