-
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
When retrying microbatch models, propagate prior successful state #10802
When retrying microbatch models, propagate prior successful state #10802
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #10802 +/- ##
=======================================
Coverage 89.17% 89.17%
=======================================
Files 183 183
Lines 23382 23388 +6
=======================================
+ Hits 20850 20856 +6
Misses 2532 2532
Flags with carried forward coverage won't be shown. Click here to find out more.
|
9502273
to
0100a58
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question and a nit but the change looks good to me!
@@ -454,7 +454,7 @@ def resource_class(cls) -> Type[HookNodeResource]: | |||
|
|||
@dataclass | |||
class ModelNode(ModelResource, CompiledNode): | |||
batches: Optional[List[BatchType]] = None | |||
batch_info: Optional[BatchResults] = None |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this cause a loading error for a previous manifest?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has no effect on the written manifest, which is intentional. That is the case because these do not exist on the artifact class for the object
Resolves #10800
Problem
If you invoked
dbt retry
on a microbatch model twice, where on the firstdbt retry
all the retried batches failed, then on the seconddbt retry
invocation the microbatch model would rerun all the batches that were run on the initialdbt run
being retried.Solution
When going through multiple
dbt retry
invocations, ensure that the priorsuccessful
batch information continues to be passed.Checklist