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

["Roman Shaposhnik (JIRA)" <ji...@apache.org>]

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

Roman Shaposhnik commented on FLUME-1735:
-----------------------------------------

+1 on the general idea. I'd love to see this pluggability exposed via Bigtop so that flume users don't have to install everything but the kitchen sink.

The bare bones implementation seems fine. A tad fancier approach would be to allow exploded jars for things that might need to be on the classpath but tweaked (sort of what wars do with WEB-INF/classes vs. WEB-INF/lib).


                
> Add support for a plugins.d directory
> -------------------------------------
>
>                 Key: FLUME-1735
>                 URL: https://issues.apache.org/jira/browse/FLUME-1735
>             Project: Flume
>          Issue Type: Improvement
>            Reporter: Mike Percy
>             Fix For: v1.4.0
>
>
> 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