[
https://issues.apache.org/jira/browse/OOZIE-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314990#comment-14314990
]
Bowen Zhang edited comment on OOZIE-2108 at 2/10/15 9:45 PM:
-------------------------------------------------------------
[~puru], RB seems to be down today. The {{JOBS}} command means you are
affecting multiple jobs while the oozie {{JOB}} is meant to be singular. In the
same way, when you try to get job info from multiple jobs, you don't use the
singular {noformat}job -info{noformat} but the {{JOBS}} sub-command. In
addition, the {{JOBS}} already has filter, offset, len, and jobtype options
which come handy and are reused by the bulk write operations.
was (Author: bowenzhangusa):
[~puru], RB seems to be down today. The {{JOBS}} command means you are
affecting multiple jobs while the oozie {{JOB}} is meant to be singular. In the
same way, when you try to get job info from multiple jobs, you don't use the
singular {noformat}job -info{noformat}, but the {{JOBS}} sub-command. In
addition, the {{JOBS}} already has filter, offset, len, and jobtype options
which come handy and are reused by the bulk write operations.
> Given a coordinator name, kill all jobs with that name
> ------------------------------------------------------
>
> 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)
