Rohith Sharma K S commented on YARN-5739:

Thanks Li Lu for raising a JIRA. This is one of the many folks major concern(I 
missed too in meetings) while I was briefing about REST end points available in 
ATSv2. They are expecting somewhat like REST end point like 

One option would be maintaining separate mapping table 
application->list-of-all-entites. If we scan entity table then it is required 
to filter it out by reader since it scans all the application/ row-keys. May be 
need to discuss more on this supporting this API and its solutions.

> Provide timeline reader API to list available timeline entity types for one 
> application
> ---------------------------------------------------------------------------------------
>                 Key: YARN-5739
>                 URL: https://issues.apache.org/jira/browse/YARN-5739
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelinereader
>            Reporter: Li Lu
>            Assignee: Li Lu
> Right now we only show a part of available timeline entity data in the new 
> YARN UI. However, some data (especially library specific data) are not 
> possible to be queried out by the web UI. It will be appealing for the UI to 
> provide an "entity browser" for each YARN application. Actually, simply 
> dumping out available timeline entities (with proper pagination, of course) 
> would be pretty helpful for UI users. 
> On timeline side, we're not far away from this goal. Right now I believe the 
> only thing missing is to list all available entity types within one 
> application. The challenge here is that we're not storing this data for each 
> application, but given this kind of call is relatively rare (compare to 
> writes and updates) we can perform some scanning during the read time. 

This message was sent by Atlassian JIRA

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