You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Reynold Xin (JIRA)" <ji...@apache.org> on 2014/09/12 10:23:33 UTC
[jira] [Commented] (SPARK-3084) Collect broadcasted tables in
parallel in joins
[ https://issues.apache.org/jira/browse/SPARK-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131258#comment-14131258 ]
Reynold Xin commented on SPARK-3084:
------------------------------------
Note that the current fix actually launches jobs immediately in explain ... we should fix that.
> Collect broadcasted tables in parallel in joins
> -----------------------------------------------
>
> Key: SPARK-3084
> URL: https://issues.apache.org/jira/browse/SPARK-3084
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Reporter: Matei Zaharia
> Assignee: Matei Zaharia
> Fix For: 1.1.0
>
>
> BroadcastHashJoin has a broadcastFuture variable that tries to collect the broadcasted table in a separate thread, but this doesn't help because it's a lazy val that only gets initialized when you attempt to build the RDD. Thus queries that broadcast multiple tables would collect and broadcast them sequentially.
--
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