hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4224) Change the ATSv2 reader side REST interface to conform to current REST APIs' in YARN
Date Mon, 14 Dec 2015 16:14:46 GMT

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

Varun Saxena commented on YARN-4224:
------------------------------------

So I looked at [~leftnoteasy]'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.
In our case no such relationship exists between cluster, user, flow, etc. Is this why we need
UID ? And we want to fetch it from server side so that UID encoding can be easily changed
in future ? Is my understanding correct ?

By the way what are implications of calling query instead of findRecord ? I guess multiple
fields can be passed when we call urlForQuery.

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.

> 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)

Mime
View raw message