-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fix and Improve Sort Pushdown for Nested Loop and Hash Join #12559
Merged
Conversation
This file contains 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
github-actions
bot
added
core
Core DataFusion crate
sqllogictest
SQL Logic Tests (.slt)
labels
Sep 20, 2024
berkaysynnada
changed the title
Feature/fix pushdown logic
Fix and Improve Sort Pushdown for Nested Loop and Hash Join
Sep 20, 2024
Thank you @berkaysynnada The Join Ordering Benchmark results turned out to be pretty promising against your PR! FYR:
|
Nice, impressive results |
ozankabak
approved these changes
Sep 23, 2024
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.
LGTM 🚀
Dandandan
approved these changes
Sep 23, 2024
bgjackma
pushed a commit
to bgjackma/datafusion
that referenced
this pull request
Sep 25, 2024
…2559) * Update sort_pushdown.rs * Update joins.slt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #12558.
Rationale for this change
HashJoinExec
andNestedLoopJoinExec
maintains the order of right child. If aSortExec
appears at the top of these joins, now it can be pushed down through its right child if all the requirements come from the right child.pushdown_requirement_to_children()
logic was problematic for join operators. It is generalized now for any kind of operators if it falls toelse{}
block.What changes are included in this PR?
pushdown_requirement_to_children()
function insort_pushdown.rs
is responsible for determining whether a sort operation can be pushed down over an operator, and if so, how the requirements are propagated. While most operators are handled properly, the mentioned operators (HashJoinExec
andNestedLoopJoinExec
) and other newly added operators may encounter issues due to missing index updates and not utilizing the generic maintains flags. Now they are handled viahandle_custom_pushdown()
.Are these changes tested?
Yes
Are there any user-facing changes?