Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 81912 invoked from network); 12 Dec 2006 21:42:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Dec 2006 21:42:44 -0000 Received: (qmail 97395 invoked by uid 500); 12 Dec 2006 21:42:51 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 97371 invoked by uid 500); 12 Dec 2006 21:42:51 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 97362 invoked by uid 99); 12 Dec 2006 21:42:51 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Dec 2006 13:42:51 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Dec 2006 13:42:42 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 55AF971413F for ; Tue, 12 Dec 2006 13:42:22 -0800 (PST) Message-ID: <24275229.1165959742348.JavaMail.jira@brutus> Date: Tue, 12 Dec 2006 13:42:22 -0800 (PST) From: "Doug Cutting (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Updated: (HADOOP-808) Enhance 'bin/hadoop job -submit <>' In-Reply-To: <8517460.1165576881049.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/HADOOP-808?page=all ] Doug Cutting updated HADOOP-808: -------------------------------- Status: Open (was: Patch Available) If someone's going to write a main() like method, why couldn't they simply write a main() that submits the job? I don't see what this simplifies. > Enhance 'bin/hadoop job -submit <>' > ----------------------------------- > > Key: HADOOP-808 > URL: http://issues.apache.org/jira/browse/HADOOP-808 > Project: Hadoop > Issue Type: Improvement > Components: mapred > Affects Versions: 0.9.1 > Reporter: Arun C Murthy > Assigned To: Arun C Murthy > Priority: Minor > Fix For: 0.10.0 > > Attachments: HADOOP-808_1_20061208.patch, myjob.tgz > > > Today 'bin/hadoop job -submit' takes a config file and just does a JobClient.submitJob(jobConf), this isn't flexible enough for cases where the user wants to submit a job which calls his main(), does some work and then calls 'JobClient.runJob', I propose we enhance this subcommand to handle that scenario. This could be really useful for the time we decide to setup a simple webpage with 'form' where the user uploads a job.xml & job.jar and we can fire the job. -- 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