[
https://issues.apache.org/jira/browse/MAPREDUCE-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776713#action_12776713
]
Todd Lipcon commented on MAPREDUCE-727:
---------------------------------------
bq. Are you proposing we replace them with hadoop_streaming style parameters
Yes - the idea here is that a lot of jobs duplicate a lot of common driver
code. The point here is to avoid having to write a main() at all - not
currently possible with hadoop jar. Obviously this interface isn't for
everyone, but might feel more familiar for some.
bq. we will have 1:1 correspondence between those switches and config knobs
anyway
Yea, and I think this is long term something we should work on. There are some
other JIRAs floating around about the configuration framework - we should
perhaps keep in mind the idea of a "flag style name" for some configuration
parameters. This is probably unrelated to this particular JIRA trhough - sorry
for taking us off-topic.
What would the new functionality for mapred job -submit do, exactly? Does
anyone make use of the current job -submit interface? Writing an xml jobconf is
a big enough pain I don't know of anyone doing it.
> Move the bin/hadoop jar command over to bin/mapred
> --------------------------------------------------
>
> Key: MAPREDUCE-727
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-727
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Arun C Murthy
> Fix For: 0.21.0
>
>
> Currently 'bin/hadoop jar' is used to submit jobs, we should move it over to
> bin/mapred.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
