You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Abhishek Kapoor (JIRA)" <ji...@apache.org> on 2013/03/07 07:54:13 UTC
[jira] [Commented] (YARN-69) RM should throw different exceptions
for while querying app/node/queue
[ https://issues.apache.org/jira/browse/YARN-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595615#comment-13595615 ]
Abhishek Kapoor commented on YARN-69:
-------------------------------------
+1
As discribed about, this will require protocol amendment
> RM should throw different exceptions for while querying app/node/queue
> ----------------------------------------------------------------------
>
> Key: YARN-69
> URL: https://issues.apache.org/jira/browse/YARN-69
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> We should distinguish the exceptions for absent app/node/queue, illegally accessed app/node/queue etc. Today everything is a {{YarnRemoteException}}. We should extend {{YarnRemoteException}} to add {{NotFoundException}}, {{AccessControlException}} etc. Today, {{AccessControlException}} exists but not as part of the protocol descriptions (i.e. only available to Java).
--
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