Sangjin Lee commented on YARN-3864:

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 ?

Yes, let's open a new JIRA. I can get to this next week, or you can take it on 
if you prefer. Let me know. I'm fine either way. For the record, I don't think 
this needs to be done by the POC time. The same goes for the REST API review.

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 

Yes, I'm specifically talking about the existing app-to-flow lookup case which 
applies only to generic entities and apps. Sorry if it was not clear. I agree 
the flow run case is a little different. I do think the UGI is not very 
meaningful in that case either (if the caller user does not match the right 
user, it will return nothing anyway). I'm OK with making the user required.

> 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