Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 29 Dec 2015 20:49:49 +0000 (UTC)
From: "Wangda Tan (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12902409.1444047290000.24005.1451422189668@Atlassian.JIRA>
In-Reply-To: <JIRA.12902409.1444047290000@Atlassian.JIRA>
References: <JIRA.12902409.1444047290000@Atlassian.JIRA>
 <JIRA.12902409.1444047290070@arcas>
Subject: [jira] [Commented] (YARN-4224) Change the ATSv2 reader side REST
 interface to conform to current REST APIs' in YARN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Hi [~varun_saxena],

I would prefer to response UID to REST client from server. Yes, Ember could fetch more contexts to build UID, but additional efforts need to be done, and it might have to make additional REST calls to get full contexts. I think it's better to keep as less information stored in client as as possible.

Please let me know if it makes sense to you.

Thanks,

> 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
>              Labels: yarn-2928-1st-milestone
>         Attachments: YARN-4224-YARN-2928.01.patch, YARN-4224-feature-YARN-2928.wip.02.patch
>
>


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