[
https://issues.apache.org/jira/browse/HIVE-14412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564689#comment-15564689
]
Rui Li commented on HIVE-14412:
-------------------------------
Thanks [~alangates] and [~jdere] for your inputs. I'll investigate how to make
the comparison right.
bq. Using the GMT+/-HH:MM format for timezone matches the spec, but it does
create a weird situation for many users where 1/2 the year their times will be
off by an hour. I think the big question is can the underlying infrastructure
handle it, as we don't want Hive in the business of understanding when DST
starts and stops all over the world.
Sorry I don't quite get the point here. For users living in a timezone with
DST, it's expected that 1/2 year's time is off by an hour right? E.g. for
America/Los_Angeles, the timezone format is GMT-07:00 in summer and GMT-08:00
in winter. Hive doesn't have to understand when DST begins and ends.
{{TimeZone::getOffset}} will cover this for us.
> 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, HIVE-14412.5.patch,
> HIVE-14412.6.patch, HIVE-14412.7.patch, HIVE-14412.8.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)
