From ee35363f7283194efdfcbea4deb0da4c93ecd17b Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Fri, 2 Feb 2024 11:12:07 -0800 Subject: [PATCH] Update state-comparison-caveats.md --- .../docs/reference/node-selection/state-comparison-caveats.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/website/docs/reference/node-selection/state-comparison-caveats.md b/website/docs/reference/node-selection/state-comparison-caveats.md index f0c84f518d1..c1673880fd5 100644 --- a/website/docs/reference/node-selection/state-comparison-caveats.md +++ b/website/docs/reference/node-selection/state-comparison-caveats.md @@ -49,10 +49,6 @@ State comparison works by identifying discrepancies between two manifests. Thos 1. Changes made to a project in development 2. Env-aware logic that causes different behavior based on the `target`, env vars, etc. -dbt will do its best to capture *only* changes that are the result of modifications made in development. In projects with intricate env-aware logic, dbt will err on the side of running too many models (i.e. false positives). Over the next several versions of dbt, we're working on: -- iterative improvements to dbt's built-in detective abilities -- better options for more complex projects, in the form of more-specific sub-selectors (see [this issue](https://github.com/dbt-labs/dbt-core/issues/2704)) - State comparison detects env-aware config in `dbt_project.yml`. This target-based config registers as a modification: