OpenLineage export¶

DQL emits OpenLineage events from block and notebook runs so your existing metadata platform sees DQL-level lineage alongside dbt-level lineage.

Enable¶

{
  "openlineage": {
    "enabled": true,
    "url": "http://marquez.internal:5000",
    "namespace": "analytics"
  }
}

Or via environment:

export OPENLINEAGE_URL=http://marquez.internal:5000
export OPENLINEAGE_NAMESPACE=analytics

Event shape¶

Every block execution emits a START and COMPLETE event:

{
  "eventType": "COMPLETE",
  "eventTime": "2026-04-15T12:34:56Z",
  "job": {
    "namespace": "analytics",
    "name": "block.revenue_by_segment"
  },
  "run": { "runId": "…" },
  "inputs":  [{ "namespace": "analytics", "name": "orders" }],
  "outputs": [{ "namespace": "analytics", "name": "block.revenue_by_segment" }]
}

Compatible receivers¶

Verified against:

Marquez (reference OL consumer)
DataHub via the OL connector
Atlan via the OL integration
Monte Carlo via OL webhook

What's emitted¶

Block runs
Notebook cell runs (one event per cell)
Dashboard compilations
dbt-backed DQL compile/sync metadata, when dbt artifacts are configured

Schema version¶

DQL currently emits OpenLineage spec 0.19. Facet support is full for schema, columnLineage (commercial build), and sql.