[
https://issues.apache.org/jira/browse/OOZIE-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947338#comment-13947338
]
Robert Kanter commented on OOZIE-1759:
--------------------------------------
{quote}make sure we don't delete children jobs of a running parent.{quote}
I think that should be ok based on the precedent set by OOZIE-1532. We just
have to make sure to also delete the associated action so that action doesn't
refer to a nonexistent workflow. Right?
> Add a command to delete jobs
> ----------------------------
>
> Key: OOZIE-1759
> URL: https://issues.apache.org/jira/browse/OOZIE-1759
> Project: Oozie
> Issue Type: New Feature
> Reporter: Robert Kanter
>
> When testing a workflow, coordinator, or bundle, you can easily end up with a
> lot of "bad" jobs that you really don't need anymore. Currently, you can
> either wait for Oozie to remove them, drop the entire Oozie database, or go
> in the database and manually delete the job (which we don't want to
> encourage).
> It would be useful if we added a "delete" command to delete jobs. We can
> restrict the command to only allow you to delete jobs that are SUCCEEDED,
> KILLED, or FAILED to prevent users from deleting jobs in progress.
> i.e.
> {noformat}
> oozie job -delete <job-id>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
