You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2022/05/13 01:01:00 UTC
[jira] [Commented] (SPARK-39169) Optimize FIRST when used as a single aggregate function
[ https://issues.apache.org/jira/browse/SPARK-39169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536390#comment-17536390 ]
Apache Spark commented on SPARK-39169:
--------------------------------------
User 'vli-databricks' has created a pull request for this issue:
https://github.com/apache/spark/pull/36527
> Optimize FIRST when used as a single aggregate function
> -------------------------------------------------------
>
> Key: SPARK-39169
> URL: https://issues.apache.org/jira/browse/SPARK-39169
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.3.0
> Reporter: Vitalii Li
> Priority: Major
>
> When `FIRST` is a single aggregate function in `Aggregate` we could either rewrite whole query or optimize execution logic.
> * Plan => `SELECT FIRST(<col>) FROM <table>` => `SELECT <col> FROM <table> LIMIT 1`. Note that setting `ignoreNulls` to `true` should block such rewrite since returns could differ in case all values of <col> are `NULL`
> * Execution => `SELECT FIRST(<col>) FROM <table> GROUP BY <some_col>` => short circuit iteration per key once a value for `FIRST` is set.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org