Varun Saxena commented on YARN-4224:

bq. So the UID in /entities/{entitytype}/{uid}/ is actually app UID? This make 
the whole endpoint looks really weird... I thought it's an entity UID to locate 
to one timeline entity. However, I think you raised a very useful use case to 
query a certain type of entity for one application. Maybe we'd like to change 
the format of this endpoint to address this case? I don't really feel like the 
current form of the endpoint...
When I had written the code,I was assuming delimiter wont be public so UID has 
to madatorily go from server. And we cant append entity type there.
As we have reached consensus on making delimiter public, UI can actually append 
the entity type in front of UID. But this will have to be a special case for 
entities endpoint.

bq. So to find one entity with cluster, user, flow, flowrun, appid and entity 
id, we do not have the hierarchical endpoint, but can only get an entity 
through the UID interface? Do we need the hierarchical interface for CLIs?
Not really. In case of hierarchical endpoint, flow context information can be 
supplied as part of optional query parameters. This would preclude the need of 
query flow context.
But for hierarchical queries we envisage direct queries too rather than only 
flows->flowruns->apps->entities sequence when query via UID. But now as 
delimiter can be public, UID endpoint can also have a direct query potentially. 
So can have similar structure as for hierarchical query. 

I think we can discuss all these points in detail in today's call.

> 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, 
> YARN-4224-feature-YARN-2928.wip.02.patch

This message was sent by Atlassian JIRA

Reply via email to