[
https://issues.apache.org/jira/browse/HIVE-14305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388851#comment-15388851
]
Rui Li commented on HIVE-14305:
-------------------------------
Hi [~rdblue], I think only changing the timezone during timestamp computation
(e.g. {{GenericUDFFromUtcTimestamp::evaluate}}) is not enough. Since
Timestamp::toString is also affected by local timezone, we need to make sure
UTC is used throughout the whole query. I'm not sure if this is acceptable.
Even if it is, we'll need a way to determine whether a query involves timestamp
computation. Or are you suggesting we can simply set UTC for any queries?
I think a simpler solution is to use string instead of Java Timestamp. What do
you think?
> To/From UTC timestamp may return incorrect result because of DST
> ----------------------------------------------------------------
>
> Key: HIVE-14305
> URL: https://issues.apache.org/jira/browse/HIVE-14305
> Project: Hive
> Issue Type: Sub-task
> Reporter: Rui Li
> Assignee: Rui Li
>
> If the machine's local timezone involves DST, the UDFs return incorrect
> results.
> For example:
> {code}
> select to_utc_timestamp('2005-04-03 02:01:00','UTC');
> {code}
> returns {{2005-04-03 03:01:00}}. Correct result should be {{2005-04-03
> 02:01:00}}.
> {code}
> select to_utc_timestamp('2005-04-03 10:01:00','Asia/Shanghai');
> {code}
> returns {{2005-04-03 03:01:00}}. Correct result should be {{2005-04-03
> 02:01:00}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
