[
https://issues.apache.org/jira/browse/HADOOP-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1971:
----------------------------------
Fix Version/s: (was: 0.14.2)
0.15.0
This isn't a bug and so should not go into 14.2. I can see the motivation for
the warning, but not all jobs need a jar file. We should probably move the
examples to be more explicit and do:
{code}
JobConf conf = new JobConf();
conf.setJarByClass(MyClass.class);
{code}
so it will be more obvious when you drop it out what is likely to happen.
*smile*
> Constructing a JobConf without a class leads to a very misleading error
> message.
> --------------------------------------------------------------------------------
>
> Key: HADOOP-1971
> URL: https://issues.apache.org/jira/browse/HADOOP-1971
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.14.2
> Environment: Centos, java 1.5
> Reporter: Ted Dunning
> Assignee: Enis Soztutar
> Priority: Minor
> Fix For: 0.15.0
>
> Attachments: notSetJarError_v1.patch
>
>
> If this line from a typical map/reduce program
> JobConf conf = new JobConf(Flatten.class);
> has the argument deleted then I get a message that the input format that I
> specify cannot be found. That message leads a naive user on a rat chase. I
> only corrected this by bisecting against a working program.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
