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

Posted to issues@spark.apache.org by "ulysses you (Jira)" <ji...@apache.org> on 2019/11/15 08:03:00 UTC

[jira] [Updated] (SPARK-29912) Pruning shuffle exchange and coalesce when input and output both are one partition

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

ulysses you updated SPARK-29912:
--------------------------------
    Summary: Pruning shuffle exchange and coalesce when input and output both are one partition  (was: Pruning shuffle exchange when input and output both are one partition)

> Pruning shuffle exchange and coalesce when input and output both are one partition
> ----------------------------------------------------------------------------------
>
>                 Key: SPARK-29912
>                 URL: https://issues.apache.org/jira/browse/SPARK-29912
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: ulysses you
>            Priority: Minor
>
> It is meaningless to do  `repartition(1)` or `coalesce(1)` when a plan child just have one partition.
> Now, we can not get the output numPartitions during logic plan, so the issue pruning the operation in physical plan.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org