Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <6413765.1156271234828.JavaMail.jira@brutus>
Date: Tue, 22 Aug 2006 11:27:14 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-472) Streaming should not crash
In-Reply-To: <12816750.1156263013893.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/HADOOP-472?page=comments#action_12429777 ] 
            
Doug Cutting commented on HADOOP-472:
-------------------------------------

Is it the stack trace that bothers you?  If you want just a single message, then we could replace the stack trace with the exception name and its message.  If you find particular exception messages confusing, then we should fix things so that a more informative exception is thrown, rather than try to translate the messages to something more informative.

> 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