Lineage Introduction
Lineage is the record of how data moves between containers and between the fields inside them, drawn as a graph on every container's Lineage tab. This deep dive is the reference for the concepts behind it. Here you will find what a connection is and the rules a connection has to obey, the four places connections come from and how each one is created, updated and removed, how to read the graph on the canvas and what an asset outside Qualytics looks like on it, how field-level lineage differs from container-level, worked scenarios, the practices that keep a graph trustworthy, and who can change what.
A data quality issue rarely stays where it starts, and a problem in a raw table spreads to every report and system fed by it. Lineage is what turns that from an investigation across several systems into a walk along a graph: upstream to the container that introduced the problem, downstream to everything that depends on what just broke. It also answers quieter questions, like which transformation carries one column, or which stages of a pipeline live in which datastore.
What You Will Find Here
-
How It Works
The connection model, the two levels of granularity, the rules a connection has to obey, and how to find the containers that have one.
-
Lineage Sources
The four categories a connection can come from, and how each is created, updated, and removed.
-
Reading the Graph
Direction, nodes, assets outside Qualytics, where a connection came from, and expanding the graph.
-
Field-level Lineage
Expanding field lists, field metadata, and the focal field workflow.
-
Examples
Enrolling a warehouse, a medallion pipeline across datastores, a remediation table, and a hop only a person can record.
-
Best Practices
Which source to lean on, how to run collection, and how to keep a graph you can trust.
-
Permissions
The add-on gate, what each role can do, and why a deleted connection can come back.