[jira] [Comment Edited] (OOZIE-2108) bulk kill, suspend, resume jobs using existing filter, offset, len, and jobtype params

["Bowen Zhang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340358#comment-14340358 ] 

Bowen Zhang edited comment on OOZIE-2108 at 2/27/15 7:03 PM:
-------------------------------------------------------------

[~shwethags], are you looking at the right patch? BulkbundleKillXCommand has been removed already in the latest patch. There are only three bulk(*)XCommand files left with the creation of OperationType for enum


was (Author: bowenzhangusa):
[~shwethags], my bad for the confusion. I should have removed the class of Bulkbundle(*)XCommand since they are no longer used. If you look at bundleEngine.java, all the bulk actions are being invoked to BulkBundleXCommand. All the workflow actions are being invoked to BulkWorkflowXCommand and similarly to BulkCoordXCommand with the creation of OperationType as an enum.

> 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, oozie-2108.patch, 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)