You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Zoltan Haindrich (JIRA)" <ji...@apache.org> on 2017/12/04 21:57:00 UTC
[jira] [Updated] (HIVE-15939) Make cast expressions comply more to
sql2011
[ https://issues.apache.org/jira/browse/HIVE-15939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zoltan Haindrich updated HIVE-15939:
------------------------------------
Attachment: HIVE-15939.6.patch
#6)
* make cast expression align with HIVE-6590 ; accept {{false|off|no|0|}}... values as false; others as true.
* I'm not sure; but I haven't changed {{CastStringToLong}} which has a very different mindset currently: {{TRUE/FALSE/T/F}} with case insensitivity to its respective values; other values are mapped to NULL... this is very different so I've left it alone..
> Make cast expressions comply more to sql2011
> --------------------------------------------
>
> Key: HIVE-15939
> URL: https://issues.apache.org/jira/browse/HIVE-15939
> Project: Hive
> Issue Type: Sub-task
> Components: SQL
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Attachments: HIVE-15939.1.patch, HIVE-15939.2.patch, HIVE-15939.3.patch, HIVE-15939.4.patch, HIVE-15939.5.patch, HIVE-15939.6.patch
>
>
> in HIVE-6590 Jason have uncovered the fact that UDFToBoolean treats all non-empty strings as true.
> It would be great to have the cast expressions closer to the standard...at least when there is an expected behaviour from the user;
> like {{cast('false' as boolean)}} should be true.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)