Thanks Guozhang. Great meetup.
-aj
On Tue, Sep 1, 2020 at 1:30 PM Guozhang Wang wrote:
> Hello folks,
>
> The Bay Area Kafka meetup will continue to be hosted online this month,
> tomorrow (Sep 2nd) at 5:00pm. This time we will have guest speakers from
> Twitter to talk about their journey
Hello folks,
The Bay Area Kafka meetup will continue to be hosted online this month,
tomorrow (Sep 2nd) at 5:00pm. This time we will have guest speakers from
Twitter to talk about their journey to adopt Apache Kafka.
*RSVP*:
https://www.meetup.com/KafkaBayArea/events/272643868/
*Date*
5:00pm,
Hi John
Please find my inline response below
Regards and Thanks
Deepak Raghav
On Tue, Sep 1, 2020 at 8:22 PM John Roesler wrote:
> Hi Deepak,
>
> It sounds like you're saying that the exception handler is
> correctly indicating that Streams should "Continue", and
> that if you stop the app
Hi Deepak,
It sounds like you're saying that the exception handler is
correctly indicating that Streams should "Continue", and
that if you stop the app after handling an exceptional
record but before the next commit, Streams re-processes the
record?
If that's what you're seeing, then it's how
Hi,
So, I started testing the steps suggested above to upgrade Kafka-Zk clusters
with confluent-kafka-2.12 which will install v5.5.1 and was able to perform a
rolling upgrade of Kafka clusters in a test env. And they are currently running
with "inter.broker.protocol.version=1.1".
Before I
Hi Team
Just a reminder.
Can you please help me with this?
Regards and Thanks
Deepak Raghav
On Tue, Sep 1, 2020 at 1:44 PM Deepak Raghav
wrote:
> Hi Team
>
> I have created a CustomExceptionHandler class by
> implementing DeserializationExceptionHandler interface to handle the
> exception
Hi Deepak,
Do you return DeserializationHandlerResponse.CONTINUE or
DeserializationHandlerResponse.FAIL in your CustomExceptionHandler?
With DeserializationHandlerResponse.CONTINUE, the processing of records
should not stop and after the next offset commit the bad records should
not be read
Hi Team
I have created a CustomExceptionHandler class by
implementing DeserializationExceptionHandler interface to handle the
exception during deserialization time.
But the problem with this approach is that if there is some exception
raised for some record and after that stream is stopped and
