You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Rohith Sharma K S (Jira)" <ji...@apache.org> on 2019/08/30 06:40:00 UTC

[jira] [Assigned] (YARN-6058) Support for listing all applications i.e /apps

     [ https://issues.apache.org/jira/browse/YARN-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rohith Sharma K S reassigned YARN-6058:
---------------------------------------

    Assignee:     (was: Rohith Sharma K S)

> Support for listing all applications i.e /apps
> ----------------------------------------------
>
>                 Key: YARN-6058
>                 URL: https://issues.apache.org/jira/browse/YARN-6058
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelinereader
>            Reporter: Rohith Sharma K S
>            Priority: Critical
>
> Primary use case for /apps is many execution engines runs on top of YARN example, Tez, MR. These engines will have their own UI's which list specific type of entities which are published by them Ex: DAG entities. 
> But, these UI's do not aware of either userName or flowName or applicationId which are submitted by these engines.
> Currently, given that user do not aware of user, flownName, and applicationId, then he can not retrieve any entities. 
> By supporting /apps with filters, user can list of application with given ApplicationType. These applications can be used for retrieving engine specific entities like DAG. 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org