[
https://issues.apache.org/jira/browse/SPARK-36822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418373#comment-17418373
]
Apache Spark commented on SPARK-36822:
--------------------------------------
User 'ulysses-you' has created a pull request for this issue:
https://github.com/apache/spark/pull/34065
> BroadcastNestedLoopJoinExec should use all condition instead of non-equi
> condition
> ----------------------------------------------------------------------------------
>
> Key: SPARK-36822
> URL: https://issues.apache.org/jira/browse/SPARK-36822
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.2.0
> Reporter: XiDuo You
> Priority: Major
>
> At JoinSelection, with ExtractEquiJoinKeys, we use `nonEquiCond` as the join
> condition. It's wrong since there should exist some equi condition.
> {code:java}
> Seq(joins.BroadcastNestedLoopJoinExec(
> planLater(left), planLater(right), buildSide, joinType, nonEquiCond))
> {code}
> But it's should not be a bug, since we always use the smj as the default join
> strategy for ExtractEquiJoinKeys.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
