Перейти к основному содержимому
Перейти к основному содержимому

Looker

Partner Integration

Looker can connect to ClickHouse Cloud or on-premise deployment via the official ClickHouse data source.

1. Gather your connection details

To connect to ClickHouse with HTTP(S) you need this information:

Parameter(s)Description
HOST and PORTTypically, the port is 8443 when using TLS or 8123 when not using TLS.
DATABASE NAMEOut of the box, there is a database named default, use the name of the database that you want to connect to.
USERNAME and PASSWORDOut 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:

ClickHouse Cloud service connect button

Choose HTTPS. Connection details are displayed in an example curl command.

ClickHouse Cloud HTTPS connection details

If you are using self-managed ClickHouse, the connection details are set by your ClickHouse administrator.

2. Create a ClickHouse data source

Navigate to Admin -> Database -> Connections and click the "Add Connection" button in the top right corner.

Adding a new connection in Looker's database management interface

Choose a name for your data source, and select ClickHouse from the dialect drop-down. Enter your credentials in the form.

Specifying your ClickHouse credentials in Looker connection form

If you are using ClickHouse Cloud or your deployment requires SSL, make sure you have SSL turned on in the additional settings.

Enabling SSL for ClickHouse connection in Looker settings

Test your connection first, and, once it is done, connect to your new ClickHouse data source.

Testing and connecting to the ClickHouse data source

Now you should be able to attach ClickHouse Datasource to your Looker project.

3. Known limitations

  1. The following data types are handled as strings by default:
    • Array - serialization does not work as expected due to the JDBC driver limitations
    • Decimal* - can be changed to number in the model
    • LowCardinality(...) - can be changed to a proper type in the model
    • Enum8, Enum16
    • UUID
    • Tuple
    • Map
    • JSON
    • Nested
    • FixedString
    • Geo types
      • MultiPolygon
      • Polygon
      • Point
      • Ring
  2. Symmetric aggregate feature is not supported
  3. Full outer join is not yet implemented in the driver