[FLUME-1735] Add support for a plugins.d directory

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Assignee: Brock Noland
• Reporter: Mike Percy
• Created: 21/Nov/12 00:51
• Updated: 13/Jan/14 06:12
• Resolved: 19/Dec/12 23:18

Description

It would be nice to have a directory, called something like plugins.d, which had the following structure:

flume/
  bin/
  conf/
  lib/
  plugins.d/
    custom-source-1/
      custom-source-1-base.jar
      custom-source-1-ext.jar
    custom-interceptor-2/
      custom-interceptor-2-main.jar
      custom-interceptor-2-lib.jar

This would make it easy for users to easily install new plugins (sources, sinks, interceptors, etc) and in the case of some conflict, they can easily be differentiated and moved out of the include path. This helps with management and debugging of plugin issues, and avoids the current requirement for users to add these plugins to their FLUME_CLASSPATH.

Issue Links

• is duplicated by: FLUME-1581 Create directory for automatic inclusion of Flume extension code
• is related to: FLUME-1845 Document plugin.d directory structure