[
https://issues.apache.org/jira/browse/SPARK-17875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017059#comment-16017059
]
Morten Hornbech commented on SPARK-17875:
-----------------------------------------
Sorry, I have now. If the class files are indeed in the flume assembly my best
guess is that this occurs because of binary compatibility issues between 4.0
and 3.8 triggered by static members upon load of ChannelPipelineFactory. I can
see that ChannelPipelineFactory does not exist in 4.0 but it references
ChannelPipeline in its class definition which does. So if that was loaded from
4.0 things could go wrong. If an upgrade of flume to netty 4.0 is a major task
a simpler solution would be to shade netty 3.8 in the flume assembly. That way
you should be able to get rid of it in spark-core.
> Remove unneeded direct dependence on Netty 3.x
> ----------------------------------------------
>
> Key: SPARK-17875
> URL: https://issues.apache.org/jira/browse/SPARK-17875
> Project: Spark
> Issue Type: Improvement
> Components: Build
> Affects Versions: 2.0.1
> Reporter: Sean Owen
> Assignee: Sean Owen
> Priority: Trivial
>
> The Spark build declares a dependency on Netty 3.x and 4.x, but only 4.x is
> used. It's best to remove the 3.x dependency (and while we're at it, update a
> few things like license info)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
