[
https://issues.apache.org/jira/browse/SPARK-10100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705161#comment-14705161
]
Herman van Hovell commented on SPARK-10100:
-------------------------------------------
You are using a grouping key in this query. This doesn't seem related to the
proposed solution (no grouping keys), how are they related?
> Eliminate hash table lookup if there is no grouping key in aggregation.
> -----------------------------------------------------------------------
>
> Key: SPARK-10100
> URL: https://issues.apache.org/jira/browse/SPARK-10100
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 1.5.0
> Reporter: Yin Huai
> Assignee: Reynold Xin
> Fix For: 1.5.0
>
> Attachments: SPARK-10100.perf.test.scala
>
>
> *Update: The title of this jira has been changed to "Eliminate hash table
> lookup if there is no grouping key in aggregation."*. For the Max and Min
> expressions, we can revisit them later if we find a better way to improve the
> performance and open a new jira.
> *The original title of this JIRA is "AggregateFunction2's Max is slower than
> AggregateExpression1's MaxFunction"*. Below is the original description:
> Looks like Max (probably Min) implemented based on AggregateFunction2 is
> slower than the old MaxFunction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
