[
https://issues.apache.org/jira/browse/HIVE-17230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208572#comment-16208572
]
Aihua Xu commented on HIVE-17230:
---------------------------------
Thanks [~kgyrtkirk] for looking into it. Seems like the standard is more about
how to store the timestamp data
http://troels.arvin.dk/db/rdbms/#data_types-date_and_time-timestamp, not about
how to display the timestamp. So either will be fine if the result is correct.
Hive follows more with Oracle and Postgres, but Oracle shows the trailing 0 and
postgres removes the trailing 0.
[~jdere] Do you have opinion on this?
> Timestamp format different in HiveCLI and Beeline
> -------------------------------------------------
>
> Key: HIVE-17230
> URL: https://issues.apache.org/jira/browse/HIVE-17230
> Project: Hive
> Issue Type: Bug
> Components: Beeline, CLI
> Reporter: Peter Vary
> Assignee: Marta Kuczora
> Attachments: HIVE-17230.1.patch, HIVE-17230.2.patch,
> HIVE-17230.3.patch
>
>
> The issue can be reproduced with the following commands:
> {code}
> create table timestamp_test(t timestamp);
> insert into table timestamp_test values('2000-01-01 01:00:00');
> select * from timestamp_test;
> {code}
> The timestamp is displayed without nanoseconds in HiveCLI:
> {code}
> 2000-01-01 01:00:00
> {code}
> When the exact same timestamp is displayed in BeeLine it displays:
> {code}
> 2000-01-01 01:00:00.0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
