tracing-downstream-lineage

Answer the critical question: "What breaks if I change this?" Use this BEFORE making changes to understand the blast radius. Find everything that reads from this target: For Tables: Search DAG source code : Look for DAGs that SELECT from this table Check for dependent views : Look for BI tool connections : If you're running on Astro, the Lineage tab in the Astro UI provides visual dependency graphs across DAGs and datasets, making downstream impact analysis faster. It shows which DAGs consume a given dataset and their current status, reducing the need for manual source code searches. For DAGs: Map the full downstream impact: Critical (breaks production): High (causes significant issues): Medium (inconvenient): Low (minimal impact): For the proposed change, evaluate: Schema Changes (adding/removing/renaming columns): Data Changes (values, volumes, timing): Deletion/Deprecation : Identify who owns downstream assets: "Changing fct.orders will impact X tables, Y DAGs, and Z dashboards" Before making changes: - Search DAG source code : Look for DAGs that SELECT from this table - Use af dags list to get all DAGs - Use af dags source to search for table references - Look for: FROM target_table , JOIN target_table - Check for dependent views : -- Snowflake SELECT * FROM information_schema . view_table_usage WHERE table_name = ' ' -- Or check SHOW VIEWS and search definitions - Look...