You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Lefty Leverenz (JIRA)" <ji...@apache.org> on 2017/08/27 06:29:02 UTC

[jira] [Commented] (HIVE-14412) Add timestamp with time zone

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

Lefty Leverenz commented on HIVE-14412:
---------------------------------------

Doc note:  This needs to be documented in the wiki, but see HIVE-16614 which changes the type name from 'TIMESTAMP WITH TIME ZONE' to 'TIMESTAMP WITH LOCAL TIME ZONE'.

* [Hive Data Types -- Timestamps | https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Types#LanguageManualTypes-TimestampstimestampTimestamps]


> Add timestamp with time zone
> ----------------------------
>
>                 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
>              Labels: TODOC3.0
>             Fix For: 3.0.0
>
>         Attachments: HIVE-14412.10.patch, HIVE-14412.11.patch, HIVE-14412.12.patch, HIVE-14412.13.patch, HIVE-14412.1.patch, HIVE-14412.2.patch, HIVE-14412.3.patch, HIVE-14412.4.patch, HIVE-14412.5.patch, HIVE-14412.6.patch, HIVE-14412.7.patch, HIVE-14412.8.patch, HIVE-14412.9.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.4.14#64029)