[
https://issues.apache.org/jira/browse/SPARK-9830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Armbrust resolved SPARK-9830.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Issue resolved by pull request 9556
[https://github.com/apache/spark/pull/9556]
> Remove AggregateExpression1 and Aggregate Operator used to evaluate
> AggregateExpression1s
> -----------------------------------------------------------------------------------------
>
> Key: SPARK-9830
> URL: https://issues.apache.org/jira/browse/SPARK-9830
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Reporter: Yin Huai
> Assignee: Yin Huai
> Priority: Blocker
> Fix For: 1.6.0
>
>
> In 1.6.0, we should remove the old aggregation code path (used to evaluate
> AggregateExpression1). While removing this code path, there are several code
> clean up we need to do,
> 1. Remove all of our hacks from ResolveFunctions.
> 2. Remove all of the conversion logics from
> {org.apache.spark.sql.catalyst.expressions.aggregate.utils}}.
> 3. Remove {{newAggregation}} field from {{logical.Aggregate}}.
> 4. Remove the query planning rule for old aggregate path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
