[
https://issues.apache.org/jira/browse/FLUME-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727742#comment-13727742
]
Roshan Naik commented on FLUME-2140:
------------------------------------
It appears that may be only the sink is able to know for certain (at the time
to delivery) that a particular event is bad.
One scenario that comes to mind here:
- an event that may be bad for one sink maynot be bad for another. for
instance, logger sink or rolling file sink may not have trouble delivering an
event that is troublesome for elastic search sink.
> Support diverting bad events from pipeline
> ------------------------------------------
>
> Key: FLUME-2140
> URL: https://issues.apache.org/jira/browse/FLUME-2140
> Project: Flume
> Issue Type: New Feature
> Components: Node
> Reporter: Arvind Prabhakar
>
> A *bad event* can be any event that causes persistent sink side processing
> failure due to the inherent nature of the event itself. Note that failures
> that are not related to the inherent nature of the event such as network
> communication failure, downstream capacity failure etc., do not make the
> event a bad-event.
> The presence of a bad event in a channel can cause the entire pipleline to
> choke and become unusable. Flume should therefore be able to identify bad
> events and provide a facility to route them out of the pipleline in order to
> ensure the transport of other events continues uninterrupted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
