[
https://issues.apache.org/jira/browse/OOZIE-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138244#comment-14138244
]
Robert Kanter commented on OOZIE-1676:
--------------------------------------
The problem with that is that the caller now has to know if Oozie HA is being
used or not. The v3 format is the same regardless of HA or how many servers
(and the v2 format remains unchanged). Even if we did something like
{{?format=new}}, isn't that really what the versions are for? This would also
be less consistent with how we updated other calls, like getting the logs,
where the user doesn't have to specify if they want all servers or not (the
returned format is the same, so we didn't have as big a problem for this
though).
If you're concern is putting v3 into Oozie 4.1 so quickly; I'm fine with
putting this into only trunk for now. But I think v3 is where this belongs.
Or what if we marked v3 as "evolving" or "unstable" (Hadoop uses annotations
like these on their classes) and made the Oozie client still use v2. Then we
could put this in v3 so it's available, but not guarantee any v3 backwards
compatibility until we're ready.
> Instrumentation and Configuration over the REST API and Web UI should include
> all Oozie servers
> -----------------------------------------------------------------------------------------------
>
> Key: OOZIE-1676
> URL: https://issues.apache.org/jira/browse/OOZIE-1676
> Project: Oozie
> Issue Type: Improvement
> Components: HA
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Minor
> Fix For: 4.1.0
>
> Attachments: OOZIE-1676.patch, OOZIE-1676.patch, OOZIE-1676.patch,
> OOZIE-1676.patch, screenshot.jpg, screenshot2.jpg
>
>
> This isn't that important, but it would be good if we updated the REST API
> and Web UI to return the instrumentation and configuration for each Oozie
> server when HA is being used. As it stands, each time you refresh the page
> (and are going through the load balancer), you'll get the
> instrumentation/configuration for a different server, which are not identical
> and there isn't really a way to tell which server they came from. This
> should be a new version of the REST API (v3) because it would change the
> return format to be an array of servers with their
> instrumentation/configuration info.
> The backend of this would have the contacted Oozie server simply ask each of
> the other Oozie servers for their instrumentation or configuration and
> combine them all (with the name of each server) into the response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
