[ http://issues.apache.org/jira/browse/HADOOP-808?page=comments#action_12457907 ] Owen O'Malley commented on HADOOP-808: --------------------------------------
But they can already do that. % bin/hadoop job -submit foo.xml will submit a pre-built JobConf as a job. This patch just enables the config to have a mapred.job.class that must extend ToolBase that can manipulate the config before it is submitted. I think it would be better to just have a richer cli processing in the generic main. In particular, it would be nice to have: % bin/hadoop job -submit -Dxxx=yyy -Daaa=bbb foo.xml in-dir out-dir To load foo.xml as a JobConf, change the values of xxx and bbb, set the input directory to in-dir and the output director to out-dir and submit it. That way, you can run without a main and yet make the most common changes. > 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
