[jira] [Assigned] (SPARK-36822) BroadcastNestedLoopJoinExec should use all condition instead of non-equi condition

2021-09-22 Thread Wenchen Fan (Jira) 


 [ 
https://issues.apache.org/jira/browse/SPARK-36822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wenchen Fan reassigned SPARK-36822:
---

Assignee: XiDuo You

> 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
>Assignee: XiDuo You
>Priority: Major
> Fix For: 3.3.0
>
>
> 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

[jira] [Assigned] (SPARK-36822) BroadcastNestedLoopJoinExec should use all condition instead of non-equi condition

2021-09-21 Thread Apache Spark (Jira) 


 [ 
https://issues.apache.org/jira/browse/SPARK-36822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Apache Spark reassigned SPARK-36822:


Assignee: Apache Spark

> 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
>Assignee: Apache Spark
>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

[jira] [Assigned] (SPARK-36822) BroadcastNestedLoopJoinExec should use all condition instead of non-equi condition

2021-09-21 Thread Apache Spark (Jira) 


 [ 
https://issues.apache.org/jira/browse/SPARK-36822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Apache Spark reassigned SPARK-36822:


Assignee: (was: Apache Spark)

> 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