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

Varun Saxena commented on YARN-4224:
------------------------------------

Coming to [~gtCarrera9]'s points,
bq.  Therefore, for applications, other than accessing through the hierarchical 
cluster, user, flow, flowrun order, we can directly access applications through 
/apps/appid. This will also help us to integrate with other YARN components. 
The key difference here is that, for YARN applications, their app id is 
actually an UID.
Yes appid can uniquely identify an app within a cluster.
For ATSv2 though we plan to host data from multiple clusters as well. So  a 
query might originate from different clusters. On the reader side, we take the 
cluster id from config if none is supplied. 
Consider we have 2 clusters but a single ATS reader. The use case for CLI is 
that it falls back on ATS if app is not found in RM. Now if our query from CLI 
does not contain cluster id the cluster timeline reader belongs to will be 
taken(from config). But ideally behavior should be same no matter which cluster 
we query from.
So we can probably have cluster id as an optional query param here. CLI can 
read it from config. Can Ember UI do however ?

bq. If there is an UID for each entity, why do we need to add entity type as 
one more layer of ID? 
We would not require it for entity endpoint but for entities endpoint.
When we return app, we cant include entity type in UID(for entities query) as 
for a generic entitiy, entity type can be anything.

bq. If we'd like to query YARN_CONTAINER entities for a given application, 
maybe we'd prefer to support this in a query like: 
"/entities?type=YARN_CONTAINER&appid=my_app_id"?
We normally keep mandatory parameters in the path for REST.
Entity type and appid are mandatory parameters to make entities query, so it is 
preferable to have them in the path.

> 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
>              Labels: yarn-2928-1st-milestone
>         Attachments: YARN-4224-YARN-2928.01.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to