[
https://issues.apache.org/jira/browse/OOZIE-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996279#comment-15996279
]
Andras Piros edited comment on OOZIE-2867 at 5/4/17 7:04 AM:
-------------------------------------------------------------
[~dbist13] can you please upload the patch w/ the failing test case.
I think I would just extend the second sentence on the CLI:
{noformat}
Give the ID (Continent/City) to the -timezone argument, and in the coordinator
definitions
{noformat}
was (Author: andras.piros):
[~dbist13] can you please upload the patch w/ the failing test case.
I think I would just extend the second sentence on the CLI:
{noformat}
Give the ID to the -timezone argument, and in the coordinator definitions
{noformat}
> 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
> Assignee: Artem Ervits
> Fix For: 5.0.0
>
> Attachments: OOZIE-2867-0.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
(v6.3.15#6346)
