Interfaces and drivers supported in Managed ClickHouse®
Find out what technologies and tools you can use to interact with Managed ClickHouse®.
Interfaces (protocols)
Managed ClickHouse® supports the following fundamental underlying interfaces (protocols):
HTTPSNative TCPMySQL InterfaceArrow Flight
Note
Arrow Flight is available for new services running ClickHouse 25.8 LTS. Its endpoint, like
the endpoint of every other interface, is listed in the service components, see
Endpoints for each interface.
Note
For security reasons, TLS is required to connect to Managed ClickHouse.
The following interfaces (protocols) are not supported:
HTTPgRPCPostgreSQL
For the full list of interfaces and protocols supported in ClickHouse, see Drivers and Interfaces.
Endpoints for each interface
Every interface is exposed as a component of your service: one host, with one port per
interface. Ports are assigned per service, so read them from your own service instead of
hardcoding them. ClickHouse commands live under exo x in the
Exoscale CLI 1.97 or later:
exo x get-dbaas-service-clickhouse my-clickhouse -z ch-gva-2 -q 'components'| Component | Interface (protocol) |
|---|---|
clickhouse | Native TCP over TLS, used by clickhouse-client |
clickhouse_https | HTTPS, used by most drivers and by curl |
clickhouse_mysql | MySQL Interface |
clickhouse_arrowflight | Arrow Flight |
The same connection details are available through the Exoscale API.
Drivers (libraries)
There are a number of drivers (libraries) that use one of the fundamental underlying interfaces supported in Managed ClickHouse under the hood. It’s up to you to pick up a driver (library) of your choice and use it for connecting to your Managed ClickHouse service.
- See how to use different drivers (libraries) for connecting to Managed ClickHouse.
- For the full list of drivers and libraries that support connecting to ClickHouse, see Drivers and Interfaces.
Note
You can connect to Managed ClickHouse with any driver that uses TLS and one of the supported protocols.