[
https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052030#comment-15052030
]
Li Lu commented on YARN-4224:
-----------------------------
OK I've got a few references for the discussion. I looked at the WebHDFS REST
APIs but the use case there is not quite similar to our use case here. The RM
REST APIs mostly only have one mandatory parameter, such as
"/apps/{appid}/appattempt". AHS web services is probably the most similar use
case here, so we can borrow much of its resource model. For multiple parameters
we organize them as an ordered sequence, each one following their parameter
names, such as
"/apps/{appid}/appattempts/{appattemptid}/containers/{containerid}". Any APIs
that do not end on a parameter (such as "/apps/{appid}/appattempts") is treated
as a list. This appears to be the typical resource model in YARN. The MapReduce
AMWebService is another example for this.
Another thing is, for special queries like flowapps, we can add them as short
cuts on the flow level, such as
"/cluster/{clusterid}/user/{userid}/flow/{flowid}/apps".
Could somebody please remind me why we decide to remove user from the path?
Thanks!
> Change the ATSv2 reader side REST interface to conform to current REST APIs'
> in YARN
> ------------------------------------------------------------------------------------
>
> Key: YARN-4224
> URL: https://issues.apache.org/jira/browse/YARN-4224
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Varun Saxena
> Assignee: Varun Saxena
> Attachments: YARN-4224-YARN-2928.01.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
