Add note about adapter_response in run_results.json, sources.json #495
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description & motivation
(reflects ongoing work in dbt-labs/dbt-core#2961 and future work proposed by dbt-labs/dbt-core#2964)
adapter_response
is going to be the best place for users to grab out database-specific info like:Today, it is populated for all "true" materializations (model runs, seeds, snapshots), but it's left empty by
dbt test
anddbt source snapshot-freshness
. We'd like to change that in a future release; the immediate benefit is for BigQuery users who want to know the bytes processed / $$ of tests and freshness checks.Also, while today it only reflects the "last" query executed within a materialization, we'd love someday to record a response for each step in multi-step materializations (e.g. incremental models with
create temp
+delete
+insert
).Pre-release docs
Is this change related to an unreleased version of dbt?
next
<Changelog>[New/Changed] in v0.x.0</Changelog>
current