[
https://issues.apache.org/jira/browse/OOZIE-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153337#comment-13153337
]
Dave commented on OOZIE-606:
----------------------------
I'll take a look at it. But, I won't assign this issue to myself. If I come
up with a fix (probably the one Mohammad suggested), what is the preferred way
to submit this?...as a comment on the issue?
> Oozie coordinator jobs behave incorrectly when given start-times in the past
> ----------------------------------------------------------------------------
>
> Key: OOZIE-606
> URL: https://issues.apache.org/jira/browse/OOZIE-606
> Project: Oozie
> Issue Type: Improvement
> Environment: CentOS
> Reporter: Dave
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> When starting a coordinator job with a start-time that has already passed, it
> queues up multiple workflow-jobs. There should probably be a special
> constant to indicate that the coord-job should start submitting workflow jobs
> "NOW". Consider the "start" parameter in the following:
> <coordinator-app name="coord_job" frequency="60" start="${coord:currentTime}"
> end="<some ending date>" timezone="UTC" xmlns="uri:oozie:coordinator:0.1">
> The meaning of this is that the start time is the current system time.
--
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
