-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[CT-2963] [Bug] CI breaking when a group is changed #8371
Comments
Thanks Grace & Matt - added to the milestone! Depending on the scope of the fix required here, we can decide if it makes sense to backport for inclusion in v1.6.x |
Added the backport label for v1.5.x and v1.6.x since groups were first introduced in v1.5.x |
I'm not sure if this is related or not (and thus if I should create a new issue), but the last few weeks we've been experiencing a similar issue when an exposure has been renamed/deleted, so a KeyError is returned when comparing to the previuos manifest. The following error is from a run on September 14th:
While we got a similar error a week later on September 22nd, but this time related to a model:
|
@grindheim That sounds like an error with partial parsing. Could I ask you to open a new issue for it, and include as many details / reproduction steps as possible? |
We're not able to reproduce this bug in dbt-core, so I'm closing it out - I've alerted our cloud team who is going to take a look :) |
Was able to finally reproduce! The reason we weren’t able to reproduce this bug originally is that group name changes don’t actually count as something that is “modified” (@jtcohen6 is this expected behavior?) so nothing is selected / built when we did But! If we changed another model in that group (we just added an |
Is this a new bug in dbt-core?
Current Behavior
Originally from a slack message from @matt-winkler
There are two parts of this issue:
Expected Behavior
CI should be able to handle a change to the name of a group.
Steps To Reproduce
dbt compile
on a project that has a group definedorder by 1
clause)dbt build --select state:modified+ --defer --state path/to/earlier/manifest
Relevant log output
No response
Environment
Which database adapter are you using with dbt?
Snowflake
Additional Context
Above was running in dbt Cloud. State comparison to a previous manifest should be the same though, I think.
Depending on the scope of the fix, we can decide if it makes sense to backport for inclusion in v1.6.x.
The text was updated successfully, but these errors were encountered: