This is an automated email from the ASF dual-hosted git repository.
jiafengzheng 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 4f58e9d9f3e fix
4f58e9d9f3e is described below
commit 4f58e9d9f3ec4009a57d7d6fae2a91113b535968
Author: jiafeng.zhang <zhang...@gmail.com>
AuthorDate: Tue Oct 25 18:33:47 2022 +0800
fix
---
docs/admin-manual/cluster-management/elastic-expansion.md | 2 +-
docs/admin-manual/config/be-config.md | 2 +-
docs/advanced/alter-table/schema-change.md | 2 +-
docs/data-operate/import/import-scenes/external-storage-load.md | 2 +-
docs/data-operate/import/import-scenes/jdbc-load.md | 4 ++--
docs/data-table/basic-usage.md | 4 ++--
.../Data-Definition-Statements/Alter/ALTER-TABLE-PARTITION.md | 2 +-
.../Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP.md | 4 ++--
.../current/admin-manual/cluster-management/elastic-expansion.md | 2 +-
.../current/admin-manual/config/be-config.md | 2 +-
.../Data-Definition-Statements/Alter/ALTER-TABLE-PARTITION.md | 2 +-
.../Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP.md | 4 ++--
12 files changed, 16 insertions(+), 16 deletions(-)
diff --git a/docs/admin-manual/cluster-management/elastic-expansion.md
b/docs/admin-manual/cluster-management/elastic-expansion.md
index ea821f69bbb..e8fd4525298 100644
--- a/docs/admin-manual/cluster-management/elastic-expansion.md
+++ b/docs/admin-manual/cluster-management/elastic-expansion.md
@@ -106,7 +106,7 @@ You can also view the BE node through the front-end page
connection: ``http://fe
All of the above methods require Doris's root user rights.
-The expansion and scaling process of BE nodes does not affect the current
system operation and the tasks being performed, and does not affect the
performance of the current system. Data balancing is done automatically.
Depending on the amount of data available in the cluster, the cluster will be
restored to load balancing in a few hours to a day. For cluster load, see the
[Tablet Load Balancing Document](../maint-monitor/tablet-repair-and-balance).
+The expansion and scaling process of BE nodes does not affect the current
system operation and the tasks being performed, and does not affect the
performance of the current system. Data balancing is done automatically.
Depending on the amount of data available in the cluster, the cluster will be
restored to load balancing in a few hours to a day. For cluster load, see the
[Tablet Load Balancing Document](../../maint-monitor/tablet-repair-and-balance).
### Add BE nodes
diff --git a/docs/admin-manual/config/be-config.md
b/docs/admin-manual/config/be-config.md
index e27118a83ed..90e9d044208 100644
--- a/docs/admin-manual/config/be-config.md
+++ b/docs/admin-manual/config/be-config.md
@@ -450,7 +450,7 @@ Cgroups assigned to doris
### `doris_max_scan_key_num`
* Type: int
-* Description: Used to limit the maximum number of scan keys that a scan node
can split in a query request. When a conditional query request reaches the scan
node, the scan node will try to split the conditions related to the key column
in the query condition into multiple scan key ranges. After that, these scan
key ranges will be assigned to multiple scanner threads for data scanning. A
larger value usually means that more scanner threads can be used to increase
the parallelism of the s [...]
+* Description: Used to limit the maximum number of scan keys that a scan node
can split in a query request. When a conditional query request reaches the scan
node, the scan node will try to split the conditions related to the key column
in the query condition into multiple scan key ranges. After that, these scan
key ranges will be assigned to multiple scanner threads for data scanning. A
larger value usually means that more scanner threads can be used to increase
the parallelism of the s [...]
* Default value: 1024
When the concurrency cannot be improved in high concurrency scenarios, try to
reduce this value and observe the impact.
diff --git a/docs/advanced/alter-table/schema-change.md
b/docs/advanced/alter-table/schema-change.md
index 3cf43598ae7..23f9fa77084 100644
--- a/docs/advanced/alter-table/schema-change.md
+++ b/docs/advanced/alter-table/schema-change.md
@@ -282,5 +282,5 @@ SHOW ALTER TABLE COLUMN\G;
## More Help
-For more detailed syntax and best practices used by Schema Change, see [ALTER
TABLE
COLUMN](../../../sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-COLUMN.md
) command manual, you can also enter `HELP ALTER TABLE COLUMN` in the MySql
client command line for more help information.
+For more detailed syntax and best practices used by Schema Change, see [ALTER
TABLE
COLUMN](../../sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-COLUMN.md)
command manual, you can also enter `HELP ALTER TABLE COLUMN` in the MySql
client command line for more help information.
diff --git a/docs/data-operate/import/import-scenes/external-storage-load.md
b/docs/data-operate/import/import-scenes/external-storage-load.md
index f2ebd53e3af..50da5abc289 100644
--- a/docs/data-operate/import/import-scenes/external-storage-load.md
+++ b/docs/data-operate/import/import-scenes/external-storage-load.md
@@ -128,7 +128,7 @@ This document mainly introduces how to import data stored
in AWS S3. It also sup
Other cloud storage systems can find relevant information compatible with S3
in corresponding documents
### Start Loading
-Like [Broker Load](../../../data-operate/import/import-way/broker-load-manual)
just replace `WITH BROKER broker_name ()` with
+Like [Broker Load](/data-operate/import/import-way/broker-load-manual) just
replace `WITH BROKER broker_name ()` with
```
WITH S3
(
diff --git a/docs/data-operate/import/import-scenes/jdbc-load.md
b/docs/data-operate/import/import-scenes/jdbc-load.md
index b84ce15e81b..b52621748cc 100644
--- a/docs/data-operate/import/import-scenes/jdbc-load.md
+++ b/docs/data-operate/import/import-scenes/jdbc-load.md
@@ -35,7 +35,7 @@ The INSERT statement is used in a similar way to the INSERT
statement used in da
* INSERT INTO table VALUES(...)
````
-Here we only introduce the second way. For a detailed description of the
INSERT command, see the
[INSERT](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Manipulation/INSERT.md)
command documentation.
+Here we only introduce the second way. For a detailed description of the
INSERT command, see the
[INSERT](/sql-manual/sql-reference/Data-Manipulation-Statements/Manipulation/INSERT)
command documentation.
## Single write
@@ -160,5 +160,5 @@ Please note the following:
As mentioned earlier, we recommend that when using INSERT to import data,
use the "batch" method to import, rather than a single insert.
- At the same time, we can set a Label for each INSERT operation. Through the
[Label mechanism](./load-atomicity.md), the idempotency and atomicity of
operations can be guaranteed, and the data will not be lost or heavy in the
end. For the specific usage of Label in INSERT, you can refer to the
[INSERT](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Manipulation/INSERT.md)
document.
+ At the same time, we can set a Label for each INSERT operation. Through the
[Label mechanism](./load-atomicity.md), the idempotency and atomicity of
operations can be guaranteed, and the data will not be lost or heavy in the
end. For the specific usage of Label in INSERT, you can refer to the
[INSERT](/sql-manual/sql-reference/Data-Manipulation-Statements/Manipulation/INSERT)
document.
diff --git a/docs/data-table/basic-usage.md b/docs/data-table/basic-usage.md
index f4bf29cfb27..3620b4e3c6a 100644
--- a/docs/data-table/basic-usage.md
+++ b/docs/data-table/basic-usage.md
@@ -103,11 +103,11 @@ Initially, a database can be created through root or
admin users:
CREATE DATABASE example_db;
```
-> All commands can use `HELP` command to see detailed grammar help. For
example: `HELP CREATE DATABASE;'`.You can also refer to the official website
[SHOW CREATE
DATABASE](../sql-manual/sql-reference/Show-Statements/SHOW-CREATE-DATABASE.md)
command manual.
+> All commands can use `HELP` command to see detailed grammar help. For
example: `HELP CREATE DATABASE;'`.You can also refer to the official website
[SHOW CREATE
DATABASE](/sql-manual/sql-reference/Show-Statements/SHOW-CREATE-DATABASE.md)
command manual.
>
> If you don't know the full name of the command, you can use "help command a
> field" for fuzzy query. If you type `HELP CREATE`, you can match commands
> like `CREATE DATABASE', `CREATE TABLE', `CREATE USER', etc.
-After the database is created, you can view the database information through
[SHOW DATABASES](../sql-manual/sql-reference/Show-Statements/SHOW-DATABASES.md).
+After the database is created, you can view the database information through
[SHOW DATABASES](/sql-manual/sql-reference/Show-Statements/SHOW-DATABASES).
```sql
MySQL> SHOW DATABASES;
diff --git
a/docs/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-PARTITION.md
b/docs/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-PARTITION.md
index 47db6d49752..9e50a2dd015 100644
---
a/docs/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-PARTITION.md
+++
b/docs/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-PARTITION.md
@@ -62,7 +62,7 @@ Notice:
- The partition is left closed and right open. If the user only specifies the
right boundary, the system will automatically determine the left boundary
- If the bucketing method is not specified, the bucketing method and bucket
number used for creating the table would be automatically used
- If the bucketing method is specified, only the number of buckets can be
modified, not the bucketing method or the bucketing column. If the bucketing
method is specified but the number of buckets not be specified, the default
value `10` will be used for bucket number instead of the number specified when
the table is created. If the number of buckets modified, the bucketing method
needs to be specified simultaneously.
-- The ["key"="value"] section can set some attributes of the partition, see
[CREATE
TABLE](../../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
+- The ["key"="value"] section can set some attributes of the partition, see
[CREATE
TABLE](/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
- If the user does not explicitly create a partition when creating a table,
adding a partition by ALTER is not supported
2. Delete the partition
diff --git
a/docs/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP.md
b/docs/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP.md
index e5d35e18758..a4a36c1b0c6 100644
---
a/docs/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP.md
+++
b/docs/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP.md
@@ -32,7 +32,7 @@ ALTER TABLE ROLLUP
### Description
-This statement is used to perform a rollup modification operation on an
existing table. The rollup is an asynchronous operation, and the task is
returned when the task is submitted successfully. After that, you can use the
[SHOW ALTER](/sql-manual/sql-reference/Show-Statements/SHOW-ALTER) command to
view the progress.
+This statement is used to perform a rollup modification operation on an
existing table. The rollup is an asynchronous operation, and the task is
returned when the task is submitted successfully. After that, you can use the
[SHOW ALTER](/docs/sql-manual/sql-reference/Show-Statements/SHOW-ALTER) command
to view the progress.
grammar:
@@ -68,7 +68,7 @@ Notice:
- If from_index_name is not specified, it will be created from base index by
default
- Columns in rollup table must be columns already in from_index
-- In properties, the storage format can be specified. For details, see [CREATE
TABLE](/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
+- In properties, the storage format can be specified. For details, see [CREATE
TABLE](/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
3. Delete rollup index
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/cluster-management/elastic-expansion.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/cluster-management/elastic-expansion.md
index 6e2c03c5cef..dbd35e6e156 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/cluster-management/elastic-expansion.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/cluster-management/elastic-expansion.md
@@ -102,7 +102,7 @@ FE 分为 Leader，Follower 和 Observer 三种角色。 默认一个集群，
以上方式，都需要 Doris 的 root 用户权限。
-BE
节点的扩容和缩容过程，不影响当前系统运行以及正在执行的任务，并且不会影响当前系统的性能。数据均衡会自动进行。根据集群现有数据量的大小，集群会在几个小时到1天不等的时间内，恢复到负载均衡的状态。集群负载情况，可以参见
[Tablet 负载均衡文档](../maint-monitor/tablet-repair-and-balance)。
+BE
节点的扩容和缩容过程，不影响当前系统运行以及正在执行的任务，并且不会影响当前系统的性能。数据均衡会自动进行。根据集群现有数据量的大小，集群会在几个小时到1天不等的时间内，恢复到负载均衡的状态。集群负载情况，可以参见
[Tablet 负载均衡文档](../../maint-monitor/tablet-repair-and-balance)。
### 增加 BE 节点
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/be-config.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/be-config.md
index e6a470c6d4c..049f89e42a0 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/be-config.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/be-config.md
@@ -445,7 +445,7 @@ BaseCompaction触发条件之一：Singleton文件大小限制，100MB
### `doris_max_scan_key_num`
* 类型：int
-* 描述：用于限制一个查询请求中，scan node 节点能拆分的最大 scan key 的个数。当一个带有条件的查询请求到达 scan node
节点时，scan node 会尝试将查询条件中 key 列相关的条件拆分成多个 scan key range。之后这些 scan key range
会被分配给多个 scanner 线程进行数据扫描。较大的数值通常意味着可以使用更多的 scanner
线程来提升扫描操作的并行度。但在高并发场景下，过多的线程可能会带来更大的调度开销和系统负载，反而会降低查询响应速度。一个经验数值为
50。该配置可以单独进行会话级别的配置，具体可参阅 [变量](../../../advanced/variables.md) 中
`max_scan_key_num` 的说明。
+* 描述：用于限制一个查询请求中，scan node 节点能拆分的最大 scan key 的个数。当一个带有条件的查询请求到达 scan node
节点时，scan node 会尝试将查询条件中 key 列相关的条件拆分成多个 scan key range。之后这些 scan key range
会被分配给多个 scanner 线程进行数据扫描。较大的数值通常意味着可以使用更多的 scanner
线程来提升扫描操作的并行度。但在高并发场景下，过多的线程可能会带来更大的调度开销和系统负载，反而会降低查询响应速度。一个经验数值为
50。该配置可以单独进行会话级别的配置，具体可参阅 [变量](../../../advanced/variables) 中
`max_scan_key_num` 的说明。
* 默认值：1024
当在高并发场景下发下并发度无法提升时，可以尝试降低该数值并观察影响。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-PARTITION.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-PARTITION.md
index f2304ae3503..fa26940a120 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-PARTITION.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-PARTITION.md
@@ -62,7 +62,7 @@ partition_desc ["key"="value"]
- 分区为左闭右开区间，如果用户仅指定右边界，系统会自动确定左边界
- 如果没有指定分桶方式，则自动使用建表使用的分桶方式和分桶数。
-
如指定分桶方式，只能修改分桶数，不可修改分桶方式或分桶列。如果指定了分桶方式，但是没有指定分桶数，则分桶数会使用默认值10，不会使用建表时指定的分桶数。如果要指定分桶数，则必须指定分桶方式。
-- ["key"="value"] 部分可以设置分区的一些属性，具体说明见 [CREATE
TABLE](../../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
+- ["key"="value"] 部分可以设置分区的一些属性，具体说明见 [CREATE
TABLE](/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
- 如果建表时用户未显式创建Partition,则不支持通过ALTER的方式增加分区
2. 删除分区
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP.md
index dabd7a87681..3fe317edf2e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP.md
@@ -32,7 +32,7 @@ ALTER TABLE ROLLUP
### Description
-该语句用于对已有 table 进行 rollup 进行修改操作。rollup 是异步操作，任务提交成功则返回，之后可使用[SHOW
ALTER](/sql-manual/sql-reference/Show-Statements/SHOW-ALTER) 命令查看进度。
+该语句用于对已有 table 进行 rollup 进行修改操作。rollup 是异步操作，任务提交成功则返回，之后可使用[SHOW
ALTER](/docs/sql-manual/sql-reference/Show-Statements/SHOW-ALTER) 命令查看进度。
语法：
@@ -68,7 +68,7 @@ ADD ROLLUP [rollup_name (column_name1, column_name2, ...)
- 如果没有指定 from_index_name，则默认从 base index 创建
- rollup 表中的列必须是 from_index 中已有的列
-- 在 properties 中，可以指定存储格式。具体请参阅 [CREATE
TABLE](/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
+- 在 properties 中，可以指定存储格式。具体请参阅 [CREATE
TABLE](/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
3. 删除 rollup index
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
