Re: [I] Default join planning loses NOT IN null semantics in SortMergeJoinExec [datafusion-ballista]

["amitvijapur (via GitHub)" <gi...@apache.org>]

amitvijapur commented on issue #2193:
URL: https://github.com/apache/datafusion-ballista/issues/2193#issuecomment-5784157551

   This looks addressed on the DataFusion side by apache/datafusion#22810 (merged 2026-07-24, three days before this issue): the physical planner now never routes a null-aware anti join to `SortMergeJoinExec`, whatever `prefer_hash_join` says (`physical_planner.rs`, the `can_repartition_join` / sort-merge branch checks `!*null_aware`). That commit is in DataFusion 55.0.0, which `main` here depends on.
   
   I have not re-run the four-partition CSV reproduction on a cluster, so this is a pointer rather than a confirmation. If the repro passes on `main` now, the issue can probably be closed.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org