You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Yuming Wang (Jira)" <ji...@apache.org> on 2019/11/19 12:18:00 UTC
[jira] [Updated] (SPARK-29962) Avoid changing merge join to
broadcast join if one side is non-shuffle and the other side can be
broadcast
[ https://issues.apache.org/jira/browse/SPARK-29962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yuming Wang updated SPARK-29962:
--------------------------------
Description:
It seem SortMergeJoin faster than BroadcastJoin if one side is non-shuffle and the other side can be broadcast:
https://issues.apache.org/jira/secure/attachment/12985671/BroadcastJoin.jpeg
https://issues.apache.org/jira/secure/attachment/12985670/SortMergeJoin.jpeg
> Avoid changing merge join to broadcast join if one side is non-shuffle and the other side can be broadcast
> ----------------------------------------------------------------------------------------------------------
>
> Key: SPARK-29962
> URL: https://issues.apache.org/jira/browse/SPARK-29962
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Yuming Wang
> Priority: Major
>
> It seem SortMergeJoin faster than BroadcastJoin if one side is non-shuffle and the other side can be broadcast:
> https://issues.apache.org/jira/secure/attachment/12985671/BroadcastJoin.jpeg
> https://issues.apache.org/jira/secure/attachment/12985670/SortMergeJoin.jpeg
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org