spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "RJ Nowling (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-4816) Maven profile netlib-lgpl does not work
Date Mon, 14 Dec 2015 17:51:46 GMT

    [ https://issues.apache.org/jira/browse/SPARK-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056368#comment-15056368
] 

RJ Nowling commented on SPARK-4816:
-----------------------------------

I want to push for two things (a) some sort of documentation for users (e.g., release notes
in the next releases) and (b) make sure it's fixed in the latest releases.  I want users to
be able to find documentation (like this JIRA) so they don't have to spend time tracking it
down like I did.  

Spark 1.4.2 hasn't been released yet and git has moved to a 1.4.3 SNAPSHOT.  You mention adding
the commit to the 1.5.x branch in the commit -- has this been done?

Until 1.4.3 and a 1.5.x release are out with your change, this could still hit certain users,
even if it's rare because it's tied to a specific Maven version or such.

> Maven profile netlib-lgpl does not work
> ---------------------------------------
>
>                 Key: SPARK-4816
>                 URL: https://issues.apache.org/jira/browse/SPARK-4816
>             Project: Spark
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.1.0
>         Environment: maven 3.0.5 / Ubuntu
>            Reporter: Guillaume Pitel
>            Priority: Minor
>             Fix For: 1.1.1
>
>
> When doing what the documentation recommends to recompile Spark with Netlib Native system
binding (i.e. to bind with openblas or, in my case, MKL), 
> mvn -Pnetlib-lgpl -Pyarn -Phadoop-2.3 -Dhadoop.version=2.3.0 -DskipTests clean package
> The resulting assembly jar still lacked the netlib-system class. (I checked the content
of spark-assembly...jar)
> When forcing the netlib-lgpl profile in MLLib package to be active, the jar is correctly
built.
> So I guess it's a problem with the way maven passes profiles activitations to children
modules.
> Also, despite the documentation claiming that if the job's jar contains netlib with necessary
bindings, it should works, it does not. The classloader must be unhappy with two occurrences
of netlib ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message