[jira] [Commented] (OOZIE-2711) Ability to set end time of coordinator to time in the past.

["sandeep samudrala (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15583781#comment-15583781 ] 

sandeep samudrala commented on OOZIE-2711:
------------------------------------------

I had earlier asked for a similar request in the below attached mail on the dev mailing list but hadn't got any response for the same.
http://markmail.org/message/gaw4fc3dizmfg7lv




> Ability to set end time of coordinator to time in the past.
> -----------------------------------------------------------
>
>                 Key: OOZIE-2711
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2711
>             Project: Oozie
>          Issue Type: Improvement
>            Reporter: sandeep samudrala
>
> At times user would want to update the coordinator end time to some time in the past but not delete the instances from the specified end time to current time. This way, when a new coordinator starts from the specified end time gives capability to user to track new coord flow with new changes from an EFFECTIVE time and not on current time(currently end time can be set at most to current time) as any instances that are succeeded in the past end time cannot be updated.
> While updating the end time of a coordinator, the coordinator is paused (by sending pause time), which means the end time can be future only as coordchangecommandx checks for the instances to be deleted to be in WAITING/READY.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)