[CHORE] Implement dispatcher for intermediate ops and streaming sink #3238
+127
−137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the streaming physical writes PR, we introduced a
dispatcher
trait, which allows a blocking sink to define how to distribute work across workers: #2992, i.e. partitioned by hash, round robin, etc.This PR enables intermediate ops and streaming sinks to use
dispatcher
as well. In the future, we can add aunordered dispatcher
which allows workers to accept input on demand instead of round robin.Stacked on #3235