dbt Fusion run_results.json dropped Databricks query_id

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.

Context: 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.

Matched source

Source: Published skill Original query: "dbt Fusion runresults.json dropped Databricks queryid" Key terms: databricks, dropped, fusion, json, query, results

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