flume-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Heinrichs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLUME-2293) Isolate Flume agent plugins to their own classloader
Date Fri, 29 Mar 2019 21:59:00 GMT

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

Michael Heinrichs commented on FLUME-2293:

Someone has done the work on a fork of the 1.8.0 release, and even included test cases. Should
consider pulling in these changes.

Anyone needing this functionality could use this fork.


> 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

To unsubscribe, e-mail: issues-unsubscribe@flume.apache.org
For additional commands, e-mail: issues-help@flume.apache.org

View raw message