[
https://issues.apache.org/jira/browse/FLUME-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077387#comment-16077387
]
Will Chase commented on FLUME-1551:
-----------------------------------
Funnily enough, the Will who opened this ticket (Will McQueen) isn't with
Cloudera anymore and I (Will Chase) grabbed the [email protected] email alias
years ago.
So, I should probably find someone to remove this email from Will McQueen's
account here!
I'll see if I can track down someone in Ops to help out.
Regarding the issue at hand, sorry I can't help resolve the ticket!
Cheers,
-- Will Chase
Senior System Administrator @ Cloudera
Sent from my iPhone
> 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)
