[ https://issues.apache.org/jira/browse/OOZIE-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317720#comment-14317720 ]
Shwetha G S commented on OOZIE-2108: ------------------------------------ >From user's perspective, they need to figure out if its job/jobs command >depending on how many jobs that they need to operate on. From oozie code >perspective, you just write it once(I understand that we need to think about >code maintainability, but thats not much of an issue here). But user needs to >think about this everytime they need to issue the command. We don't need to deprecate jobs right now or as part of this jira. We can do it later if we don't add kill etc as part of jobs > 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)