Can reviewers see lineage impact in a pull request?
Surface the affected downstream assets in CI on each PR, so reviewers understand the blast radius of a change before approving it.
Command
bruin lineageDefined in
SQL + YAML
Works with
Bruin CLI + your warehouse
What you get
Impact analysisemergent lineagecross-language
How it works in code
$ bruin lineage ./pipeline --downstream --column orders.amountRun bruin lineage and you see the full downstream blast radius before you change anything.
Related use cases
Impact analysis and debugging
See which columns feed a metric
How do I trace a metric back to its source columns?
Impact analysis and debuggingRun impact analysis before a schema change
What breaks if I drop or rename this column?
Impact analysis and debuggingFind unused columns in a model
Which columns in this table are never used downstream?
Know what a change will break
Open source. Emergent column-level lineage across SQL and Python assets.