[
https://issues.apache.org/jira/browse/OOZIE-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Purshotam Shah updated OOZIE-1703:
----------------------------------
Description:
This is one of the important use-case in case of versioning.
User can set end date of old coord/bundle before start date( if coord/bundle 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.
was:
This is one of the important use-case in case of versioning.
User can set end date of old coord/bundle before start date( if coord/bundle 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 suspend the bundle, if it's in PREP and new end-date is before
kick off time. Suspend coord if it's in PREP and new end-date is before start
date.
> User should be able to set bundle/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/bundle before start date( if coord/bundle
> 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)
