You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2016/02/17 22:42:18 UTC

[jira] [Created] (SPARK-13365) should coalesce do anything if coalescing to same number of partitions without shuffle

Thomas Graves created SPARK-13365:
-------------------------------------

             Summary: should coalesce do anything if coalescing to same number of partitions without shuffle
                 Key: SPARK-13365
                 URL: https://issues.apache.org/jira/browse/SPARK-13365
             Project: Spark
          Issue Type: Improvement
          Components: Spark Core
    Affects Versions: 1.6.0
            Reporter: Thomas Graves


Currently if a user does a coalesce to the same number of partitions as already exist it spends a bunch of time doing stuff when it seems like it shouldn't do anything.

for instance I have an RDD with 100 partitions if I run coalesce(100) it seems like it should skip any computation since it already has 100 partitions.  One case I've seen this is actually when users do coalesce(1000) without the shuffle which really turns into a coalesce(100).

I'm presenting this as a question as I'm not sure if there are use cases I haven't thought of where this would break.





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