Connect Looker to your ClickHouse database to analyze your data and build interactive dashboards. This connection helps make your ClickHouse data available for reporting and analysis within Looker, supporting direct data-driven decisions.
This page guides you through configuring your ClickHouse instance and Looker connection settings, including how to encrypt network traffic, define user permissions, and review supported features. Looker supports ClickHouse version 0.2 or later, and ClickHouse 26+ using modernized JDBC drivers and symmetric aggregation support.
Encrypting network traffic
It is a best practice to encrypt network traffic between the Looker application and your database. Consider one of the options that are described on the Enabling secure database access documentation page.
To enable SSL encryption on the server side, see the ClickHouse Global Server Settings documentation.
Users and security
First, configure your Looker user on the ClickHouse server. ClickHouse database users can be configured by using SQL (CREATE USER) or through the users section in the users.xml file. Follow the ClickHouse access rights documentation to configure user access. The following basic example uses users.xml:
<!-- Users and ACL. -->
<users>
<looker>
<password>CHANGEIT</password>
<networks incl="networks" />
<profile>default</profile>
<quota>default</quota>
</looker>
<web>
<password></password>
<networks incl="networks" />
<profile>web</profile>
<quota>default</quota>
<allow_databases>
<database>test</database>
</allow_databases>
<allow_dictionaries>
<dictionary>test</dictionary>
</allow_dictionaries>
</web>
</users>
Also within this file, configure the appropriate database access:
<allow_databases>
<database>database_1</database>
<database>database_2</database>
<database>database_3</database>
</allow_databases>
Creating the Looker connection to your database
In the Admin section of Looker, select Connections, and then click Add Connection.
Fill out the connection details. The majority of the settings are common to most database dialects. See the Connecting Looker to your database documentation page for information. Some of the settings are described next:
- Dialect: Select ClickHouse 26+ or ClickHouse.
- Host: Reachable hostname or IP address of the ClickHouse server.
- Port: Port on which the ClickHouse service is reachable over HTTP(S).
- By default, HTTP connections use
8123, and HTTPS connections use8443. - Ports
9000and9440are by default used by the ClickHouse native TCP command line client, but HTTP(S) ports must be used by Looker to connect to ClickHouse. - Your ClickHouse administrator may have chosen alternate ports with the
http_portorhttps_portsettings in the ClickHouse configuration. Ask your ClickHouse admin for the settings that are appropriate to your configuration.
- By default, HTTP connections use
- Database: Database name (must be one of the databases that's allowed in your ClickHouse permissions).
- Username: Database username.
- Password: Database password.
- SSL: Check to connect to ClickHouse over SSL/TLS.
- Verify SSL: (Optional) Check to enforce strict SSL certificate and hostname verification on the ClickHouse server. Select Verify SSL only if you're using an SSL certificate that is signed by a generally trusted Certificate Authority. If you're using a self-signed SSL certificate, leave this setting unchecked.
- Additional JDBC parameters: (Optional) Additional JDBC string parameters. See the Supported JDBC parameters section on this page for the list of parameters that Looker supports.
To verify that the connection is successful, click the Test Connection button in the Status details section at the bottom of the Connection Settings page.
If Looker displays Can Connect, press Connect to create the connection.
Your database connection is then added to the list on the Looker Connections Admin page.
Supported JDBC parameters
For ClickHouse, Looker supports the following JDBC parameters in the Additional JDBC parameters field for the connection. See the documentation for your database for information on these parameters.
ClickHouse 26+ parameters
async_insertautoCommitcompresscompress_algorithmcompress_levelconnect_timeoutconnection_timeoutcontinueBatchOnErrorcreateDatabaseIfNotExistcustom_settingsdatabasedatabaseTermexternalDatabasefetchSizeformatjdbcCompliantkeep_alive_timeoutmax_buffer_sizemax_execution_timemax_result_bytesmax_result_rowsmax_threadsnamedParameterquery_timeoutreceive_timeoutresult_overflow_moderetrysession_checksession_idsession_timeoutsession_timezonesocket_timeoutsslsslmodetransactionSupportuse_server_time_zoneuse_time_zonewait_for_async_insertwrapperObject
ClickHouse (Legacy) parameters
beta.row_binary_for_simple_insertcompressconnection_timeoutcontinueBatchOnErrorcreateDatabaseIfNotExistcustom_http_headerscustom_http_paramsdefault_query_settingsdisable_frameworks_detectionjdbc_ignore_unsupported_valuesjdbc_resultset_auto_closejdbc_sql_parserjdbc_use_max_result_rowsjdbcCompliancemax_execution_timepasswordsession_timezonesocket_timeouttypeMappingsuse_server_time_zoneuse_time_zoneuserwrapperObject
Feature support
For Looker to support some features, your database dialect must also support them.
ClickHouse 26+ feature support
ClickHouse 26+ supports the following features as of Looker 26.18:
| Feature | Supported? |
|---|---|
| Looker (Google Cloud core) | |
| Symmetric aggregates | |
| Derived tables | |
| Persistent SQL derived tables | |
| Persistent native derived tables | |
| Stable views | |
| Query killing | |
| SQL-based pivots | |
| Time zones | |
| SSL | |
| Subtotals | |
| JDBC additional params | |
| Case-sensitive | |
| Location type | |
| List type | |
| Percentile | |
| Distinct percentile | |
| SQL Runner Show Processes | |
| SQL Runner Describe Table | |
| SQL Runner Show Indexes | |
| SQL Runner Select 10 | |
| SQL Runner Count | |
| SQL Explain | |
| OAuth 2.0 credentials | |
| Context comments | |
| Connection pooling | |
| HLL sketches | |
| Aggregate awareness | |
| Incremental PDTs | |
| Milliseconds | |
| Microseconds | |
| Materialized views | |
| Period-over-period measures | |
| Approximate count distinct | |
| In-database analytic models | |
| Custom calendars |
ClickHouse feature support
ClickHouse supports the following features as of Looker 26.18:
| Feature | Supported? |
|---|---|
| Looker (Google Cloud core) | |
| Symmetric aggregates | |
| Derived tables | |
| Persistent SQL derived tables | |
| Persistent native derived tables | |
| Stable views | |
| Query killing | |
| SQL-based pivots | |
| Time zones | |
| SSL | |
| Subtotals | |
| JDBC additional params | |
| Case-sensitive | |
| Location type | |
| List type | |
| Percentile | |
| Distinct percentile | |
| SQL Runner Show Processes | |
| SQL Runner Describe Table | |
| SQL Runner Show Indexes | |
| SQL Runner Select 10 | |
| SQL Runner Count | |
| SQL Explain | |
| OAuth 2.0 credentials | |
| Context comments | |
| Connection pooling | |
| HLL sketches | |
| Aggregate awareness | |
| Incremental PDTs | |
| Milliseconds | |
| Microseconds | |
| Materialized views | |
| Period-over-period measures | |
| Approximate count distinct | |
| In-database analytic models | |
| Custom calendars |
Next steps
After you have completed the database connection, configure authentication options.