Introducing Cross-layer Lineage: One Connected Visualization

ADOC 26.9.0 introduces cross-layer lineage stitching that combines orchestration, processing, catalog, and storage relationships into a single navigable graph intended to simplify incident response, impact analysis, provenance tracking, and compliance evidence. Rather than replacing lineage generated by platforms such as Unity Catalog, AWS Glue, Trino, and Redshift, ADOC consumes their metadata and connects handoffs between systems, linking Airflow DAGs, processing jobs, catalog assets, and underlying storage through concrete mappings and OpenLineage events. The release aims to reduce manual investigation across separate tools by allowing users to trace failures or data changes from scheduled workflows through transformations to downstream datasets, while attaching asset profiles, quality history, and observability information to graph nodes. It also presents the connected graph as more suitable for automated or agent-based reasoning, since dependencies can be graded by the reliability of their evidence. Adoption requires Airflow and processing engines to emit OpenLineage events and relevant catalogs to be crawled into ADOC; once integrated, stitching is designed to occur automatically, with future plans including column-level traversal, additional orchestrators, and richer agent capabilities.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.