[
https://issues.apache.org/jira/browse/HIVE-20095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545209#comment-16545209
]
Jonathan Doron commented on HIVE-20095:
---------------------------------------
[~jcamachorodriguez]
I am afraid that your commit for HIVE-20007 also broke the timestamp consuming
from external table, as JavaTimestampObjectInspector now expect
org.apache.hadoop.hive.common.type.Timestamp instead of java.sql.Timestamp
which the jdbc generates.
> Fix jdbc external table feature
> -------------------------------
>
> Key: HIVE-20095
> URL: https://issues.apache.org/jira/browse/HIVE-20095
> Project: Hive
> Issue Type: Bug
> Reporter: Jonathan Doron
> Assignee: Jonathan Doron
> Priority: Major
> Attachments: HIVE-20095.1.patch, HIVE-20095.2.patch,
> HIVE-20095.3.patch, HIVE-20095.4.patch
>
>
> It seems like the committed code for HIVE-19161
> (7584b3276bebf64aa006eaa162c0a6264d8fcb56) reverted some of HIVE-18423
> updates, and therefore some of the external table queries are not working
> correctly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
