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

Posted to issues@spark.apache.org by "Yin Huai (JIRA)" <ji...@apache.org> on 2015/08/20 16:54:45 UTC

[jira] [Resolved] (SPARK-10100) AggregateFunction2's Max is slower than AggregateExpression1's MaxFunction

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

Yin Huai resolved SPARK-10100.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0

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

> AggregateFunction2's Max is slower than AggregateExpression1's MaxFunction
> --------------------------------------------------------------------------
>
>                 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: Herman van Hovell
>             Fix For: 1.5.0
>
>         Attachments: SPARK-10100.perf.test.scala
>
>
> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org