2017-12-28 15:13:23 +00:00
|
|
|
<a name="settings"></a>
|
|
|
|
|
|
|
|
|
|
# Settings
|
|
|
|
|
|
|
|
|
|
There are multiple ways to make all the settings described below.
|
|
|
|
|
Settings are configured in layers, so each subsequent layer redefines the previous settings.
|
|
|
|
|
|
|
|
|
|
Ways to configure settings, in order of priority:
|
|
|
|
|
|
|
|
|
|
- Settings in the server config file.
|
|
|
|
|
|
2018-03-26 14:00:55 +00:00
|
|
|
Set via user profiles.
|
2017-12-28 15:13:23 +00:00
|
|
|
|
2018-03-26 14:00:55 +00:00
|
|
|
- For the session.
|
2017-12-28 15:13:23 +00:00
|
|
|
|
|
|
|
|
Send ` SET setting=value` from the ClickHouse console client in interactive mode.
|
|
|
|
|
Similarly, you can use ClickHouse sessions in the HTTP protocol. To do this, you need to specify the `session_id` HTTP parameter.
|
|
|
|
|
|
|
|
|
|
- For a query.
|
|
|
|
|
- When starting the ClickHouse console client in non-interactive mode, set the startup parameter `--setting=value`.
|
|
|
|
|
- When using the HTTP API, pass CGI parameters (`URL?setting_1=value&setting_2=value...`).
|
|
|
|
|
|
|
|
|
|
Settings that can only be made in the server config file are not covered in this section.
|
|
|
|
|
|
