Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 17 Jun 2013 18:25:20 +0000 (UTC)
From: "Omkar Vinit Joshi (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12652973.1371244916238.126849.1371493520574@arcas>
In-Reply-To: <JIRA.12652973.1371244916238@arcas>
References: <JIRA.12652973.1371244916238@arcas>
Subject: [jira] [Commented] (YARN-822) Rename ApplicationToken to AMRMToken
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Omkar Vinit Joshi commented on YARN-822:
----------------------------------------

yes I will... YARN-843
                
> Rename ApplicationToken to AMRMToken
> ------------------------------------
>
>                 Key: YARN-822
>                 URL: https://issues.apache.org/jira/browse/YARN-822
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Omkar Vinit Joshi
>            Assignee: Omkar Vinit Joshi
>         Attachments: YARN-822-20130617.patch
>
>
> API change. At present this token is getting used on scheduler api AMRMProtocol. Right now name wise it is little confusing as it might be useful for the application to talk to complete yarn system (RM/NM) but that is not the case after YARN-694. NM will have specific NMToken so it is better to name it as AMRMToken.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira