[
https://issues.apache.org/jira/browse/YARN-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030428#comment-16030428
]
Giovanni Matteo Fumarola commented on YARN-6634:
------------------------------------------------
In patch v4 I added all the missing javadoc.
I noticed that in RMWebServices most of the methods had a wrong throws in the
signature.
Few examples:
* getNodes throws a NotFoundException and it was not defined;
* getAppState throws a NotFoundException and it was AuthorizationException;
* getNodeToLabels does not throws any exception and it was IOException;
[~leftnoteasy]/[~subru] can you please a look?
> [API] Define an API for ResourceManager WebServices
> ---------------------------------------------------
>
> Key: YARN-6634
> URL: https://issues.apache.org/jira/browse/YARN-6634
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
> Affects Versions: 2.8.0
> Reporter: Subru Krishnan
> Assignee: Giovanni Matteo Fumarola
> Priority: Critical
> Attachments: YARN-6634.proto.patch, YARN-6634.v1.patch,
> YARN-6634.v2.patch, YARN-6634.v3.patch, YARN-6634.v4.patch
>
>
> The RM exposes few REST queries but there's no clear API interface defined.
> This makes it painful to build either clients or extension components like
> Router (YARN-5412) that expose REST interfaces themselves. This jira proposes
> adding a RM WebServices protocol similar to the one we have for RPC, i.e.
> {{ApplicationClientProtocol}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
