[jira] Commented: (HBASE-2030) HBase RPC Server stringifies stack trace as exception message; pollutes client-side notion of message vs stacktrace

[stack (JIRA)]

    [ 
https://issues.apache.org/jira/browse/HBASE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787101#action_12787101
 ] 

stack commented on HBASE-2030:
------------------------------

See v3 and v4 of the patches over in hbase-2029 where Lars changes what the 
server sends for a start on this issue.

{code}
Index: src/java/org/apache/hadoop/hbase/ipc/HBaseServer.java
===================================================================
--- src/java/org/apache/hadoop/hbase/ipc/HBaseServer.java       (revision 
887156)
+++ src/java/org/apache/hadoop/hbase/ipc/HBaseServer.java       (working copy)
@@ -916,7 +916,7 @@
           } catch (Throwable e) {
             LOG.info(getName()+", call "+call+": error: " + e, e);
             errorClass = e.getClass().getName();
-            error = StringUtils.stringifyException(e);
+            error = e.getLocalizedMessage();
           }
           UserGroupInformation.setCurrentUser(previous);
           CurCall.set(null);

{code}

> HBase RPC Server stringifies stack trace as exception message; pollutes 
> client-side notion of message vs stacktrace
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-2030
>                 URL: https://issues.apache.org/jira/browse/HBASE-2030
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>
> See hbase-2029 for context.  Shows in the shell in particular.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.