I see in the documentation for org.apache.flume.interceptor.Interceptor
that the result of intercept(List) must not exceed the size of the
input (in all-caps, even). This is unfortunate for my use-case: I'm
interfacing with a scribe source that provides each message as a
serialization of some numbe
ke you
> are describing.
>
> So basically just make sure that your channel.transactionCapacity > max
> batch size * max # sub-events per "wrapper" event.
>
> Hope this makes sense. The above explanation is somewhat subtle and since
> it has sharp edges when misconfigured, we just
There may be even simpler ways, but you can implement
org.apache.flume.interceptor.Interceptor to construct a timestamp
(milliseconds) from those fields, and then set an event header for
"timestamp".
private static final String TIMESTAMP = "timestamp";
@Override
public Event intercept(Event event
Hi Guillermo --
If I understand correctly, you want to create two paths. Events that pass
the validating interceptor get directed to one path in HDFS and events that
fail get directed to another. If so, you could define your interceptor to
set a 'valid' header to 'yes' or 'no' depending on its int