UBarney commented on code in PR #16210:
URL: https://github.com/apache/datafusion/pull/16210#discussion_r2147410263
##########
datafusion/physical-plan/src/joins/nested_loop_join.rs:
##########
@@ -178,6 +187,18 @@ pub struct NestedLoopJoinExec {
metrics: ExecutionPlanMetricsSet,
/// Cache holding plan properties like equivalences, output partitioning
etc.
cache: PlanProperties,
+ /// Null matching behavior: If `null_equals_null` is true, rows that have
+ /// `null`s in both left and right equijoin columns will be matched.
+ /// Otherwise, rows that have `null`s in the join columns will not be
+ /// matched and thus will not appear in the output.
+ null_equals_null: bool,
+ /// Set of equijoin columns from the relations: `(left_col, right_col)`
+ ///
+ /// This is optional as a nested loop join can be passed a 'on' clause
+ /// in the case that a Hash Join cost is more expensive than a
+ /// nested loop join or when a user would like to pick nested loop
+ /// join by hint
+ on: Option<Vec<(PhysicalExprRef, PhysicalExprRef)>>,
Review Comment:
> > If null_equal_null is true, we can replace = in the ON clause with <=>
and merge it into the filter in the planner
>
> This seems slower, we should just pass this to smj or hj. I can play
around with the threshold logic that duckdb has for smaller tables where nljs
may be faster.
>
> >
Under the premise that we prefer NLJ
Rest lgtm
null_equals_null equals true + <=> condition -> we can always pass the <=>
expressions into the on clause
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
