Metadata Management and Lineage
Scanning a warehouse produces a complete catalog of names and types that answers almost none of the questions people actually arrive with.
Scanning a warehouse produces a complete catalog of names and types that answers almost none of the questions people actually arrive with.
Before changing a column, find everything that depends on it. Lineage finds the pipelines; query logs find the people; neither finds everyone on its own.
Column-level lineage narrows the dependencies to investigate. Its usefulness depends on whether selected fields, filters, joins, and other relevant paths were captured.
The dangerous model change is the one that passes every check. See what breaks consumers, why meaning changes are invisible, and how to publish one safely.
See how run metadata, column-level lineage, coverage measurement, and consumer discovery turn “who uses this column?” into a candidate list you can validate.