[
https://issues.apache.org/jira/browse/HIVE-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136803#comment-14136803
]
Eugene Koifman commented on HIVE-8105:
--------------------------------------
I'm wondering if it's not better to disallow NULL until we create the input
format as you suggest. As it is, this works for numeric types, but for
boolean/string types this will take NULL from user input and insert an
FALSE/empty string. This doesn't seem right.
Is it possible to check the target type and throw if it's not numeric?
> booleans and nulls not handled properly in insert/values
> --------------------------------------------------------
>
> Key: HIVE-8105
> URL: https://issues.apache.org/jira/browse/HIVE-8105
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.14.0
> Reporter: Alan Gates
> Assignee: Alan Gates
> Priority: Critical
> Attachments: HIVE-8105.2.patch, HIVE-8105.patch
>
>
> Doing an insert/values with a boolean always results in a value of true,
> regardless of whether true or false is given in the query.
> Doing an insert/values with a null for a column value results in a semantic
> error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
