You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Christian Kunz (JIRA)" <ji...@apache.org> on 2009/06/13 07:07:07 UTC

[jira] Updated: (HADOOP-6030) hadoop jar and hadoop/mapred pipes might return exit code 0 even when failing

     [ https://issues.apache.org/jira/browse/HADOOP-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Kunz updated HADOOP-6030:
-----------------------------------

    Component/s: mapred

> hadoop jar and hadoop/mapred pipes might return exit code 0 even when failing
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6030
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6030
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Christian Kunz
>
> up to  hadoop 0.18.3 org.apache.hadoop.mapred.JobShell ensured that 'hadoop jar' returns non-zero exit code when the job fails.
> This is no longer true after moving this to org.apache.hadoop.util.RunJar.
> Pipes jobs submitted through cli never returned proper exit code.
> The main methods in org.apache.hadoop.util.RunJar. and org.apache.hadoop.mapred.pipes.Submitter should be modified to return an exit code similar to how org.apache.hadoop.mapred.JobShell did it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.