Skip to content

Commit

Permalink
Update state-comparison-caveats.md
Browse files Browse the repository at this point in the history
  • Loading branch information
runleonarun authored Oct 2, 2024
1 parent 8c148d0 commit 6c1514f
Showing 1 changed file with 1 addition and 10 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -16,16 +16,7 @@ dbt will mark modified any resource that depends on a changed macro, or on a mac

### Vars

<VersionBlock lastVersion="1.8">

If a model uses a `var` or `env_var` in its definition, dbt Core 1.8 and earlier are unable today to identify that lineage in such a way that it can include the model in `state:modified` because the `var` or `env_var` value has changed. It's likely that the model will be marked modified if the change in variable results in a different configuration.
</VersionBlock>

<VersionBlock firstVersion="1.9">

Beginning in dbt Core 1.9, when you set the `state_modified_compare_vars` [behavior flag](/reference/global-configs/behavior-changes#behavior-change-flags) to `True` and a model uses a `var` or `env_var` in its definition, dbt will identify that lineage in such a way that it will include the model in `state:modified` when the `var` or `env_var` value has changed.

</VersionBlock>
If a model uses a `var` or `env_var` in its definition, dbt is unable today to identify that lineage in such a way that it can include the model in `state:modified` because the `var` or `env_var` value has changed. It's likely that the model will be marked modified if the change in variable results in a different configuration.

### Tests

Expand Down

0 comments on commit 6c1514f

Please sign in to comment.