Varun Saxena commented on YARN-3864:

bq. At some point, let's take a look at the REST API (as discussed earlier), 
and see if we need to make them more consistent with the overall REST best 
practices and more importantly hadoop's REST style (YARN, etc.). It's not 
terribly urgent, and we just need to review it some time soon.
We can do so. For user facing APIs' the form and the naming is very important. 
Everyone can chime in on this one.

bq. storing user in the app-to-flow table
Even I was wondering why its not there. In FS implementation, it was kept in 
the mapping.
I think this should be fixed. Should I raise a new JIRA for this and fix it ?

bq. I propose that we store the user id in the app-to-flow table, and when we 
recover the context on the read path, we use that user if the user is not 
provided by the caller.
But for certain queries such as querying flows and flowruns or all apps for a 
flow/flow run, we will not have context information. Because context is for 
cluster and app. And for these queries, a single app has no meaning. I think 
for these queries, we can take UGI and for others take it from context. But 
this can make it confusing for user. So one option is to disregard UGI 
altogether and force user to be supplied for queries for which context cant be 

> 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, 
> YARN-3864-YARN-2928.02.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

Reply via email to