You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2018/07/07 23:12:00 UTC
[jira] [Commented] (SPARK-24759) No reordering keys for broadcast
hash join
[ https://issues.apache.org/jira/browse/SPARK-24759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535931#comment-16535931 ]
Apache Spark commented on SPARK-24759:
--------------------------------------
User 'gatorsmile' has created a pull request for this issue:
https://github.com/apache/spark/pull/21728
> No reordering keys for broadcast hash join
> ------------------------------------------
>
> Key: SPARK-24759
> URL: https://issues.apache.org/jira/browse/SPARK-24759
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.4.0
> Reporter: Xiao Li
> Assignee: Xiao Li
> Priority: Major
>
> As the implementation of the broadcast hash join is independent of the input hash partitioning, reordering keys is not necessary. Thus, we solve this issue by simply removing the broadcast hash join from the reordering rule in EnsureRequirements.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org