hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5201) getDiagnostics in TaskReport should return exceptions
Date Wed, 18 Mar 2009 15:19:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683041#action_12683041
] 

Steve Loughran commented on HADOOP-5201:
----------------------------------------

Santhosh, are you trying to read the results in and create a new exception at the far end?
Does it get thrown? 

I've started a basic writable exception, but not looked at the back-convert to an exception.
It's pretty hard to do this well, and I wouldn't attempt to try and create new exceptions
of the same classname as before, instead they'd be some wrapper exception that would be trickier
to work with. This is the only way to reliably send failures back over the wire without requiring
everyone a both ends to have the same set of JARs, all in perfect sync.

> 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.


Mime
View raw message