[
https://issues.apache.org/jira/browse/HIVE-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Blue updated HIVE-12195:
-----------------------------
Description:
Using an unknown time zone with the {{from_utc_timestamp}} or
{{to_utc_timetamp}} methods returns the time un-adjusted instead of throwing an
error:
{code}
hive> select from_utc_timestamp('2015-04-11 12:24:34.535', 'panda');
OK
2015-04-11 12:24:34.535
{code}
This should be an error because users may attempt to adjust to valid but
unknown zones, like PDT or MDT. This would produce incorrect results with no
warning or error.
*Update*: A good work-around is to add a table of known zones that maps to
offset zone identifiers, like {{GMT-07:00}}. The table is small enough to
always be a broadcast join and results can be filtered (e.g. {{offset_zone IS
NOT NULL}}) so that only valid zones are passed to {{from_utc_timestamp}}.
was:
Using an unknown time zone with the {{from_utc_timestamp}} or
{{to_utc_timetamp}} methods returns the time un-adjusted instead of throwing an
error:
{code}
hive> select from_utc_timestamp('2015-04-11 12:24:34.535', 'panda');
OK
2015-04-11 12:24:34.535
{code}
This should be an error because users may attempt to adjust to valid but
unknown zones, like PDT or MDT. This would produce incorrect results with no
warning or error.
> Unknown zones should cause an error instead of silently failing
> ---------------------------------------------------------------
>
> Key: HIVE-12195
> URL: https://issues.apache.org/jira/browse/HIVE-12195
> Project: Hive
> Issue Type: Sub-task
> Components: Hive
> Reporter: Ryan Blue
> Assignee: Shinichi Yamashita
> Attachments: HIVE-12195.1.patch, HIVE-12195.2.patch,
> HIVE-12195.3.patch, HIVE-12195.4.patch
>
>
> Using an unknown time zone with the {{from_utc_timestamp}} or
> {{to_utc_timetamp}} methods returns the time un-adjusted instead of throwing
> an error:
> {code}
> hive> select from_utc_timestamp('2015-04-11 12:24:34.535', 'panda');
> OK
> 2015-04-11 12:24:34.535
> {code}
> This should be an error because users may attempt to adjust to valid but
> unknown zones, like PDT or MDT. This would produce incorrect results with no
> warning or error.
> *Update*: A good work-around is to add a table of known zones that maps to
> offset zone identifiers, like {{GMT-07:00}}. The table is small enough to
> always be a broadcast join and results can be filtered (e.g. {{offset_zone IS
> NOT NULL}}) so that only valid zones are passed to {{from_utc_timestamp}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
