You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Mona Chitnis (JIRA)" <ji...@apache.org> on 2014/03/17 18:53:42 UTC

[jira] [Commented] (OOZIE-1704) Add ability to use Bulk API with bundle ID

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

Mona Chitnis commented on OOZIE-1704:
-------------------------------------

Current patch breaks backward compatibility due to change of param name. Will upload new patch today to retain old param name and use logic to determine whether value is job ID or app name

> Add ability to use Bulk API with bundle ID
> ------------------------------------------
>
>                 Key: OOZIE-1704
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1704
>             Project: Oozie
>          Issue Type: Sub-task
>          Components: bundle
>    Affects Versions: trunk
>            Reporter: Mona Chitnis
>            Assignee: Mona Chitnis
>             Fix For: trunk
>
>
> Usage of this bulk API currently is
> oozie bulk -bundleName="abc" [-filters...]
> And it has a fail-fast strategy if more than one bundle ID correspond to same bundle name. However, in testing, this is a very common scenario and so we should extend API to accept bundle ID too
> At the same time, added the ability to mention coordinator IDs in addition to only appNames.
> therefore API params changed from bundle=a,b,c;coordinators=x,y,z to bundleName= or bundleId= and coordName= or coordId=.. Every param is case insensitive



--
This message was sent by Atlassian JIRA
(v6.2#6252)