Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

uence/display/KAFKA/KIP-419%3A+Safely+notify+Kafka+Connect+SourceTask+is+stopped, > just took a different approach. > > > From: dev@kafka.apache.org At: 11/29/22 15:31:31 UTC-5:00To: > dev@kafka.apache.org > Subject: Re: [DISCUSS] KIP-883: Add delete callback method to Connector API > >

Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

+Safely+notify+Kafka+Connect+SourceTask+is+stopped, just took a different approach. From: dev@kafka.apache.org At: 11/29/22 15:31:31 UTC-5:00To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP-883: Add delete callback method to Connector API Hi Hector, Thanks for the KIP! Here are my initial

Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

ctor Geraldino (BLOOMBERG/ 919 3RD A) At: 11/16/22 17:38:59 > UTC-5:00To: dev@kafka.apache.org > Subject: Re: [DISCUSS] KIP-883: Add delete callback method to Connector API > > Hi Mickael, > > I agree that the new STOPPED state proposed in KIP-875 will improve the > connector l

Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

e existing one. Please let me know what your thoughts are. Cheers, Hector From: Hector Geraldino (BLOOMBERG/ 919 3RD A) At: 11/16/22 17:38:59 UTC-5:00To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP-883: Add delete callback method to Connector API Hi Mickael, I agree that the new STO

Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

t: 11/16/22 11:13:17 UTC-5:00To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP-883: Add delete callback method to Connector API Hi Hector, Thanks for the KIP. One tricky aspect is that currently there's no real way to stop a connector so to do so people often just delete them temporarily. KIP

Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

n overloaded method (with a default implementation) that connectors can override. Wdyt? From: dev@kafka.apache.org At: 11/15/22 11:40:26 UTC-5:00To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP-883: Add delete callback method to Connector API Hey Hector, Thanks for the KIP. I have a minor

Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

shoold keeping it more > > narrow-focused on providing a callback mechanism for when connectors are > > deleted, and what the expectations are around this newly introduced method. > > What do you think? > > > > > > From: dev@kafka.apache.org At: 11/09/22 16:55:04

Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

From: dev@kafka.apache.org At: 11/09/22 16:55:04 UTC-5:00To: > dev@kafka.apache.org > Subject: Re: [DISCUSS] KIP-883: Add delete callback method to Connector API > > Hi Hector, > > Thanks for the KIP! > > This is certainly missing functionality from the native Connect fr

Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

At: 11/09/22 16:55:04 UTC-5:00To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP-883: Add delete callback method to Connector API Hi Hector, Thanks for the KIP! This is certainly missing functionality from the native Connect framework, and we should try to make it possible to inform connectors

Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

Hi Hector, Thanks for the KIP! This is certainly missing functionality from the native Connect framework, and we should try to make it possible to inform connectors about this part of their lifecycle. However, as with most functionality that was left out of the initial implementation of the

[DISCUSS] KIP-883: Add delete callback method to Connector API

Hi everyone, I've submitted KIP-883, which introduces a callback to the public Connector API called when deleting a connector: https://cwiki.apache.org/confluence/display/KAFKA/KIP-883%3A+Add+delete+callback+method+to+Connector+API It adds a new `deleted()` method (open to better naming