[ https://issues.apache.org/jira/browse/OOZIE-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965650#comment-13965650 ]
Bowen Zhang commented on OOZIE-1703: ------------------------------------ My biggest concern is the assumption that coord frequency is always an integer(which is not true) displayed in the 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 > Attachments: 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)