Skip to content

Commit 8f8220a

Browse files
authored
Update set-global.md
1 parent fd4c6f9 commit 8f8220a

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

docs/doc/30-reference/30-sql/80-setting-cmds/set-global.md

+8-8
Original file line numberDiff line numberDiff line change
@@ -2,30 +2,30 @@
22
title: SET
33
---
44

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).
66

77
## Syntax
88

99
```sql
1010
SET [GLOBAL] <setting_name> = <new_value>;
1111
```
1212

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.
1414

1515
:::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.
1717
:::
1818

1919
## Examples
2020

21-
The following example sets the `skip_header` setting to 1:
21+
The following example sets the `max_threads` setting to `4`:
2222

2323
```sql
24-
SET skip_header = 1;
24+
SET max_threads = 4;
2525
```
2626

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:
2828

2929
```sql
30-
SET GLOBAL skip_header = 1;
31-
```
30+
SET GLOBAL max_threads = 4;
31+
```

0 commit comments

Comments
 (0)