You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Reynold Xin (JIRA)" <ji...@apache.org> on 2015/07/20 02:24:04 UTC

[jira] [Closed] (SPARK-2863) Emulate Hive type coercion in native reimplementations of Hive functions

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

Reynold Xin closed SPARK-2863.
------------------------------
       Resolution: Duplicate
    Fix Version/s: 1.5.0

Closing this one since I believe most of the issues are now addressed because we support almost all functions natively in Spark SQL, and the type coercion interface has been massively refactored in 1.5.


> Emulate Hive type coercion in native reimplementations of Hive functions
> ------------------------------------------------------------------------
>
>                 Key: SPARK-2863
>                 URL: https://issues.apache.org/jira/browse/SPARK-2863
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.0.0
>            Reporter: William Benton
>            Assignee: William Benton
>             Fix For: 1.5.0
>
>
> Native reimplementations of Hive functions no longer have the same type-coercion behavior as they would if executed via Hive.  As [Michael Armbrust points out|https://github.com/apache/spark/pull/1750#discussion_r15790970], queries like {{SELECT SQRT("2") FROM src LIMIT 1}} succeed in Hive but fail if {{SQRT}} is implemented natively.
> Spark SQL should have Hive-compatible type coercions for arguments to natively-implemented functions.



--
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