Re: A way to meter number of deserialization errors

2024-06-21 Thread Ilya Karpov
to understand and > potentially fix the source / parser limitations. > > > > Kind regards, David. > > > > From: Ilya Karpov > Date: Monday, 17 June 2024 at 12:39 > To: user > Subject: [EXTERNAL] A way to meter number of deserialization errors > > Hi all,

Re: A way to meter number of deserialization errors

2024-06-19 Thread David Radley
: Ilya Karpov Date: Monday, 17 June 2024 at 12:39 To: user Subject: [EXTERNAL] A way to meter number of deserialization errors Hi all, we are planning to use flink as a connector between kafka and external systems. We use protobuf as a message format in kafka. If non-backward compatible changes oc

Re: A way to meter number of deserialization errors

2024-06-19 Thread Ilya Karpov
Does anybody experience the problem of metering deserialization errors? пн, 17 июн. 2024 г. в 14:39, Ilya Karpov : > Hi all, > we are planning to use flink as a connector between kafka and > external systems. We use protobuf as a message format in kafka. If > non-backward compatible changes

A way to meter number of deserialization errors

2024-06-17 Thread Ilya Karpov
Hi all, we are planning to use flink as a connector between kafka and external systems. We use protobuf as a message format in kafka. If non-backward compatible changes occur we want to skip those messages ('protobuf.ignore-parse-errors' = 'true') but record an error and raise an alert. I didn't