[
https://issues.apache.org/jira/browse/OOZIE-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980336#comment-13980336
]
Robert Kanter commented on OOZIE-1805:
--------------------------------------
{quote}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.{quote}
Oozie does everything in UTC time. I don't think we should change this unless
we start allowing other timezones everywhere. But the reason we don't do that
is that timezone and daylight savings time can make things problematic.
Currently, the user has to translate to UTC when setting start time, end time,
etc.
{quote}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.{quote}
There are differences in syntax even among cron tools. Quartz uses 1-7 for the
for the Day-of-Week field, so that's what we used. While it wouldn't be that
difficult to re-index before calling Quartz, I'm not sure we want to establish
a bunch of stuff on top of Quartz. The documentation, and my blog post you
linked to, clearly states that its 1-7 and uses Quartz. In any case, you can
also use SUN-SAT so you don't have to worry about the indexing. Switching the
indexing would also be problematic for anyone already using the cron-like
scheduling feature...
> 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: Bug
> 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)
