Removed behavior flags

When dbt Core v2 removes a behavior flag, you can no longer configure the flag. The new behavior is always enabled and the old behavior is not supported. Any flag still set in dbt_project.yml will be ignored.

If you're upgrading to dbt Core v2, remove these flags from your dbt_project.yml.

Flags removed in dbt Core v2

The following dbt Core v2 behavior flags are removed in dbt Core v2. For intro and maturity dates, refer to the dbt Core behavior changes table.

Flag	New behavior (always enabled)
require_explicit_package_overrides_for_builtin_materializations	Packages cannot override built-in materializations without explicit opt-in.
require_resource_names_without_spaces	Spaces in resource names raise an error.
source_freshness_run_project_hooks	Project hooks run during dbt source freshness.
skip_nodes_if_on_run_start_fails	All selected nodes are skipped if an on-run-start hook fails.
state_modified_compare_more_unrendered_values	state:modified comparisons use unrendered Jinja values.
require_yaml_configuration_for_mf_time_spines	MetricFlow time spine deprecation warning is suppressed.
require_batched_execution_for_custom_microbatch_strategy	Custom microbatch macros are called once per batch window.

Loading table...

dbt adapter flags removed in v2.0.0

The following adapter behavior flags are also removed in dbt Core v2:

Flag	Adapter	New behavior (always enabled)
use_info_schema_for_columns	Databricks	Uses information schema for column metadata.
use_user_folder_for_python	Databricks	Uses user folder for Python model notebooks.

Loading table...

Was this page helpful?

Privacy policyCreate a GitHub issue

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.