[
https://issues.apache.org/jira/browse/OOZIE-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1565:
---------------------------------
Attachment: OOZIE-1565.patch
The patch makes the {{V2JobServlet}} use the new behavior while
{{V1JobServlet}} uses the old behavior. This was really only a one line
change; I also updated {{TestV1JobServlet}} and {{TestV2JobServlet}} to match.
The client uses the v2 API, which already has the new behavior, so I didn't
have to change anything there.
> OOZIE-1481 should only affect v2 of the API, not v1
> ---------------------------------------------------
>
> Key: OOZIE-1565
> URL: https://issues.apache.org/jira/browse/OOZIE-1565
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Affects Versions: trunk, 4.0.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: trunk, 4.0.1
>
> Attachments: OOZIE-1565.patch
>
>
> OOZIE-1481 changed the behavior of the v1 API such that when getting coord
> info, specifying {{len=0}} now returns 0 actions instead of all actions.
> Also, on the REST call, not specifying any {{len}} parameter is interpreted
> by the Oozie server as {{len=0}}.
> This is a logically backwards incompatible change. We should keep this
> change in the v2 API, but change the v1 API back to the original (incorrect)
> behavior.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
