[
https://issues.apache.org/jira/browse/OOZIE-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316966#comment-14316966
]
Rohini Palaniswamy commented on OOZIE-2108:
-------------------------------------------
[~bowenzhangusa],
bq. I am not sure if it's a good idea to deprecate JOBS due to the backward
incompatibility introduced.
You are right. Deprecating and removing something that is used by users
for a long time is hard and would not work without disrupting many people.
bq. From sharelib installation behavior change to OOZIE-1754 to the recent
new maven build change, we see some of our affected customers absolutely
furious about the changes.
In most of the cases the changes are unintentional or missing scenarios
to take care of when trying to enhance something and is not done with the
intent of breaking backward compatibility. Cannot avoid something happening
like that occasionally and is a matter of fixing it if found during testing or
enhancing our test suites to cover those cases. Usually when someone is trying
to change something that involves backward compatibility or bigger change, I
have always seen folks asking others for review or confirmation before going
ahead with it.
> 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)
