jonathanc-n commented on code in PR #16210:
URL: https://github.com/apache/datafusion/pull/16210#discussion_r2143227797


##########
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:
   But how would you suggest doing the null_equal_null check. I do think that 
it willl probably be faster to merge the two.



-- 
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-unsubscr...@datafusion.apache.org

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


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

Reply via email to