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 behave like “continue” when error occurs at Converter or SMT. The infrastructure should send the broken byte message directly to SinkTask. The benefits of having this additional option are: • Being user friendly. Connectors can handle broken record and hide that from clients • Providing more flexibility to SinkTask in terms of broken record handling Best, Zihan
