This page is meant as a template for writing a KIP. To create a KIP choose Tools->Copy on this page and modify with your content and replace the heading with the next KIP number and a description of your issue. Replace anything in italics with your own description.

Status

Current state: "Under Discussion"

Discussion thread: here [Change the link from the KIP proposal email archive to your own email thread]

...

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

The base class for all Source and Sink connectors is the org.apache.kafka.connect.connector.Connector abstract class. This class defines a few abstract methods (e.g. void start(Map<String, String> props) and void stop()) that are then implemented by Connectors and are invoked as part of their lifecycle.

As connectors interact with external systems, they sometimes need to provision external resources. We can think of a Sink connector that creates new queues in the Messaging System it wants to write messages to; an Object Store Sink connector that creates new buckets to store its messages; a Source connector that activates an account before requesting data from a source system. A more concrete example is a source connector that audits database changes by creating an "audit" table and database triggers which inserts the row-level updates to that table. In many cases, creating these resources is an idempotent operation. In other cases, the targeted system can be queried beforehand, and resources are provisioned only if they not exist.

The connector void start(Map<String, String> props) method is invoked when the connector is first started, or when it is restarted by the Worker (e.g. when the connector configuration changes). Similarly, the void stop() method is invoked when the connector is stopped by the Worker (e.g.  (for example, when the connector configuration changes).

ese are just a small and triggers  and  and   creating new queues on the Some connectors perform  a connector starts, it can perform ome connectors  creating new connectors, the 've some custom connectors that require provisioning external resources 

(think of creating queues, S3 buckets, or activating accounts) when the 

connector instance is created, but also need to cleanup these resources 

(delete, deactivate) when the connector instance is deleted.

  entry points for Connector implementations ,he a new connector is created, or an Describe the problems you are trying to solve.

Public Interfaces

Briefly list any new interfaces that will be introduced as part of this proposal or any existing interfaces that will be removed or changed. The purpose of this section is to concisely call out the public contract that will come along with this feature.

...