Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5ED831051C for ; Mon, 9 Mar 2015 22:53:42 +0000 (UTC) Received: (qmail 21952 invoked by uid 500); 9 Mar 2015 22:53:39 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 21696 invoked by uid 500); 9 Mar 2015 22:53:39 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 21644 invoked by uid 99); 9 Mar 2015 22:53:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Mar 2015 22:53:39 +0000 Date: Mon, 9 Mar 2015 22:53:39 +0000 (UTC) From: "Allen Wittenauer (JIRA)" To: common-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HADOOP-7220) documentation lists options in wrong order 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/HADOOP-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-7220. -------------------------------------- Resolution: Won't Fix stale > documentation lists options in wrong order > ------------------------------------------ > > Key: HADOOP-7220 > URL: https://issues.apache.org/jira/browse/HADOOP-7220 > Project: Hadoop Common > Issue Type: Bug > Reporter: Dieter Plaetinck > Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > On http://hadoop.apache.org/common/docs/r0.20.2/streaming.html various example use -D flags. > I noticed if you invoke hadoop this way, it won't work. > ======================== > dplaetin@n-0:/usr/local/hadoop/bin$ ./hadoop jar /usr/local/hadoop/contrib/streaming/hadoop-0.20.2-streaming.jar -file /proj/Search/wall/experiment/ -mapper './build-models.py --mapper' -reducer './build-models.py --reducer' -input sim-input -output sim-output -D mapred.output.key.comparator.class=org.apache.hadoop.mapred.lib.KeyFieldBasedComparator -D mapred.text.key.comparator.options=-k1,2n > 11/04/12 10:39:28 ERROR streaming.StreamJob: Unrecognized option: -D > Usage: $HADOOP_HOME/bin/hadoop jar \ > $HADOOP_HOME/hadoop-streaming.jar [options] > Options: > -input DFS input file(s) for the Map step > -output DFS output directory for the Reduce step > -mapper The streaming command to run > -combiner Combiner has to be a Java class > -reducer The streaming command to run > -file File/dir to be shipped in the Job jar file > -inputformat TextInputFormat(default)|SequenceFileAsTextInputFormat|JavaClassName Optional. > -outputformat TextOutputFormat(default)|JavaClassName Optional. > -partitioner JavaClassName Optional. > -numReduceTasks Optional. > -inputreader Optional. > -cmdenv = Optional. Pass env.var to streaming commands > -mapdebug Optional. To run this script when a map task fails > -reducedebug Optional. To run this script when a reduce task fails > -verbose > Generic options supported are > -conf specify an application configuration file > -D use value for given property > -fs specify a namenode > -jt specify a job tracker > -files specify comma separated files to be copied to the map reduce cluster > -libjars specify comma separated jar files to include in the classpath. > -archives specify comma separated archives to be unarchived on the compute machines. > The general command line syntax is > bin/hadoop command [genericOptions] [commandOptions] > For more details about these options: > Use $HADOOP_HOME/bin/hadoop jar build/hadoop-streaming.jar -info > Streaming Job Failed! > ======================== > I could only make it work by moving the '-D flags to the front' (right after the streaming.jar part). maybe because it's a generic option, it needs to be in front or something. -- This message was sent by Atlassian JIRA (v6.3.4#6332)