You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@spark.apache.org by gtinside <gt...@gmail.com> on 2015/03/14 00:12:42 UTC
Spark SQL 1.3 max operation giving wrong results
Hi ,
I am playing around with Spark SQL 1.3 and noticed that "max" function does
not give the correct result i.e doesn't give the maximum value. The same
query works fine in Spark SQL 1.2 .
Is any one aware of this issue ?
Regards,
Gaurav
--
View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/Spark-SQL-1-3-max-operation-giving-wrong-results-tp22043.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@spark.apache.org
For additional commands, e-mail: user-help@spark.apache.org
Re: Spark SQL 1.3 max operation giving wrong results
Posted by Michael Armbrust <mi...@databricks.com>.
Do you have an example that reproduces the issue?
On Fri, Mar 13, 2015 at 4:12 PM, gtinside <gt...@gmail.com> wrote:
> Hi ,
>
> I am playing around with Spark SQL 1.3 and noticed that "max" function does
> not give the correct result i.e doesn't give the maximum value. The same
> query works fine in Spark SQL 1.2 .
>
> Is any one aware of this issue ?
>
> Regards,
> Gaurav
>
>
>
> --
> View this message in context:
> http://apache-spark-user-list.1001560.n3.nabble.com/Spark-SQL-1-3-max-operation-giving-wrong-results-tp22043.html
> Sent from the Apache Spark User List mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@spark.apache.org
> For additional commands, e-mail: user-help@spark.apache.org
>
>