a fair amount of time working out what was going on I thought I'd
> flag it up in case it wasn't known about.
>
> Tim Ward
>
> -Original Message-
> From: Matthias J. Sax
> Sent: 14 September 2018 19:57
> To: users@kafka.apache.or
@kafka.apache.org
Subject: Re: Understanding default.deserialization.exception.handler
Your observation is correct. It's a known bug:
https://issues.apache.org/jira/browse/KAFKA-6502
In practice, it should not be a big issue though.
- you would only hit this bug if you don't process a "
Your observation is correct. It's a known bug:
https://issues.apache.org/jira/browse/KAFKA-6502
In practice, it should not be a big issue though.
- you would only hit this bug if you don't process a "good message"
afterwards
- even if you hit this bug, you would just skip the message again
With
props.put(StreamsConfig.DEFAULT_DESERIALIZATION_EXCEPTION_HANDLER_CLASS_CONFIG,
LogAndContinueExceptionHandler.class);
Scenario A:
Run application. Feed a message into the topic that will fail deserialization.
Application logs exception and keeps running.
Shut down application.
