[ https://issues.apache.org/jira/browse/OOZIE-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986454#comment-13986454 ]
Hari Sekhon commented on OOZIE-1805: ------------------------------------ maybe some kind of "cron compatability mode" where it uses local time and also fixes the days to start at 0 => Sunday to be the same as ISC cron. That would allow for much more intuitive behaviour without breaking existing behaviour for legacy installations. > 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)