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
This is related to a previous issue where source freshness have also the same dynamic capabilities like tests. While a fix was merged, it wasn't extended to source freshness. The docs mentions source freshness is supported.
Running dbt --warn-error source freshness still returns a WARN rather than an ERROR
Expected Behavior
dbt --warn-error source freshness should return as an ERROR if the freshness falls within the warn_after value
Steps To Reproduce
#models/sources.ymlversion: 2sources:
- name: jaffle_shopdescription: This is a replica of the Postgres database used by our app.database: rawschema: jaffle_shoptables:
- name: ordersdescription: One record per order. Includes cancelled and deleted orders.freshness:
warn_after: {count: 1000, period: day}
$ dbt --warn-error source freshness
...
23:32:29 Pulling freshness from warehouse metadata tables for 1 sources
23:32:32 Concurrency: 1 threads (target='dev')
23:32:32
23:32:32 1 of 1 START freshness of jaffle_shop.orders ................................... [RUN]
23:32:32 1 of 1 WARN freshness of jaffle_shop.orders .................................... [WARN in 0.00s]
23:32:33
23:32:33 Finished running 1 source in 0 hours 0 minutes and 6.92 seconds (6.92s).
23:32:33 Done.
^^ WARN still appeared even if I included the --warn-error flag
dbeatty10
changed the title
[Bug] --warn-error-options doesn't support configuration of turning source freshness warnings into failures
[Bug] --warn-error-options doesn't support configuration of turning source freshness warnings into failures
Dec 10, 2024
Is this a new bug in dbt-core?
Current Behavior
This is related to a previous issue where source freshness have also the same dynamic capabilities like tests. While a fix was merged, it wasn't extended to source freshness. The docs mentions source freshness is supported.
Running
dbt --warn-error source freshness
still returns aWARN
rather than anERROR
Expected Behavior
dbt --warn-error source freshness
should return as anERROR
if the freshness falls within thewarn_after
valueSteps To Reproduce
^^
WARN
still appeared even if I included the--warn-error
flagRelevant log output
No response
Environment
Which database adapter are you using with dbt?
snowflake
Additional Context
No response
The text was updated successfully, but these errors were encountered: