[
https://issues.apache.org/jira/browse/OOZIE-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013931#comment-14013931
]
Purshotam Shah commented on OOZIE-1703:
---------------------------------------
We noticed some issue while testing internally.
If we set endtime multiple times, coord remains in running state.
Attaching amendment patch.
> User should be able to set coord end-time before start time
> -----------------------------------------------------------
>
> Key: OOZIE-1703
> URL: https://issues.apache.org/jira/browse/OOZIE-1703
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
> Assignee: Purshotam Shah
> Fix For: trunk
>
> Attachments: OOZIE-1703-V5.patch, OOZIE-1703-V6.patch,
> OOZIE-1703-V7.patch, OOZIE-1703.patch
>
>
> This is one of the important use-case in case of versioning.
> User can set end date of old coord before start date( if coord is supposed to
> run in future), so that it doesn't run and user can safely upload new version.
> We should also lookahead at created actions that become invalid because of
> the new end time.
> These actions should be deleted from DB.
> We should also update the status of bundle. If it's in PREP and new end-date
> is before kick off time, then job status will be set to SUCCEEDED. User can
> again change the end date to future date, the status will be changed to
> RUNNING.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
