Add data processed info into dbt run logs for all statement types
See original GitHub issueDescribe the feature
When using BigQuery dbt run
logs should show the data scan value for create table statement and not just for script.
Describe alternatives you’ve considered
No alternative
Additional context
This specific improvement is about BigQuery. However, this might apply for other database too I do not have experience to give specific examples.
Who will this benefit?
Everyone using dbt to get easier access to usage.
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (14 by maintainers)
Top Results From Across the Web
Add data processed info into dbt run logs for all statement types
Describe the feature When using BigQuery dbt run logs should show the data scan value for create table statement and not just for...
Read more >SQL models - dbt Developer Hub
To check out the SQL that dbt is running, you can look in: dbt Cloud: Within the run output, click on a model...
Read more >Events and logs - dbt Developer Hub
With every task that dbt performs, it generates events. It records those events as log messages, and writes them (in real time) to...
Read more >Debugging errors - dbt Developer Hub
The logs/dbt.log file contains all the queries that dbt runs, and additional logging. Recent errors will be at the bottom of the file....
Read more >Incremental models - dbt Developer Hub
Incremental models. Overview. Incremental models are built as tables in your data warehouseA data warehouse is a data management system used for data...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Huh, I think that this is a string templating issue, and I think Jinja could be a good tool to solve that kind of problem 😃
I think we should keep the focus narrow for this particular PR, but in the future, I would like to:
job
,materialization
,status
,runtime
, etc)What do y’all think?
Thanks all. Much appreciated