You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Tsz Wo (Nicholas), SZE (Updated) (JIRA)" <ji...@apache.org> on 2012/02/27 20:40:46 UTC
[jira] [Updated] (HADOOP-7897) ProtobufRPCEngine client side
exception mechanism is not consistent with WritableRpcEngine
[ https://issues.apache.org/jira/browse/HADOOP-7897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo (Nicholas), SZE updated HADOOP-7897:
-------------------------------------------
Component/s: ipc
Fix Version/s: 0.23.3
I have merged this to 0.23.
> ProtobufRPCEngine client side exception mechanism is not consistent with WritableRpcEngine
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-7897
> URL: https://issues.apache.org/jira/browse/HADOOP-7897
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.24.0
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Fix For: 0.24.0, 0.23.3
>
> Attachments: HADOOP-7897.txt, HADOOP-7897.txt
>
>
> In ProtobufRpcEngine the client side exceptions are wrapped in RpcClientException. The RpcClientException is used to create RemoteException which is set as cause in the thrown ServiceException. However WritableRpcEngine throws the client encountered exception as is. This difference in behavior causes, many tests to fail in the existing unit tests, which expect the client invoker() to thrown the exception as is. This jira makes the ProtobufRpcEngine behavior consistent with that of WritableRpcEngine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira