to implement custom handling is okay...
Thanks
Adrian
- Original message -From: Nico Kruber To: Adrian Vasiliu Cc: user@flink.apache.orgSubject: Re: Unrecoverable job failure after Json parse error?Date: Tue, Jan 16, 2018 3:18 PM
Nice, I didn't even read that far myself :P-> turns
o have a solution in hands.
> Thanks again.
> Adrian
>
>
> - Original message -
> From: Nico Kruber
> To: Adrian Vasiliu , user@flink.apache.org
> Cc:
> Subject: Re: Unrecoverable job failure after Json parse error?
> Date: Tue, Jan 16,
improvement for JSONKeyValueDeserializationSchema to provide this behaviour as an out-of-the-box option. But anyway, I do have a solution in hands.
Thanks again.
Adrian
- Original message -From: Nico Kruber To: Adrian Vasiliu , user@flink.apache.orgCc:Subject: Re: Unrecoverable job failure after Json parse error?Date: Tu
Hi Adrian,
couldn't you solve this by providing your own DeserializationSchema [1],
possibly extending from JSONKeyValueDeserializationSchema and catching
the error there?
Nico
[1]
https://ci.apache.org/projects/flink/flink-docs-release-1.4/dev/connectors/kafka.html#the-deserializationschema
On
Hello,
When using FlinkKafkaConsumer011 with JSONKeyValueDeserializationSchema, if an invalid, non-parsable message is sent to the Kafka topic, the consumer expectedly fails with JsonParseException. So far so good, but this leads to the following loop: the job switches to FAILED then attempts to re