[
https://issues.apache.org/jira/browse/OOZIE-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432860#comment-13432860
]
Alejandro Abdelnur commented on OOZIE-948:
------------------------------------------
A solution would be add an Oozie configuration property 'processing.timezone',
that could be set to a {{GMT(+/-)####}} offset timezone. Note that a GMT offset
timezone does not support DST.
In addition, to reduce users/admins possibility of mistakes because the non UTC
timezone, if the processing time is set to a value other than UTC, all datetime
parameters in the coordinator applications and job parameters must be expressed
with the corresponding GMT offset. For example, if the processing timezone is
set to {{GMT+0530}}, a valid datetime would be {{2009-08-10T05:30+0530}}.
> Add support for Oozie coordinator to work in an UTC offset
> ----------------------------------------------------------
>
> Key: OOZIE-948
> URL: https://issues.apache.org/jira/browse/OOZIE-948
> Project: Oozie
> Issue Type: Improvement
> Components: bundle, coordinator
> Affects Versions: 3.2.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Priority: Critical
> Fix For: trunk
>
>
> Current Oozie coordinator expects and resolves dates in UTC (ie
> {{2009-08-10T00:00Z}}). UTC datetimes are used for start/end/pause of jobs,
> datasets initial-instance and to resolve dataset instance URI templates.
> Adding support for a non UTC timezone it would enable deployments where they
> use a timezone different than UTC as standard. This seems quite common in
> countries where they don't observe DST changes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
