[
https://issues.apache.org/jira/browse/HADOOP-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683418#action_12683418
]
Steve Loughran commented on HADOOP-5201:
----------------------------------------
wow, that is a pretty complex bit of reverse-exception parsing. I will put the
needs of your code back in to HADOOP-5348
-you want to get the full stack trace details as StackTraceElements
-you use error codes.
Error codes are good for letting code identifying problems without having a
vast tree of classes, but there is the risk that you are on the slippery
SoapFault road, which started off with an error code and a client/server bit
and ended up with a whole chain of user agents. What may be useful is to allow
a serializable exception to include a Map<String,String> into which code can
add facts (hostname, error code), giving you a class that is extensible when
needed, but still easily deserialized.
> getDiagnostics in TaskReport should return exceptions
> -----------------------------------------------------
>
> Key: HADOOP-5201
> URL: https://issues.apache.org/jira/browse/HADOOP-5201
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Santhosh Srinivasan
>
> Currently, getDiagnostics() returns Strings. When exceptions are thrown in
> user code and/or Hadoop, it would be cleaner to propagate the exception back
> to the application for better error handling. Hadoop should return the
> exceptions instead of returning string representations that correspond to
> printStackTrace() output.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
