I believe that the bottom of this is the problems with setJarByClass
that were documented some weeks ago.

On Sun, May 8, 2011 at 5:58 PM, Sean Owen <[email protected]> wrote:
> If I recall the last discussion on this correctly --
>
> No you don't want to put anything in Hadoop's lib/ directory. Even if
> you can, that's not the "right" way.
> You want to use the job file indeed, which should contain all dependencies.
> However, it packages dependencies as jars-in-the-jar, which doesn't
> work for Hadoop.
>
> I think if you modify the Maven build to just repackage all classes
> into the main jar, it works. It works for me at least.
>
> And then I forget why we don't just do that in the build.
>
> On Sun, May 8, 2011 at 10:56 PM, Jake Mannix <[email protected]> wrote:
>> On Sun, May 8, 2011 at 2:01 PM, EDUARDO ANTONIO BUITRAGO ZAPATA <
>> [email protected]> wrote:
>>
>>> you should try copying the mahout-math-(YOURVERSION).jar into the lib
>>> folder
>>> in the $HADOOP_HOME.
>>>
>>
>> That works just fine if you're on a cluster where you have privileges to do
>> this.  The mahout-math-0.5-SHAPSHOT.jar
>> is in the lib directory of the mahout-examples-0.5-SNAPSHOT-job.jar, so it
>> *should* be finding it. :\
>>
>>  -jake
>>
>>
>>>
>>> 2011/5/8 Jake Mannix <[email protected]>
>>>
>>> > Running on the cluster, I'm hit with this again, on using a freshly built
>>> > distribution (with mvn package -Prelease).  What is the solution we
>>> always
>>> > give people to deal with this?
>>> >
>>> > (just running things like "./bin/mahout svd -i <input> -o <output> etc...
>>> > ")
>>> >
>>> >  -jake
>>> >
>>>
>>>
>>>
>>> --
>>> EDUARDO BUITRAGO
>>> Est. Msc. en Ingeniería - Sistemas y Computación - Universidad de los Andes
>>> Ing. de Sistemas - Universidad Francisco de Paula Santander
>>> Cisco Certified Network Associate - CCNA
>>>
>>
>

Reply via email to