[
https://issues.apache.org/jira/browse/HADOOP-9343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591033#comment-13591033
]
Suresh Srinivas commented on HADOOP-9343:
-----------------------------------------
+1 for the patch.
As regards to returning error codes, the RPC layer currently returns:
- Reply status - (success, error, fatal)
- exception name - which could be treated as an error name or translated to
error ID
- exception stack trace - details related to error
Implementation that have awareness of exception could use the above
information. If not, it can be translated to suitable error code returns, right?
> Allow additional exceptions through the RPC layer
> -------------------------------------------------
>
> Key: HADOOP-9343
> URL: https://issues.apache.org/jira/browse/HADOOP-9343
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.0.3-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: HADOOP-9343_2.txt, HADOOP-9343.txt
>
>
> The RPC layer currently only allows IOException, RuntimeException,
> InterruptedException and their derivatives - which limits exceptions declared
> by protocols.
> Other exceptions end up at the client as an UndeclaredThrowableException
> wrapped in RemoteException.
> Additional exception types should be allowed.
--
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
