[
https://issues.apache.org/jira/browse/SPARK-34853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takeshi Yamamuro resolved SPARK-34853.
--------------------------------------
Fix Version/s: 3.2.0
Assignee: Cheng Su
Resolution: Fixed
Resolved by https://github.com/apache/spark/pull/31950
> Move partitioning and ordering to common limit trait
> ----------------------------------------------------
>
> Key: SPARK-34853
> URL: https://issues.apache.org/jira/browse/SPARK-34853
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.2.0
> Reporter: Cheng Su
> Assignee: Cheng Su
> Priority: Trivial
> Fix For: 3.2.0
>
>
> Both local limit and global limit define the output partitioning and output
> ordering in the same way and this is duplicated
> ([https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/limit.scala#L159-L175]
> ). We can move the output partitioning and ordering into their parent trait
> - BaseLimitExec. This is a minor code refactoring.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
