[
https://issues.apache.org/jira/browse/KAFKA-14354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hector Geraldino updated KAFKA-14354:
-------------------------------------
Description: It would be useful to have a callback method added to the
Connector API, so connectors extending the SourceConnector and SinkConnector
classes can be notified when their connector instance is being deleted. This
will give a chance to connectors to perform any cleanup tasks (e.g. deleting
external resources, or deleting offsets) before the connector is completely
removed from the cluster. (was: KIP-795:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-795%3A+Add+public+APIs+for+AbstractCoordinator
The AbstractCoordinator should have a companion public interface that is part
of Kafka's public API, so backwards compatibility can be maintained in future
versions of the client libraries)
> Add delete callback method to Connector API
> -------------------------------------------
>
> Key: KAFKA-14354
> URL: https://issues.apache.org/jira/browse/KAFKA-14354
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Reporter: Hector Geraldino
> Assignee: Hector Geraldino
> Priority: Minor
>
> It would be useful to have a callback method added to the Connector API, so
> connectors extending the SourceConnector and SinkConnector classes can be
> notified when their connector instance is being deleted. This will give a
> chance to connectors to perform any cleanup tasks (e.g. deleting external
> resources, or deleting offsets) before the connector is completely removed
> from the cluster.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
