`state:modified` selectors do not select a column databricks_tags change

[pyrobat]

Describe the bug

Column level databricks_tags do not get picked up when using the state:modified selectors.

Steps To Reproduce

1. Build the following models with a dbt run -s tag_test

tag_test.sql:

select 1 as tag_column

tag_test.yml

models:
  - name: tag_test
     columns:
       - name: tag_column

2. Copy the manifest to a location (e.g. target/) to do a deferred run.

3. Update tag_test.yml with a databricks_tag

models:
  - name: tag_test
     columns:
       - name: tag_column
          databricks_tags:
            test_tag: 'test_value'

4. Run dbt run -s state:modified --defer --state target/

~~~ dbt run -s state:modified --defer --state defer/
23:52:55  Running with dbt=1.10.11
23:52:59  Registered adapter: databricks=1.10.12
23:53:01  Found 63 models, 53 data tests, 2 seeds, 2 operations, 15 sources, 9 metrics, 955 macros, 5 semantic models, 1 saved query
23:53:01  The selection criterion 'state:modified' does not match any enabled nodes
23:53:01  Nothing to do. Try checking your model configs and model specification args

Expected behavior

I expect state:modified to pick up the column level documentation change.

Screenshots and log output

Logs above in repro steps.

System information

The output of dbt --version:

Core:
  - installed: 1.10.11
  - latest:    1.11.9  - Update available!

  Your version of dbt-core is out of date!
  You can find instructions for upgrading here:
  https://docs.getdbt.com/docs/installation

Plugins:
  - databricks: 1.10.12 - Update available!
  - spark:      1.9.3   - Update available!

  At least one plugin is out of date with dbt-core.
  You can find instructions for upgrading here:
  https://docs.getdbt.com/docs/installation

The operating system you're using: macOS 26.4

The output of python --version: Python 3.11.15

Additional context

This is necessary to ensure our CI and CD can continue to use slimCI to test and apply these changes on merge. Without this, tags can be in our repo, but not applied until the next time the model gets run by a schedule. Since databricks_tags will be tied to ABAC, we want to make sure repo configuration matches deployment configuration.

Was redirected here from dbt core (dbt-labs/dbt-core#10189 (comment))

[sd-db]

Hi @pyrobat , thanks for raising an issue. This actually requires a wider discussion with dbt-core folks as the limitation here is from core side (and related to how databricks_tags are implemented). I am following up on this and will let you know if we are able to find a solve here

[pyrobat]

Thanks, is there an issue in dbt core that we could track?

When I mentioned this issue in dbt core they referred me here.