You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org> on 2012/02/24 19:45:50 UTC
[jira] [Commented] (FLUME-946) Allow multiplexing channel selector
to specify optional channels.
[ https://issues.apache.org/jira/browse/FLUME-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215804#comment-13215804 ]
jiraposter@reviews.apache.org commented on FLUME-946:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4034/
-----------------------------------------------------------
Review request for Flume.
Summary
-------
Support for optional channels in multiplexing channel selector. If no required channels configured, but there are optional channels then it means, write to default channels and optionally write to optional channels if they are available.
This addresses bug FLUME-946.
https://issues.apache.org/jira/browse/FLUME-946
Diffs
-----
flume-ng-core/src/main/java/org/apache/flume/channel/MultiplexingChannelSelector.java c63d0a1
flume-ng-core/src/test/java/org/apache/flume/channel/TestMultiplexingChannelSelector.java 2626b20
Diff: https://reviews.apache.org/r/4034/diff
Testing
-------
Updated unit tests to support these cases
Thanks,
Hari
> Allow multiplexing channel selector to specify optional channels.
> -----------------------------------------------------------------
>
> Key: FLUME-946
> URL: https://issues.apache.org/jira/browse/FLUME-946
> Project: Flume
> Issue Type: Improvement
> Affects Versions: v1.0.0
> Reporter: Arvind Prabhakar
>
> Right now the multiplexing channel selector treats all channels as required channels. There should be a simple provision where some channel can be marked optional so that a failure in publishing the event to that particular channel does not cause the entire request to fail. For example, the following configuration:
> agent.sources.foo.selector.mapping.foo = ch1 ch2
> agent.sources.foo.selector.mapping.bar = ch2 ch3
> agent.sources.foo.selector.optional.channels = ch2
> Would imply that for mapping value "foo", ch1 is a required channel whereas ch2 is an optional channel. Similarly, for mapping "bar', ch3 is a required channel but ch2 is optional.
--
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