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

Posted to issues@spark.apache.org by "jiaan.geng (Jira)" <ji...@apache.org> on 2022/12/02 08:54:00 UTC

[jira] [Resolved] (SPARK-41337) Add a physical rule to remove the partialLimitExec node

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

jiaan.geng resolved SPARK-41337.
--------------------------------
    Resolution: Invalid

> Add a physical rule to remove the partialLimitExec node
> -------------------------------------------------------
>
>                 Key: SPARK-41337
>                 URL: https://issues.apache.org/jira/browse/SPARK-41337
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 3.4.0
>            Reporter: jiaan.geng
>            Priority: Major
>
> Currently, the planner WindowGroupLimit creates two WindowGroupLimitExec node.
> We can add a physical rule to remove the partialLimitExec node, if there is no shuffle between the two nodes (partialLimitExec's outputPartitioning satisfies the finalLimitExec's requiredChildDistribution)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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