[
https://issues.apache.org/jira/browse/FLUME-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274038#comment-13274038
]
Hudson commented on FLUME-1001:
-------------------------------
Integrated in flume-trunk #203 (See
[https://builds.apache.org/job/flume-trunk/203/])
FLUME-1001. Support custom sink processors.
(Juhani Connolly via Arvind Prabhakar) (Revision 1337577)
Result = SUCCESS
arvind : http://svn.apache.org/viewvc/?view=rev&rev=1337577
Files :
*
/incubator/flume/trunk/flume-ng-configuration/src/main/java/org/apache/flume/conf/sink/SinkProcessorType.java
*
/incubator/flume/trunk/flume-ng-core/src/main/java/org/apache/flume/sink/SinkProcessorFactory.java
*
/incubator/flume/trunk/flume-ng-core/src/test/java/org/apache/flume/sink/SinkProcessorFactoryTest.java
> Support custom processors
> -------------------------
>
> Key: FLUME-1001
> URL: https://issues.apache.org/jira/browse/FLUME-1001
> 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.2.0
>
> Attachments: FLUME-1001.5.patch
>
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira