[
https://issues.apache.org/jira/browse/IMPALA-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489039#comment-16489039
]
Jim Apple commented on IMPALA-7060:
-----------------------------------
For a user that depends on these, a breaking change in 3.1 or 3.2 could be a
very bad user experience.
Given our tradition of holding breaking changes until a major version bump, I
strongly suggest we talk about this on the dev@ mailing list before committing
it without bumping the major version.
I'm not necessarily opposed to going straight to 4.0 is this is so important is
can't wait.
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
