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

Vrushali C commented on YARN-3864:
----------------------------------

Thanks [~varun_saxena]!
- For the /app endpoint, I think we need only the app id as the path param, 
none of the others are needed. For a given cluster, an application id will be 
unique. What do you think

- for the /apps endpoint, do you think we can call it flowApps or appsflow or 
something so that it is clear that we are querying for all applications in this 
particular in this endpoint. As such, later we may want to add/enhance an 
endpoint for apps such that we can return all apps for a given user or all apps 
in a given queue or some other criteria. For this endpoint in this jira, I 
believe we are considering only the applications in a given flow run.

- I think this endpoint should be also available without requiring the flow run 
id. For instance, if I want to see all the apps for a particular pig job (say 
default is last run), then I may not know the run id but I know only the pig 
job name. In that case, the reader should scan the applications table for that 
flow and return the latest run id's applications.



> Implement support for querying single app and all apps for a flow run
> ---------------------------------------------------------------------
>
>                 Key: YARN-3864
>                 URL: https://issues.apache.org/jira/browse/YARN-3864
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>            Priority: Blocker
>         Attachments: YARN-3864-YARN-2928.01.patch
>
>
> This JIRA will handle support for querying all apps for a flow run in HBase 
> reader implementation.
> And also REST API implementation for single app and multiple apps.



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

Reply via email to