-Re: Lib conflicts
Jay Vyas 2012-10-03, 12:01
Yup! I hate this issue. It also happens with json libs if you have an old
Its really easy also to dump the exact class path at runtime using the
very very very very useful :)
I always do this just to make sure before going and mucking with the
I've found using this trick can save a lot of headaches, especially if your
dealing with jars that you can't programmatically get version #'s out of.
On Wed, Oct 3, 2012 at 7:45 AM, Ben Rycroft <[EMAIL PROTECTED]> wrote:
> Hi guys,
> Thanks the speedy replies.
> I will try Harsh's suggestion and see if this solves the issue, if not I
will just do what Michael suggested and replace the jars on each of the
> Thanks again!
> On Wed, Oct 3, 2012 at 12:39 PM, Harsh J <[EMAIL PROTECTED]> wrote:
>> Hi Ben,
>> As long as the switch of libraries doesn't impact the execution of the
>> Child task code itself, for Apache Hadoop 1.x, using the config
>> "mapreduce.user.classpath.first" set to true may solve your trouble.
>> On Wed, Oct 3, 2012 at 4:51 PM, Ben Rycroft <[EMAIL PROTECTED]> wrote:
>> > Hi all,
>> > I have a jar that uses the Hadoop API to launch various remote
>> > jobs (ie, im not using the command-line to initiate the job). The
>> > jar that executes the various jobs is built with maven's
>> > "jar-with-dependencies".
>> > My jobs all run fine except one that uses commons-codec 1.7, I get:
>> > FATAL org.apache.hadoop.mapred.Child: Error running child :
>> > java.lang.NoSuchMethodError:
>> > I think this is because my jar is including commons-codec 1.7 whereas
>> > Hadoop install's lib has commons-codec 1.4 ...
>> > Is their any way to instruct Hadoop to use the distributed
>> > (I assume this is distributed as a job dependency) rather than the
>> > commons-codec 1.4 in the hadoop 1.0.3 core lib?
>> > Removing commons-codec-1.4.jar from my Hadoop library folder did seem
>> > solve the problem for a bit, but is not working on another VM.
>> > 1.4 jar with the 1.7 does seem to fix the problem but this doesn't
>> > sane. Hopefully there is a better alternative.
>> > Thanks!
>> Harsh J