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] Commented: (HADOOP-808) Enhance 'bin/hadoop job -submit <>'
Date Tue, 12 Dec 2006 22:33:25 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-808?page=comments#action_12457923 ] 
Doug Cutting commented on HADOOP-808:

And 'in-dir out-dir' is shorthand for -Dmapred.input.dir=xxx -Dmapred.output.dir=yyy, so isn't
strictly required, but would be convenient.

Also, the foo.xml becomes essentially a config file.  So another way to do this might be to
permit the specification of multiple config files that are read in order.

bin/hadoop job -submit -conf my-site.xml -conf my-job.xml -Dmapred.input.dir=xxx ...

> 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