You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/doc/30-reference/30-sql/80-setting-cmds/set-global.md
+8-8
Original file line number
Diff line number
Diff line change
@@ -2,30 +2,30 @@
2
2
title: SET
3
3
---
4
4
5
-
Changes the value of a session-level or global-level setting. To show all the current settings, use [SHOW SETTINGS](show-settings.md).
5
+
Changes the value of a session-level or cluster-level setting. To show all the current settings, use [SHOW SETTINGS](show-settings.md).
6
6
7
7
## Syntax
8
8
9
9
```sql
10
10
SET [GLOBAL] <setting_name>=<new_value>;
11
11
```
12
12
13
-
`GLOBAL`: Include this option when you change the value of a global-level setting. If you include this option preceding a session-level setting, the setting will become a global-level setting.
13
+
`GLOBAL`: Include this option when you change the value of a global-level setting. If you include this option preceding a session-level setting, the setting will become a cluster-level(or global-level) setting.
14
14
15
15
:::note
16
-
A global-level setting is a cluster setting and the value will be stored in the `metasrv`.
16
+
A cluster-level setting is a cluster setting and the value will be stored in the meta service.
17
17
:::
18
18
19
19
## Examples
20
20
21
-
The following example sets the `skip_header` setting to 1:
21
+
The following example sets the `max_threads` setting to `4`:
22
22
23
23
```sql
24
-
SETskip_header=1;
24
+
SETmax_threads=4;
25
25
```
26
26
27
-
The following example sets the `skip_header` setting to 1 and changes it to be a global-level setting:
27
+
The following example sets the `max_threads` setting to `4` and changes it to be a cluster-level setting:
0 commit comments