[
https://issues.apache.org/jira/browse/HIVE-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618916#comment-13618916
]
Ashutosh Chauhan commented on HIVE-4267:
----------------------------------------
This looks a bit odd to me. java.sql.Timestamp which is meant to be jdbc
compliant preserves '.0' in toString() If it indeed is compliant than it seems
like jdbc driver is currently doing the right thing and cli
(TimestampWritable.toString()) is the one which needs to be fixed. It will be
good to check if standard says something about resultset.getNext().toString()
method when resultset.getNext() is timestamp. If not, than may be a quick test
against mysql/postgres jdbc driver will be good to verify.
> hiveserver2 jdbc driver - remove trailing ".0" in resultset.getString() for
> timestamp field
> --------------------------------------------------------------------------------------------
>
> Key: HIVE-4267
> URL: https://issues.apache.org/jira/browse/HIVE-4267
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, JDBC
> Reporter: Thejas M Nair
> Assignee: Thejas M Nair
> Fix For: 0.11.0
>
> Attachments: HIVE-4267.1.patch
>
>
> In case of timestamp field, it is printed with a .0 at the end, which is
> inconsistent with hive cli. The format without ".0" is compatible with
> java.sql.Timestamp.valueOf(String).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
