Update 53 upgrade guide to note release, other changes#21449
Merged
alamb merged 4 commits intoapache:mainfrom Apr 9, 2026
Merged
Update 53 upgrade guide to note release, other changes#21449alamb merged 4 commits intoapache:mainfrom
alamb merged 4 commits intoapache:mainfrom
Conversation
alamb
changed the title
26 tasks
rluvaton
approved these changes
Apr 8, 2026
Comment on lines
+154
to
+162
| ### `HashJoinExec::try_new` adds `null_aware` | ||
|
|
||
| `HashJoinExec::try_new` now takes an extra `null_aware: bool` argument. This | ||
| flag is used for null-aware anti joins, such as plans generated for `NOT IN` | ||
| subqueries. | ||
|
|
||
| Most callers should pass `false`. Pass `true` only for null-aware | ||
| `JoinType::LeftAnti` joins. DataFusion validates that null-aware joins are | ||
| single-column `LeftAnti` joins. |
Member
There was a problem hiding this comment.
Could you mention what was the prev behavior?
Contributor
Author
|
Thank you for the review @rluvaton |
12 tasks
Rich-T-kid
pushed a commit
to Rich-T-kid/datafusion
that referenced
this pull request
Apr 21, 2026
## Which issue does this PR close? - Related to apache#19692 ## Rationale for this change @rluvaton noted some issues with the 53 upgrade guide apache#19692 (comment): > FYI, the migration guide says 53.0.0 was not released yet and it miss the following breaking changes: > > apache#20319 - removed deprecated function from ExecutionPlan trait > apache#19635 - added argument to HashJoinExec::try_new function ## What changes are included in this PR? Fix the above ## Are these changes tested? Yes by CI ## Are there any user-facing changes? Better docs
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?
53.0.0(Feb 2026 / Mar 2026) #19692Rationale for this change
@rluvaton noted some issues with the 53 upgrade guide #19692 (comment):
What changes are included in this PR?
Fix the above
Are these changes tested?
Yes by CI
Are there any user-facing changes?
Better docs