[
https://issues.apache.org/jira/browse/IMPALA-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Csaba Ringhofer resolved IMPALA-7060.
-------------------------------------
Resolution: Won't Do
[~mikesbrown]
Yes, as IMPALA-3307 is already merged to master, this ticket can be closed.
Thanks for the reminder!
> Restrict Impala to only support timezones that work in Hive (IANA + Java)
> -------------------------------------------------------------------------
>
> Key: IMPALA-7060
> URL: https://issues.apache.org/jira/browse/IMPALA-7060
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Csaba Ringhofer
> Assignee: Csaba Ringhofer
> Priority: Major
>
> IANA timezone integration (IMPALA-3307) will drop the support for many
> non-standard timezone aliases. As IMPALA-3307 is a very large change, its
> release may be delayed - meanwhile, it would be better to discourage Impala
> 3.x users from using timezone names that will not be supported in the future.
> For this reason, the current boost based implementation could drop the
> support for non-standard aliases.
> Note that the current implementation has some major issues:
> - Some of the aliases are ambiguous - Impala will always interpret it the
> same way, but this is based on an arbitrary ordering of timezones, so the
> timezone may be actually different than what the user wanted. I think that it
> is better the print a warning in this case.
> - If the name is not among the standard names, the lookup among aliases is
> extremely slow (linear search on all supported standard timezones).
> - Most of the aliases are not covered by test cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
