[
https://issues.apache.org/jira/browse/FLUME-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308136#comment-14308136
]
Hari Shreedharan commented on FLUME-2580:
-----------------------------------------
Couple of questions came up offline:
# How to drop events? Unfortunately I don't think we can drop events directly.
The interceptor will need to return dummy events that the sink ignores.
# Batch intercepts? This is sort of possible. We can take a batch size in the
config, buffer the events and pass them to the interceptor as a batch. When the
sink starts pulling events out, we pass the returned events one by one.
# Increasing event count? My feeling is we should not support it - we don't do
that even for source side interceptors today.
> Sink side interceptors
> ----------------------
>
> Key: FLUME-2580
> URL: https://issues.apache.org/jira/browse/FLUME-2580
> Project: Flume
> Issue Type: New Feature
> Reporter: Hari Shreedharan
> Assignee: Hari Shreedharan
> Attachments: SinkSideInterceptors.pdf
>
>
> Currently, we only have source-side interceptors that help routing. But if we
> use something like Kafka Channel, having a sink-side interceptor can help us
> modify events as they come in. We could also do validation on event schemas
> and drop them before they hit the sink, rather than have an infinite loop due
> to such events.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
