[ https://issues.apache.org/jira/browse/MAHOUT-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347723#comment-14347723 ]
ASF GitHub Bot commented on MAHOUT-1636: ---------------------------------------- Github user pferrel commented on the pull request: https://github.com/apache/mahout/pull/69#issuecomment-77268475 Made a first cut of including a "dependency-reduced" jar with only Guava and Scopt included with <include> directive, see PR#76 https://github.com/apache/mahout/pull/76 > Class dependencies for the spark module are put in a job.jar, which is very > inefficient > --------------------------------------------------------------------------------------- > > Key: MAHOUT-1636 > URL: https://issues.apache.org/jira/browse/MAHOUT-1636 > Project: Mahout > Issue Type: Bug > Components: spark > Affects Versions: 1.0-snapshot > Reporter: Pat Ferrel > Assignee: Ted Dunning > Fix For: 1.0-snapshot > > > using a maven plugin and an assembly job.xml a job.jar is created with all > dependencies including transitive ones. This job.jar is in > mahout/spark/target and is included in the classpath when a Spark job is run. > This allows dependency classes to be found at runtime but the job.jar include > a great deal of things not needed that are duplicates of classes found in the > main mrlegacy job.jar. If the job.jar is removed, drivers will not find > needed classes. A better way needs to be implemented for including class > dependencies. > I'm not sure what that better way is so am leaving the assembly alone for > now. Whoever picks up this Jira will have to remove it after deciding on a > better method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)