Li Lu commented on YARN-4224:

Thanks [~leftnoteasy]! I agree that we should separate the semantics and 
implementations. Our web UI, as one user of the REST API, does not really need 
general queries for timeline entities (I can always attach an entity type if 
needed). However, as from the API design perspective, I'd hope our API to be 
general enough. Having APIs like "list all entities within one application" may 
seems too ambitious for implementations, but something like "on this end point 
I assume you want all entities for this application, but to avoid crash myself 
I'm only returning a part of it" looks fine. However, enforcing an entity type 
to all such queries and add them as part of the end point looks a little bit 
suboptimal (it also changes the way we organize resources). 

> 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