[
https://issues.apache.org/jira/browse/HIVE-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thejas M Nair updated HIVE-4267:
--------------------------------
Resolution: Won't Fix
Status: Resolved (was: Patch Available)
The jdbc spec doesn't clearly say what representation should be returned by
getString() on a timestamp column. But I think what is more
natural/less-surprising is to have the value of java.sql.Timestamp.toString()
being returned.
Hive cli code has extra logic to remove the trailing ".0". There might have
been some motivations behind that.
I think it is OK to have this difference in behavior with cli.
Marking as 'Won't Fix' .
> 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
