Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <29482352.1165577602273.JavaMail.jira@brutus>
Date: Fri, 8 Dec 2006 03:33:22 -0800 (PST)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
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

     [ http://issues.apache.org/jira/browse/HADOOP-808?page=all ]

Arun C Murthy updated HADOOP-808:
---------------------------------

               Status: Patch Available  (was: Open)
        Fix Version/s: 0.10.0
    Affects Version/s: 0.9.1

> 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