ystem?
>
> Cheers,
>
> Chris
>
> On Thu, Apr 30, 2020 at 1:01 PM Zihan Li wrote:
>
> > Hi Chris and Andrew,
> >
> > Thanks a lot for your reply!
> >
> > I think in most cases it is easier to analysis broken records in an
> > external
&
t; KIP is trying to
> > achieve, only without needing any interface or behaviour changes in the
> > connectors. Yes,
> > you need to run more connectors, but in a distributed connect cluster,
> > that's easy to achieve.
> >
> > Thanks,
> > Andrew Schofi
> destination sink. It'd be nice if this were called out in the "Rejected
> Alternatives" section with a reason on why the changes proposed in the KIP
> are preferable, especially since it may still work as a viable workaround
> for users who are working on older vers
t;
> destination sink. It'd be nice if this were called out in the "Rejected>
> Alternatives" section with a reason on why the changes proposed in the KIP>
> are preferable, especially since it may still work as a viable workaround>
> for users who are working
FKA-9740
<https://issues.apache.org/jira/browse/KAFKA-9740>
Please share your thoughts about adding this new error handling option to Kafka
Connect.
Best,
Zihan
> On Mar 18, 2020, at 12:55 PM, Zihan Li wrote:
>
> Hi all,
>
> I'd like to use this thread to discuss KIP-582 Ad
Zihan Li created KAFKA-9740:
---
Summary: Add a "continue" option for Kafka Connect error handling
Key: KAFKA-9740
URL: https://issues.apache.org/jira/browse/KAFKA-9740
Project: Kafka
Hi all,
I'd like to use this thread to discuss KIP-582 Add a "continue" option for
Kafka Connect error handling, please see detail at:
https://cwiki.apache.org/confluence/x/XRvcC
<https://cwiki.apache.org/confluence/x/XRvcC>
Best,
Zihan Li
Hi,
I’m writing to request permission to create KIP.
My proposal:
Currently there are two error handling options in Kafka connect, “none” and
“all”. Option “none” will config the connector to fail fast, and option “all”
will ignore broken records.
I'm proposing a third option, which should
