Connecteurs de destination pour l’exportation

Welcome to the final lesson on Kafka Connect! We've learned how to bring data into Kafka using Source Connectors. Now, let's explore how to get data out.

This lesson focuses on Sink Connectors, which are essential for moving data from your Kafka topics to external systems like databases, data warehouses, or analytics platforms.

Imagine you have real-time data streaming into Kafka, but your business intelligence tools or legacy applications need that data in a different system.

• Integration: Connect Kafka to almost any data store.
• No Custom Code: Avoid writing complex consumer applications for common destinations.
• Reliability: Built-in fault tolerance and delivery guarantees.
• Scalability: Easily scale data export by adding more connector tasks.

A Sink Connector acts like a specialized Kafka consumer. Here's the basic workflow:

1. The connector runs within a Kafka Connect worker.
2. It subscribes to one or more Kafka topics.
3. It consumes messages from these topics.
4. It transforms (if configured) and writes the data to the target external system.
5. It manages Kafka offsets, ensuring data is processed reliably.

Kafka Connect offers a rich ecosystem of pre-built sink connectors for a wide variety of destinations. Some popular examples include:

• Databases: PostgreSQL, MySQL, Oracle, SQL Server (via JDBC)
• Cloud Storage: Amazon S3, Google Cloud Storage, Azure Blob Storage
• Search Engines: Elasticsearch, Solr
• Data Warehouses: Snowflake, Redshift
• Other Systems: HDFS, JMS queues, HTTP endpoints

Configuring a sink connector is similar to source connectors. You define its properties in a JSON file or directly via the Connect REST API. Key properties include:

• name: Unique name for your connector.
• connector.class: The specific connector implementation (e.g., JdbcSinkConnector).
• topics or topics.regex: The Kafka topics to read from.
• key.converter & value.converter: How to deserialize data from Kafka.

Let's look at a simple example: the FileStreamSinkConnector. This built-in connector writes data from a Kafka topic to a local file. It's great for observing how sink connectors work.

Here's a basic configuration JSON for it:

Once you have your connector configuration (like the file-sink-config.json above), you deploy it to your Kafka Connect cluster using a curl command against the Connect REST API:

This command tells the Connect cluster to create and start a new connector instance based on your configuration.

When a sink connector reads data from Kafka, it uses converters to deserialize the message keys and values. Common converters include:

• StringConverter: For plain text data.
• JsonConverter: For JSON formatted data.
• AvroConverter: For Avro-serialized data (often with Schema Registry).

The connector then takes this deserialized data and formats it appropriately for the target system (e.g., SQL INSERT statements for a database sink).

Kafka Connect sink connectors are designed for reliability:

• At-Least-Once Delivery: Most sink connectors guarantee that each message will be delivered to the destination at least once, even if failures occur.
• Offset Management: Connectors automatically commit offsets to Kafka, tracking what data has been successfully processed.
• Error Handling: Connectors can be configured to retry failed operations or send problematic messages to a Dead Letter Queue (DLQ) for later inspection.

Let's check your understanding of Kafka Connect Sink Connectors!

Great job! You've now grasped the core concepts of Kafka Connect Sink Connectors.

• Sink Connectors export data from Kafka topics to various external systems.
• They provide a reliable, scalable, and code-free way to integrate Kafka with your data ecosystem.
• Configuration involves specifying the connector class, topics, and destination-specific properties.
• They handle data deserialization, formatting, and ensure delivery guarantees.

Kafka Connect significantly simplifies building robust data pipelines!