Repository navigation
[AURON #2540] Support residual conditions in native shuffled hash joins - #2552
Merged
Merged
Conversation
richox
approved these changes
Sep 30, 2026
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?
Closes #2540
Rationale for this change
Native shuffled hash joins currently support residual conditions only for inner joins. Outer, semi, anti, and existence joins with additional conditions therefore fall back to Spark.
With residual-condition evaluation now available in the native hash join engine, this PR extends SHJ conversion to use it, preserving the matching and unmatched-row semantics required by each join type.
What changes are included in this PR?
Are there any user-facing changes?
No.
How was this patch tested?
UTs.