dbt Fusion run_results.json dropped Databricks query_id

TL;DR

Pin a Fusion version carrying the fix before building observability or lineage on adapter_response fields. Expected: Fixed in the referenced commit by serramatutu.

Steps

1. If tooling that parses runresults.json for Databricks query IDs gets nothing on Fusion, this is the artifact-divergence gap, not your parser: Fusion's adapterresponse carried only generic fields. Pin a Fusion version carrying the fix before building observability or lineage on adapter_response fields. Agents consuming dbt artifacts should assert the presence of the fields they depend on, since Core and Fusion diverged here silently.

When to use

You are seeing this: If tooling that parses runresults.json for Databricks query IDs gets nothing on Fusion, this is the artifact-divergence gap, not your parser: Fusion's adapterresponse carried only generic fields. Use this skill when you run into "dbt Fusion runresults.json dropped Databricks queryid".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: GitHub issue dbt-labs/dbt#15627 (closed): on dbt Fusion, runresults.json for Databricks was missing the adapterresponse queryid that dbt Core exposes (mapped from the Databricks SQL statement/command ID, the only Databricks-specific signal in Core's AdapterResponse). It was a sub-issue of #14366, which tracked Fusion/Core artifact divergences: compiledcode missing entirely, identical timestamps for timing.compile and timing.execute, failures omitted instead of null, and adapter_response carrying only generic fields. Fixed in the referenced commit by serramatutu.

Verified resolution: If tooling that parses runresults.json for Databricks query IDs gets nothing on Fusion, this is the artifact-divergence gap, not your parser: Fusion's adapterresponse carried only generic fields. Pin a Fusion version carrying the fix before building observability or lineage on adapter_response fields. Agents consuming dbt artifacts should assert the presence of the fields they depend on, since Core and Fusion diverged here silently.

Source URL: https://github.com/dbt-labs/dbt/issues/15627