Return-Path: 
 <mapreduce-issues-return-62727-apmail-hadoop-mapreduce-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id F003DC5BB
	for <apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org>;
 Wed, 17 Jul 2013 10:55:08 +0000 (UTC)
Received: (qmail 60209 invoked by uid 500); 17 Jul 2013 10:55:07 -0000
Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org
Received: (qmail 60112 invoked by uid 500); 17 Jul 2013 10:55:07 -0000
Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:mapreduce-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:mapreduce-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:mapreduce-issues@hadoop.apache.org>
List-Id: <mapreduce-issues.hadoop.apache.org>
Reply-To: mapreduce-issues@hadoop.apache.org
Delivered-To: mailing list mapreduce-issues@hadoop.apache.org
Received: (qmail 59962 invoked by uid 99); 17 Jul 2013 10:55:07 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jul 2013 10:55:07 +0000
Date: Wed, 17 Jul 2013 10:55:07 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12657156.1373495104782.64929.1374058507184@arcas>
In-Reply-To: <JIRA.12657156.1373495104782@arcas>
References: <JIRA.12657156.1373495104782@arcas>
Subject: [jira] [Commented] (MAPREDUCE-5380) Invalid mapred command should
 return non-zero exit code
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/MAPREDUCE-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710962#comment-13710962 ] 

Hudson commented on MAPREDUCE-5380:
-----------------------------------

SUCCESS: Integrated in Hadoop-Yarn-trunk #273 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/273/])
MAPREDUCE-5380. Invalid mapred command should return non-zero exit code. Contributed by Stephen Chu (jlowe: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1503957)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/bin/mapred

                
> Invalid mapred command should return non-zero exit code
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-5380
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5380
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 2.0.4-alpha
>            Reporter: Stephen Chu
>            Assignee: Stephen Chu
>             Fix For: 3.0.0, 2.3.0, 0.23.10
>
>         Attachments: MAPREDUCE-5380.patch, MAPREDUCE-5380.patch
>
>
> Running the mapred bin script with an invalid command returns exit code 0, but it should return a non-zero exit code.
> {code}
> [schu@hdfs-snapshots-1 ~]$ hadoop-3.0.0-SNAPSHOT/bin/mapred gibberish
> gibberish - invalid command
> Usage: mapred [--config confdir] COMMAND
>        where COMMAND is one of:
>   pipes                run a Pipes job
>   job                  manipulate MapReduce jobs
>   queue                get information regarding JobQueues
>   classpath            prints the class path needed for running
>                        mapreduce subcommands
>   historyserver        run job history servers as a standalone daemon
>   distcp <srcurl> <desturl> copy file or directories recursively
>   archive -archiveName NAME -p <parent path> <src>* <dest> create a hadoop archive
> Most commands print help when invoked w/o parameters.
> [schu@hdfs-snapshots-1 ~]$ echo $?
> 0
> [schu@hdfs-snapshots-1 ~]$ 
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira