incubator-flume-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From " (Commented) (JIRA)" <>
Subject [jira] [Commented] (FLUME-1001) Support custom processors
Date Fri, 02 Mar 2012 08:24:02 GMT

] commented on FLUME-1001:

This is an automatically generated e-mail. To reply, visit:

Review request for Flume.


Made custom processors possible in the same way as sink and source: the type can represent
a classname or a shorthand name from the typedef.

This addresses bug FLUME-1001.


  flume-ng-core/src/main/java/org/apache/flume/ be1891b 
  flume-ng-core/src/main/java/org/apache/flume/sink/ 10f9f4e 
  flume-ng-core/src/test/java/org/apache/flume/sink/ PRE-CREATION



Existing tests pass, except I'm having an issue with TestNetcatSource which seems to be totally
unrelated... It turns up on flume-728 head too, probably something in my environment

Added a new test to verify that processors created by shorthand name and by full class create
the same class, verifying that creation by classname also works



> Support custom processors
> -------------------------
>                 Key: FLUME-1001
>                 URL:
>             Project: Flume
>          Issue Type: Improvement
>          Components: Sinks+Sources
>    Affects Versions: v1.1.0
>         Environment: RHEL 6.2 64-bit
>            Reporter: Will McQueen
>            Assignee: Juhani Connolly
>             Fix For: v1.1.0
> Currently there doesn't seem to be a way for a user to specify a custom processor...
for example, a replicating processor that replicates a channel's output to all sinks. If this
is implemented in a way to how custom sources and sinks are implemented, then we'd need a
SinkProcessor.OTHER type, as a start.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message