Enterprise Metadata Management System  ·  View 06 of 22  ·  Structure

Connector Coverage

What each class of source can actually give up, and where the honest gaps are.

Editable source SVG draw.io All views
Schema & structure
Schema & structure
Usage & popularity
Usage & popularity
Lineage granularity
Lineage granularity
Quality results
Quality results
Classification
Classification
Cloud warehouse
Cloud warehouse
Full
incl. constraints
Full...
Full
access history
Full...
Column level
SQL parsed
Column level...
Via DQ platform
Via DQ platform
Auto + curated
Auto + curated
Lakehouse
Lakehouse
Full
Unity Catalog
Full...
Full
Full
Column level
system tables
Column level...
Native + DQ
Native + DQ
Auto + curated
Auto + curated
Relational OLTP
Relational OLTP
Full
Full
Partial
sampled logs
Partial...
Table level
Table level
Via DQ platform
Via DQ platform
Auto + curated
Auto + curated
BI & reporting
BI & reporting
Full
datasets · fields
Full...
Full
views · viewers
Full...
Field to column
semantic model
Field to column...
Not available
Not available
Inherited
from upstream
Inherited...
Orchestration & ELT
Orchestration & ELT
Jobs & tasks
Jobs & tasks
Run history
Run history
Column level
OpenLineage
Column level...
Test results
dbt tests
Test results...
Not applicable
Not applicable
Streaming
Streaming
Full
Avro · Protobuf
Full...
Partial
consumer groups
Partial...
Topic level
Topic level
Not available
Not available
Auto + curated
Auto + curated
SaaS & files
SaaS & files
Objects & fields
Objects & fields
Not available
Not available
Manual only
declared
Manual only...
Not available
Not available
Curated
Curated
Connector Coverage by Source Class
Connector Coverage by Source Class
Application we own
Application we own
Interface / broker
Interface / broker
Risk / gap
Risk / gap
External / third party
External / third party
Red cells are declared gaps, not omissions. Lineage below column level is stated on each asset profile so trust is never assumed.
Red cells are declared gaps, not omissions. Lineage below column level is stated on each asset profile so trust is never assumed.
v 1.0 · owner Integration Architecture · date 2026-08
v 1.0 · owner Integration Architecture · date 2026-08
Text is not SVG - cannot display

Why this view exists

  • Lineage granularity is a per-source property, not a platform property. Promising column-level lineage across an estate that cannot supply it is the single most common way these programmes lose credibility.
  • Coverage is published on every asset profile, so a consumer sees the strength of the evidence alongside the answer.

Declared gaps

  • No usage metadata from SaaS applications and no quality results from BI or streaming — those systems do not expose them.
  • SaaS and file sources are manual-lineage only at go-live. They are the first candidates for the declarative lineage API.

Assumption

  • Warehouse access-history retention is at least 90 days, which is what column-level lineage inference from query logs requires (view 11).