[
https://issues.apache.org/jira/browse/OOZIE-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315641#comment-14315641
]
Purshotam Shah commented on OOZIE-2108:
---------------------------------------
My point is, if kill ( as an example) is needed for for both {{JOBS}} and
{{JOB}}, then why do we need to specify {{JOBS}} or {{JOB}}.
Can't kill be a just command rather then being subcommand of job or jobs.
oozie kill [<id>] [ -value] [name=<abc>]
Based on parameter to kill, we can decide to kill multiple jobs or single job.
After all, kill command is only applicable to job(s), why do we need to specify
{{JOBS}} or {{JOB}}.
> bulk kill, suspend, resume jobs using existing filter, offset, len, and
> jobtype params
> --------------------------------------------------------------------------------------
>
> Key: OOZIE-2108
> URL: https://issues.apache.org/jira/browse/OOZIE-2108
> Project: Oozie
> Issue Type: New Feature
> Reporter: Bowen Zhang
> Assignee: Bowen Zhang
> Attachments: oozie-2108.patch
>
>
> Currently, there is no bulk write operations in "jobs" API. We would like to
> first introduce a bulk kill operation that kills all jobs which satisfy the
> filter. The desired usage will be {noformat}oozie jobs -oozie
> http://localhost:11000/oozie -kill -filter name=something{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
