[
https://issues.apache.org/jira/browse/OOZIE-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316803#comment-14316803
]
Bowen Zhang commented on OOZIE-2108:
------------------------------------
{quote}It makes sense to use same job command for both single and multiple job
so that end-user interface is simpler{quote}
[~shwethags], unfortunately, I don't think this approach makes the user
interface simpler because you will need to duplicate "filter", "len", "offset",
and "jobtype" options onto {{JOB}} command and from codebase perspective, this
is duplicated codes to maintain.
{quote}We can even give existing 'jobs' functionality with 'job' as well and
slowly deprecate 'jobs'{quote}
I am not sure if it's a good idea to deprecate {{JOBS}} due to the backward
incompatibility introduced. If it is a good idea, I think it's beyond the scope
of this jira.
[~egashira], same thing here, I am not sure it's a good idea to consolidate the
two commands.
On a side note, I want to talk about Oozie's backward compatibility. In the
past year or so, I've seen a couple incidents when it comes to maintaining
backward compatibility. From sharelib installation behavior change to
[OOZIE-1754|https://issues.apache.org/jira/browse/OOZIE-1754] to the recent new
maven build change, we see some of our affected customers absolutely furious
about the changes. Just like what [~rohini] says, my approach is the most
backward-compatible way and minimize duplicated codes going forward.
> 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)
