[
https://issues.apache.org/jira/browse/HIVE-14412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15485772#comment-15485772
]
Xuefu Zhang commented on HIVE-14412:
------------------------------------
Hi [~lirui], thanks for working on this. It may take me sometime going through
the code changes, but here are few high-level comments:
1. TIMESTAMP WITH TIME ZONE is the standard name, TIMESTAMPTZ can be an
extension of Hive as an alias of that.
2. Naming conversions. HiveTimestampWritable and TimestampWritables are a
little confusing. Can we use TimestampTZWritable for HiveTimestampWritable?
Same applied to other class names.
3. Can you draw an executive summary on Hive timestamp and why we need
tiemstamptz, especially the difference between the two? This would help others
understand the underlying motivation.
> 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)
