# stitching (cross-system lineage), defined with a sourced example

GLOSSARY, read 10 Nov 2026

**The short answer.** Joining lineage collected from separate systems into one connected graph, for example warehouse queries, a dbt project and a BI tool. It works by matching asset names across sources. Gaps appear where names do not match or a system is not connected. Snowflake says Horizon Context stitches lineage from query history, external query logs, BI systems and OpenLineage events.

## Definition

Joining lineage collected from separate systems into one connected graph, for example warehouse queries, a dbt project and a BI tool. It works by matching asset names across sources. Gaps appear where names do not match or a system is not connected.

## Example from a real tool

**Example.** Snowflake says Horizon Context stitches lineage from query history, external query logs, BI systems and OpenLineage events.

## Related terms

- [lineage freshness](/glossary/lineage-freshness/): How soon the lineage graph reflects a change in the real pipeline.
- [data lineage](/glossary/data-lineage/): A record of where data comes from and where it goes.
- [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.

## Where to read more

- [The Lineage Depth Matrix](/matrix/)
- [All glossary terms](/glossary/)

## Sources

- docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md: https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalineagecompare.com/glossary/stitching-cross-system-lineage/
