Skip to content
Upstream

GUIDE, read 10 Nov 2026

Lineage carries meaning when definitions, owners and tags move along the path instead of being retyped at each node

The matrixAll guides

A path without meaning is only a path

A lineage graph tells you column A feeds column B. It does not tell you what B means, who answers for it, or whether it holds a regulated value. Teams attach that information in a catalog, by hand, node by node. It goes stale the day after it is entered, and the label on the source column never reaches the report built from it.

Meaning that travels along the path solves this. Document a source column once, and every column derived from it by a passthrough shows the same text. Mark a column as personal data, and the downstream columns pick up the mark. The effort moves from many nodes to one.

Three ways meaning travels

The evidence shows three mechanisms, and they differ in who has to act.

  • Inheritance by rule. The platform copies a description down through lineage when a simple rule holds. dbt's passthrough and renamed columns inherit descriptions from upstream columns automatically, as far back as possible. Coalesce Catalog copies a parent column's description to child columns only when names match, there is no SQL transform and there is one parent. It states dashboard fields are not covered.
  • Propagation by automation. An app or rule pushes metadata downstream. Atlan's Metadata Propagator pushes owners, certificates, tags and custom metadata from upstream assets to downstream dependents. DataHub's Documentation Propagation sends column descriptions along downstream column-level lineage and sibling relationships, and is enabled by default in open source.
  • Propagation on request. A person triggers the push. Secoda lets users propagate properties such as owners and tags from one resource to related resources, selectable by downstream lineage, with an option to override existing values.

What each tool documents moving along lineage

The table separates what moves from how. Where a page read does not document propagation, the cell says none found on 10 Nov 2026.

ToolWhat moves along lineageHow, per the vendor's docs
dbtDescriptions on passthrough and renamed columnsAutomatic inheritance
Coalesce CatalogParent column description to child columnsAutomatic only if names match, no SQL transform, one parent; dashboard fields not covered
DataHubColumn descriptions; glossary termsDocumentation Propagation on by default in open source; Glossary Term Propagation is Public Beta in DataHub Cloud
AtlanOwners, certificates, tags, custom metadataMetadata Propagator app; can restrict to single-upstream targets
SecodaOwners, tags and other propertiesUser-triggered, with override option
Select StarPII classification tagsVendor says lineage powers such automations
EunoLabels such as certified and PII-free; signals along traced data flowsEuno says governance rules label assets automatically, and it propagates signals along traced data flows
SnowflakeTags, with mismatch detection along columnsLineage tab flags missing or mismatched tags on upstream and downstream columns
AlationOwnership, trust flags, quality scores and definitions shown on nodesDrawn from the catalog; automatic propagation along edges: none found
CollibraNo mechanism named on the lineage pageNone found on 10 Nov 2026

Meaning attached to nodes is not meaning that moves

Alation says lineage nodes carry ownership, trust flags, quality scores and business definitions from the catalog. That is useful: open a node in the graph and see who owns it. But the information is looked up per node. It does not flow from the source to the report. We found no Alation page documenting automatic propagation of tags, classifications or glossary terms to downstream lineage nodes (none found on 10 Nov 2026).

The OpenLineage spec shows the same split in a lighter form. Its ownership dataset facet lists owners with a type such as MAINTAINER. That is metadata attached to an entity in an event. Whether it spreads to downstream entities is up to the consuming tool.

Collibra's lineage page markets lineage with business context and audit trails, and names no mechanism that propagates tags, classifications or ownership along lineage. That does not mean Collibra users cannot do it by other means, only that none was found on the page read.

Conflicts when several sources feed one table

A table fed by three upstream tables has three candidate owners and three candidate classifications. A propagator must choose. Atlan's propagator can restrict itself to single-upstream targets to avoid conflicting metadata when several sources feed one table. Secoda offers an option to override existing values, and leaves the decision to the person who triggers the push. Coalesce Catalog's rule avoids the problem by copying only when there is one parent.

Ask any vendor what happens in the many-to-one case before you turn propagation on. A wrongly propagated PII flag creates work. A wrongly propagated certified flag creates risk.

Where the scores land on meaning

Upstream weights lineage that carries meaning at 20 of 100 points, the second-heaviest criterion. Euno's total is 67.0, first of 16, ahead of DataHub at 62.5, Secoda at 61.5, Atlan at 58.5 and Alation at 55.0. Euno is cloud SaaS only and publishes no dollar prices; a team that needs lineage inside its own network, or a full catalog around it, will pair it with another tool. The totals combine all criteria, so they do not isolate meaning.

DataHub earns its place with documentation propagation that is on by default in open source. Atlan's strength is the explicit propagator app. Secoda's is a documented, controllable push. The matrix and the method page hold the underlying grid and weights.

A test for propagation

Propagation is also a governance decision, not only a feature. If a description travels automatically, whoever wrote the source description now speaks for every downstream column. If an owner travels, the person named inherits questions about reports they have never seen. Decide in advance which attributes should move on their own and which should be set by hand at the report layer. A common split is that classification moves automatically, because a missed PII flag costs more than a spurious one, while ownership and certification are set by a person at each consuming asset.

Also decide where the source of truth lives. If descriptions live in dbt YAML, a propagation tool that writes back into the catalog can create two versions of the same text. Pick one home for each attribute and let the propagation tool copy from it.

Pick a source column and give it a description, an owner and a PII tag. Wait for the next sync. Then open a passthrough column two hops down, a calculated column, and a dashboard field. Record which of the three attributes arrived at each, and how long it took. Then change the source description and see whether the downstream copy updates or stays frozen. A tool that copies once and never refreshes will drift. The result is a small grid of three attributes by three column types, and it is worth more than any feature list. Run it again after a change to the source, since a tool that propagates once and never refreshes fails the second run.

Sources

  1. dbt: docs.getdbt.com/docs/explore/column-level-lineage, read 10 Nov 2026
  2. Coalesce Catalog: docs.coalesce.io/docs/catalog/document-your-data/catalog-scribe/column-descripti, read 10 Nov 2026
  3. DataHub: docs.datahub.com/docs/automations/docs-propagation, read 10 Nov 2026
  4. DataHub: docs.datahub.com/docs/automations/glossary-term-propagation, read 10 Nov 2026
  5. Atlan: docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-l, read 10 Nov 2026
  6. Secoda: docs.secoda.co/resource-and-metadata-management/add-documentation/propagating-me, read 10 Nov 2026
  7. Select Star: www.selectstar.com/product/data-lineage, read 10 Nov 2026
  8. Euno: euno.ai, read 10 Nov 2026
  9. Snowflake: docs.snowflake.com/en/user-guide/ui-snowsight-lineage.md, read 10 Nov 2026
  10. Alation: www.alation.com/product/data-lineage, read 10 Nov 2026
  11. Collibra: www.collibra.com/products/data-lineage, read 10 Nov 2026
  12. OpenLineage: openlineage.io/docs/spec/facets/dataset-facets/ownership, read 10 Nov 2026

Last reviewed 10 Nov 2026.