Skip to main content
Version: 0.13.1

About DataHub Lineage Impact Analysis

Feature Availability
Self-Hosted DataHub
Managed DataHub

Lineage Impact Analysis is a powerful workflow for understanding the complete set of upstream and downstream dependencies of a Dataset, Dashboard, Chart, and many other DataHub Entities.

This allows Data Practitioners to proactively identify the impact of breaking schema changes or failed data pipelines on downstream dependencies, rapidly discover which upstream dependencies may have caused unexpected data quality issues, and more.

Lineage Impact Analysis is available via the DataHub UI and GraphQL endpoints, supporting manual and automated workflows.

Lineage Impact Analysis Setup, Prerequisites, and Permissions

Lineage Impact Analysis is enabled for any Entity that has associated Lineage relationships with other Entities and does not require any additional configuration.

Any DataHub user with “View Entity Page” permissions is able to view the full set of upstream or downstream Entities and export results to CSV from the DataHub UI.

Using Lineage Impact Analysis

Follow these simple steps to understand the full dependency chain of your data entities.

  1. On a given Entity Page, select the Lineage tab

  1. Easily toggle between Upstream and Downstream dependencies

  1. Choose the Degree of Dependencies you are interested in. The default filter is “1 Degree of Dependency” to minimize processor-intensive queries.

  1. Slice and dice the result list by Entity Type, Platform, Owner, and more to isolate the relevant dependencies

  1. Export the full list of dependencies to CSV

  1. View the filtered set of dependencies via CSV, with details about assigned ownership, domain, tags, terms, and quick links back to those entities within DataHub

Additional Resources


DataHub 201: Impact Analysis


Looking for an example of how to use searchAcrossLineage to read lineage? Look here

DataHub Blog

FAQ and Troubleshooting

The Lineage Tab is greyed out - why can’t I click on it?

This means you have not yet ingested Lineage metadata for that entity. Please see the Lineage Guide to get started.

Why is my list of exported dependencies incomplete?

We currently limit the list of dependencies to 10,000 records; we suggest applying filters to narrow the result set if you hit that limit.

Need more help? Join the conversation in Slack!