[
https://issues.apache.org/jira/browse/OOZIE-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462304#comment-16462304
]
Peter Bacsko commented on OOZIE-3214:
-------------------------------------
[~jphelps] then we need extra logic if we want to follow the approach of cron.
I have to double-check, but IIRC {{CronExpression}} does exactly the opposite,
ie. actions at 2am will be skipped in one direction and will be run twice 6
months later. If we want to correct this, we need extra calculations.
Also, we have to consider the case when we explicitly define execution times at
2am and 3am. When there is a change from 1:59:59 to 3:00:00, shall we start the
action twice?
> Allow configurable timezone for coordinators
> --------------------------------------------
>
> Key: OOZIE-3214
> URL: https://issues.apache.org/jira/browse/OOZIE-3214
> Project: Oozie
> Issue Type: New Feature
> Components: coordinator
> Affects Versions: trunk
> Reporter: Julia Kinga Marton
> Assignee: Julia Kinga Marton
> Priority: Major
>
> Right now in case of coordinators only daylight saving time corrections are
> applied, the processing timezone for the coordinators is always the Oozie
> processing timezone.
> It would be more transparent to have an option for changing the {{timezone}}
> attribute itself, such as an additional attribute in the {{coordinator.xml}}
> (meaning a new version of {{coordinator.xsd}}). I would make this option
> switched off by default(to have the actual behavior).
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
