Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] semantic models always included as part of state:modified #9548

Closed
2 tasks done
Tracked by #9562
MichelleArk opened this issue Feb 9, 2024 · 2 comments · Fixed by #9549
Closed
2 tasks done
Tracked by #9562

[Bug] semantic models always included as part of state:modified #9548

MichelleArk opened this issue Feb 9, 2024 · 2 comments · Fixed by #9549
Assignees
Labels
backport 1.7.latest bug Something isn't working

Comments

@MichelleArk
Copy link
Contributor

Is this a new bug in dbt-core?

  • I believe this is a new bug in dbt-core
  • I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

Currently, dbt always detects that semantic models have changed during state:modified, even if none of their model, description, defaults, entities, dimensions, measures, configs, primary entities, or groups have changed.

Expected Behavior

dbt only includes semantic models if one of the above listed properties has changed.

Steps To Reproduce

dbt ls --select "state:modified" on a project with unchanged semantic models

Relevant log output

No response

Environment

- OS:
- Python:
- dbt:

Which database adapter are you using with dbt?

No response

Additional Context

No response

@gshank
Copy link
Contributor

gshank commented Jun 4, 2024

I wasn't able to recreate this. Could you give me a brief reproduction test case? (Commented on wrong ticket!)

@MichelleArk
Copy link
Contributor Author

I think it was already resolved by the combination of #9549 and #9561

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 1.7.latest bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants