[
https://issues.apache.org/jira/browse/OOZIE-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315375#comment-14315375
]
Robert Kanter commented on OOZIE-2108:
--------------------------------------
As Puru points out, this is repeating all of the commands. On top of that, the
"jobs" command has been read-only so far. Though I can see the logic in having
the single job commands under "job" and the multiple job commands under "jobs".
So I'm not really sure which is the best way to do this. Our CLI is already
pretty complicated with some subcommands that are only used with other
subcommands, etc; and I don't want to make it even more complicated.
[~shwethags], [~egashira], [~rohini], [~chitnis], any thoughts?
> 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)
