require_fresh_data_from

Project YAML file

dbt_project.yml

models:
  <resource-path>:
    +state:
      require_fresh_data_from: any | all

Properties YAML file

models/<filename>.yml

models:
  - name: my_model
    config:
      state:
        require_fresh_data_from: any | all

SQL file config

models/<filename>.sql

{{ config(
    state={
      "require_fresh_data_from": "any" | "all"
    }
) }}

Definition

require_fresh_data_from controls how many direct parent nodes need fresh data before dbt State considers this node eligible for a rebuild. dbt State still looks for an object to reuse before triggering an actual rebuild.

Value	Behavior
any (default)	The node becomes eligible for a rebuild when any direct parent has fresh data. Rebuilds more frequently; may increase spend.
all	The node only becomes eligible for a rebuild when all direct parents have fresh data. Rebuilds less frequently; reduces spend.

Loading table...

Default

any

Examples

Require all parents to have fresh data

Use all for a model that joins multiple sources and should only rebuild when every upstream dependency has updated:

models/fct_orders.yml

models:
  - name: fct_orders
    config:
      state:
        require_fresh_data_from: all

Apply a project-wide default

dbt_project.yml

models:
  +state:
    require_fresh_data_from: all

Related docs

• About dbt State
• Set up dbt State

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.