[ 
https://issues.apache.org/jira/browse/YARN-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041583#comment-16041583
 ] 

Carlo Curino commented on YARN-6634:
------------------------------------

[~giovanni.fumarola], thanks for the contribution. I have committed it to 
trunk. I tried to cheerry-pick back into branch-2 but the patch does not apply 
cleanly. Can you look into it and provide a version that works for branch-2? 

> [API] Refactor ResourceManager WebServices to make API explicit
> ---------------------------------------------------------------
>
>                 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, 
> YARN-6634.v5.patch, YARN-6634.v6.patch, YARN-6634.v7.patch, 
> YARN-6634.v8.patch, YARN-6634.v9.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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to