Add BufferExec execution plan #19760
Draft
+895
−80
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.
Which issue does this PR close?
Rationale for this change
This is a PR from a batch of PRs that attempt to improve performance in hash joins:
It adds a building block that allows eagerly collecting data on the probe side of a hash join before the build side is finished.
Even if the intended use case is for hash joins, the new execution node is generic and is designed to work anywhere in the plan.
What changes are included in this PR?
Adds a new
BufferExecnode that can buffer up to a certain size in bytes for each partition eagerly performing work that otherwise would be delayed.Schematically, it looks like this:
Are these changes tested?
yes, by new unit tests
Are there any user-facing changes?
users can import a new
BufferExecexecution plan in their codebase, but no internal usage is shipped yet in this PR.