[
https://issues.apache.org/jira/browse/OOZIE-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mona Chitnis updated OOZIE-1704:
--------------------------------
Description:
Usage of this bulk API currently is
oozie bulk -bundle="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 the API will now accept either job-id or appname:
e.g.
bundle=0000-1234-B;coordinators=my-coord-name1,my-coord-name2
OR
bundle=my-bundle-name1,my-bundle-name2;coordinators=0000-23434-C
OR both appnames or both ids
was:
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
> 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
>
> Attachments: OOZIE-1704-3.patch
>
>
> Usage of this bulk API currently is
> oozie bulk -bundle="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 the API will now accept either job-id or appname:
> e.g.
> bundle=0000-1234-B;coordinators=my-coord-name1,my-coord-name2
> OR
> bundle=my-bundle-name1,my-bundle-name2;coordinators=0000-23434-C
> OR both appnames or both ids
--
This message was sent by Atlassian JIRA
(v6.2#6252)
