You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "wangfei (JIRA)" <ji...@apache.org> on 2015/01/09 13:39:34 UTC

[jira] [Closed] (SPARK-4673) Optimizing limit using coalesce

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

wangfei closed SPARK-4673.
--------------------------
    Resolution: Fixed

since coalesce (1) will lead to run with a single thread， not always speed up limit so close this one.

> Optimizing limit using coalesce
> -------------------------------
>
>                 Key: SPARK-4673
>                 URL: https://issues.apache.org/jira/browse/SPARK-4673
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.1.0
>            Reporter: wangfei
>             Fix For: 1.3.0
>
>
> Now limit used ShuffledRDD and HashPartitioner to repartition 1 which leads to shuffle.



--
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