[
https://issues.apache.org/jira/browse/HADOOP-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated HADOOP-8661:
----------------------------------------
Description: 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. (was: It looks like all exceptions produced by
RemoteException include the full stack trace of the original exception in the
message. This is causing issues for oozie because they store the message in
their database and it is getting very large. This appears to be a regression
from 1.0 behavior.)
Priority: Major (was: Critical)
Target Version/s: 2.2.0-alpha (was: 0.23.3)
Issue Type: Improvement (was: Bug)
Summary: RemoteException's Stack Trace would be better returned by
getStackTrace (was: Stack Trace in Exception.getMessage causing oozie DB to
have issues)
OOZIE-946 was just closed as invalid, because the data is stored in a blob not
a varchar. I am changing this over to be an improvement, dropping the
severity, and renaming the JIRA. Sorry for causing others issues by filing a
JIRA as a bug before totally understanding the issue. I am also updating the
target to 2.2 as 0.23 is closed to new work.
> 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
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Attachments: 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 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
