You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Ferenc Szabo (JIRA)" <ji...@apache.org> on 2017/07/06 23:07:00 UTC

[jira] [Commented] (FLUME-1551) Create a home for custom Flume components

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

Ferenc Szabo commented on FLUME-1551:
-------------------------------------

Looks like flume has this feature already:
https://flume.apache.org/FlumeUserGuide.html#installing-third-party-plugins

[~will@cloudera.com] does this resolve this ticket?

> Create a home for custom Flume components
> -----------------------------------------
>
>                 Key: FLUME-1551
>                 URL: https://issues.apache.org/jira/browse/FLUME-1551
>             Project: Flume
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.3.0
>            Reporter: Will McQueen
>              Labels: possibly_complete
>
> Create an 'ext' dir where all Flume NG custom components can live (eg, custom channels, sources, sinks, interceptors, serializers). Modify the flume-ng script to include this 'ext' dir in the classpath (probably include it right after the lib dir). Doing this will standardize the location of custom components.
> An manual alternative is for a user to create the 'ext' dir and include that dir in the flume-env.sh file's FLUME_CLASSPATH value.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)