GitHub user atokhy opened a pull request:

    https://github.com/apache/spark/pull/12800

    [SPARK-15024] NoClassDefFoundError in spark-examples due to Guava rel…

    ## What changes were proposed in this pull request?
    This change will only shade and relocate Guava in the spark-examples JAR 
used by the Apache Bigtop distribution (as of writing the Bigtop distribution 
uses the unshaded JAR).  Since only Guava and Jetty are relocated, and since 
there are 0 references to Jetty in the spark-examples codebase, only Guava 
needs to be shaded.  The shaded spark-assembly JAR provides the rest of the 
dependencies needed to get the spark-examples to run without any 
NoClassDefFoundErrors
    
    ## How was this patch tested?
    mvn package -DrecompileMode=all -Pbigtop-dist -Pyarn -Phadoop-2.6 -Phive 
-Phive-thriftserver -Dprotobuf.version=2.5.0
    
    $ unzip -l target/scala-2.10/spark-examples-1.6.1-hadoop2.6.0.jar | grep 
org.spark-project.guava | wc -l
    1602

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/atokhy/spark spark-examples-guava

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/12800.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #12800
    
----
commit 4130e0614b9237e51e774b22a971fd7aa06b088d
Author: Aaron Tokhy <[email protected]>
Date:   2016-04-30T02:50:26Z

    [SPARK-15024] NoClassDefFoundError in spark-examples due to Guava relocation

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to