My guess is that you have set your CLASSPATH variable such that when you ran your jar, it was actually finding the classes from the original .class files, and not from the jar. When you moved it out, it was just the jar on the classpath as it should be, and this solved the issue.
-Todd On Mon, Nov 23, 2009 at 9:17 PM, Zhengguo 'Mike' SUN <[email protected]>wrote: > Hi All, > > I figured out. It is related to my directory structure. I have my jar under > $HADOOP_HOME and my package and class files are under $HADOOP_HOME too. When > I moved my package and class files somewhere else, it worked. It seemed that > this structure made JobConf.findContainingJar break. > > > > > ________________________________ > From: Rekha Joshi <[email protected]> > To: "[email protected]" <[email protected]>; " > [email protected]" <[email protected]> > Sent: Mon, November 23, 2009 11:51:12 PM > Subject: Re: Job.setJarByClass in Hadoop 0.20.1 > > If your paths/files are alright, think > job.setJarByClass(yourClassName.class); should work.Thanks! > > > On 11/24/09 9:58 AM, "Zhengguo 'Mike' SUN" <[email protected]> wrote: > > Job.setJarByClass() > > > > >
