You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Bruce Robbins (JIRA)" <ji...@apache.org> on 2018/04/29 03:04:00 UTC

[jira] [Created] (HIVE-19354) from_utc_timestamp returns incorrect results for datetime values with timezone

Bruce Robbins created HIVE-19354:
------------------------------------

             Summary: from_utc_timestamp returns incorrect results for datetime values with timezone
                 Key: HIVE-19354
                 URL: https://issues.apache.org/jira/browse/HIVE-19354
             Project: Hive
          Issue Type: Bug
          Components: Hive
    Affects Versions: 3.1.0
            Reporter: Bruce Robbins


On the master branch, from_utc_timestamp returns incorrect results for datetime strings that containĀ a timezone:
{noformat}
hive> select from_utc_timestamp('2000-10-10 00:00:00+00:00', 'America/Los_Angeles');
OK
2000-10-09 10:00:00
Time taken: 0.294 seconds, Fetched: 1 row(s)
hive> select from_utc_timestamp('2000-10-10 00:00:00', 'America/Los_Angeles');
OK
2000-10-09 17:00:00
Time taken: 0.121 seconds, Fetched: 1 row(s)
hive> 
{noformat}
Both inputs are 2000-10-10 00:00:00 in UTC time, but I got two different results.

In version 2.3.3, from_utc_timestamp doesn't accept timezones in its input strings, so it does not have this bug:
{noformat}
hive> select from_utc_timestamp('2000-10-10 00:00:00+00:00', 'America/Los_Angeles');
OK
NULL
Time taken: 5.152 seconds, Fetched: 1 row(s)
hive> select from_utc_timestamp('2000-10-10 00:00:00', 'America/Los_Angeles');
OK
2000-10-09 17:00:00
Time taken: 0.069 seconds, Fetched: 1 row(s)
hive> 
{noformat}
Since the function is expecting a UTC datetime value, it probably should continue to reject input that contains a timezone component.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)