Uploaded image for project: 'Flume'
  1. Flume
  2. FLUME-2293

Isolate Flume agent plugins to their own classloader

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.7.0
    • None
    • None

    Description

      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).

      Attachments

        Activity

          People

            Unassigned Unassigned
            jrh3k5 Joshua Hyde
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: