You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Michael Armbrust (JIRA)" <ji...@apache.org> on 2015/07/06 23:34:04 UTC
[jira] [Resolved] (SPARK-4485) Add broadcast outer join to
optimize left outer join and right outer join
[ https://issues.apache.org/jira/browse/SPARK-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Armbrust resolved SPARK-4485.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Issue resolved by pull request 7162
[https://github.com/apache/spark/pull/7162]
> Add broadcast outer join to optimize left outer join and right outer join
> --------------------------------------------------------------------------
>
> Key: SPARK-4485
> URL: https://issues.apache.org/jira/browse/SPARK-4485
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 1.1.0
> Reporter: XiaoJing wang
> Assignee: Kai Zeng
> Priority: Critical
> Fix For: 1.5.0
>
> Original Estimate: 0.05h
> Remaining Estimate: 0.05h
>
> For now, spark use broadcast join instead of hash join to optimize {{inner join}} when the size of one side data did not reach the {{AUTO_BROADCASTJOIN_THRESHOLD}}
> However,Spark SQL will perform shuffle operations on each child relations while executing
> {{left outer join}} and {{right outer join}}. {outer join}} is more suitable for optimiztion with broadcast join.
> We are planning to create a {{BroadcastHashouterJoin}} to implement the broadcast join for {{left outer join}} and {{right outer join}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org