[
https://issues.apache.org/jira/browse/HIVE-22706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015109#comment-17015109
]
Zoltan Haindrich commented on HIVE-22706:
-----------------------------------------
[~srahman] well...it's not nice to have this fixed here in hive's
jdbc-handler...but yes; it makes sense to also cover the write in case it's
needed at some point
I've found traces that at some point derby wrote 0/1 into CHAR types and not
true/false https://issues.apache.org/jira/browse/DERBY-4965
note: there is some very flexible error handling in the
[DBOutputFormat|https://github.com/apache/hadoop/blob/1c51f36be79924489ca4a2e5ca7e96ac75a6ec18/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/lib/db/DBOutputFormat.java#L125]
...it may make resultsets disappear in some cases - when there is a jdbc issue
I fixed the write path - and extended the test to cover this as well.
> Jdbc storage handler incorrectly interprets boolean column value in derby
> -------------------------------------------------------------------------
>
> Key: HIVE-22706
> URL: https://issues.apache.org/jira/browse/HIVE-22706
> Project: Hive
> Issue Type: Bug
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Attachments: HIVE-22706.01.patch, HIVE-22706.01.patch,
> HIVE-22706.01.patch, HIVE-22706.01.patch, HIVE-22706.02.patch
>
>
> in case the column value is false ; the storage handler interprets it as true
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
