You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2015/09/16 21:03:45 UTC

[jira] [Resolved] (SPARK-4738) Update the netty-3.x version in spark-assembly-*.jar

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

Josh Rosen resolved SPARK-4738.
-------------------------------
    Resolution: Incomplete

Resolving as "Incomplete" since this an old issue and it doesn't look like there's any action to take here. In newer Spark versions, you should be able to use the various user-classpath-first configurationst o work around this.

> Update the netty-3.x version in spark-assembly-*.jar
> ----------------------------------------------------
>
>                 Key: SPARK-4738
>                 URL: https://issues.apache.org/jira/browse/SPARK-4738
>             Project: Spark
>          Issue Type: Improvement
>          Components: Deploy
>    Affects Versions: 1.1.0
>            Reporter: Tobias Pfeiffer
>            Priority: Minor
>
> It seems as if the version of akka-remote (2.2.3-shaded-protobuf) that is bundled in the spark-assembly-1.1.1-hadoop2.4.0.jar file pulls in an ancient version of netty, namely io.netty:netty:3.6.6.Final (using the package org.jboss.netty). This means that when using spark-submit, there will always be this netty version on the classpath before any versions added by the user. This may lead to issues with other packages that depend on newer versions and may fail with java.lang.NoSuchMethodError etc.(finagle-http in my case).
> I wonder if it possible to manually include a newer netty version, like netty-3.8.0.Final.



--
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