-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Make ExecutionPlan::execute
Sync
#2434
Conversation
I plan to review this PR carefully today |
Oops meant to mark this as draft, #2428 needs to go in first |
@tustvold This PR didn't take as long to review as I thought. It is really just the Ballista changes that were large and I will rely on the integration tests to confirm that everything is working as expected, so LGTM so far but needs rebasing/upmerging now before I can complete my review. |
d2d5397
to
d89be58
Compare
d89be58
to
2ae8cd8
Compare
Rebased, this PR is pretty mechanical, as prior PRs laid the necessary groundwork for it |
@@ -125,23 +122,8 @@ impl ExecutionPipeline { | |||
// Construct the output streams | |||
let output_count = proxied.output_partitioning().partition_count(); | |||
let outputs = (0..output_count) | |||
.map(|x| { |
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.
👋
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.
Ballista integration tests still pass with this change so LGTM. Thanks @tustvold!
I agree this is a good change -- thanks @tustvold and @andygrove 👍 |
Which issue does this PR close?
Closes #2307
Rationale for this change
See ticket but the major benefits are:
ExecutionPlan::Execute
, i.e. during planWhat changes are included in this PR?
Makes
ExecutionPlan::execute
and by extensionExecutionPlan
itself, syncAre there any user-facing changes?
Yes, this is a breaking change to a fundamental trait.