[
https://issues.apache.org/jira/browse/HIVE-14412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488427#comment-15488427
]
Xuefu Zhang edited comment on HIVE-14412 at 9/13/16 9:29 PM:
-------------------------------------------------------------
I think the standard type name is TIMESTAMP WITH TIME ZONE. However, I'm not
sure how hard to change the grammar to handle spaces in type name. It seems
doable. It's fine to leave this for the future, but it's better not to
introduce a nonstandard name. We can have TIMESTAMPTZ for now.
[~mmccline], I believe what you mentioned can be done incrementally.
was (Author: xuefuz):
I think the standard type name is TIMESTAMP WITH TIMEZONE. However, I'm not
sure how hard to change the grammar to handle spaces in type name. It seems
doable.
[~mmccline], I believe what you mentioned can be done incrementally.
> 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.2.patch,
> HIVE-14412.3.patch, HIVE-14412.4.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)
