Avoid concatenating record batches in joins#23032
Open
maxburke wants to merge 2 commits into
Open
Conversation
This avoids significant memory pressure on large queries.
maxburke
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Closes issue #23031
Rationale for this change
We run into two problems when operating on datasets with approximately 60 million rows:
What changes are included in this PR?
This removes record batch concatenation from several joins (hash join, nested loop join, piecewise merge join)
Are these changes tested?
Yes
Are there any user-facing changes?
I sure hope not! (no)