[ https://issues.apache.org/jira/browse/OOZIE-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175438#comment-17175438 ]
Lars Francke commented on OOZIE-2867: ------------------------------------- The logic for the error message is the wrong way around. It prints warnings for all valid timezones now. See OOZIE-3608 > [Coordinators] Emphasize Region/City timezone 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 > Assignee: Artem Ervits > Priority: Major > Fix For: 5.1.0 > > Attachments: OOZIE-2867-0.patch, OOZIE-2867-1.patch, > OOZIE-2867-2.patch, OOZIE-2867-3.patch, OOZIE-2867-4.patch, > OOZIE-2867-5.patch, OOZIE-2867-6.patch, OOZIE-2867-7.patch > > > 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 (v8.3.4#803005)