Integrating Confluent platform with ClickHouse
Prerequisites
We assume you are familiar with:
- ClickHouse Connector Sink
- Confluent Platform and Custom Connectors.
The official Kafka connector from ClickHouse with Confluent Platform
Installing on Confluent platform
This is meant to be a quick guide to get you started with the ClickHouse Sink Connector on Confluent Platform. For more details, please refer to the official Confluent documentation.
Create a Topic
Creating a topic on Confluent Platform is fairly simple, and there are detailed instructions here.
Important notes
- The Kafka topic name must be the same as the ClickHouse table name. The way to tweak this is by using a transformer (for example
ExtractTopic). - More partitions does not always mean more performance - see our upcoming guide for more details and performance tips.
Install connector
You can download the connector from our repository - please feel free to submit comments and issues there as well!
Navigate to "Connector Plugins" -> "Add plugin" and using the following settings:
Example:
Gather your connection details
To connect to ClickHouse with HTTP(S) you need this information:
| Parameter(s) | Description |
|---|---|
HOST and PORT | Typically, the port is 8443 when using TLS or 8123 when not using TLS. |
DATABASE NAME | Out of the box, there is a database named default, use the name of the database that you want to connect to. |
USERNAME and PASSWORD | Out of the box, the username is default. Use the username appropriate for your use case. |
The details for your ClickHouse Cloud service are available in the ClickHouse Cloud console. Select a service and click Connect:
Choose HTTPS. Connection details are displayed in an example curl command.
If you are using self-managed ClickHouse, the connection details are set by your ClickHouse administrator.
Configure the connector
Navigate to Connectors -> Add Connector and use the following settings (note that the values are examples only):
Specify the connection endpoints
You need to specify the allow-list of endpoints that the connector can access.
You must use a fully-qualified domain name (FQDN) when adding the networking egress endpoint(s).
Example: u57swl97we.eu-west-1.aws.clickhouse.com:8443
You must specify HTTP(S) port. The Connector doesn't support Native protocol yet.
You should be all set!
Known limitations
- Custom Connectors must use public internet endpoints. Static IP addresses aren't supported.
- You can override some Custom Connector properties. See the fill list in the official documentation.
- Custom Connectors are available only in some AWS regions
- See the list of Custom Connectors limitations in the official docs