[
https://issues.apache.org/jira/browse/OOZIE-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680734#comment-13680734
]
Robert Kanter commented on OOZIE-1306:
--------------------------------------
I talked with Alejandro offline and at a high level, we should be able to
support cron-like scheduling using crontab syntax. We may have to do some
refactoring, but it should be possible to modify the EL functions (e.g.
{{current(-1)}}) to handle cron frequencies as we're typically resolving
frequencies to specific datetimes and using those anyway. So, we'd have a new
time unit called "CRON" and the user would specify the crontab syntax as the
frequency. We'd have to create a function that can parse crontab syntax, and
some object that can handle the calculations for cron stuff. The EL functions
currently just directly use the frequency and do some math, but if we do some
abstraction here, we can make a version that handles cron, handles days, a
version that handles months, etc.
If we want to do this, or even something similar, we'll need to change the
datatype of the frequency column in the database to a varchar instead of an int
to be able to store the crontab in there; in anticipation of this, perhaps we
should make this database change in Oozie 4.0 while we can, even if we don't
have the cron stuff ready yet?
> add flexibility to oozie coordinator job scheduling
> ---------------------------------------------------
>
> Key: OOZIE-1306
> URL: https://issues.apache.org/jira/browse/OOZIE-1306
> Project: Oozie
> Issue Type: New Feature
> Reporter: Bowen Zhang
>
> Right now, to have a job that runs everyday from 9-5pm, we need to schedule 8
> identical daily coordinator job, each of which starts at one particular hour;
> To have a job that runs from Monday through Friday, we need 5 identical
> weekly jobs with different start time. And there is no way right now to
> schedule a job to runevery first day of the month. This ticket aims to solve
> this inconvenience.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
