Repository navigation
fix: reject null-aware LeftAnti hash join in Partitioned mode
#26586
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
Merged
jayzhan211
merged 3 commits into
apache:main
from
cool9850311:fix-26496-null-aware-partitioned
Oct 23, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
On the second commit, in case it reads as unrelated cleanup, here is why that
branch cannot be reached.
Entering it requires three things at once:
partition_mode == PartitionMode::Partitioned— it is thatmatcharm;can_swap_hash_join(hash_join)— the enclosingif;hash_join.null_aware— the ternary'strueside.Given (3),
!hash_join.null_awareisfalse, so (2) can only hold through itsright-hand side:
LeftAnti, a single key, no filter.NullAwareMode::try_newderives
correlated = num_keys > 1 || has_filter, so that is exactlyLeftAnti { correlated: false }. With (1) the join is therefore an uncorrelatednull-aware
LeftAntiinPartitionedmode — the combination the first commitrejects in
try_new, whichHashJoinExec::try_new, the builder and protobufdecode all go through.
So on that line
null_awareis alwaysfalseand the chosen mode is alwaysPartitioned: for every input that can reach it, the old ternary andswap_inputs(PartitionMode::Partitioned)compute the same value. Reverting thefirst commit and re-running the crate's tests confirms the construction is what
blocks it, not the optimizer: the only two failures are the new
test_null_aware_validation_left_anti_partitionedandtry_from_proto_rejects_a_null_aware_partitioned_join.The
RightAntinamed in the old comment never reached the line either: anull-aware
RightAntifailscan_swap_hash_join, and(RightAnti, Partitioned)falls throughtry_new'smatch (join_type, partition_mode)toplan_err.This is not needed for the fix, which is why it is a separate commit — happy to
drop it if you would rather leave the branch in place.