[
https://issues.apache.org/jira/browse/HIVE-14412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422200#comment-15422200
]
Rui Li commented on HIVE-14412:
-------------------------------
[~xuefuz], thanks for your comments. In {{TimestampColumnVector}}, we store the
time and nanos of each timestamp, then we read/write them in
{{TimestampTreeReader}} and {{TimestampTreeWriter}} accordingly. I guess we
can't maintain compatibility here since we're adding a new field.
Another possible solution is, instead of extending timestamp, we treat
HiveTimestamp as a totally new data type. What do you think?
> 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)
