[
https://issues.apache.org/jira/browse/OOZIE-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986815#comment-13986815
]
Robert Kanter commented on OOZIE-1805:
--------------------------------------
Have an oozie-site config to switch between 1-7 and 0-6 indexing sounds fine to
me.
The local time thing I'm not so sure about. Nowhere else do we use local time,
so if we were to add this, we should make it an available for everything too
(e.g. coordinator start/end times, dataset instance times, etc).
That said, we do have the [{{oozie.processing.timezone}} configuration
property|https://oozie.apache.org/docs/4.0.1/AG_Install.html#Oozie_CoordinatorsBundles_Processing_Timezone]
that lets you add an offset to the UTC timezone Oozie uses for everything. If
you add an offset here to make it your local timezone, the cron syntax should
take that into account as well (if it doesn't, then that's a bug that we should
fix). Note that this doesn't take into account daylight savings time; it's
just an offset. Would this be enough?
> Oozie Cron diverges from standard timezone and day behaviours
> -------------------------------------------------------------
>
> Key: OOZIE-1805
> URL: https://issues.apache.org/jira/browse/OOZIE-1805
> Project: Oozie
> Issue Type: New Feature
> Environment: CDH5
> Reporter: Hari Sekhon
>
> The addition of cron syntax in Oozie (OOZIE-1306) is a good idea but the
> implementation of the fields diverges from standard cron which seems counter
> intuitive for unix veterans.
> Taken from Cloudera's blog:
> http://blog.cloudera.com/blog/2014/04/how-to-use-cron-like-scheduling-in-apache-oozie
> 1. Executing in UTC seems like a bad idea when cron uses local time… if you
> wanted to use UTC you would do it for everything and set your servers to UTC
> timezone.
> Having to translate timezones to figure out what to enter requires more
> effort on the part of the user.
> 2. The day field offsets are wrong/needlessly different compared to ISC cron
> which is zero indexed and uses 0 or 7 for Sunday instead of starting from 1.
> These points will cause a less intuitive experience and surely some
> misconfigurations... could we realign this or would it require an upstream
> fix to the Quartz Scheduler? If the latter would it be easier to just reindex
> the days and calculate the timezone in Oozie before feeding to Quartz?
> Thanks
> Hari Sekhon
> http://www.linkedin.com/in/harisekhon
--
This message was sent by Atlassian JIRA
(v6.2#6252)
