You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
We add metadata to models using the meta config. We wanted to process the log messages downstream and noticed that messages about test failures didn't include the metadata.
Expected Behavior
I expect it to be in the log message, like the messages about models being created.
Hey @tomwphillips thank you for raising this issue and putting up an associated PR (complete with testing!) 🏆
I was able to reproduce the same you described by using your instructions.
Agreed that we'd categorize this as a bug since our documentation says that node_info fields are intended to include the user-configured meta dictionary (which should apply to generic data tests).
Is this a new bug in dbt-core?
Current Behavior
We add metadata to models using the
meta
config. We wanted to process the log messages downstream and noticed that messages about test failures didn't include the metadata.Expected Behavior
I expect it to be in the log message, like the messages about models being created.
Steps To Reproduce
my_model
.sql:select null as id
dbt build --log-level-file info --log-format-file json -s my_model
Relevant log output
grep 'error' logs/dbt.log | jq
:In contrast, we have the metadata in these messages, via
grep 'analytics' logs/dbt.log | jq
:Environment
Which database adapter are you using with dbt?
bigquery
Additional Context
I have a fix and will open a PR.
The text was updated successfully, but these errors were encountered: