feat: Create dynamic filters in SortMergeJoin#21267
Draft
stuhood wants to merge 5 commits intoapache:mainfrom
Draft
feat: Create dynamic filters in SortMergeJoin#21267stuhood wants to merge 5 commits intoapache:mainfrom
stuhood wants to merge 5 commits intoapache:mainfrom
Conversation
Contributor
Author
|
Supersedes #20455. |
github-actions
bot
added
sqllogictest
stuhood
force-pushed
the
stuhood.smj-dynamic-filter-creation
branch
from
7bb33b9 to
ff61597
Compare
stuhood
force-pushed
the
stuhood.smj-dynamic-filter-creation
branch
from
ff61597 to
d7dcdd5
Compare
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
2 participants
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?
SortMergeJoinExec#20443.Rationale for this change
This change fixes #20443, and adds support for generating dynamic filters for the left and right sides of a
SortMergeJoin, in order to allow for range-based pruning of both sides of the join. Some consumers of the dynamic filter may even be able to seek/skip ahead on their inputs.What changes are included in this PR?
To allow
SortMergeJointo actually propagate dynamic filters down to scans and get things working end to end, it was necessary to fix thehandle_child_pushdown_resultimplementations of a variety of nodes which were failing to clone and update themselves.Are these changes tested?
Yes.
Are there any user-facing changes?
Explain will now show dynamic filters for
SortMergeJoin, and for the scans that they consume.