[
https://issues.apache.org/jira/browse/HIVE-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907972#comment-13907972
]
Xuefu Zhang commented on HIVE-3635:
-----------------------------------
[~thejas] I found no standard regarding this. SQL standards define three
literal values for boolean: TRUE, FALSE, and UNKNOWN [1]. The standard is also
controversial, and as a result, different DB has different implementations [2].
It seems that only Postgre SQL allows this. Other legacy data, such as that in
MS Access, may also have this. That's why I think it makes sense to have a
configuration or serde property to turn this on only if it's desired.
[1] http://en.wikipedia.org/wiki/Boolean_data_type
[2] http://community.actian.com/wiki/SQL_BOOLEAN_type
> allow 't', 'T', '1', 'f', 'F', and '0' to be allowable true/false values for
> the boolean hive type
> ---------------------------------------------------------------------------------------------------
>
> Key: HIVE-3635
> URL: https://issues.apache.org/jira/browse/HIVE-3635
> Project: Hive
> Issue Type: Improvement
> Components: CLI
> Affects Versions: 0.9.0
> Reporter: Alexander Alten-Lorenz
> Assignee: Xuefu Zhang
> Attachments: HIVE-3635.patch
>
>
> interpret t as true and f as false for boolean types. PostgreSQL exports
> represent it that way.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
