# 36 lineage terms, each with an example from a real tool

GLOSSARY, read 10 Nov 2026

**The short answer.** The Upstream glossary defines 36 data lineage terms, from table-level and column-level lineage to OpenLineage facets, ACCESS_HISTORY, dbt exposures and persona-scoped context. Each term carries a plain definition and one example from a named tool, with the source URL and the date it was read.

- [data lineage](/glossary/data-lineage/): A record of where data comes from and where it goes.
- [table-level lineage](/glossary/table-level-lineage/): Lineage that links whole tables, views and models to each other.
- [column-level lineage](/glossary/column-level-lineage/): Lineage that links individual columns across tables.
- [field-level lineage](/glossary/field-level-lineage/): Lineage down to a single field, usually a column in a table or a field on a BI dashboard.
- [transformation lineage](/glossary/transformation-lineage/): Lineage that records how a value was changed on its way, not only where it moved.
- [BI lineage](/glossary/bi-lineage/): Lineage that continues past the warehouse into dashboards, reports and workbooks.
- [metric lineage](/glossary/metric-lineage/): Lineage that follows a business metric, such as revenue, back to the columns and filters that define it.
- [upstream](/glossary/upstream/): Everything that feeds a given asset: the tables, columns and jobs that come before it in the flow of data.
- [downstream](/glossary/downstream/): Everything that depends on a given asset: the tables, dashboards and models that come after it.
- [impact analysis](/glossary/impact-analysis/): Checking what will be affected before a change ships, by walking downstream from the thing you plan to alter.
- [root cause analysis](/glossary/root-cause-analysis/): Working backward from a bad number or failed check to the step that caused it.
- [lineage graph](/glossary/lineage-graph/): The network of assets and the links between them that a lineage tool builds.
- [SQL parsing](/glossary/sql-parsing/): Reading the text of SQL statements to work out which columns feed which.
- [query log lineage](/glossary/query-log-lineage/): Lineage built from the history of queries a warehouse has already run.
- [runtime lineage](/glossary/runtime-lineage/): Lineage emitted by a job while it runs, describing the inputs and outputs of that specific run.
- [design-time lineage](/glossary/design-time-lineage/): Lineage worked out from code and configuration before anything runs.
- [OpenLineage](/glossary/openlineage/): An open standard for describing lineage events, hosted by the LF AI & Data Foundation.
- [OpenLineage facet](/glossary/openlineage-facet/): An extension block attached to a run, job or dataset in an OpenLineage event.
- [Marquez](/glossary/marquez/): The open-source reference implementation of the OpenLineage API.
- [run event](/glossary/run-event/): A single OpenLineage message saying that a job run started, completed or failed, with its input and output datasets.
- [job](/glossary/job/): In OpenLineage, a process that reads datasets and writes datasets, such as an Airflow task, a Spark application or a dbt model run.
- [dataset (OpenLineage sense)](/glossary/dataset-openlineage-sense/): In OpenLineage, any named collection of data a job reads or writes: a table, a file, a topic.
- [dbt manifest](/glossary/dbt-manifest/): The manifest.json file dbt writes after a run, describing every model, test, source and the dependencies between them.
- [dbt exposure](/glossary/dbt-exposure/): A dbt declaration that something outside the project, such as a dashboard, depends on certain models.
- [ref() in dbt](/glossary/ref-in-dbt/): The dbt function one model uses to point at another, as in ref('model_a').
- [ACCESS_HISTORY](/glossary/access-history/): A Snowflake Account Usage view that records which objects, including columns, each query read and wrote.
- [GET_LINEAGE](/glossary/get-lineage/): A Snowflake SQL function that returns upstream or downstream lineage for an object.
- [Unity Catalog lineage](/glossary/unity-catalog-lineage/): The lineage Databricks captures for tables registered in Unity Catalog.
- [tag propagation](/glossary/tag-propagation/): Copying a tag, such as PII, from one asset to the assets built from it along lineage links.
- [semantic layer](/glossary/semantic-layer/): A shared set of business definitions, such as metrics and dimensions, that sits between raw tables and the tools that query them.
- [data observability](/glossary/data-observability/): Monitoring data for freshness, volume, schema changes and quality problems, with alerts when something breaks.
- [MCP (Model Context Protocol)](/glossary/mcp-model-context-protocol/): An open protocol that lets an AI application call tools and read data from another system through a standard interface.
- [persona-scoped context](/glossary/persona-scoped-context/): Context for an agent that is filtered by the role of the person asking.
- [metadata-only access](/glossary/metadata-only-access/): A way of connecting a lineage tool to a warehouse so it reads schemas, query logs and usage but not table contents.
- [stitching (cross-system lineage)](/glossary/stitching-cross-system-lineage/): Joining lineage collected from separate systems into one connected graph, for example warehouse queries, a dbt project and a BI tool.
- [lineage freshness](/glossary/lineage-freshness/): How soon the lineage graph reflects a change in the real pipeline.

Last reviewed 10 Nov 2026. Canonical: https://datalineagecompare.com/glossary/
