hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8661) RemoteException's Stack Trace would be better returned by getStackTrace
Date Mon, 11 Sep 2017 05:17:01 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Junping Du updated HADOOP-8661:
-------------------------------
    Target Version/s: 2.8.3  (was: 2.8.1)

> RemoteException's Stack Trace would be better returned by getStackTrace
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-8661
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8661
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 0.23.3, 2.0.0-alpha, 3.0.0-alpha1
>            Reporter: Robert Joseph Evans
>              Labels: BB2015-05-TBR
>         Attachments: HADOOP-8661.txt, HADOOP-8661.txt, HADOOP-8661.txt
>
>
> It looks like all exceptions produced by RemoteException include the full stack trace
of the original exception in the message.  This is different from 1.0 behavior to aid in debugging,
but it would be nice to actually parse the stack trace and return it through getStackTrace
instead of through getMessage.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message