[
https://issues.apache.org/jira/browse/OOZIE-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462421#comment-16462421
]
Peter Bacsko commented on OOZIE-3214:
-------------------------------------
OK, I found it. I'm linking this here as a reference, because it's important:
http://www.quartz-scheduler.org/documentation/best-practices#daylight-savings-time
This writes about {{CronTrigger}}, but it internally uses {{CronExpression}}:
https://github.com/quartz-scheduler/quartz/blob/master/quartz-core/src/main/java/org/quartz/impl/triggers/CronTriggerImpl.java#L76
> 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)
