hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "arkady borkovsky (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-472) Streaming should not crash
Date Thu, 24 Aug 2006 23:39:07 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-472?page=comments#action_12430336 ] 
arkady borkovsky commented on HADOOP-472:

Yoram suggested that this issue is split into several ones.

So let's keep this one for what it's heading says:

"Hadoop Streaming should not crash".

That is, Streaming client (hadoop-streaming.jar) should not complete with a stack trace. 
It should catch all exceptions and provide a human readable error message.
Common exceptions caused by common user mistakes should be explained by these messages.  

When a user tries to execute a Perl script and sees a Java stack trace, she immediately assumes
that the tools is broken.  
I have obsereved this ssepcifically trying to get people to use Streaming.

Unlike some other Hadoop components that are supposed to be used Java code, Streaming is a
user facing application.  This imposes different requirements on exception handling.

> Streaming should not crash
> --------------------------
>                 Key: HADOOP-472
>                 URL: http://issues.apache.org/jira/browse/HADOOP-472
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/streaming
>            Reporter: arkady borkovsky
> Streaming framework should not end with a Java stack dump.
> All the abnormal conditions should be checked and reported.
> Specific conditions that need to be exmplicitly checked by the framework are:
> -- does the input exist?
> -- do the top level executables or scripts for -mapper and exist
> Any other Exceptions should also be cought and explained in an error message.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message