You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2013/06/25 02:02:20 UTC

[jira] [Updated] (FLUME-1735) Add support for a plugins.d directory

     [ https://issues.apache.org/jira/browse/FLUME-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Percy updated FLUME-1735:
------------------------------

    Issue Type: New Feature  (was: Improvement)
    
> Add support for a plugins.d directory
> -------------------------------------
>
>                 Key: FLUME-1735
>                 URL: https://issues.apache.org/jira/browse/FLUME-1735
>             Project: Flume
>          Issue Type: New Feature
>            Reporter: Mike Percy
>            Assignee: Brock Noland
>             Fix For: v1.4.0
>
>         Attachments: FLUME-1735-0.patch, FLUME-1735-1.patch
>
>
> It would be nice to have a directory, called something like plugins.d, which had the following structure:
> {noformat}
> 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
> {noformat}
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira