hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10234) "hadoop.cmd jar" does not propagate exit code.
Date Wed, 15 Jan 2014 05:43:20 GMT

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

Chris Nauroth commented on HADOOP-10234:

bq. -1 tests included. The patch doesn't appear to include any new or modified tests.

This patch covered just a script file, so there wasn't a way to add a test.  We've confirmed
that this patch fixes the Hive test failure that made us notice the problem.

I'll commit this.

> "hadoop.cmd jar" does not propagate exit code.
> ----------------------------------------------
>                 Key: HADOOP-10234
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10234
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 2.2.0
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>             Fix For: 2.3.0
>         Attachments: HADOOP-10234.1.patch
> Running "hadoop.cmd jar" does not always propagate the exit code to the caller.  In interactive
use, it works fine.  However, in some usages (notably Hive), it gets called through {{Shell#getRunScriptCommand}},
which needs to do an intermediate "cmd /c" to execute the script.  In that case, the last
exit code is getting dropped, so Hive can't detect job failures.

This message was sent by Atlassian JIRA

View raw message