You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2021/08/09 08:53:00 UTC

[jira] [Resolved] (SPARK-36424) Support eliminate limits in AQE Optimizer

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

Wenchen Fan resolved SPARK-36424.
---------------------------------
    Fix Version/s: 3.3.0
       Resolution: Fixed

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

> Support eliminate limits in AQE Optimizer
> -----------------------------------------
>
>                 Key: SPARK-36424
>                 URL: https://issues.apache.org/jira/browse/SPARK-36424
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 3.2.0
>            Reporter: XiDuo You
>            Priority: Major
>             Fix For: 3.3.0
>
>
> In Ad-hoc scenario, we always add limit for the query if user have no special limit value, but not all limit is nesessary.
> With the power of AQE, we can eliminate limits using running statistics.



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