You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Hari Shreedharan (Commented) (JIRA)" <ji...@apache.org> on 2012/02/14 01:26:59 UTC
[jira] [Commented] (FLUME-945) Add the ability to specify a default
channel for multiplexing channel selector.
[ https://issues.apache.org/jira/browse/FLUME-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207389#comment-13207389 ]
Hari Shreedharan commented on FLUME-945:
----------------------------------------
I have added support for this. Now if an event comes in which has header value which does not map to any of the configured mappings, then the event is routed to default channels. It is now mandatory to define mandatory channels in the config. Also if an event comes in with no header value, then it is also sent to the the default channels. Unit tests have been updated to cover these cases.
> Add the ability to specify a default channel for multiplexing channel selector.
> -------------------------------------------------------------------------------
>
> Key: FLUME-945
> URL: https://issues.apache.org/jira/browse/FLUME-945
> Project: Flume
> Issue Type: Improvement
> Affects Versions: v1.0.0
> Reporter: Arvind Prabhakar
> Fix For: v1.1.0
>
>
> For events that do not match any mapping specified in the selector configuration, there should be the ability to setup a default channel. This will ensure that no events are getting dropped from the system.
--
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