[
https://issues.apache.org/jira/browse/OOZIE-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975135#comment-15975135
]
Andras Piros commented on OOZIE-2867:
-------------------------------------
[~dbist13] you're welcome.
I thought of something like this:
* update docs to emphasize {{Continent/City}} format
* as both {{BST}} and {{Europe/London}} are present in
{{java.util.TimeZone#getAvailableIds}}, within {{DateUtils#getTimeZone}}:
** {{TRACE}} log the input {{tzId}}
** {{WARN}} log if {{tzId}} doesn't match following regex:
{{^(Africa|America|Asia|Atlantic|Australia|Europe|Indian|Pacific)/.*}}, but let
the calculations happen in exactly the same way as before
> Timezone handling for Coordinators: emphasize "Continent/City" format
> ---------------------------------------------------------------------
>
> Key: OOZIE-2867
> URL: https://issues.apache.org/jira/browse/OOZIE-2867
> Project: Oozie
> Issue Type: Sub-task
> Components: coordinator
> Affects Versions: 4.3.0
> Reporter: Andras Piros
> Fix For: 5.0.0
>
>
> It seems that some time zone abbreviations like {{BST}} for British Summer
> Time silently just do not get accepted correctly by Oozie and the underlying
> JVM.
> It would be great to:
> * emphasize in the Coordinator Functional Specification that it's best to
> only use time zone format {{Continent/City}}, like {{Europe/London}}, or
> {{America/Los_Angeles}}, instead of other formats like {{PDT}}, {{PST}}, or
> {{BST}}
> * if the timezone is not recognized by Oozie, it's best to emit a {{WARN}}
> log and suppose {{UTC}} instead of silently ignoring the unknown specified
> timezone
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
