hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-808) Enhance 'bin/hadoop job -submit <>'
Date Tue, 12 Dec 2006 21:42:22 GMT
     [ 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


View raw message