Matt, no prob!
Mike
Sent from my iPhone
> On Jun 24, 2014, at 8:35 PM, Matt Tenenbaum
> wrote:
>
> Thanks Mike. That's very helpful.
>
> It should be no trouble to establish an upper bound on the intra-event
> packing, so I should be able to tune the capacity parameters in the way you
> su
Thanks Mike. That's very helpful.
It should be no trouble to establish an upper bound on the intra-event
packing, so I should be able to tune the capacity parameters in the way you
suggest. Besides, aren't the sharp edges what make it fun to play with?
I may be able to impose suitable restriction
Hi Matt,
If you can guarantee there are a certain # of events in a single "wrapper"
event, or bound the limit, then you could potentially get away with this.
However if you're not careful you could get stuck in an infinite
fail-backoff-retry loop due to exceeding the (configurable) channel
transact
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
