This is an automated email from the ASF dual-hosted git repository.
morningman pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new 355d2ab3a27 [fix] correct table-function, table-valued-function, and
SQL-statement doc errors (#3715)
355d2ab3a27 is described below
commit 355d2ab3a27443f01f7f6c9b46105d371a8424b2
Author: boluor <[email protected]>
AuthorDate: Wed May 20 09:57:55 2026 -0700
[fix] correct table-function, table-valued-function, and SQL-statement doc
errors (#3715)
## Summary
Fixes 23 small documentation issues across the table-functions,
table-valued-functions, and SQL-statement (account-management,
cluster-management) references. Each item below is independent.
### table-functions
- **explode-bitmap.md** — a stray sentence describing the
*outer-variant* behavior was sitting in the non-outer doc; removed.
- **explode-outer.md** — frontmatter title was `"EXPLODE-OUTER"`
(hyphen); corrected to `"EXPLODE_OUTER"`. The Syntax line and three
lateral-view examples invoked `explode(...)` rather than
`explode_outer(...)`; corrected.
- **explode-json-array-int-outer.md** — Description referenced `explode`
(non-outer) instead of `explode_outer`.
- **explode-map.md** — Examples 1 and 2 invoked `explode_map_outer(...)`
in this non-outer doc; changed to `explode_map(...)`.
- **unnest.md** — Example 3's result table had columns labeled `ord` /
`tag` swapped vs the underlying values; header labels reordered. Also
frontmatter `language: \"en-US\"` → `\"en\"`.
### table-valued-functions
- **frontends.md** — Return Value table was missing the
`CurrentConnected` field; added.
- **numbers.md** — Syntax `[, \"<const_value>\" = \"<const_value>\" ]`
placed the placeholder on the KEY side; the KEY is the literal string
`\"const_value\"`. Corrected.
- **local.md** — a stray fragment `+---+---+---+` immediately followed
by an orphan closing fence; removed.
- **query.md** — a result block was opened with a plain ``` fence (no
language hint); changed to ```text for consistency with sibling docs.
### sql-statements
- **ALTER-WORKLOAD-POLICY.md** — frontmatter description and body said
\"Workload Group\" (this doc is for Workload Policy); corrected. Code
fence tagged as ```Java for a SQL example; corrected to ```sql.
- **REVOKE-FROM.md** — access-control note text said "perform the GRANT
operation"; corrected to "perform the REVOKE operation".
- **ALTER-USER.md** — garbled sentence `\"This command give over
supports modifying user roles from versions 2.0…\"` rewritten as
`\"Starting from version 2.0, this command no longer supports modifying
user roles…\"`. Two full-width pipes `｜` in the `PASSWORD_LOCK_TIME`
syntax / description block replaced with ASCII `|`.
- **CREATE-USER.md** — same full-width-pipe fix in the same syntax
block.
- **ALTER-WORKLOAD-GROUP.md / CREATE-WORKLOAD-GROUP.md** — a full-width
comma `，` in English prose replaced with ASCII `, and `.
- **CREATE-RESOURCE.md** — parameter table heading read `1.\`<type>\``
but the immediately following text describes `<property>`; corrected.
- **ADD-BROKER.md** — Syntax `\"host>:<ipc_port>\"` was missing the
opening `<`; corrected. Two examples omitted the required
`<broker_name>` argument; added a placeholder name.
- **ADD-BACKEND.md** — Usage Notes list had two items both numbered
`3.`; renumbered the trailing items.
- **DROP-USER.md** — Syntax wrapped the `<user_identity>` placeholder in
extra single quotes; removed for consistency with the other
account-management docs.
- **SHOW-COMPUTE-GROUPS.md** — result-table header column widths were
off by 1, so the pipes didn't align with the rulers; corrected.
## Test plan
- [ ] CI doc build passes
- [ ] Spot-check the affected pages render correctly (titles, fixed
examples, added frontends row, syntax punctuation, list numbering,
aligned compute-groups result table)
---
docs/sql-manual/sql-functions/table-functions/explode-bitmap.md | 1 -
.../sql-functions/table-functions/explode-json-array-double.md | 2 +-
.../sql-functions/table-functions/explode-json-array-int-outer.md | 2 +-
.../sql-functions/table-functions/explode-json-array-int.md | 2 +-
.../sql-functions/table-functions/explode-json-array-json.md | 2 +-
.../sql-functions/table-functions/explode-json-array-string.md | 2 +-
docs/sql-manual/sql-functions/table-functions/explode-map.md | 4 ++--
docs/sql-manual/sql-functions/table-functions/explode-outer.md | 8 ++++----
docs/sql-manual/sql-functions/table-valued-functions/frontends.md | 1 +
docs/sql-manual/sql-functions/table-valued-functions/numbers.md | 2 +-
docs/sql-manual/sql-statements/account-management/ALTER-USER.md | 6 +++---
docs/sql-manual/sql-statements/account-management/CREATE-USER.md | 4 ++--
docs/sql-manual/sql-statements/account-management/DROP-USER.md | 2 +-
docs/sql-manual/sql-statements/account-management/GRANT-TO.md | 2 +-
docs/sql-manual/sql-statements/account-management/REVOKE-FROM.md | 2 +-
.../cluster-management/compute-management/ALTER-WORKLOAD-GROUP.md | 2 +-
.../compute-management/ALTER-WORKLOAD-POLICY.md | 6 +++---
.../cluster-management/compute-management/CREATE-RESOURCE.md | 2 +-
.../compute-management/CREATE-WORKLOAD-GROUP.md | 2 +-
.../cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md | 2 +-
.../cluster-management/instance-management/ADD-BACKEND.md | 6 +++---
.../cluster-management/instance-management/ADD-BROKER.md | 6 +++---
.../sql-manual/sql-functions/table-functions/explode-map.md | 4 ++--
.../sql-manual/sql-functions/table-functions/explode-outer.md | 8 ++++----
.../sql-manual/sql-functions/table-valued-functions/numbers.md | 2 +-
.../sql-manual/sql-statements/account-management/ALTER-USER.md | 4 ++--
.../sql-manual/sql-statements/account-management/CREATE-USER.md | 4 ++--
.../compute-management/ALTER-WORKLOAD-POLICY.md | 4 ++--
.../cluster-management/instance-management/ADD-BROKER.md | 4 ++--
.../sql-manual/sql-functions/table-valued-functions/numbers.md | 2 +-
.../sql-manual/sql-statements/account-management/ALTER-USER.md | 4 ++--
.../sql-manual/sql-statements/account-management/CREATE-USER.md | 4 ++--
.../compute-management/ALTER-WORKLOAD-POLICY.md | 4 ++--
.../cluster-management/instance-management/ADD-BROKER.md | 4 ++--
.../sql-manual/sql-functions/table-valued-functions/numbers.md | 2 +-
.../sql-manual/sql-statements/account-management/ALTER-USER.md | 4 ++--
.../sql-manual/sql-statements/account-management/CREATE-USER.md | 4 ++--
.../compute-management/ALTER-WORKLOAD-POLICY.md | 4 ++--
.../cluster-management/instance-management/ADD-BROKER.md | 4 ++--
.../sql-manual/sql-functions/table-functions/explode-map.md | 4 ++--
.../sql-manual/sql-functions/table-functions/explode-outer.md | 8 ++++----
.../sql-manual/sql-functions/table-valued-functions/numbers.md | 2 +-
.../sql-manual/sql-statements/account-management/ALTER-USER.md | 4 ++--
.../sql-manual/sql-statements/account-management/CREATE-USER.md | 4 ++--
.../compute-management/ALTER-WORKLOAD-POLICY.md | 4 ++--
.../cluster-management/instance-management/ADD-BROKER.md | 4 ++--
.../sql-manual/sql-functions/table-valued-functions/frontends.md | 1 +
.../sql-manual/sql-functions/table-valued-functions/numbers.md | 2 +-
.../sql-manual/sql-statements/account-management/ALTER-USER.md | 6 +++---
.../sql-manual/sql-statements/account-management/CREATE-USER.md | 4 ++--
.../sql-manual/sql-statements/account-management/DROP-USER.md | 2 +-
.../sql-manual/sql-statements/account-management/GRANT-TO.md | 2 +-
.../sql-manual/sql-statements/account-management/REVOKE-FROM.md | 2 +-
.../compute-management/ALTER-WORKLOAD-POLICY.md | 4 ++--
.../cluster-management/compute-management/CREATE-RESOURCE.md | 2 +-
.../cluster-management/instance-management/ADD-BACKEND.md | 6 +++---
.../cluster-management/instance-management/ADD-BROKER.md | 6 +++---
.../sql-manual/sql-functions/table-valued-functions/frontends.md | 1 +
.../sql-manual/sql-functions/table-valued-functions/numbers.md | 2 +-
.../sql-manual/sql-statements/account-management/ALTER-USER.md | 6 +++---
.../sql-manual/sql-statements/account-management/CREATE-USER.md | 4 ++--
.../sql-manual/sql-statements/account-management/DROP-USER.md | 2 +-
.../sql-manual/sql-statements/account-management/GRANT-TO.md | 2 +-
.../sql-manual/sql-statements/account-management/REVOKE-FROM.md | 2 +-
.../compute-management/ALTER-WORKLOAD-POLICY.md | 6 +++---
.../cluster-management/compute-management/CREATE-RESOURCE.md | 2 +-
.../cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md | 2 +-
.../cluster-management/instance-management/ADD-BACKEND.md | 6 +++---
.../cluster-management/instance-management/ADD-BROKER.md | 6 +++---
.../sql-manual/sql-functions/table-functions/explode-bitmap.md | 1 -
.../sql-functions/table-functions/explode-json-array-double.md | 2 +-
.../sql-functions/table-functions/explode-json-array-int-outer.md | 2 +-
.../sql-functions/table-functions/explode-json-array-int.md | 2 +-
.../sql-functions/table-functions/explode-json-array-json.md | 2 +-
.../sql-functions/table-functions/explode-json-array-string.md | 2 +-
.../sql-manual/sql-functions/table-functions/explode-map.md | 4 ++--
.../sql-manual/sql-functions/table-functions/explode-outer.md | 8 ++++----
.../sql-manual/sql-functions/table-valued-functions/frontends.md | 1 +
.../sql-manual/sql-functions/table-valued-functions/numbers.md | 2 +-
.../sql-manual/sql-statements/account-management/ALTER-USER.md | 6 +++---
.../sql-manual/sql-statements/account-management/CREATE-USER.md | 4 ++--
.../sql-manual/sql-statements/account-management/DROP-USER.md | 2 +-
.../sql-manual/sql-statements/account-management/GRANT-TO.md | 2 +-
.../sql-manual/sql-statements/account-management/REVOKE-FROM.md | 2 +-
.../cluster-management/compute-management/ALTER-WORKLOAD-GROUP.md | 2 +-
.../compute-management/ALTER-WORKLOAD-POLICY.md | 6 +++---
.../cluster-management/compute-management/CREATE-RESOURCE.md | 2 +-
.../compute-management/CREATE-WORKLOAD-GROUP.md | 2 +-
.../cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md | 2 +-
.../cluster-management/instance-management/ADD-BACKEND.md | 6 +++---
.../cluster-management/instance-management/ADD-BROKER.md | 6 +++---
91 files changed, 156 insertions(+), 154 deletions(-)
diff --git a/docs/sql-manual/sql-functions/table-functions/explode-bitmap.md
b/docs/sql-manual/sql-functions/table-functions/explode-bitmap.md
index 3bb314121c9..35ccbe0d63c 100644
--- a/docs/sql-manual/sql-functions/table-functions/explode-bitmap.md
+++ b/docs/sql-manual/sql-functions/table-functions/explode-bitmap.md
@@ -9,7 +9,6 @@
## Description
The `explode_bitmap` table function accepts a bitmap type data and maps each
bit in the bitmap to a separate row.
It is commonly used to process bitmap data, expanding each element in the
bitmap into a separate record. It should be used together with [`LATERAL
VIEW`](../../../query-data/lateral-view.md).
-`explode_bitmap_outer` is similar to `explode_bitmap`, but behaves differently
when handling empty or NULL values. It allows records with empty or NULL
bitmaps to exist and expands them into NULL rows in the result.
## Syntax
```sql
diff --git
a/docs/sql-manual/sql-functions/table-functions/explode-json-array-double.md
b/docs/sql-manual/sql-functions/table-functions/explode-json-array-double.md
index 27a6d942214..354971b3fef 100644
--- a/docs/sql-manual/sql-functions/table-functions/explode-json-array-double.md
+++ b/docs/sql-manual/sql-functions/table-functions/explode-json-array-double.md
@@ -7,7 +7,7 @@
---
## Description
-The `explode_json_array_double` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode` function for processing. The behavior is equivalent to:
`explode(cast(<json_array> as Array<DOUBLE>))`.
+The `explode_json_array_double` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode_outer` function for processing. The behavior is equivalent
to: `explode(cast(<json_array> as Array<DOUBLE>))`.
It should be used together with [`LATERAL
VIEW`](../../../query-data/lateral-view.md).
## Syntax
diff --git
a/docs/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
b/docs/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
index 323e454269f..ca33c999608 100644
---
a/docs/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
+++
b/docs/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
@@ -7,7 +7,7 @@
---
## Description
-The `explode_json_array_int_outer` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode` function for processing. The behavior is equivalent to:
`explode_outer(cast(<json_array> as Array<BIGINT>))`.
+The `explode_json_array_int_outer` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode_outer` function for processing. The behavior is equivalent
to: `explode_outer(cast(<json_array> as Array<BIGINT>))`.
It should be used together with [`LATERAL
VIEW`](../../../query-data/lateral-view.md).
## Syntax
diff --git
a/docs/sql-manual/sql-functions/table-functions/explode-json-array-int.md
b/docs/sql-manual/sql-functions/table-functions/explode-json-array-int.md
index 5d1949af6de..347f6de57de 100644
--- a/docs/sql-manual/sql-functions/table-functions/explode-json-array-int.md
+++ b/docs/sql-manual/sql-functions/table-functions/explode-json-array-int.md
@@ -7,7 +7,7 @@
---
## Description
-The `explode_json_array_int` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode` function for processing. The behavior is equivalent to:
`explode(cast(<json_array> as Array<BIGINT>))`.
+The `explode_json_array_int` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode_outer` function for processing. The behavior is equivalent
to: `explode(cast(<json_array> as Array<BIGINT>))`.
It should be used together with [`LATERAL
VIEW`](../../../query-data/lateral-view.md).
## Syntax
diff --git
a/docs/sql-manual/sql-functions/table-functions/explode-json-array-json.md
b/docs/sql-manual/sql-functions/table-functions/explode-json-array-json.md
index 92e41569b39..e38dee62b3a 100644
--- a/docs/sql-manual/sql-functions/table-functions/explode-json-array-json.md
+++ b/docs/sql-manual/sql-functions/table-functions/explode-json-array-json.md
@@ -7,7 +7,7 @@
---
## Description
-The `explode_json_array_json` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode` function for processing. The behavior is equivalent to:
`explode(cast(<json_array> as Array<JSON>))`.
+The `explode_json_array_json` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode_outer` function for processing. The behavior is equivalent
to: `explode(cast(<json_array> as Array<JSON>))`.
It should be used together with [`LATERAL
VIEW`](../../../query-data/lateral-view.md).
## Syntax
diff --git
a/docs/sql-manual/sql-functions/table-functions/explode-json-array-string.md
b/docs/sql-manual/sql-functions/table-functions/explode-json-array-string.md
index 25ce9af8faa..e614130a116 100644
--- a/docs/sql-manual/sql-functions/table-functions/explode-json-array-string.md
+++ b/docs/sql-manual/sql-functions/table-functions/explode-json-array-string.md
@@ -7,7 +7,7 @@
---
## Description
-The `explode_json_array_string` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode` function for processing. The behavior is equivalent to:
`explode(cast(<json_array> as Array<STRING>))`.
+The `explode_json_array_string` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode_outer` function for processing. The behavior is equivalent
to: `explode(cast(<json_array> as Array<STRING>))`.
It should be used together with [`LATERAL
VIEW`](../../../query-data/lateral-view.md).
## Syntax
diff --git a/docs/sql-manual/sql-functions/table-functions/explode-map.md
b/docs/sql-manual/sql-functions/table-functions/explode-map.md
index 73950d79827..dba969ccf3a 100644
--- a/docs/sql-manual/sql-functions/table-functions/explode-map.md
+++ b/docs/sql-manual/sql-functions/table-functions/explode-map.md
@@ -35,7 +35,7 @@ EXPLODE_MAP(<map>)
```
1. Regular parameters
```sql
- select * from example lateral view explode_map_outer(map("k", "v", "k2",
123, null, null)) t2 as c;
+ select * from example lateral view explode_map(map("k", "v", "k2", 123,
null, null)) t2 as c;
```
```text
+------+-----------------------------+
@@ -48,7 +48,7 @@ EXPLODE_MAP(<map>)
```
2. Expand key-value pairs into separate columns
```sql
- select * from example lateral view explode_map_outer(map("k", "v", "k2",
123, null, null)) t2 as k, v;
+ select * from example lateral view explode_map(map("k", "v", "k2", 123,
null, null)) t2 as k, v;
```
```text
+------+------+------+
diff --git a/docs/sql-manual/sql-functions/table-functions/explode-outer.md
b/docs/sql-manual/sql-functions/table-functions/explode-outer.md
index a132655b26e..a12c99c5416 100644
--- a/docs/sql-manual/sql-functions/table-functions/explode-outer.md
+++ b/docs/sql-manual/sql-functions/table-functions/explode-outer.md
@@ -1,6 +1,6 @@
---
{
- "title": "EXPLODE-OUTER",
+ "title": "EXPLODE_OUTER",
"language": "en",
"description": "The explode function accepts an array and maps each
element of the array to a separate row."
}
@@ -11,7 +11,7 @@ The `explode` function accepts an array and maps each element
of the array to a
## Syntax
```sql
-EXPLODE(<array>[, ...])
+EXPLODE_OUTER(<array>[, ...])
```
## Variadic Parameters
@@ -38,7 +38,7 @@ EXPLODE(<array>[, ...])
```
1. Regular parameters
```sql
- select * from example lateral view explode([1, 2, null, 4, 5]) t2 as c;
+ select * from example lateral view explode_outer([1, 2, null, 4, 5]) t2
as c;
```
```text
+------+------+
@@ -53,7 +53,7 @@ EXPLODE(<array>[, ...])
```
2. Multiple parameters
```sql
- select * from example lateral view explode([], [1, 2, null, 4, 5], ["ab",
"cd", "ef"], [null, null, 1, 2, 3, 4, 5]) t2 as c0, c1, c2, c3;
+ select * from example lateral view explode_outer([], [1, 2, null, 4, 5],
["ab", "cd", "ef"], [null, null, 1, 2, 3, 4, 5]) t2 as c0, c1, c2, c3;
```
```text
+------+------+------+------+------+
diff --git a/docs/sql-manual/sql-functions/table-valued-functions/frontends.md
b/docs/sql-manual/sql-functions/table-valued-functions/frontends.md
index d5b0ff14552..0c8b0934b66 100644
--- a/docs/sql-manual/sql-functions/table-valued-functions/frontends.md
+++ b/docs/sql-manual/sql-functions/table-valued-functions/frontends.md
@@ -42,6 +42,7 @@ FRONTENDS()
| **IsHelper** | Indicates whether the frontend node is a helper
node (true/false). |
| **ErrMsg** | Any error messages reported by the frontend node.
|
| **Version** | The version of the frontend node.
|
+| **CurrentConnected** | Indicates whether the frontend node is currently
connected to the cluster (Yes/No). |
## Examples
diff --git a/docs/sql-manual/sql-functions/table-valued-functions/numbers.md
b/docs/sql-manual/sql-functions/table-valued-functions/numbers.md
index 24fc0ce6c5c..7a041fa3dc6 100644
--- a/docs/sql-manual/sql-functions/table-valued-functions/numbers.md
+++ b/docs/sql-manual/sql-functions/table-valued-functions/numbers.md
@@ -14,7 +14,7 @@ Table function that generates a temporary table containing
only one column with
```sql
NUMBERS(
"number" = "<number>"
- [, "<const_value>" = "<const_value>" ]
+ [, "const_value" = "<const_value>" ]
);
```
diff --git a/docs/sql-manual/sql-statements/account-management/ALTER-USER.md
b/docs/sql-manual/sql-statements/account-management/ALTER-USER.md
index 2630a855fdf..ee1f1dd86a9 100644
--- a/docs/sql-manual/sql-statements/account-management/ALTER-USER.md
+++ b/docs/sql-manual/sql-statements/account-management/ALTER-USER.md
@@ -21,7 +21,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
5. ACCOUNT_UNLOCK
```
@@ -55,7 +55,7 @@ password_policy:
>
> When the current user logs in, if the user logs in with the wrong password
> for n times, the account will be locked.For example, `FAILED_LOGIN_ATTEMPTS
> 3` means that if you log in wrongly for 3 times, the account will be locked.
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> When the account is locked, the lock time is set. For example,
> `PASSWORD_LOCK_TIME 1 DAY` means that the account will be locked for one day.
>
@@ -77,7 +77,7 @@ The user executing this SQL command must have at least the
following privileges:
## Usage Notes
-1. This command give over supports modifying user roles from versions 2.0.
Please use [GRANT](./GRANT-TO.md) and [REVOKE](./REVOKE-FROM.md) for related
operations
+1. Starting from version 2.0, this command no longer supports modifying user
roles. Please use [GRANT](./GRANT-TO.md) and [REVOKE](./REVOKE-FROM.md) for
related operations.
2. In an ALTER USER command, only one of the following account attributes can
be modified at the same time:
- Change password
diff --git a/docs/sql-manual/sql-statements/account-management/CREATE-USER.md
b/docs/sql-manual/sql-statements/account-management/CREATE-USER.md
index 6ecea989e40..93c19133b99 100644
--- a/docs/sql-manual/sql-statements/account-management/CREATE-USER.md
+++ b/docs/sql-manual/sql-statements/account-management/CREATE-USER.md
@@ -22,7 +22,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
```
## Required Parameters
@@ -60,7 +60,7 @@ password_policy:
>
> When the current user logs in, if the user logs in with the wrong password
> for n times, the account will be locked.For example, `FAILED_LOGIN_ATTEMPTS
> 3` means that if you log in wrongly for 3 times, the account will be locked.
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> When the account is locked, the lock time is set. For example,
> `PASSWORD_LOCK_TIME 1 DAY` means that the account will be locked for one day.
diff --git a/docs/sql-manual/sql-statements/account-management/DROP-USER.md
b/docs/sql-manual/sql-statements/account-management/DROP-USER.md
index e2d10a24895..52dec934a87 100644
--- a/docs/sql-manual/sql-statements/account-management/DROP-USER.md
+++ b/docs/sql-manual/sql-statements/account-management/DROP-USER.md
@@ -13,7 +13,7 @@ The `DROP USER` statement is used to delete a user.
## Syntax
```sql
- DROP USER '<user_identity>'
+ DROP USER <user_identity>
```
## Required Parameters
diff --git a/docs/sql-manual/sql-statements/account-management/GRANT-TO.md
b/docs/sql-manual/sql-statements/account-management/GRANT-TO.md
index 63cda1c6c4a..2f623774614 100644
--- a/docs/sql-manual/sql-statements/account-management/GRANT-TO.md
+++ b/docs/sql-manual/sql-statements/account-management/GRANT-TO.md
@@ -108,7 +108,7 @@ Users executing this SQL command must have at least the
following privileges:
| Privilege | Object | Notes |
| :---------------- | :------------- | :---------------------------- |
-| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the GRANT operation. |
+| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the REVOKE operation. |
## Examples
diff --git a/docs/sql-manual/sql-statements/account-management/REVOKE-FROM.md
b/docs/sql-manual/sql-statements/account-management/REVOKE-FROM.md
index ae764764bc8..aac148c6d42 100644
--- a/docs/sql-manual/sql-statements/account-management/REVOKE-FROM.md
+++ b/docs/sql-manual/sql-statements/account-management/REVOKE-FROM.md
@@ -104,7 +104,7 @@ Users executing this SQL command must have at least the
following privileges:
| Privilege | Object | Notes |
| :---------------- | :------------- | :---------------------------- |
-| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the GRANT operation. |
+| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the REVOKE operation. |
## Examples
diff --git
a/docs/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-GROUP.md
b/docs/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-GROUP.md
index d13e2be3119..c6f53c900b6 100644
---
a/docs/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-GROUP.md
+++
b/docs/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-GROUP.md
@@ -24,7 +24,7 @@ PROPERTIES (
1.`<property>`
-`<property>` format is `<key>` = `<value>`，`<key>`'s specific optional values
can be referred to [workload
group](../../../../admin-manual/workload-management/workload-group.md).
+`<property>` format is `<key>` = `<value>`, and `<key>`'s specific optional
values can be referred to [workload
group](../../../../admin-manual/workload-management/workload-group.md).
## Examples
diff --git
a/docs/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
b/docs/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
index c254f7bd889..d38382fe5f4 100644
---
a/docs/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
+++
b/docs/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
@@ -2,13 +2,13 @@
{
"title": "ALTER WORKLOAD POLICY",
"language": "en",
- "description": "Modify the properties of a Workload Group. Currently, only
property modifications are supported;"
+ "description": "Modify the properties of a Workload Policy. Currently,
only property modifications are supported;"
}
---
## Description
-Modify the properties of a Workload Group. Currently, only property
modifications are supported; modifications to actions and conditions are not
supported.
+Modify the properties of a Workload Policy. Currently, only property
modifications are supported; modifications to actions and conditions are not
supported.
## Syntax
@@ -38,6 +38,6 @@ You must have at least ADMIN_PRIV permissions.
1. Disable a Workload Policy
- ```Java
+ ```sql
alter workload policy cancel_big_query properties('enabled'='false')
```
\ No newline at end of file
diff --git
a/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
b/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
index 219ee34c444..05c38386f02 100644
---
a/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
+++
b/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
@@ -23,7 +23,7 @@ PROPERTIES (
## Parameters
-1.`<type>`
+1.`<property>`
`<property>` format as `<key>` = `<value>`, and the specific available values
for `<key>` are as follows:
diff --git
a/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-GROUP.md
b/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-GROUP.md
index 464f7dd67ee..9f8dbbebe4e 100644
---
a/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-GROUP.md
+++
b/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-GROUP.md
@@ -27,7 +27,7 @@ PROPERTIES (
1.`<property>`
-`<property>` format is `<key>` = `<value>`，`<key>`'s specific optional values
can be referred to [workload
group](../../../../admin-manual/workload-management/workload-group.md).
+`<property>` format is `<key>` = `<value>`, and `<key>`'s specific optional
values can be referred to [workload
group](../../../../admin-manual/workload-management/workload-group.md).
## Examples
diff --git
a/docs/sql-manual/sql-statements/cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md
b/docs/sql-manual/sql-statements/cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md
index 43844ff001d..d106fa30d84 100644
---
a/docs/sql-manual/sql-statements/cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md
+++
b/docs/sql-manual/sql-statements/cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md
@@ -37,7 +37,7 @@ The result is:
```sql
+-----------------+-----------+-------+------------+
-| Name | IsCurrent | Users | BackendNum |
+| Name | IsCurrent | Users | BackendNum |
+-----------------+-----------+-------+------------+
| compute_cluster | TRUE | | 3 |
+-----------------+-----------+-------+------------+
diff --git
a/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
b/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
index bf54cc606a7..997ef3d63d7 100644
---
a/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
+++
b/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
@@ -49,9 +49,9 @@ The user executing this SQL must have at least the following
permissions:
1. Before adding a new BE node, make sure the node is correctly configured and
running.
2. Using [Resource
Group](../../../../admin-manual/workload-management/resource-group.md) can help
you better manage and organize the BE nodes in the cluster.
3. When adding multiple BE nodes, you can specify them in one command to
improve efficiency.
-3. After adding the BE nodes, use the [`SHOW BACKENDS`](./SHOW-BACKENDS.md) to
verify whether they have been successfully added and are in a normal state.
-4. Consider adding BE nodes in different physical locations or racks to
improve the availability and fault tolerance of the cluster.
-5. Regularly check and balance the load in the cluster to ensure that the
newly added BE nodes are properly utilized.
+4. After adding the BE nodes, use the [`SHOW BACKENDS`](./SHOW-BACKENDS.md) to
verify whether they have been successfully added and are in a normal state.
+5. Consider adding BE nodes in different physical locations or racks to
improve the availability and fault tolerance of the cluster.
+6. Regularly check and balance the load in the cluster to ensure that the
newly added BE nodes are properly utilized.
## Examples
diff --git
a/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
b/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
index 093d5c930a9..7914bee804b 100644
---
a/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
+++
b/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
@@ -13,7 +13,7 @@ This statement is used to add one or more BROKER nodes.
## Syntax
```sql
-ALTER SYSTEM ADD BROKER <broker_name> "<host>:<ipc_port>" [,
"host>:<ipc_port>" [, ... ] ];
+ALTER SYSTEM ADD BROKER <broker_name> "<host>:<ipc_port>" [,
"<host>:<ipc_port>" [, ... ] ];
```
## Required Parameters
@@ -39,10 +39,10 @@ The user who executes this operation needs to have the
NODE_PRIV permission.
1. Add two Brokers
```sql
- ALTER SYSTEM ADD BROKER "host1:port", "host2:port";
+ ALTER SYSTEM ADD BROKER broker1 "host1:port", "host2:port";
```
2. Add a Broker using FQDN
```sql
- ALTER SYSTEM ADD BROKER "broker_fqdn1:port";
+ ALTER SYSTEM ADD BROKER broker1 "broker_fqdn1:port";
```
\ No newline at end of file
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-map.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-map.md
index 06e8d7e2f32..3b41a10e3ab 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-map.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-map.md
@@ -35,7 +35,7 @@ EXPLODE_MAP(<map>)
```
1. 常规参数
```sql
- select * from example lateral view explode_map_outer(map("k", "v", "k2",
123, null, null)) t2 as c;
+ select * from example lateral view explode_map(map("k", "v", "k2", 123,
null, null)) t2 as c;
```
```text
+------+-----------------------------+
@@ -48,7 +48,7 @@ EXPLODE_MAP(<map>)
```
2. 将键值对展开为独立的列
```sql
- select * from example lateral view explode_map_outer(map("k", "v", "k2",
123, null, null)) t2 as k, v;
+ select * from example lateral view explode_map(map("k", "v", "k2", 123,
null, null)) t2 as k, v;
```
```text
+------+------+------+
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-outer.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-outer.md
index f14e1635b72..fb22422c8a6 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-outer.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-outer.md
@@ -1,6 +1,6 @@
---
{
- "title": "EXPLODE-OUTER",
+ "title": "EXPLODE_OUTER",
"language": "zh-CN",
"description": "explode 函数接受一个数组，会将数组的每个元素映射为单独的行。需要与 LATERAL VIEW
配合使用，以将嵌套数据结构展开为标准的平面表格式。 explodeouter 和 explode 区别主要在于空值处理。"
}
@@ -11,7 +11,7 @@
## 语法
```sql
-EXPLODE(<array>[, ...])
+EXPLODE_OUTER(<array>[, ...])
```
## 可变参数
@@ -38,7 +38,7 @@ EXPLODE(<array>[, ...])
```
1. 常规参数
```sql
- select * from example lateral view explode([1, 2, null, 4, 5]) t2 as c;
+ select * from example lateral view explode_outer([1, 2, null, 4, 5]) t2
as c;
```
```text
+------+------+
@@ -53,7 +53,7 @@ EXPLODE(<array>[, ...])
```
2. 多个参数
```sql
- select * from example lateral view explode([], [1, 2, null, 4, 5], ["ab",
"cd", "ef"], [null, null, 1, 2, 3, 4, 5]) t2 as c0, c1, c2, c3;
+ select * from example lateral view explode_outer([], [1, 2, null, 4, 5],
["ab", "cd", "ef"], [null, null, 1, 2, 3, 4, 5]) t2 as c0, c1, c2, c3;
```
```text
+------+------+------+------+------+
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-valued-functions/numbers.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-valued-functions/numbers.md
index 37723a691af..f3cb209729b 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-valued-functions/numbers.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-valued-functions/numbers.md
@@ -14,7 +14,7 @@
```sql
NUMBERS(
"number" = "<number>"
- [, "<const_value>" = "<const_value>" ]
+ [, "const_value" = "<const_value>" ]
);
```
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/ALTER-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/ALTER-USER.md
index 582cf923251..da6b0e8413c 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/ALTER-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/ALTER-USER.md
@@ -21,7 +21,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
5. ACCOUNT_UNLOCK
```
@@ -56,7 +56,7 @@ password_policy:
> 设置当前用户登录时，如果使用错误的密码登录 n 次后，账户将被锁定。如 `FAILED_LOGIN_ATTEMPTS 3` 表示如果 3
> 次错误登录，则账户会被锁定。
> 被锁定的账户可以通过 ALTER USER 语句主动解锁。
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> 设置如果账户被锁定，将设置锁定时间。如 `PASSWORD_LOCK_TIME 1 DAY` 表示账户会被锁定一天。
>
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/CREATE-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/CREATE-USER.md
index afc81906ad0..cc676e31018 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/CREATE-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/CREATE-USER.md
@@ -22,7 +22,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
```
## 必选参数
@@ -60,7 +60,7 @@ password_policy:
>
> 设置当前用户登录时，如果使用错误的密码登录 n 次后，账户将被锁定。如 `FAILED_LOGIN_ATTEMPTS 3
> PASSWORD_LOCK_TIME 1 DAY` 表示如果 3 次错误登录，则账户会被锁定。
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> 设置如果账户被锁定，将设置锁定时间。如 `PASSWORD_LOCK_TIME 1 DAY` 表示账户会被锁定一天。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
index 5939a59353f..edb364684a5 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
@@ -2,13 +2,13 @@
{
"title": "ALTER WORKLOAD POLICY",
"language": "zh-CN",
- "description": "修改一个 Workload Group 的属性，目前只支持修改属性，不支持修改 action 和
condition。"
+ "description": "修改一个 Workload Policy 的属性，目前只支持修改属性，不支持修改 action 和
condition。"
}
---
## 描述
-修改一个 Workload Group 的属性，目前只支持修改属性，不支持修改 action 和 condition。
+修改一个 Workload Policy 的属性，目前只支持修改属性，不支持修改 action 和 condition。
## 语法
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
index 8ff6cd278e2..30c6d82bf1f 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
@@ -40,10 +40,10 @@ ALTER SYSTEM ADD BROKER <broker_name> "<host>:<ipc_port>"
[,"<host>:<ipc_port>"
1. 增加两个 Broker
```sql
- ALTER SYSTEM ADD BROKER "host1:port", "host2:port";
+ ALTER SYSTEM ADD BROKER broker1 "host1:port", "host2:port";
```
2. 增加一个 Broker，使用 FQDN
```sql
- ALTER SYSTEM ADD BROKER "broker_fqdn1:port";
+ ALTER SYSTEM ADD BROKER broker1 "broker_fqdn1:port";
```
\ No newline at end of file
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/table-valued-functions/numbers.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/table-valued-functions/numbers.md
index 37723a691af..f3cb209729b 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/table-valued-functions/numbers.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/table-valued-functions/numbers.md
@@ -14,7 +14,7 @@
```sql
NUMBERS(
"number" = "<number>"
- [, "<const_value>" = "<const_value>" ]
+ [, "const_value" = "<const_value>" ]
);
```
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/ALTER-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/ALTER-USER.md
index 65f4b35c99c..f949568fbfd 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/ALTER-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/ALTER-USER.md
@@ -21,7 +21,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
5. ACCOUNT_UNLOCK
```
@@ -56,7 +56,7 @@ password_policy:
> 设置当前用户登录时，如果使用错误的密码登录 n 次后，账户将被锁定。如 `FAILED_LOGIN_ATTEMPTS 3` 表示如果 3
> 次错误登录，则账户会被锁定。
> 被锁定的账户可以通过 ALTER USER 语句主动解锁。
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> 设置如果账户被锁定，将设置锁定时间。如 `PASSWORD_LOCK_TIME 1 DAY` 表示账户会被锁定一天。
>
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/CREATE-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/CREATE-USER.md
index 16a0d4935e5..2827a59d1a2 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/CREATE-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/CREATE-USER.md
@@ -22,7 +22,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
```
## 必选参数
@@ -60,7 +60,7 @@ password_policy:
>
> 设置当前用户登录时，如果使用错误的密码登录 n 次后，账户将被锁定。如 `FAILED_LOGIN_ATTEMPTS 3
> PASSWORD_LOCK_TIME 1 DAY` 表示如果 3 次错误登录，则账户会被锁定。
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> 设置如果账户被锁定，将设置锁定时间。如 `PASSWORD_LOCK_TIME 1 DAY` 表示账户会被锁定一天。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
index 5939a59353f..edb364684a5 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
@@ -2,13 +2,13 @@
{
"title": "ALTER WORKLOAD POLICY",
"language": "zh-CN",
- "description": "修改一个 Workload Group 的属性，目前只支持修改属性，不支持修改 action 和
condition。"
+ "description": "修改一个 Workload Policy 的属性，目前只支持修改属性，不支持修改 action 和
condition。"
}
---
## 描述
-修改一个 Workload Group 的属性，目前只支持修改属性，不支持修改 action 和 condition。
+修改一个 Workload Policy 的属性，目前只支持修改属性，不支持修改 action 和 condition。
## 语法
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
index 8ff6cd278e2..30c6d82bf1f 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
@@ -40,10 +40,10 @@ ALTER SYSTEM ADD BROKER <broker_name> "<host>:<ipc_port>"
[,"<host>:<ipc_port>"
1. 增加两个 Broker
```sql
- ALTER SYSTEM ADD BROKER "host1:port", "host2:port";
+ ALTER SYSTEM ADD BROKER broker1 "host1:port", "host2:port";
```
2. 增加一个 Broker，使用 FQDN
```sql
- ALTER SYSTEM ADD BROKER "broker_fqdn1:port";
+ ALTER SYSTEM ADD BROKER broker1 "broker_fqdn1:port";
```
\ No newline at end of file
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/table-valued-functions/numbers.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/table-valued-functions/numbers.md
index 37723a691af..f3cb209729b 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/table-valued-functions/numbers.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/table-valued-functions/numbers.md
@@ -14,7 +14,7 @@
```sql
NUMBERS(
"number" = "<number>"
- [, "<const_value>" = "<const_value>" ]
+ [, "const_value" = "<const_value>" ]
);
```
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/ALTER-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/ALTER-USER.md
index 6325c1fb77f..be89d848997 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/ALTER-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/ALTER-USER.md
@@ -25,7 +25,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
5. ACCOUNT_UNLOCK
```
@@ -60,7 +60,7 @@ password_policy:
> 设置当前用户登录时，如果使用错误的密码登录 n 次后，账户将被锁定。如 `FAILED_LOGIN_ATTEMPTS 3` 表示如果 3
> 次错误登录，则账户会被锁定。
> 被锁定的账户可以通过 ALTER USER 语句主动解锁。
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> 设置如果账户被锁定，将设置锁定时间。如 `PASSWORD_LOCK_TIME 1 DAY` 表示账户会被锁定一天。
>
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/CREATE-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/CREATE-USER.md
index 69003fb2d92..21312b631e2 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/CREATE-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/CREATE-USER.md
@@ -22,7 +22,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
```
## 必选参数
@@ -60,7 +60,7 @@ password_policy:
>
> 设置当前用户登录时，如果使用错误的密码登录 n 次后，账户将被锁定。如 `FAILED_LOGIN_ATTEMPTS 3
> PASSWORD_LOCK_TIME 1 DAY` 表示如果 3 次错误登录，则账户会被锁定。
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> 设置如果账户被锁定，将设置锁定时间。如 `PASSWORD_LOCK_TIME 1 DAY` 表示账户会被锁定一天。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
index 5939a59353f..edb364684a5 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
@@ -2,13 +2,13 @@
{
"title": "ALTER WORKLOAD POLICY",
"language": "zh-CN",
- "description": "修改一个 Workload Group 的属性，目前只支持修改属性，不支持修改 action 和
condition。"
+ "description": "修改一个 Workload Policy 的属性，目前只支持修改属性，不支持修改 action 和
condition。"
}
---
## 描述
-修改一个 Workload Group 的属性，目前只支持修改属性，不支持修改 action 和 condition。
+修改一个 Workload Policy 的属性，目前只支持修改属性，不支持修改 action 和 condition。
## 语法
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
index 8ff6cd278e2..30c6d82bf1f 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
@@ -40,10 +40,10 @@ ALTER SYSTEM ADD BROKER <broker_name> "<host>:<ipc_port>"
[,"<host>:<ipc_port>"
1. 增加两个 Broker
```sql
- ALTER SYSTEM ADD BROKER "host1:port", "host2:port";
+ ALTER SYSTEM ADD BROKER broker1 "host1:port", "host2:port";
```
2. 增加一个 Broker，使用 FQDN
```sql
- ALTER SYSTEM ADD BROKER "broker_fqdn1:port";
+ ALTER SYSTEM ADD BROKER broker1 "broker_fqdn1:port";
```
\ No newline at end of file
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-map.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-map.md
index 06e8d7e2f32..3b41a10e3ab 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-map.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-map.md
@@ -35,7 +35,7 @@ EXPLODE_MAP(<map>)
```
1. 常规参数
```sql
- select * from example lateral view explode_map_outer(map("k", "v", "k2",
123, null, null)) t2 as c;
+ select * from example lateral view explode_map(map("k", "v", "k2", 123,
null, null)) t2 as c;
```
```text
+------+-----------------------------+
@@ -48,7 +48,7 @@ EXPLODE_MAP(<map>)
```
2. 将键值对展开为独立的列
```sql
- select * from example lateral view explode_map_outer(map("k", "v", "k2",
123, null, null)) t2 as k, v;
+ select * from example lateral view explode_map(map("k", "v", "k2", 123,
null, null)) t2 as k, v;
```
```text
+------+------+------+
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-outer.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-outer.md
index f14e1635b72..fb22422c8a6 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-outer.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-outer.md
@@ -1,6 +1,6 @@
---
{
- "title": "EXPLODE-OUTER",
+ "title": "EXPLODE_OUTER",
"language": "zh-CN",
"description": "explode 函数接受一个数组，会将数组的每个元素映射为单独的行。需要与 LATERAL VIEW
配合使用，以将嵌套数据结构展开为标准的平面表格式。 explodeouter 和 explode 区别主要在于空值处理。"
}
@@ -11,7 +11,7 @@
## 语法
```sql
-EXPLODE(<array>[, ...])
+EXPLODE_OUTER(<array>[, ...])
```
## 可变参数
@@ -38,7 +38,7 @@ EXPLODE(<array>[, ...])
```
1. 常规参数
```sql
- select * from example lateral view explode([1, 2, null, 4, 5]) t2 as c;
+ select * from example lateral view explode_outer([1, 2, null, 4, 5]) t2
as c;
```
```text
+------+------+
@@ -53,7 +53,7 @@ EXPLODE(<array>[, ...])
```
2. 多个参数
```sql
- select * from example lateral view explode([], [1, 2, null, 4, 5], ["ab",
"cd", "ef"], [null, null, 1, 2, 3, 4, 5]) t2 as c0, c1, c2, c3;
+ select * from example lateral view explode_outer([], [1, 2, null, 4, 5],
["ab", "cd", "ef"], [null, null, 1, 2, 3, 4, 5]) t2 as c0, c1, c2, c3;
```
```text
+------+------+------+------+------+
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-valued-functions/numbers.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-valued-functions/numbers.md
index 37723a691af..f3cb209729b 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-valued-functions/numbers.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-valued-functions/numbers.md
@@ -14,7 +14,7 @@
```sql
NUMBERS(
"number" = "<number>"
- [, "<const_value>" = "<const_value>" ]
+ [, "const_value" = "<const_value>" ]
);
```
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/ALTER-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/ALTER-USER.md
index 582cf923251..da6b0e8413c 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/ALTER-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/ALTER-USER.md
@@ -21,7 +21,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
5. ACCOUNT_UNLOCK
```
@@ -56,7 +56,7 @@ password_policy:
> 设置当前用户登录时，如果使用错误的密码登录 n 次后，账户将被锁定。如 `FAILED_LOGIN_ATTEMPTS 3` 表示如果 3
> 次错误登录，则账户会被锁定。
> 被锁定的账户可以通过 ALTER USER 语句主动解锁。
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> 设置如果账户被锁定，将设置锁定时间。如 `PASSWORD_LOCK_TIME 1 DAY` 表示账户会被锁定一天。
>
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/CREATE-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/CREATE-USER.md
index afc81906ad0..cc676e31018 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/CREATE-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/CREATE-USER.md
@@ -22,7 +22,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
```
## 必选参数
@@ -60,7 +60,7 @@ password_policy:
>
> 设置当前用户登录时，如果使用错误的密码登录 n 次后，账户将被锁定。如 `FAILED_LOGIN_ATTEMPTS 3
> PASSWORD_LOCK_TIME 1 DAY` 表示如果 3 次错误登录，则账户会被锁定。
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> 设置如果账户被锁定，将设置锁定时间。如 `PASSWORD_LOCK_TIME 1 DAY` 表示账户会被锁定一天。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
index 5939a59353f..edb364684a5 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
@@ -2,13 +2,13 @@
{
"title": "ALTER WORKLOAD POLICY",
"language": "zh-CN",
- "description": "修改一个 Workload Group 的属性，目前只支持修改属性，不支持修改 action 和
condition。"
+ "description": "修改一个 Workload Policy 的属性，目前只支持修改属性，不支持修改 action 和
condition。"
}
---
## 描述
-修改一个 Workload Group 的属性，目前只支持修改属性，不支持修改 action 和 condition。
+修改一个 Workload Policy 的属性，目前只支持修改属性，不支持修改 action 和 condition。
## 语法
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
index 8ff6cd278e2..30c6d82bf1f 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
@@ -40,10 +40,10 @@ ALTER SYSTEM ADD BROKER <broker_name> "<host>:<ipc_port>"
[,"<host>:<ipc_port>"
1. 增加两个 Broker
```sql
- ALTER SYSTEM ADD BROKER "host1:port", "host2:port";
+ ALTER SYSTEM ADD BROKER broker1 "host1:port", "host2:port";
```
2. 增加一个 Broker，使用 FQDN
```sql
- ALTER SYSTEM ADD BROKER "broker_fqdn1:port";
+ ALTER SYSTEM ADD BROKER broker1 "broker_fqdn1:port";
```
\ No newline at end of file
diff --git
a/versioned_docs/version-2.1/sql-manual/sql-functions/table-valued-functions/frontends.md
b/versioned_docs/version-2.1/sql-manual/sql-functions/table-valued-functions/frontends.md
index 9a64b01af17..54a59acb7ba 100644
---
a/versioned_docs/version-2.1/sql-manual/sql-functions/table-valued-functions/frontends.md
+++
b/versioned_docs/version-2.1/sql-manual/sql-functions/table-valued-functions/frontends.md
@@ -42,6 +42,7 @@ FRONTENDS()
| **IsHelper** | Indicates whether the frontend node is a helper
node (true/false). |
| **ErrMsg** | Any error messages reported by the frontend node.
|
| **Version** | The version of the frontend node.
|
+| **CurrentConnected** | Indicates whether the frontend node is currently
connected to the cluster (Yes/No). |
## Examples
diff --git
a/versioned_docs/version-2.1/sql-manual/sql-functions/table-valued-functions/numbers.md
b/versioned_docs/version-2.1/sql-manual/sql-functions/table-valued-functions/numbers.md
index 24fc0ce6c5c..7a041fa3dc6 100644
---
a/versioned_docs/version-2.1/sql-manual/sql-functions/table-valued-functions/numbers.md
+++
b/versioned_docs/version-2.1/sql-manual/sql-functions/table-valued-functions/numbers.md
@@ -14,7 +14,7 @@ Table function that generates a temporary table containing
only one column with
```sql
NUMBERS(
"number" = "<number>"
- [, "<const_value>" = "<const_value>" ]
+ [, "const_value" = "<const_value>" ]
);
```
diff --git
a/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/ALTER-USER.md
b/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/ALTER-USER.md
index d8831a88c47..e8c5250a04f 100644
---
a/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/ALTER-USER.md
+++
b/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/ALTER-USER.md
@@ -21,7 +21,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
5. ACCOUNT_UNLOCK
```
@@ -55,7 +55,7 @@ password_policy:
>
> When the current user logs in, if the user logs in with the wrong password
> for n times, the account will be locked.For example, `FAILED_LOGIN_ATTEMPTS
> 3` means that if you log in wrongly for 3 times, the account will be locked.
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> When the account is locked, the lock time is set. For example,
> `PASSWORD_LOCK_TIME 1 DAY` means that the account will be locked for one day.
>
@@ -77,7 +77,7 @@ The user executing this SQL command must have at least the
following privileges:
## Usage Notes
-1. This command give over supports modifying user roles from versions 2.0.
Please use [GRANT](./GRANT-TO.md) and [REVOKE](./REVOKE-FROM.md) for related
operations
+1. Starting from version 2.0, this command no longer supports modifying user
roles. Please use [GRANT](./GRANT-TO.md) and [REVOKE](./REVOKE-FROM.md) for
related operations.
2. In an ALTER USER command, only one of the following account attributes can
be modified at the same time:
- Change password
diff --git
a/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/CREATE-USER.md
b/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/CREATE-USER.md
index 2568ef9f4c2..4a0e2478b78 100644
---
a/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/CREATE-USER.md
+++
b/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/CREATE-USER.md
@@ -22,7 +22,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
```
## Required Parameters
@@ -59,7 +59,7 @@ password_policy:
>
> When the current user logs in, if the user logs in with the wrong password
> for n times, the account will be locked.For example, `FAILED_LOGIN_ATTEMPTS
> 3` means that if you log in wrongly for 3 times, the account will be locked.
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> When the account is locked, the lock time is set. For example,
> `PASSWORD_LOCK_TIME 1 DAY` means that the account will be locked for one day.
diff --git
a/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/DROP-USER.md
b/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/DROP-USER.md
index e2d10a24895..52dec934a87 100644
---
a/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/DROP-USER.md
+++
b/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/DROP-USER.md
@@ -13,7 +13,7 @@ The `DROP USER` statement is used to delete a user.
## Syntax
```sql
- DROP USER '<user_identity>'
+ DROP USER <user_identity>
```
## Required Parameters
diff --git
a/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/GRANT-TO.md
b/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/GRANT-TO.md
index 1a9f067cee3..7a028099d5d 100644
---
a/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/GRANT-TO.md
+++
b/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/GRANT-TO.md
@@ -97,7 +97,7 @@ Users executing this SQL command must have at least the
following privileges:
| Privilege | Object | Notes |
| :---------------- | :------------- | :---------------------------- |
-| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the GRANT operation. |
+| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the REVOKE operation. |
## Examples
diff --git
a/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/REVOKE-FROM.md
b/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/REVOKE-FROM.md
index 939c8d62161..0dde92af785 100644
---
a/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/REVOKE-FROM.md
+++
b/versioned_docs/version-2.1/sql-manual/sql-statements/account-management/REVOKE-FROM.md
@@ -92,7 +92,7 @@ Users executing this SQL command must have at least the
following privileges:
| Privilege | Object | Notes |
| :---------------- | :------------- | :---------------------------- |
-| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the GRANT operation. |
+| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the REVOKE operation. |
## Examples
diff --git
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
index b3528095b07..40d541b2892 100644
---
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
+++
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
@@ -2,13 +2,13 @@
{
"title": "ALTER WORKLOAD POLICY",
"language": "en",
- "description": "Modify the properties of a Workload Group. Currently, only
property modifications are supported;"
+ "description": "Modify the properties of a Workload Policy. Currently,
only property modifications are supported;"
}
---
## Description
-Modify the properties of a Workload Group. Currently, only property
modifications are supported; modifications to actions and conditions are not
supported.
+Modify the properties of a Workload Policy. Currently, only property
modifications are supported; modifications to actions and conditions are not
supported.
## Syntax
diff --git
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
index b65e81a3c5c..4b61df74518 100644
---
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
+++
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
@@ -23,7 +23,7 @@ PROPERTIES (
## Parameters
-1.`<type>`
+1.`<property>`
`<property>` format as `<key>` = `<value>`, and the specific available values
for `<key>` are as follows:
diff --git
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
index b506ffd56dc..bb4994e8f6d 100644
---
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
+++
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
@@ -46,9 +46,9 @@ The user executing this SQL must have at least the following
permissions:
1. Before adding a new BE node, make sure the node is correctly configured and
running.
2. Using [Resource
Group](../../../../admin-manual/workload-management/resource-group.md) can help
you better manage and organize the BE nodes in the cluster.
3. When adding multiple BE nodes, you can specify them in one command to
improve efficiency.
-3. After adding the BE nodes, use the [`SHOW BACKENDS`](./SHOW-BACKENDS.md) to
verify whether they have been successfully added and are in a normal state.
-4. Consider adding BE nodes in different physical locations or racks to
improve the availability and fault tolerance of the cluster.
-5. Regularly check and balance the load in the cluster to ensure that the
newly added BE nodes are properly utilized.
+4. After adding the BE nodes, use the [`SHOW BACKENDS`](./SHOW-BACKENDS.md) to
verify whether they have been successfully added and are in a normal state.
+5. Consider adding BE nodes in different physical locations or racks to
improve the availability and fault tolerance of the cluster.
+6. Regularly check and balance the load in the cluster to ensure that the
newly added BE nodes are properly utilized.
## Examples
diff --git
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
index 093d5c930a9..7914bee804b 100644
---
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
+++
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
@@ -13,7 +13,7 @@ This statement is used to add one or more BROKER nodes.
## Syntax
```sql
-ALTER SYSTEM ADD BROKER <broker_name> "<host>:<ipc_port>" [,
"host>:<ipc_port>" [, ... ] ];
+ALTER SYSTEM ADD BROKER <broker_name> "<host>:<ipc_port>" [,
"<host>:<ipc_port>" [, ... ] ];
```
## Required Parameters
@@ -39,10 +39,10 @@ The user who executes this operation needs to have the
NODE_PRIV permission.
1. Add two Brokers
```sql
- ALTER SYSTEM ADD BROKER "host1:port", "host2:port";
+ ALTER SYSTEM ADD BROKER broker1 "host1:port", "host2:port";
```
2. Add a Broker using FQDN
```sql
- ALTER SYSTEM ADD BROKER "broker_fqdn1:port";
+ ALTER SYSTEM ADD BROKER broker1 "broker_fqdn1:port";
```
\ No newline at end of file
diff --git
a/versioned_docs/version-3.x/sql-manual/sql-functions/table-valued-functions/frontends.md
b/versioned_docs/version-3.x/sql-manual/sql-functions/table-valued-functions/frontends.md
index d5b0ff14552..0c8b0934b66 100644
---
a/versioned_docs/version-3.x/sql-manual/sql-functions/table-valued-functions/frontends.md
+++
b/versioned_docs/version-3.x/sql-manual/sql-functions/table-valued-functions/frontends.md
@@ -42,6 +42,7 @@ FRONTENDS()
| **IsHelper** | Indicates whether the frontend node is a helper
node (true/false). |
| **ErrMsg** | Any error messages reported by the frontend node.
|
| **Version** | The version of the frontend node.
|
+| **CurrentConnected** | Indicates whether the frontend node is currently
connected to the cluster (Yes/No). |
## Examples
diff --git
a/versioned_docs/version-3.x/sql-manual/sql-functions/table-valued-functions/numbers.md
b/versioned_docs/version-3.x/sql-manual/sql-functions/table-valued-functions/numbers.md
index 24fc0ce6c5c..7a041fa3dc6 100644
---
a/versioned_docs/version-3.x/sql-manual/sql-functions/table-valued-functions/numbers.md
+++
b/versioned_docs/version-3.x/sql-manual/sql-functions/table-valued-functions/numbers.md
@@ -14,7 +14,7 @@ Table function that generates a temporary table containing
only one column with
```sql
NUMBERS(
"number" = "<number>"
- [, "<const_value>" = "<const_value>" ]
+ [, "const_value" = "<const_value>" ]
);
```
diff --git
a/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/ALTER-USER.md
b/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/ALTER-USER.md
index ffadbe7376d..5a88214dd03 100644
---
a/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/ALTER-USER.md
+++
b/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/ALTER-USER.md
@@ -21,7 +21,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
5. ACCOUNT_UNLOCK
```
@@ -55,7 +55,7 @@ password_policy:
>
> When the current user logs in, if the user logs in with the wrong password
> for n times, the account will be locked.For example, `FAILED_LOGIN_ATTEMPTS
> 3` means that if you log in wrongly for 3 times, the account will be locked.
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> When the account is locked, the lock time is set. For example,
> `PASSWORD_LOCK_TIME 1 DAY` means that the account will be locked for one day.
>
@@ -77,7 +77,7 @@ The user executing this SQL command must have at least the
following privileges:
## Usage Notes
-1. This command give over supports modifying user roles from versions 2.0.
Please use [GRANT](./GRANT-TO.md) and [REVOKE](./REVOKE-FROM.md) for related
operations
+1. Starting from version 2.0, this command no longer supports modifying user
roles. Please use [GRANT](./GRANT-TO.md) and [REVOKE](./REVOKE-FROM.md) for
related operations.
2. In an ALTER USER command, only one of the following account attributes can
be modified at the same time:
- Change password
diff --git
a/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/CREATE-USER.md
b/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/CREATE-USER.md
index 2568ef9f4c2..4a0e2478b78 100644
---
a/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/CREATE-USER.md
+++
b/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/CREATE-USER.md
@@ -22,7 +22,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
```
## Required Parameters
@@ -59,7 +59,7 @@ password_policy:
>
> When the current user logs in, if the user logs in with the wrong password
> for n times, the account will be locked.For example, `FAILED_LOGIN_ATTEMPTS
> 3` means that if you log in wrongly for 3 times, the account will be locked.
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> When the account is locked, the lock time is set. For example,
> `PASSWORD_LOCK_TIME 1 DAY` means that the account will be locked for one day.
diff --git
a/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/DROP-USER.md
b/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/DROP-USER.md
index e2d10a24895..52dec934a87 100644
---
a/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/DROP-USER.md
+++
b/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/DROP-USER.md
@@ -13,7 +13,7 @@ The `DROP USER` statement is used to delete a user.
## Syntax
```sql
- DROP USER '<user_identity>'
+ DROP USER <user_identity>
```
## Required Parameters
diff --git
a/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/GRANT-TO.md
b/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/GRANT-TO.md
index 63cda1c6c4a..2f623774614 100644
---
a/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/GRANT-TO.md
+++
b/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/GRANT-TO.md
@@ -108,7 +108,7 @@ Users executing this SQL command must have at least the
following privileges:
| Privilege | Object | Notes |
| :---------------- | :------------- | :---------------------------- |
-| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the GRANT operation. |
+| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the REVOKE operation. |
## Examples
diff --git
a/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/REVOKE-FROM.md
b/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/REVOKE-FROM.md
index ae764764bc8..aac148c6d42 100644
---
a/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/REVOKE-FROM.md
+++
b/versioned_docs/version-3.x/sql-manual/sql-statements/account-management/REVOKE-FROM.md
@@ -104,7 +104,7 @@ Users executing this SQL command must have at least the
following privileges:
| Privilege | Object | Notes |
| :---------------- | :------------- | :---------------------------- |
-| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the GRANT operation. |
+| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the REVOKE operation. |
## Examples
diff --git
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
index c254f7bd889..d38382fe5f4 100644
---
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
+++
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
@@ -2,13 +2,13 @@
{
"title": "ALTER WORKLOAD POLICY",
"language": "en",
- "description": "Modify the properties of a Workload Group. Currently, only
property modifications are supported;"
+ "description": "Modify the properties of a Workload Policy. Currently,
only property modifications are supported;"
}
---
## Description
-Modify the properties of a Workload Group. Currently, only property
modifications are supported; modifications to actions and conditions are not
supported.
+Modify the properties of a Workload Policy. Currently, only property
modifications are supported; modifications to actions and conditions are not
supported.
## Syntax
@@ -38,6 +38,6 @@ You must have at least ADMIN_PRIV permissions.
1. Disable a Workload Policy
- ```Java
+ ```sql
alter workload policy cancel_big_query properties('enabled'='false')
```
\ No newline at end of file
diff --git
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
index e9e622dcb76..f3f71e4a407 100644
---
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
+++
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
@@ -23,7 +23,7 @@ PROPERTIES (
## Parameters
-1.`<type>`
+1.`<property>`
`<property>` format as `<key>` = `<value>`, and the specific available values
for `<key>` are as follows:
diff --git
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md
index 43844ff001d..d106fa30d84 100644
---
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md
+++
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md
@@ -37,7 +37,7 @@ The result is:
```sql
+-----------------+-----------+-------+------------+
-| Name | IsCurrent | Users | BackendNum |
+| Name | IsCurrent | Users | BackendNum |
+-----------------+-----------+-------+------------+
| compute_cluster | TRUE | | 3 |
+-----------------+-----------+-------+------------+
diff --git
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
index 225f6397d85..a44b65584ef 100644
---
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
+++
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
@@ -49,9 +49,9 @@ The user executing this SQL must have at least the following
permissions:
1. Before adding a new BE node, make sure the node is correctly configured and
running.
2. Using [Resource
Group](../../../../admin-manual/workload-management/resource-group.md) can help
you better manage and organize the BE nodes in the cluster.
3. When adding multiple BE nodes, you can specify them in one command to
improve efficiency.
-3. After adding the BE nodes, use the [`SHOW BACKENDS`](./SHOW-BACKENDS.md) to
verify whether they have been successfully added and are in a normal state.
-4. Consider adding BE nodes in different physical locations or racks to
improve the availability and fault tolerance of the cluster.
-5. Regularly check and balance the load in the cluster to ensure that the
newly added BE nodes are properly utilized.
+4. After adding the BE nodes, use the [`SHOW BACKENDS`](./SHOW-BACKENDS.md) to
verify whether they have been successfully added and are in a normal state.
+5. Consider adding BE nodes in different physical locations or racks to
improve the availability and fault tolerance of the cluster.
+6. Regularly check and balance the load in the cluster to ensure that the
newly added BE nodes are properly utilized.
## Examples
diff --git
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
index 641dab219ef..c072fbe7a35 100644
---
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
+++
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
@@ -13,7 +13,7 @@ This statement is used to add one or more BROKER nodes.
## Syntax
```sql
-ALTER SYSTEM ADD BROKER <broker_name> "<host>:<ipc_port>" [,
"host>:<ipc_port>" [, ... ] ];
+ALTER SYSTEM ADD BROKER <broker_name> "<host>:<ipc_port>" [,
"<host>:<ipc_port>" [, ... ] ];
```
## Required Parameters
@@ -39,11 +39,11 @@ The user who executes this operation needs to have the
NODE_PRIV permission.
1. Add two Brokers
```sql
- ALTER SYSTEM ADD BROKER "host1:port", "host2:port";
+ ALTER SYSTEM ADD BROKER broker1 "host1:port", "host2:port";
```
2. Add a Broker using FQDN
```sql
- ALTER SYSTEM ADD BROKER "broker_fqdn1:port";
+ ALTER SYSTEM ADD BROKER broker1 "broker_fqdn1:port";
```
\ No newline at end of file
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-bitmap.md
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-bitmap.md
index 3bb314121c9..35ccbe0d63c 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-bitmap.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-bitmap.md
@@ -9,7 +9,6 @@
## Description
The `explode_bitmap` table function accepts a bitmap type data and maps each
bit in the bitmap to a separate row.
It is commonly used to process bitmap data, expanding each element in the
bitmap into a separate record. It should be used together with [`LATERAL
VIEW`](../../../query-data/lateral-view.md).
-`explode_bitmap_outer` is similar to `explode_bitmap`, but behaves differently
when handling empty or NULL values. It allows records with empty or NULL
bitmaps to exist and expands them into NULL rows in the result.
## Syntax
```sql
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-double.md
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-double.md
index 27a6d942214..354971b3fef 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-double.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-double.md
@@ -7,7 +7,7 @@
---
## Description
-The `explode_json_array_double` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode` function for processing. The behavior is equivalent to:
`explode(cast(<json_array> as Array<DOUBLE>))`.
+The `explode_json_array_double` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode_outer` function for processing. The behavior is equivalent
to: `explode(cast(<json_array> as Array<DOUBLE>))`.
It should be used together with [`LATERAL
VIEW`](../../../query-data/lateral-view.md).
## Syntax
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
index 323e454269f..ca33c999608 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
@@ -7,7 +7,7 @@
---
## Description
-The `explode_json_array_int_outer` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode` function for processing. The behavior is equivalent to:
`explode_outer(cast(<json_array> as Array<BIGINT>))`.
+The `explode_json_array_int_outer` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode_outer` function for processing. The behavior is equivalent
to: `explode_outer(cast(<json_array> as Array<BIGINT>))`.
It should be used together with [`LATERAL
VIEW`](../../../query-data/lateral-view.md).
## Syntax
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-int.md
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-int.md
index 5d1949af6de..347f6de57de 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-int.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-int.md
@@ -7,7 +7,7 @@
---
## Description
-The `explode_json_array_int` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode` function for processing. The behavior is equivalent to:
`explode(cast(<json_array> as Array<BIGINT>))`.
+The `explode_json_array_int` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode_outer` function for processing. The behavior is equivalent
to: `explode(cast(<json_array> as Array<BIGINT>))`.
It should be used together with [`LATERAL
VIEW`](../../../query-data/lateral-view.md).
## Syntax
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-json.md
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-json.md
index 92e41569b39..e38dee62b3a 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-json.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-json.md
@@ -7,7 +7,7 @@
---
## Description
-The `explode_json_array_json` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode` function for processing. The behavior is equivalent to:
`explode(cast(<json_array> as Array<JSON>))`.
+The `explode_json_array_json` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode_outer` function for processing. The behavior is equivalent
to: `explode(cast(<json_array> as Array<JSON>))`.
It should be used together with [`LATERAL
VIEW`](../../../query-data/lateral-view.md).
## Syntax
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-string.md
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-string.md
index 25ce9af8faa..e614130a116 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-string.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-string.md
@@ -7,7 +7,7 @@
---
## Description
-The `explode_json_array_string` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode` function for processing. The behavior is equivalent to:
`explode(cast(<json_array> as Array<STRING>))`.
+The `explode_json_array_string` table function accepts a JSON array. Its
implementation logic is to convert the JSON array to an array type and then
call the `explode_outer` function for processing. The behavior is equivalent
to: `explode(cast(<json_array> as Array<STRING>))`.
It should be used together with [`LATERAL
VIEW`](../../../query-data/lateral-view.md).
## Syntax
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-map.md
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-map.md
index 73950d79827..dba969ccf3a 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-map.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-map.md
@@ -35,7 +35,7 @@ EXPLODE_MAP(<map>)
```
1. Regular parameters
```sql
- select * from example lateral view explode_map_outer(map("k", "v", "k2",
123, null, null)) t2 as c;
+ select * from example lateral view explode_map(map("k", "v", "k2", 123,
null, null)) t2 as c;
```
```text
+------+-----------------------------+
@@ -48,7 +48,7 @@ EXPLODE_MAP(<map>)
```
2. Expand key-value pairs into separate columns
```sql
- select * from example lateral view explode_map_outer(map("k", "v", "k2",
123, null, null)) t2 as k, v;
+ select * from example lateral view explode_map(map("k", "v", "k2", 123,
null, null)) t2 as k, v;
```
```text
+------+------+------+
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-outer.md
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-outer.md
index a132655b26e..a12c99c5416 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-outer.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-functions/explode-outer.md
@@ -1,6 +1,6 @@
---
{
- "title": "EXPLODE-OUTER",
+ "title": "EXPLODE_OUTER",
"language": "en",
"description": "The explode function accepts an array and maps each
element of the array to a separate row."
}
@@ -11,7 +11,7 @@ The `explode` function accepts an array and maps each element
of the array to a
## Syntax
```sql
-EXPLODE(<array>[, ...])
+EXPLODE_OUTER(<array>[, ...])
```
## Variadic Parameters
@@ -38,7 +38,7 @@ EXPLODE(<array>[, ...])
```
1. Regular parameters
```sql
- select * from example lateral view explode([1, 2, null, 4, 5]) t2 as c;
+ select * from example lateral view explode_outer([1, 2, null, 4, 5]) t2
as c;
```
```text
+------+------+
@@ -53,7 +53,7 @@ EXPLODE(<array>[, ...])
```
2. Multiple parameters
```sql
- select * from example lateral view explode([], [1, 2, null, 4, 5], ["ab",
"cd", "ef"], [null, null, 1, 2, 3, 4, 5]) t2 as c0, c1, c2, c3;
+ select * from example lateral view explode_outer([], [1, 2, null, 4, 5],
["ab", "cd", "ef"], [null, null, 1, 2, 3, 4, 5]) t2 as c0, c1, c2, c3;
```
```text
+------+------+------+------+------+
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-valued-functions/frontends.md
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-valued-functions/frontends.md
index d5b0ff14552..0c8b0934b66 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-valued-functions/frontends.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-valued-functions/frontends.md
@@ -42,6 +42,7 @@ FRONTENDS()
| **IsHelper** | Indicates whether the frontend node is a helper
node (true/false). |
| **ErrMsg** | Any error messages reported by the frontend node.
|
| **Version** | The version of the frontend node.
|
+| **CurrentConnected** | Indicates whether the frontend node is currently
connected to the cluster (Yes/No). |
## Examples
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-valued-functions/numbers.md
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-valued-functions/numbers.md
index 24fc0ce6c5c..7a041fa3dc6 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-functions/table-valued-functions/numbers.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-functions/table-valued-functions/numbers.md
@@ -14,7 +14,7 @@ Table function that generates a temporary table containing
only one column with
```sql
NUMBERS(
"number" = "<number>"
- [, "<const_value>" = "<const_value>" ]
+ [, "const_value" = "<const_value>" ]
);
```
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/ALTER-USER.md
b/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/ALTER-USER.md
index 2630a855fdf..ee1f1dd86a9 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/ALTER-USER.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/ALTER-USER.md
@@ -21,7 +21,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
5. ACCOUNT_UNLOCK
```
@@ -55,7 +55,7 @@ password_policy:
>
> When the current user logs in, if the user logs in with the wrong password
> for n times, the account will be locked.For example, `FAILED_LOGIN_ATTEMPTS
> 3` means that if you log in wrongly for 3 times, the account will be locked.
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> When the account is locked, the lock time is set. For example,
> `PASSWORD_LOCK_TIME 1 DAY` means that the account will be locked for one day.
>
@@ -77,7 +77,7 @@ The user executing this SQL command must have at least the
following privileges:
## Usage Notes
-1. This command give over supports modifying user roles from versions 2.0.
Please use [GRANT](./GRANT-TO.md) and [REVOKE](./REVOKE-FROM.md) for related
operations
+1. Starting from version 2.0, this command no longer supports modifying user
roles. Please use [GRANT](./GRANT-TO.md) and [REVOKE](./REVOKE-FROM.md) for
related operations.
2. In an ALTER USER command, only one of the following account attributes can
be modified at the same time:
- Change password
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/CREATE-USER.md
b/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/CREATE-USER.md
index 6ecea989e40..93c19133b99 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/CREATE-USER.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/CREATE-USER.md
@@ -22,7 +22,7 @@ password_policy:
1. PASSWORD_HISTORY { <n> | DEFAULT }
2. PASSWORD_EXPIRE { DEFAULT | NEVER | INTERVAL <n> { DAY | HOUR | SECOND
}}
3. FAILED_LOGIN_ATTEMPTS <n>
- 4. PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}
+ 4. PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}
```
## Required Parameters
@@ -60,7 +60,7 @@ password_policy:
>
> When the current user logs in, if the user logs in with the wrong password
> for n times, the account will be locked.For example, `FAILED_LOGIN_ATTEMPTS
> 3` means that if you log in wrongly for 3 times, the account will be locked.
>
-> `PASSWORD_LOCK_TIME { UNBOUNDED ｜ <n> { DAY | HOUR | SECOND }}`
+> `PASSWORD_LOCK_TIME { UNBOUNDED | <n> { DAY | HOUR | SECOND }}`
>
> When the account is locked, the lock time is set. For example,
> `PASSWORD_LOCK_TIME 1 DAY` means that the account will be locked for one day.
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/DROP-USER.md
b/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/DROP-USER.md
index e2d10a24895..52dec934a87 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/DROP-USER.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/DROP-USER.md
@@ -13,7 +13,7 @@ The `DROP USER` statement is used to delete a user.
## Syntax
```sql
- DROP USER '<user_identity>'
+ DROP USER <user_identity>
```
## Required Parameters
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/GRANT-TO.md
b/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/GRANT-TO.md
index 63cda1c6c4a..2f623774614 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/GRANT-TO.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/GRANT-TO.md
@@ -108,7 +108,7 @@ Users executing this SQL command must have at least the
following privileges:
| Privilege | Object | Notes |
| :---------------- | :------------- | :---------------------------- |
-| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the GRANT operation. |
+| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the REVOKE operation. |
## Examples
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/REVOKE-FROM.md
b/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/REVOKE-FROM.md
index ae764764bc8..aac148c6d42 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/REVOKE-FROM.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-statements/account-management/REVOKE-FROM.md
@@ -104,7 +104,7 @@ Users executing this SQL command must have at least the
following privileges:
| Privilege | Object | Notes |
| :---------------- | :------------- | :---------------------------- |
-| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the GRANT operation. |
+| GRANT_PRIV | User or Role | Only users or roles with the GRANT_PRIV
privilege can perform the REVOKE operation. |
## Examples
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-GROUP.md
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-GROUP.md
index d13e2be3119..c6f53c900b6 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-GROUP.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-GROUP.md
@@ -24,7 +24,7 @@ PROPERTIES (
1.`<property>`
-`<property>` format is `<key>` = `<value>`，`<key>`'s specific optional values
can be referred to [workload
group](../../../../admin-manual/workload-management/workload-group.md).
+`<property>` format is `<key>` = `<value>`, and `<key>`'s specific optional
values can be referred to [workload
group](../../../../admin-manual/workload-management/workload-group.md).
## Examples
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
index c254f7bd889..d38382fe5f4 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/ALTER-WORKLOAD-POLICY.md
@@ -2,13 +2,13 @@
{
"title": "ALTER WORKLOAD POLICY",
"language": "en",
- "description": "Modify the properties of a Workload Group. Currently, only
property modifications are supported;"
+ "description": "Modify the properties of a Workload Policy. Currently,
only property modifications are supported;"
}
---
## Description
-Modify the properties of a Workload Group. Currently, only property
modifications are supported; modifications to actions and conditions are not
supported.
+Modify the properties of a Workload Policy. Currently, only property
modifications are supported; modifications to actions and conditions are not
supported.
## Syntax
@@ -38,6 +38,6 @@ You must have at least ADMIN_PRIV permissions.
1. Disable a Workload Policy
- ```Java
+ ```sql
alter workload policy cancel_big_query properties('enabled'='false')
```
\ No newline at end of file
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
index 219ee34c444..05c38386f02 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/CREATE-RESOURCE.md
@@ -23,7 +23,7 @@ PROPERTIES (
## Parameters
-1.`<type>`
+1.`<property>`
`<property>` format as `<key>` = `<value>`, and the specific available values
for `<key>` are as follows:
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-GROUP.md
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-GROUP.md
index 464f7dd67ee..9f8dbbebe4e 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-GROUP.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-GROUP.md
@@ -27,7 +27,7 @@ PROPERTIES (
1.`<property>`
-`<property>` format is `<key>` = `<value>`，`<key>`'s specific optional values
can be referred to [workload
group](../../../../admin-manual/workload-management/workload-group.md).
+`<property>` format is `<key>` = `<value>`, and `<key>`'s specific optional
values can be referred to [workload
group](../../../../admin-manual/workload-management/workload-group.md).
## Examples
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md
index 43844ff001d..d106fa30d84 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/compute-management/SHOW-COMPUTE-GROUPS.md
@@ -37,7 +37,7 @@ The result is:
```sql
+-----------------+-----------+-------+------------+
-| Name | IsCurrent | Users | BackendNum |
+| Name | IsCurrent | Users | BackendNum |
+-----------------+-----------+-------+------------+
| compute_cluster | TRUE | | 3 |
+-----------------+-----------+-------+------------+
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
index bf54cc606a7..997ef3d63d7 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND.md
@@ -49,9 +49,9 @@ The user executing this SQL must have at least the following
permissions:
1. Before adding a new BE node, make sure the node is correctly configured and
running.
2. Using [Resource
Group](../../../../admin-manual/workload-management/resource-group.md) can help
you better manage and organize the BE nodes in the cluster.
3. When adding multiple BE nodes, you can specify them in one command to
improve efficiency.
-3. After adding the BE nodes, use the [`SHOW BACKENDS`](./SHOW-BACKENDS.md) to
verify whether they have been successfully added and are in a normal state.
-4. Consider adding BE nodes in different physical locations or racks to
improve the availability and fault tolerance of the cluster.
-5. Regularly check and balance the load in the cluster to ensure that the
newly added BE nodes are properly utilized.
+4. After adding the BE nodes, use the [`SHOW BACKENDS`](./SHOW-BACKENDS.md) to
verify whether they have been successfully added and are in a normal state.
+5. Consider adding BE nodes in different physical locations or racks to
improve the availability and fault tolerance of the cluster.
+6. Regularly check and balance the load in the cluster to ensure that the
newly added BE nodes are properly utilized.
## Examples
diff --git
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
index 093d5c930a9..7914bee804b 100644
---
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
+++
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-BROKER.md
@@ -13,7 +13,7 @@ This statement is used to add one or more BROKER nodes.
## Syntax
```sql
-ALTER SYSTEM ADD BROKER <broker_name> "<host>:<ipc_port>" [,
"host>:<ipc_port>" [, ... ] ];
+ALTER SYSTEM ADD BROKER <broker_name> "<host>:<ipc_port>" [,
"<host>:<ipc_port>" [, ... ] ];
```
## Required Parameters
@@ -39,10 +39,10 @@ The user who executes this operation needs to have the
NODE_PRIV permission.
1. Add two Brokers
```sql
- ALTER SYSTEM ADD BROKER "host1:port", "host2:port";
+ ALTER SYSTEM ADD BROKER broker1 "host1:port", "host2:port";
```
2. Add a Broker using FQDN
```sql
- ALTER SYSTEM ADD BROKER "broker_fqdn1:port";
+ ALTER SYSTEM ADD BROKER broker1 "broker_fqdn1:port";
```
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
