[
https://issues.apache.org/jira/browse/FLUME-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728247#comment-14728247
]
Alex Cruise commented on FLUME-2293:
------------------------------------
This bites especially hard now that Scala 2.10 is in the main Flume classpath
(presumably because of the transitive dependency via Kafka). Scala doesn't
have binary compatibility between 2.x versions, and all my stuff is 2.11. I'll
try replacing the Kafka and Scala libraries in the Flume distribution with 2.11
versions.
> Isolate Flume agent plugins to their own classloader
> ----------------------------------------------------
>
> Key: FLUME-2293
> URL: https://issues.apache.org/jira/browse/FLUME-2293
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Reporter: Joshua Hyde
>
> This is tangential to the FLUME-2286 issue I raised, but this would probably
> negate it:
> It'd be nice if Flume plugins had classloaders isolated from the {{lib/}}
> directory of Flume (and the Flume agent itself was isolated from the plugins
> directory). This would allow plugins to exercise a bit more freedom in their
> dependency stack (such as using more recent versions of Guava) without
> interfering with the ability of the Flume agent to run (and without
> interference from the agent's dependencies).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
