mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pat Ferrel (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAHOUT-1636) Class dependencies for the spark module are put in a job.jar, which is very inefficient
Date Fri, 27 Mar 2015 13:34:54 GMT

     [ https://issues.apache.org/jira/browse/MAHOUT-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pat Ferrel resolved MAHOUT-1636.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.0-snapshot)
                   0.10.0

Created a the smallest possible assembly of classes that satisfy both client and worker need
for all of scala code. This is needed for the Spark context but may have classes only required
by the client, Need to separate out eventually. but this will do for 0.10.1

> 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
>              Labels: DSL, scala, spark
>             Fix For: 0.10.0
>
>
> 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)

Mime
View raw message