[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-25。"],[],[],null,["# ClickHouse\n\n| **Note:** Looker supports ClickHouse version 0.2 and higher.\n\nEncrypting network traffic\n--------------------------\n\nIt is a best practice to encrypt network traffic between the Looker application and your database. Consider one of the options described on the [Enabling secure database access](/looker/docs/enabling-secure-db-access) documentation page.\n\nTo enable SSL encryption on the server side, see the [ClickHouse Global Server Settings documentation](https://ClickHouse.yandex/docs/en/operations/server_settings/settings/#server_settings-openssl).\n\nUsers and security\n------------------\n\nFirst, configure your Looker user on the ClickHouse server. ClickHouse database users are not created with the `CREATE USER` command. Follow the [ClickHouse access rights documentation](https://clickhouse.yandex/docs/en/operations/access_rights/) to configure the `users` section in the `users.xml` file. Here is a basic example: \n\n \u003c!-- Users and ACL. --\u003e\n \u003cusers\u003e\n \u003clooker\u003e\n \u003cpassword\u003eCHANGEIT\u003c/password\u003e\n \u003cnetworks incl=\"networks\" /\u003e\n \u003cprofile\u003edefault\u003c/profile\u003e\n \u003cquota\u003edefault\u003c/quota\u003e\n \u003c/looker\u003e\n\n \u003cweb\u003e\n \u003cpassword\u003e\u003c/password\u003e\n \u003cnetworks incl=\"networks\" /\u003e\n \u003cprofile\u003eweb\u003c/profile\u003e\n \u003cquota\u003edefault\u003c/quota\u003e\n \u003callow_databases\u003e\n \u003cdatabase\u003etest\u003c/database\u003e\n \u003c/allow_databases\u003e\n \u003callow_dictionaries\u003e\n \u003cdictionary\u003etest\u003c/dictionary\u003e\n \u003c/allow_dictionaries\u003e\n \u003c/web\u003e\n \u003c/users\u003e\n\nAlso within this file, configure the appropriate database access. \n\n \u003callow_databases\u003e\n \u003cdatabase\u003edatabase_1\u003c/database\u003e\n \u003cdatabase\u003edatabase_2\u003c/database\u003e\n \u003cdatabase\u003edatabase_3\u003c/database\u003e\n \u003c/allow_databases\u003e\n\nCreating the Looker connection to your database\n-----------------------------------------------\n\nIn the **Admin** section of Looker, select **Connections** , and then click **Add Connection**.\n\nFill out the connection details. The majority of the settings are common to most database dialects. See the [Connecting Looker to your database](/looker/docs/connecting-to-your-db) documentation page for information. Some of the settings are described next:\n\n- **Dialect**: ClickHouse.\n- **Host**: Reachable hostname.\n- **Port** : Port on which the ClickHouse service is reachable over HTTP(S).\n - By default, HTTP connections will use 8123, and HTTPS will use 8443.\n - Port 9000 and 9440 are by default used by the ClickHouse command line client, but these ports cannot be used by Looker to connect to ClickHouse.\n - Your ClickHouse administrator may have chosen alternate ports with the [`http_port/https_port`](https://ClickHouse.yandex/docs/en/operations/server_settings/settings/#http-port-https-port) settings in the ClickHouse configuration. Ask your ClickHouse admin for the settings appropriate to your local configuration.\n- **Database** : Database name (must be one of the databases allowed in the `users.xml` file).\n- **Username**: Database username.\n- **Password**: Database password.\n- **Additional JDBC parameters**: (Optional) Additional JDBC string parameters.\n- **Maintenance Schedule**: ClickHouse does not support PDTs, so this setting can be ignored.\n- **SSL**: Check to connect to ClickHouse over SSL.\n- **Verify SSL**: (Optional) Check to enforce strict hostname verification on the ClickHouse server. Check this only if you are using an SSL certificate that is signed by a generally trusted Certificate Authority. If you are using a self-signed SSL certificate, leave it unchecked.\n\nTo verify that the connection is successful, click **Test** . See the [Testing database connectivity](/looker/docs/testing-db-connectivity) documentation page for troubleshooting information.\n\nTo save these settings, click **Connect**.\n\nFeature support\n---------------\n\nFor Looker to support some features, your database dialect must also support them.\n\nClickHouse supports the following features as of Looker 25.14:"]]