search

grafana / dbt_leaner_query

MIT License
23 stars 3 forks source link

leaner_query produces a number of warnings in the run log #17

Open MalteNiederstadt opened 4 months ago

MalteNiederstadt commented 4 months ago

We're using the package for cost monitoring, and for the most part it's amazing. So thank you for that, still on every dbt cloud run these warnings find their way into the run log

07:14:03 [WARNING]: Did not find matching node for patch with name 'dim_query_statement' in the 'models' section of file 'models/marts/bigquery_audit_log.yml' 07:14:03 [WARNING]: Did not find matching node for patch with name 'int_dbt_execution_info' in the 'models' section of file 'models/intermediate/int_bigquery_audit_log.yml' 07:14:03 [WARNING]: Did not find matching node for patch with name 'int_importance_calculation' in the 'models' section of file 'models/intermediate/int_bigquery_audit_log.yml' 07:14:04 [WARNING]: Test 'test.leaner_query.not_null_dim_query_statement_job_key.dde1be6c77' (models/marts/bigquery_audit_log.yml) depends on a node named 'dim_query_statement' in package '' which was not found

Is there any way to surpress these warnings? If every dbt run is labelled as warning, it's becoming rather difficult to identify the actual issues. (latest version)

fdawans commented 4 months ago

We have the same issues - there's a PR waiting for be merged on this topic. https://github.com/grafana/dbt_leaner_query/pull/16

duncan771 commented 4 months ago

Thanks for using LeanerQuery and for helping to find some of the (many?) ways we can improve this! Hopefully merging #16 and the subsequent release will help with some of this. Please comment back here if not.