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

Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2024/01/13 21:19:00 UTC

[jira] [Resolved] (SPARK-46693) Inject LocalLimitExec when matching OffsetAndLimit or LimitAndOffset

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

Dongjoon Hyun resolved SPARK-46693.
-----------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Issue resolved by pull request 44699
[https://github.com/apache/spark/pull/44699]

> Inject LocalLimitExec when matching OffsetAndLimit or LimitAndOffset
> --------------------------------------------------------------------
>
>                 Key: SPARK-46693
>                 URL: https://issues.apache.org/jira/browse/SPARK-46693
>             Project: Spark
>          Issue Type: Improvement
>          Components: Optimizer
>    Affects Versions: 3.5.0
>            Reporter: Nick Young
>            Assignee: Nick Young
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>
> For queries containing both a LIMIT and an OFFSET in a subquery, physical translation will drop the `LocalLimit` planned in the optimizer stage by mistake; this manifests as larger than necessary shuffle sizes for `GlobalLimitExec`. Fix to not drop this node.



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