[ https://issues.apache.org/jira/browse/FLUME-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810833#comment-16810833 ] 

Michael Heinrichs commented on FLUME-2293:
------------------------------------------

The work seems to be on the branch 'FLUME-2293'

[https://github.com/apache/flume/compare/flume-1.8...cognitree:FLUME-2293]

Most of the changes are in these commits:

[https://github.com/apache/flume/commit/9213c3637aebb5c25a0a3319a3e7add98a8ae8bc]

[https://github.com/apache/flume/commit/47b802578830821c55d352cb5c134cfc4595c073]

 

> 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