[
https://issues.apache.org/jira/browse/OOZIE-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585682#comment-14585682
]
Shwetha G S commented on OOZIE-2020:
------------------------------------
[~rkanter], [~puru], [~bowenzhangusa], does anyone use the oozie REST APIs
directly? Instead of keep adding more arguments to re-run command, I was
thinking we can merge -actions, -date, -status into one option -filter. We can
still expose these in CLI and OozieClient for backward compatibility. But
internally, all these can map to just one argument 'filter' at the client side
and pass just this to the server. Or we can merge this in server as well, if
some users use REST APIs directly.
> Rerun all Failed/killed/timedout coordinator actions rather than specifying
> action numbers
> ------------------------------------------------------------------------------------------
>
> Key: OOZIE-2020
> URL: https://issues.apache.org/jira/browse/OOZIE-2020
> Project: Oozie
> Issue Type: New Feature
> Components: action
> Reporter: Sreedish P S
> Assignee: Narayan Periwal
> Priority: Minor
> Attachments: OOZIE-2020-v10.patch, OOZIE-2020-v11.patch,
> OOZIE-2020-v12.patch, OOZIE-2020-v13.patch, OOZIE-2020-v14.patch,
> OOZIE-2020-v15.patch, OOZIE-2020-v16.patch, OOZIE-2020-v17.patch,
> OOZIE-2020-v8.patch, OOZIE-2020-v9.patch
>
>
> Currently rerun of coordinator actions are made through coordinator id and
> action numbers, this feature request is for rerunning all coordinator actions
> by mentioning a particular state
> for example :
> oozie job -rerun coord-id -state killed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
