Skip to main content

Sink connectors13

A sink connector reads Kafka topics and writes the records to a target system. Each page covers creating the connector and its settings.

PostgreSQLDeliver change data from Kafka topics into tables in a PostgreSQL schema, after you grant the connector user rights on that schema.MySQLDeliver change data from Kafka topics into MySQL tables, and map each topic to a new or an existing table.MariaDBDeliver change data from Kafka topics into MariaDB tables, and choose for each topic whether to create a table or write to an existing one.SQL ServerDeliver change data from Kafka topics into SQL Server tables, with one target table for each topic you read.MongoDBDeliver change data from Kafka topics into MongoDB collections over a connection URL, with one collection for each topic.ClickHouse (logs)Keep every change from your Kafka topics as a new row in existing ClickHouse tables, for change history and audit.ClickHouse (Replication)Keep the current state of your source tables in existing ClickHouse tables, from the Kafka topics that a source connector writes.IcebergKeep Iceberg tables in S3 storage in step with your source tables, with updates and deletes applied through an Iceberg catalog.Iceberg (logs)Append every record of your Kafka topics to Iceberg tables in S3 storage, as a change log in the file format you choose.OpenSearchSend the changes in your Kafka topics to OpenSearch, in a database from FPT Database Engine or one you reach by connection string.ElasticsearchIndex the changes in your Kafka topics in Elasticsearch, mapping each topic to a new or an existing index.S3Store the changes in your Kafka topics as files in an S3 bucket, in the file format and timezone you choose.RedisWrite the changes in your Kafka topics to a Redis database, with the Redis command you choose for storing each record.