hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8661) RemoteException's Stack Trace would be better returned by getStackTrace
Date Sun, 30 Nov 2014 17:54:12 GMT

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

Steve Loughran updated HADOOP-8661:
-----------------------------------
    Target Version/s: 2.7.0  (was: 2.0.2-alpha)
              Status: Patch Available  (was: Open)

> 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: 2.0.0-alpha, 0.23.3, 3.0.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>         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.3.4#6332)

Mime
View raw message