-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Mark new tasks readyForScheduling when fragment children are finished #20736
Conversation
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 nitpick, otherwise LGTM.
@@ -109,6 +109,7 @@ | |||
import it.unimi.dsi.fastutil.ints.IntOpenHashSet; | |||
import it.unimi.dsi.fastutil.ints.IntSet; | |||
import jakarta.annotation.Nullable; | |||
import jakarta.ws.rs.HEAD; |
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.
Can you help me understand why this new import
is necessary?
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 is artifact of IntelliJ doing automatic imports. And conflict resolition with
HEAD <<<<<<<<<<<
makers
Makes isReadyForExecution() resilient to changes in estimate classification.
Previously, StageExecution#updatePartition() always created new tasks as speculative. But if the fragment's children are completed, the task is not really speculative -- it can get scheduled without fear of its precursors failing.
No description provided.