[
https://issues.apache.org/jira/browse/MAHOUT-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012050#comment-13012050
]
Julien Nioche commented on MAHOUT-368:
--------------------------------------
I agree with Hui Wen and am exactly in the same situation. I have a custom
mapreduce class that uses Mahout and am getting the ClassNotFound exception
because core, math and collections are in separate jars. I could of course use
the job file but would rather use Ivy/Maven just as I do for all the other
dependencies I use.
Why not having a bundle artifact where all the Mahout submodules would be put
it a single jar?
> should package core ,math and collections to one Jar package for hadoop
> recommendations
> ---------------------------------------------------------------------------------------
>
> Key: MAHOUT-368
> URL: https://issues.apache.org/jira/browse/MAHOUT-368
> Project: Mahout
> Issue Type: Improvement
> Components: Collaborative Filtering
> Affects Versions: 0.4
> Reporter: Han Hui Wen
> Assignee: Sean Owen
> Labels: classloader, hadoop, mahout
> Fix For: 0.4
>
>
> should package core ,math and collections to one Jar package for
> org.apache.mahout.cf.taste.hadoop.item.RecommenderJob.
> because RecommenderJob used classes (for example
> org.apache.mahout.math.VectorWritable )of the math module of mahout project,
> but math and core module is the separated jar package.
> so when work on the hadoop env ,the class of math module can not load to
> classloader in the datanode.
> it will cause class not found exception.
> the work around is package all mahout classes to one package manually.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
