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

Wangda Tan commented on YARN-4224:
----------------------------------

Hi [~varun_saxena],

For your last comment: 
bq. So I looked at Wangda Tan's code at YARN-3368. I see that for single record 
like a single app attempt, we are extending urlForFindRecord and that takes 
only a single string id as input instead of an object as is the case with 
urlForQuery. In case of app attempt and containers, we can get both appid from 
app attempt id, and app attempt from container so a single id would do.
That's the major reason why I asked to support flat namespace in REST API. Yes 
you're correct, front JS library could support multi layer hierarchy REST API, 
but it's very painful. We have to extend JS library to support it, and we need 
to keep context of objects (in your case we need username/cluster-id/flow-id 
when try to get flow related info). This is very painful from my experience on 
writing web UI.

bq. Moreover, what do you mean by batch query ? Does that mean support for 
multiple optional query parameters like filters etc. to trim down the results ? 
We already have them.
Not sure if it is possible to support queries like: give me flows which users 
satisfy a given regex, and begin/end time is from a range? Could you give me an 
example about what does the query look like?

In addition, I'm planning to propose adding flat namespace REST APIs to RM side 
as well (and keep existing REST APIs in RM unchanged for compatibility). For 
example, we should be able to get container with id 
{{/containers/\{container-id\}}} directly, instead of using existing 
hierarchical REST API. My goal is to make RM/ATSv2 have consistent REST API 
view.

Thoughts?


> Change the ATSv2 reader side REST interface to conform to current REST APIs' 
> in YARN
> ------------------------------------------------------------------------------------
>
>                 Key: YARN-4224
>                 URL: https://issues.apache.org/jira/browse/YARN-4224
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>         Attachments: YARN-4224-YARN-2928.01.patch
>
>




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

Reply via email to