You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Artem Ervits (JIRA)" <ji...@apache.org> on 2017/06/01 15:07:04 UTC
[jira] [Commented] (OOZIE-2867) Timezone handling for Coordinators:
emphasize "Continent/City" format
[ https://issues.apache.org/jira/browse/OOZIE-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033123#comment-16033123 ]
Artem Ervits commented on OOZIE-2867:
-------------------------------------
testUpdateConfForTimeLineServiceEnabled is related to https://issues.apache.org/jira/browse/OOZIE-2902
the other two tests pass locally.
> 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, OOZIE-2867-1.patch, OOZIE-2867-2.patch, OOZIE-2867-3.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)