[jira] [Updated] (YARN-822) Rename ApplicationToken to AMRMToken

2013-06-17 Thread Omkar Vinit Joshi (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Omkar Vinit Joshi updated YARN-822:
---

Attachment: YARN-822-20130617.patch

Renaming TokenIdentifier, TokenSelector and SecretManager. Did grep on complete 
source code. 

 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


[jira] [Updated] (YARN-822) Rename ApplicationToken to AMRMToken

2013-06-16 Thread Omkar Vinit Joshi (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Omkar Vinit Joshi updated YARN-822:
---

Issue Type: Sub-task  (was: Bug)
Parent: YARN-386

 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

 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