[jira] [Work stopped] (HIVE-21094) Store TIMESTAMP WITH LOCAL TIME ZONE in UTC instead of writer's time zone

["Karen Coppage (JIRA)" <ji...@apache.org>]

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

Work on HIVE-21094 stopped by Karen Coppage.
--------------------------------------------
> Store TIMESTAMP WITH LOCAL TIME ZONE in UTC instead of writer's time zone
> -------------------------------------------------------------------------
>
>                 Key: HIVE-21094
>                 URL: https://issues.apache.org/jira/browse/HIVE-21094
>             Project: Hive
>          Issue Type: Improvement
>          Components: Hive
>            Reporter: Karen Coppage
>            Assignee: Karen Coppage
>            Priority: Major
>         Attachments: HIVE-21094.1.patch, HIVE-21094.1.patch, HIVE-21094.1.patch, HIVE-21094.1.patch, HIVE-21094.1.patch
>
>
> TIMESTAMP WITH LOCAL TIME ZONE (aka TIMESTAMPTZ) is stored in writer's local time, and the writer's zone is stored with it. When reading, the timestamp in reader local time + reader zone is displayed. This is misleading for the user, since it looks like all the data was written in the reader's time zone.
> TIMESTAMPTZ should be stored in UTC time and be displayed in reader local time (as it was before) but should not display the reader's time zone.
> This was discussed in the community doc [Consistent timestamp types in Hadoop SQL engines|https://docs.google.com/document/d/1gNRww9mZJcHvUDCXklzjFEQGpefsuR_akCDfWsdE35Q/edit?usp=sharing]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)