-
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-3085] [Bug] dbt retry
doesn't unpack resource-type
#8575
Comments
dbt retry
doesn't unpack resource-typedbt retry
doesn't unpack resource-type
Thanks for reporting this @kevin-chao and providing such a nice example of how to reproduce it 🤩 Following your example, I got the same results as you, namely that this doesn't work correctly: dbt build -s some_model --resource-type all
dbt retry And neither does this: dbt build -s some_model --resource-type model test
dbt retry But this works fine: dbt build -s some_model
dbt retry |
I wonder if this will be incidentally resolved by this work: |
@dbeatty10 my first approach in that PR did not actually solve this problem but I tweaked it a bit more and it seems to be resolved. |
Is this a new bug in dbt-core?
Current Behavior
When using
dbt retry
after usingdbt build
with a resource-type specified, dbt will warn of aBadParameter
since the resource-type from the previous run is returned as a string of a list.Expected Behavior
When using
dbt retry
in conjunction with adbt build
with a resource-type specified, it would run the appropriate nodes without a parameter issue. It would run whether I had a single resource-type specified or multiple resource-types specified.Steps To Reproduce
some_model.sql
some_model.yml
dbt build -s some_model --resource-type all
(optionally,--resource-type model test
)dbt retry
to see failure-- On the happy path
dbt build -s some_model
dbt retry
to see proper flowRelevant log output
Environment
Which database adapter are you using with dbt?
snowflake
Additional Context
Can confirm that without the resource-type specified in
dbt build
,dbt retry
works as intended.The text was updated successfully, but these errors were encountered: