[
https://issues.apache.org/jira/browse/HADOOP-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672443#action_12672443
]
Steve Loughran commented on HADOOP-5201:
----------------------------------------
we could make it a list of DiagnosticEvents, which could be simple strings or a
fully recursively marshalled exception trace; other events (with toString()
methods) could be added later?
Looking at how I handle failures, I do print this out; no attempt is made to
understand the text:
{code}
if (event.getTaskStatus() !=
TaskCompletionEvent.Status.SUCCEEDED) {
String[] diagnostics =
runningJob.getTaskDiagnostics(event.getTaskAttemptId());
for (String line : diagnostics) {
builder.append("\n ");
builder.append(line);
}
}
{code}
> 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.
