lineage-diff

Comparing column-level SQL lineage between two versions requires parsing the data-flow edges of both queries to identify added, removed, and unchanged connections. This Skill analyzes before and after SQL inputs to produce a structured diff for review.

SQL lineage diffing is the process of identifying changes in data-flow edges between two query versions. You need it during version-control scenarios, code reviews, or data pipeline debugging to assess the impact of modifications on downstream data models.

Yes, you can check git-staged SQL changes for lineage impact by providing the before and after SQL files as manual inputs. The tool computes the column-level data-flow edges and returns a structured diff showing added, removed, and unchanged connections.

Yes, SQL lineage comparison works across any supported SQL dialect. The tool parses the provided before and after SQL inputs, computes the column-level data-flow edges regardless of dialect, and returns the added, removed, and unchanged edges.

To identify added or removed data flow edges in modified SQL models, provide the original and updated SQL files. The analysis computes the column-level lineage for both versions and returns a structured diff detailing the specific edges that were added, removed, or remained unchanged.

The best way to debug data pipeline changes using version control is to compare the column-level lineage of the original and modified SQL. This reveals the evolution of data flow by showing added, removed, and unchanged edges, allowing you to assess the exact impact of your changes.