Thanks David - chaining them with %3B (';') works!
This sort of information is not available in the Oozie Web Services
documentation:
https://oozie.apache.org/docs/3.1.3-incubating/WebServicesAPI.html
It would be very helpful to have it there.
-Michael
On Mon, Mar 24, 2014 at 4:37 PM, David Morel <[email protected]>wrote:
> On 24 Mar 2014, at 21:12, [email protected] wrote:
>
> Thanks, David. I've been testing them with Groovy code and that is
>> working
>> well.
>>
>> I've hit a new snag with the REST API I'm hoping someone can help with:
>> is
>> it possible to chain multiple filters in one REST call?
>>
>> For example -
>>
>> If I query:
>> http://myserver:11000/oozie/v1/jobs?jobtype=coord&filter=user%3Dmyuser
>> I get 51 results.
>>
>>
>> If I query:
>> http://myserver:11000/oozie/v1/jobs?jobtype=coord&filter=name%3Dcoord-abc
>> I get 5 results.
>>
>>
>> If I put them together with the user filter first
>> http://myserver:11000/oozie/v1/jobs?jobtype=coord&filter=
>> user%3Dmyuser&filter=name%3Dcoord-abc
>> I get 51 results
>>
>>
>> If I put them together with the name filter first:
>> http://myserver:11000/oozie/v1/jobs?jobtype=coord&filter=
>> name%3Dcoord-abc&filter=user%3Dmyuser
>> I get 5 results.
>>
>>
>> If I put them together with the name filter first and a non-existent user
>> http://myserver:11000/oozie/v1/jobs?jobtype=coord&filter=
>> name%3Dcoord-abc&filter=user%3Dnobodythere
>> I get 5 results.
>>
>>
>> So the second filter is *completely ignored*. *Is there a way to set two
>> or more filters on one REST query?*
>>
>
> try this:
>
> http://myserver:11000/oozie/v1/jobs?jobtype=coord&filter=
> name%3Dcoord-abc%3Buser%3Dnobodythere
>
> david
>
