No, looks like you'd have to catch them in the serializer and have the serializer return option or something. The new consumer builds a buffer full of records, not one at a time. On Mar 8, 2016 4:43 AM, "Marius Soutier" <mps....@gmail.com> wrote:
> > > On 04.03.2016, at 22:39, Cody Koeninger <c...@koeninger.org> wrote: > > > > The only other valid use of messageHandler that I can think of is > > catching serialization problems on a per-message basis. But with the > > new Kafka consumer library, that doesn't seem feasible anyway, and > > could be handled with a custom (de)serializer. > > What do you mean, that doesn't seem feasible? You mean when using a custom > deserializer? Right now I'm catching serialization problems in the message > handler, after your proposed change I'd catch them in `map()`. > >
