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
dbt's warn-error option causes warnings to be treated as errors, and I added this option so that the user is forced to see these warnings. But while testing a fresh setup (in my distributed_data_where_house skeleton project), I discovered that dbt will raise warnings if there aren't any dbt nodes (aka "resources"; includes models) in paths defined in the dbt_project.yml file.
As I built the pipeline-update taskflow to automatically generate dbt models as the DAG runs, a fresh setup (that drops all of the included models) would always define paths to the dbt/models/ directories data_raw, clean, feature, dwh, and report but would only have model files in the data_raw dir at the time it would reach the first dbt-model-running script.
Per the dbt v1.4 changelog, it looks like it's possible to define which warnings should be raised as errors. Determine how to configure dbt to ignore the issue above (ideally tailored as narrowly as possible, so that other defined-but-unused paths still raise errors and get attention).
The text was updated successfully, but these errors were encountered:
dbt's
warn-error
option causes warnings to be treated as errors, and I added this option so that the user is forced to see these warnings. But while testing a fresh setup (in mydistributed_data_where_house
skeleton project), I discovered that dbt will raise warnings if there aren't any dbt nodes (aka "resources"; includesmodels
) in paths defined in thedbt_project.yml
file.As I built the pipeline-update taskflow to automatically generate dbt models as the DAG runs, a fresh setup (that drops all of the included models) would always define paths to the
dbt/models/
directoriesdata_raw
,clean
,feature
,dwh
, andreport
but would only have model files in thedata_raw
dir at the time it would reach the first dbt-model-running script.Per the dbt v1.4 changelog, it looks like it's possible to define which warnings should be raised as errors. Determine how to configure dbt to ignore the issue above (ideally tailored as narrowly as possible, so that other defined-but-unused paths still raise errors and get attention).
The text was updated successfully, but these errors were encountered: