You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flume.apache.org by "Ferenc Szabo (JIRA)" <ji...@apache.org> on 2019/04/05 08:23:00 UTC
[jira] [Commented] (FLUME-2293) Isolate Flume agent plugins to
their own classloader
[ https://issues.apache.org/jira/browse/FLUME-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810601#comment-16810601 ]
Ferenc Szabo commented on FLUME-2293:
-------------------------------------
[~slipperySloth] can you link the commit that solved this issue?
I have checked the release-1.8.0-cognitree branch and it was still adding the plugins to the application FLUME_CLASSPATH so I am not sure how the solution works.
> 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, Technical Debt
> Affects Versions: 1.7.0
> Reporter: Joshua Hyde
> Priority: Major
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@flume.apache.org
For additional commands, e-mail: issues-help@flume.apache.org