hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rui Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-14412) Add a timezone-aware timestamp
Date Wed, 17 Aug 2016 02:23:20 GMT

    [ https://issues.apache.org/jira/browse/HIVE-14412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423762#comment-15423762
] 

Rui Li commented on HIVE-14412:
-------------------------------

To read the new field, we need another IntegerReader in {{TimestampTreeReader}}. If we use
the reader to read the field from old data, I guess we either hit exceptions or get wrong
data. In order to maintain b/c, we need a way to indicate whether the new field exists, like
in TimestampWritable encoding. But I don't find any way to do it for ORC/vectorization.

> Add a timezone-aware timestamp
> ------------------------------
>
>                 Key: HIVE-14412
>                 URL: https://issues.apache.org/jira/browse/HIVE-14412
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Hive
>            Reporter: Rui Li
>            Assignee: Rui Li
>         Attachments: HIVE-14412.1.patch, HIVE-14412.1.patch, HIVE-14412.1.patch
>
>
> Java's Timestamp stores the time elapsed since the epoch. While it's by itself unambiguous,
ambiguity comes when we parse a string into timestamp, or convert a timestamp to string, causing
problems like HIVE-14305.
> To solve the issue, I think we should make timestamp aware of timezone.



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

Mime
View raw message