You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Thejas M Nair (JIRA)" <ji...@apache.org> on 2013/04/01 01:03:15 UTC
[jira] [Updated] (HIVE-4267) hiveserver2 jdbc driver - remove
trailing ".0" in resultset.getString() for timestamp field
[ https://issues.apache.org/jira/browse/HIVE-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thejas M Nair updated HIVE-4267:
--------------------------------
Description:
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).
was:
The jdbc driver for hive server2 is printing binary using byte[].toString() instead of first converting it string by using it as a string constructor argument. In case of timestamp field, it is printed with a .0 at the end, which is inconsistent with hive cli.
Summary: hiveserver2 jdbc driver - remove trailing ".0" in resultset.getString() for timestamp field (was: fix ResultSet.getString in hiveserver2 jdbc driver for binary, timestamp)
> 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
>
>
> 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