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

Hudson commented on HADOOP-7897:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #1404 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1404/])
    HADOOP-7897. ProtobufRpcEngine client side exception mechanism is not 
consistent with WritableRpcEngine. Contributed by Suresh Srinivas.

suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1212004
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/ProtobufHelper.java
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/ProtobufRpcEngine.java

                
> 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
>    Affects Versions: 0.24.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 0.24.0
>
>         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

        

Reply via email to