hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aihua Xu (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HIVE-10212) When timestamp is converted to bigint, it's always interpreted as seconds while bigint to timestamp is in milliseconds.
Date Sat, 04 Apr 2015 13:42:33 GMT

     [ https://issues.apache.org/jira/browse/HIVE-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aihua Xu resolved HIVE-10212.
-----------------------------
    Resolution: Won't Fix

Since the future right approach is to convert everything in seconds, we will leave like this.
So we will see inconsistent behavior, converting an int to timestamp in milliseconds, and
when converting back, we get different number. But it should be OK.  

> When timestamp is converted to bigint, it's always interpreted as seconds while bigint
to timestamp is in milliseconds.
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-10212
>                 URL: https://issues.apache.org/jira/browse/HIVE-10212
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>              Labels: timestamp
>
> select cast(ts as bigint) from tbl1. We are treating ts always in seconds. 
> After HIVE-9917 is done, we should also convert based on the config hive.int.timestamp.conversion.in.seconds
is true or false to convert to time in seconds or milliseconds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message