[
https://issues.apache.org/jira/browse/HADOOP-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854281#action_12854281
]
Doug Cutting commented on HADOOP-6686:
--------------------------------------
This is definitely an improvement, but I wonder if it might be better yet if
RemoteException didn't include the exception name in its message. It might
include it in toString(), as is standard, but not in getMessage().
RemoteException has a field named "className" that already stores the remote
exception name. It also redundantly includes the exception name in the
exceptions message, since that's created from the value of
Throwable#printStackTrace(). Rather RemoteException might parseout just the
message (the first line, after the class name) and use that as its message and
separately store the remote stack trace in a field, like the class name. Then,
even if the exception is not unwrapped, its message and toString() would still
match that of the original exception.
> Remove redundant exception class name in unwrapped exceptions thrown at the
> RPC client
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-6686
> URL: https://issues.apache.org/jira/browse/HADOOP-6686
> Project: Hadoop Common
> Issue Type: Improvement
> Environment: At RPC client, when the exception thrown by the server
> is unwrapped, the exception message includes redundant exception class name.
> This redundant information should be removed.
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Fix For: 0.22.0
>
> Attachments: HADOOP-6686.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
