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
In dbt-core, it is generally expected that values passed via CLI flags take precedence over model level configs. However, full_refresh on a model is an exception to this rule, where in the model config takes precedence. This config exists specifically to prevent accidental full refreshes of large incremental models, as doing so can be costly. It is actually best practice to set full_refresh=False on incremental models.
Currently, for microbatch models the above is not happening. The CLI flag --full-refresh is taking precedence over the model config full_refresh. That means that currently if --full-refresh is supplied then the microbatch model will be refreshed even if full_refresh=False is set on the model. This needs to not be the case.
The text was updated successfully, but these errors were encountered:
In dbt-core, it is generally expected that values passed via CLI flags take precedence over model level configs. However,
full_refresh
on a model is an exception to this rule, where in the model config takes precedence. This config exists specifically to prevent accidental full refreshes of large incremental models, as doing so can be costly. It is actually best practice to setfull_refresh=False
on incremental models.Currently, for microbatch models the above is not happening. The CLI flag
--full-refresh
is taking precedence over the model configfull_refresh
. That means that currently if--full-refresh
is supplied then the microbatch model will be refreshed even iffull_refresh=False
is set on the model. This needs to not be the case.The text was updated successfully, but these errors were encountered: