This is an automated email from the ASF dual-hosted git repository.
zykkk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris.git
The following commit(s) were added to refs/heads/master by this push:
new a57ad36c4e8 [fix](docs) Update Link for 404 page of dev docs (#29213)
a57ad36c4e8 is described below
commit a57ad36c4e8e1ac983210a3f745e56fbe8b35f4a
Author: KassieZ <139741991+kass...@users.noreply.github.com>
AuthorDate: Fri Dec 29 11:37:50 2023 +0800
[fix](docs) Update Link for 404 page of dev docs (#29213)
---
.../docs/advanced/best-practice/import-analysis.md | 2 +-
docs/en/docs/advanced/broker.md | 6 +++---
.../import/import-scenes/external-storage-load.md | 8 ++++----
.../import/import-scenes/load-atomicity.md | 4 ++--
.../import/import-scenes/load-data-convert.md | 6 +++---
.../import/import-scenes/load-strict-mode.md | 10 ++++-----
.../import/import-way/broker-load-manual.md | 24 +++++++++++-----------
docs/zh-CN/docs/advanced/broker.md | 6 +++---
.../import/import-scenes/external-storage-load.md | 8 ++++----
.../import/import-scenes/load-data-convert.md | 2 +-
.../import/import-scenes/load-strict-mode.md | 2 +-
.../import/import-way/broker-load-manual.md | 24 +++++++++++-----------
.../update-delete/batch-delete-manual.md | 2 +-
13 files changed, 52 insertions(+), 52 deletions(-)
diff --git a/docs/en/docs/advanced/best-practice/import-analysis.md
b/docs/en/docs/advanced/best-practice/import-analysis.md
index 95fc1c3ace0..3c97c3d3a9a 100644
--- a/docs/en/docs/advanced/best-practice/import-analysis.md
+++ b/docs/en/docs/advanced/best-practice/import-analysis.md
@@ -35,7 +35,7 @@ Doris provides a graphical command to help users analyze a
specific import more
If you don't know much about Doris' query plan tree, please read the previous
article [DORIS/best practices/query analysis](./query-analysis.md).
-The execution process of a [Broker
Load](../../data-operate/import/import-way/broker-load-manual.md) request is
also based on Doris' query framework. A Broker Load job will be split into
multiple subtasks based on the number of DATA INFILE clauses in the import
request. Each subtask can be regarded as an independent import execution plan.
An import plan consists of only one Fragment, which is composed as follows:
+The execution process of a [Broker
Load](../../data-operate/import/import-way/broker-load-manual) request is also
based on Doris' query framework. A Broker Load job will be split into multiple
subtasks based on the number of DATA INFILE clauses in the import request. Each
subtask can be regarded as an independent import execution plan. An import plan
consists of only one Fragment, which is composed as follows:
```sql
┌────────────────┐
diff --git a/docs/en/docs/advanced/broker.md b/docs/en/docs/advanced/broker.md
index 47e4c7bd833..549699744b7 100644
--- a/docs/en/docs/advanced/broker.md
+++ b/docs/en/docs/advanced/broker.md
@@ -78,9 +78,9 @@ Different types of brokers support different storage systems.
## Function provided by Broker
-1. [Broker Load](../data-operate/import/import-way/broker-load-manual.md)
-2. [Export](../data-operate/export/export-manual.md)
-3. [Backup](../admin-manual/data-admin/backup.md)
+1. [Broker Load](../data-operate/import/import-way/broker-load-manual)
+2. [Export](../data-operate/export/export-manual)
+3. [Backup](../admin-manual/data-admin/backup)
## Broker Information
diff --git
a/docs/en/docs/data-operate/import/import-scenes/external-storage-load.md
b/docs/en/docs/data-operate/import/import-scenes/external-storage-load.md
index aaf4bf73396..e5e152a8d28 100644
--- a/docs/en/docs/data-operate/import/import-scenes/external-storage-load.md
+++ b/docs/en/docs/data-operate/import/import-scenes/external-storage-load.md
@@ -35,7 +35,7 @@ Upload the files to be imported to HDFS. For specific
commands, please refer to
### start import
-Hdfs load creates an import statement. The import method is basically the same
as [Broker
Load](../../../data-operate/import/import-way/broker-load-manual.md), only need
to `WITH BROKER broker_name () ` statement with the following
+Hdfs load creates an import statement. The import method is basically the same
as [Broker Load](../../../data-operate/import/import-way/broker-load-manual),
only need to `WITH BROKER broker_name () ` statement with the following
```
LOAD LABEL db_name.label_name
@@ -78,11 +78,11 @@ Hdfs load creates an import statement. The import method is
basically the same a
);
```
- For parameter introduction, please refer to [Broker
Load](../../../data-operate/import/import-way/broker-load-manual.md), HA
cluster creation syntax, view through `HELP BROKER LOAD`
+ For parameter introduction, please refer to [Broker
Load](../../../data-operate/import/import-way/broker-load-manual), HA cluster
creation syntax, view through `HELP BROKER LOAD`
3. Check import status
- Broker load is an asynchronous import method. The specific import results
can be accessed through [SHOW
LOAD](../../../sql-manual/sql-reference/Show-Statements/SHOW-LOAD.md) command
to view
+ Broker load is an asynchronous import method. The specific import results
can be accessed through [SHOW
LOAD](../../../sql-manual/sql-reference/Show-Statements/SHOW-LOAD) command to
view
```
mysql> show load order by createtime desc limit 1\G;
@@ -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.md) 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/en/docs/data-operate/import/import-scenes/load-atomicity.md
b/docs/en/docs/data-operate/import/import-scenes/load-atomicity.md
index 821d6d29b61..9ffd79e5ed0 100644
--- a/docs/en/docs/data-operate/import/import-scenes/load-atomicity.md
+++ b/docs/en/docs/data-operate/import/import-scenes/load-atomicity.md
@@ -28,9 +28,9 @@ under the License.
All import operations in Doris have atomicity guarantees, that is, the data in
an import job either all succeed or all fail. It will not happen that only part
of the data is imported successfully.
-In [BROKER
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
we can also implement atomic import of multiple tables .
+In [BROKER
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
we can also implement atomic import of multiple tables .
-For the [materialized view](../../../query-acceleration/materialized-view.md)
attached to the table, atomicity and consistency with the base table are also
guaranteed.
+For the [materialized view](../../../query-acceleration/materialized-view)
attached to the table, atomicity and consistency with the base table are also
guaranteed.
## Label mechanism
diff --git
a/docs/en/docs/data-operate/import/import-scenes/load-data-convert.md
b/docs/en/docs/data-operate/import/import-scenes/load-data-convert.md
index e686da128c0..e1a79fda32c 100644
--- a/docs/en/docs/data-operate/import/import-scenes/load-data-convert.md
+++ b/docs/en/docs/data-operate/import/import-scenes/load-data-convert.md
@@ -28,7 +28,7 @@ under the License.
## Supported import methods
-- [BROKER
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
+- [BROKER
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
```sql
LOAD LABEL example_db.label1
@@ -48,7 +48,7 @@ under the License.
);
````
-- [STREAM
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/STREAM-LOAD.md)
+- [STREAM
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/STREAM-LOAD)
```bash
curl
@@ -60,7 +60,7 @@ under the License.
http://host:port/api/testDb/testTbl/_stream_load
````
-- [ROUTINE
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/CREATE-ROUTINE-LOAD.md)
+- [ROUTINE
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/CREATE-ROUTINE-LOAD)
```sql
CREATE ROUTINE LOAD example_db.label1 ON my_table
diff --git a/docs/en/docs/data-operate/import/import-scenes/load-strict-mode.md
b/docs/en/docs/data-operate/import/import-scenes/load-strict-mode.md
index 2887543cc4b..23699ee4ebc 100644
--- a/docs/en/docs/data-operate/import/import-scenes/load-strict-mode.md
+++ b/docs/en/docs/data-operate/import/import-scenes/load-strict-mode.md
@@ -36,7 +36,7 @@ Strict mode is all False by default, i.e. off.
Different import methods set strict mode in different ways.
-1. [BROKER
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
+1. [BROKER
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
```sql
LOAD LABEL example_db.label1
@@ -57,7 +57,7 @@ Different import methods set strict mode in different ways.
)
````
-2. [STREAM
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/STREAM-LOAD.md)
+2. [STREAM
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/STREAM-LOAD)
```bash
curl --location-trusted -u user:passwd \
@@ -66,7 +66,7 @@ Different import methods set strict mode in different ways.
http://host:port/api/example_db/my_table/_stream_load
````
-3. [ROUTINE
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/CREATE-ROUTINE-LOAD.md)
+3. [ROUTINE
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/CREATE-ROUTINE-LOAD)
```sql
CREATE ROUTINE LOAD example_db.test_job ON my_table
@@ -81,9 +81,9 @@ Different import methods set strict mode in different ways.
);
````
-4.
[INSERT](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Manipulation/INSERT.md)
+4.
[INSERT](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Manipulation/INSERT)
- Set via [session variables](../../../advanced/variables.md):
+ Set via [session variables](../../../advanced/variables):
```sql
SET enable_insert_strict = true;
diff --git a/docs/en/docs/data-operate/import/import-way/broker-load-manual.md
b/docs/en/docs/data-operate/import/import-way/broker-load-manual.md
index c059c05c68f..92f4d8ca142 100644
--- a/docs/en/docs/data-operate/import/import-way/broker-load-manual.md
+++ b/docs/en/docs/data-operate/import/import-way/broker-load-manual.md
@@ -26,11 +26,11 @@ under the License.
# Broker Load
-Broker load is an asynchronous import method, and the supported data sources
depend on the data sources supported by the
[Broker](../../../advanced/broker.md) process.
+Broker load is an asynchronous import method, and the supported data sources
depend on the data sources supported by the [Broker](../../../advanced/broker)
process.
-Because the data in the Doris table is ordered, Broker load uses the doris
cluster resources to sort the data when importing data. Complete massive
historical data migration relative to Spark load, the Doris cluster resource
usage is relatively large. , this method is used when the user does not have
Spark computing resources. If there are Spark computing resources, it is
recommended to use [Spark
load](../../../data-operate/import/import-way/spark-load-manual.md).
+Because the data in the Doris table is ordered, Broker load uses the doris
cluster resources to sort the data when importing data. Complete massive
historical data migration relative to Spark load, the Doris cluster resource
usage is relatively large. , this method is used when the user does not have
Spark computing resources. If there are Spark computing resources, it is
recommended to use [Spark
load](../../../data-operate/import/import-way/spark-load-manual).
-Users need to create [Broker
load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
import through MySQL protocol and import by viewing command to check the
import result.
+Users need to create [Broker
load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
import through MySQL protocol and import by viewing command to check the
import result.
## Applicable scene
@@ -78,7 +78,7 @@ BE pulls data from the broker during execution, and imports
the data into the sy
## start import
-Let's look at [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
through several actual scenario examples. use
+Let's look at [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
through several actual scenario examples. use
### Data import of Hive partition table
@@ -111,7 +111,7 @@ Then use Hive's Load command to import your data into the
Hive table
load data local inpath '/opt/custorm' into table ods_demo_detail;
````
-2. Create a Doris table, refer to the specific table syntax: [CREATE
TABLE](../../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE.md)
+2. Create a Doris table, refer to the specific table syntax: [CREATE
TABLE](../../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
````
CREATE TABLE `doris_ods_test_detail` (
@@ -149,7 +149,7 @@ PROPERTIES (
3. Start importing data
- Specific syntax reference: [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
+ Specific syntax reference: [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
```sql
LOAD LABEL broker_load_2022_03_23
@@ -256,13 +256,13 @@ LOAD LABEL demo.label_20220402
);
````
-The specific parameters here can refer to:
[Broker](../../../advanced/broker.md) and [Broker
Load](../../../sql-manual/sql-reference-v2
/Data-Manipulation-Statements/Load/BROKER-LOAD.md) documentation
+The specific parameters here can refer to:
[Broker](../../../advanced/broker.md) and [Broker
Load](../../../sql-manual/sql-reference-v2
/Data-Manipulation-Statements/Load/BROKER-LOAD) documentation
## View import status
We can view the status information of the above import task through the
following command,
-The specific syntax reference for viewing the import status [SHOW
LOAD](../../../sql-manual/sql-reference/Show-Statements/SHOW-LOAD.md)
+The specific syntax reference for viewing the import status [SHOW
LOAD](../../../sql-manual/sql-reference/Show-Statements/SHOW-LOAD)
```sql
mysql> show load order by createtime desc limit 1\G;
@@ -287,7 +287,7 @@ LoadFinishTime: 2022-04-01 18:59:11
## Cancel import
-When the broker load job status is not CANCELLED or FINISHED, it can be
manually canceled by the user. When canceling, you need to specify the Label of
the import task to be canceled. Cancel the import command syntax to execute
[CANCEL
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/CANCEL-LOAD.md)
view.
+When the broker load job status is not CANCELLED or FINISHED, it can be
manually canceled by the user. When canceling, you need to specify the Label of
the import task to be canceled. Cancel the import command syntax to execute
[CANCEL
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/CANCEL-LOAD)
view.
For example: cancel the import job with the label broker_load_2022_03_23 on
the database demo
@@ -298,7 +298,7 @@ CANCEL LOAD FROM demo WHERE LABEL =
"broker_load_2022_03_23";
### Broker parameters
-Broker Load needs to use the Broker process to access remote storage.
Different brokers need to provide different parameters. For details, please
refer to [Broker documentation](../../../advanced/broker.md).
+Broker Load needs to use the Broker process to access remote storage.
Different brokers need to provide different parameters. For details, please
refer to [Broker documentation](../../../advanced/broker).
### FE configuration
@@ -399,7 +399,7 @@ The configuration parameter
`async_loading_load_task_pool_size` of FE is used to
Session variables can be enabled by executing `set enable_profile=true` before
submitting the LOAD job. Then submit the import job. After the import job is
completed, you can view the profile of the import job in the `Queris` tab of
the FE web page.
-You can check the [SHOW LOAD
PROFILE](../../../sql-manual/sql-reference/Show-Statements/SHOW-LOAD-PROFILE.md)
help document for more usage help information.
+You can check the [SHOW LOAD
PROFILE](../../../sql-manual/sql-reference/Show-Statements/SHOW-LOAD-PROFILE)
help document for more usage help information.
This Profile can help analyze the running status of import jobs.
@@ -442,4 +442,4 @@ Currently the Profile can only be viewed after the job has
been successfully exe
## more help
-For more detailed syntax and best practices used by Broker Load, see [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
command manual, you can also enter `HELP BROKER LOAD` in the MySql client
command line for more help information.
+For more detailed syntax and best practices used by Broker Load, see [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
command manual, you can also enter `HELP BROKER LOAD` in the MySql client
command line for more help information.
diff --git a/docs/zh-CN/docs/advanced/broker.md
b/docs/zh-CN/docs/advanced/broker.md
index bb6058d5f82..1d0ab3c9de2 100644
--- a/docs/zh-CN/docs/advanced/broker.md
+++ b/docs/zh-CN/docs/advanced/broker.md
@@ -73,9 +73,9 @@ Broker 在 Doris 系统架构中的位置如下：
2. 对象存储
- 所有支持S3协议的对象存储
-1. [Broker Load](../data-operate/import/import-way/broker-load-manual.md)
-2. [数据导出（Export）](../data-operate/export/export-manual.md)
-3. [数据备份](../admin-manual/data-admin/backup.md)
+1. [Broker Load](../data-operate/import/import-way/broker-load-manual)
+2. [数据导出（Export）](../data-operate/export/export-manual)
+3. [数据备份](../admin-manual/data-admin/backup)
## Broker 信息
diff --git
a/docs/zh-CN/docs/data-operate/import/import-scenes/external-storage-load.md
b/docs/zh-CN/docs/data-operate/import/import-scenes/external-storage-load.md
index e64b27879a6..0aae25d0f34 100644
--- a/docs/zh-CN/docs/data-operate/import/import-scenes/external-storage-load.md
+++ b/docs/zh-CN/docs/data-operate/import/import-scenes/external-storage-load.md
@@ -36,7 +36,7 @@ under the License.
### 开始导入
-Hdfs load 创建导入语句，导入方式和[Broker
Load](../../../data-operate/import/import-way/broker-load-manual.md) 基本相同，只需要将
`WITH BROKER broker_name ()` 语句替换成如下部分
+Hdfs load 创建导入语句，导入方式和[Broker
Load](../../../data-operate/import/import-way/broker-load-manual) 基本相同，只需要将
`WITH BROKER broker_name ()` 语句替换成如下部分
```
LOAD LABEL db_name.label_name
@@ -82,11 +82,11 @@ Hdfs load 创建导入语句，导入方式和[Broker Load](../../../data-operat
"max_filter_ratio"="0.1"
);
```
- 关于参数介绍，请参阅[Broker
Load](../../../data-operate/import/import-way/broker-load-manual.md)，HA集群的创建语法，通过`HELP
BROKER LOAD`查看
+ 关于参数介绍，请参阅[Broker
Load](../../../data-operate/import/import-way/broker-load-manual)，HA集群的创建语法，通过`HELP
BROKER LOAD`查看
3. 查看导入状态
- Broker load 是一个异步的导入方式，具体导入结果可以通过[SHOW
LOAD](../../../sql-manual/sql-reference/Show-Statements/SHOW-LOAD.md)命令查看
+ Broker load 是一个异步的导入方式，具体导入结果可以通过[SHOW
LOAD](../../../sql-manual/sql-reference/Show-Statements/SHOW-LOAD)命令查看
```
mysql> show load order by createtime desc limit 1\G;
@@ -134,7 +134,7 @@ Hdfs load 创建导入语句，导入方式和[Broker Load](../../../data-operat
其他云存储系统可以相应的文档找到与S3兼容的相关信息
### 开始导入
-导入方式和 [Broker
Load](../../../data-operate/import/import-way/broker-load-manual.md) 基本相同，只需要将
`WITH BROKER broker_name ()` 语句替换成如下部分
+导入方式和 [Broker
Load](../../../data-operate/import/import-way/broker-load-manual) 基本相同，只需要将
`WITH BROKER broker_name ()` 语句替换成如下部分
```
WITH S3
(
diff --git
a/docs/zh-CN/docs/data-operate/import/import-scenes/load-data-convert.md
b/docs/zh-CN/docs/data-operate/import/import-scenes/load-data-convert.md
index ffaee2b2162..85ea1c7b5cb 100644
--- a/docs/zh-CN/docs/data-operate/import/import-scenes/load-data-convert.md
+++ b/docs/zh-CN/docs/data-operate/import/import-scenes/load-data-convert.md
@@ -28,7 +28,7 @@ under the License.
## 支持的导入方式
-- [BROKER
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
+- [BROKER
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
```sql
LOAD LABEL example_db.label1
diff --git
a/docs/zh-CN/docs/data-operate/import/import-scenes/load-strict-mode.md
b/docs/zh-CN/docs/data-operate/import/import-scenes/load-strict-mode.md
index 7708a461fc5..bc2ef570995 100644
--- a/docs/zh-CN/docs/data-operate/import/import-scenes/load-strict-mode.md
+++ b/docs/zh-CN/docs/data-operate/import/import-scenes/load-strict-mode.md
@@ -37,7 +37,7 @@ under the License.
不同的导入方式设置严格模式的方式不尽相同。
-1. [BROKER
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
+1. [BROKER
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
```sql
LOAD LABEL example_db.label1
diff --git
a/docs/zh-CN/docs/data-operate/import/import-way/broker-load-manual.md
b/docs/zh-CN/docs/data-operate/import/import-way/broker-load-manual.md
index e0a26843360..ef04f67ddd3 100644
--- a/docs/zh-CN/docs/data-operate/import/import-way/broker-load-manual.md
+++ b/docs/zh-CN/docs/data-operate/import/import-way/broker-load-manual.md
@@ -26,11 +26,11 @@ under the License.
# Broker Load
-Broker load 是一个异步的导入方式，支持的数据源取决于 [Broker](../../../advanced/broker.md)
进程支持的数据源。
+Broker load 是一个异步的导入方式，支持的数据源取决于 [Broker](../../../advanced/broker) 进程支持的数据源。
-因为 Doris 表里的数据是有序的，所以 Broker load 在导入数据的时是要利用doris 集群资源对数据进行排序，相对于 Spark load
来完成海量历史数据迁移，对 Doris 的集群资源占用要比较大，这种方式是在用户没有 Spark 这种计算资源的情况下使用，如果有 Spark
计算资源建议使用 [Spark
load](../../../data-operate/import/import-way/spark-load-manual.md)。
+因为 Doris 表里的数据是有序的，所以 Broker load 在导入数据的时是要利用doris 集群资源对数据进行排序，相对于 Spark load
来完成海量历史数据迁移，对 Doris 的集群资源占用要比较大，这种方式是在用户没有 Spark 这种计算资源的情况下使用，如果有 Spark
计算资源建议使用 [Spark
load](../../../data-operate/import/import-way/spark-load-manual)。
-用户需要通过 MySQL 协议 创建 [Broker
load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
导入，并通过查看导入命令检查导入结果。
+用户需要通过 MySQL 协议 创建 [Broker
load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
导入，并通过查看导入命令检查导入结果。
## 适用场景
@@ -78,7 +78,7 @@ BE 在执行的过程中会从 Broker 拉取数据，在对数据 transform 之
## 开始导入
-下面我们通过几个实际的场景示例来看 [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
的使用
+下面我们通过几个实际的场景示例来看 [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
的使用
### Hive 分区表的数据导入
@@ -111,7 +111,7 @@ lines terminated by '\n'
load data local inpath '/opt/custorm' into table ods_demo_detail;
```
-2. 创建 Doris 表，具体建表语法参照：[CREATE
TABLE](../../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE.md)
+2. 创建 Doris 表，具体建表语法参照：[CREATE
TABLE](../../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
```
CREATE TABLE `doris_ods_test_detail` (
@@ -149,7 +149,7 @@ PROPERTIES (
3. 开始导入数据
- 具体语法参照： [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
+ 具体语法参照： [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
```sql
LOAD LABEL broker_load_2022_03_23
(
@@ -255,13 +255,13 @@ LOAD LABEL demo.label_20220402
);
```
-这里的具体 参数可以参照： [Broker](../../../advanced/broker.md) 及 [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
文档
+这里的具体 参数可以参照： [Broker](../../../advanced/broker) 及 [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
文档
## 查看导入状态
我们可以通过下面的命令查看上面导入任务的状态信息，
-具体的查看导入状态的语法参考 [SHOW
LOAD](../../../sql-manual/sql-reference/Show-Statements/SHOW-LOAD.md)
+具体的查看导入状态的语法参考 [SHOW
LOAD](../../../sql-manual/sql-reference/Show-Statements/SHOW-LOAD)
```sql
mysql> show load order by createtime desc limit 1\G;
@@ -286,7 +286,7 @@ LoadFinishTime: 2022-04-01 18:59:11
## 取消导入
-当 Broker load 作业状态不为 CANCELLED 或 FINISHED 时，可以被用户手动取消。取消时需要指定待取消导入任务的 Label
。取消导入命令语法可执行 [CANCEL
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/CANCEL-LOAD.md)
查看。
+当 Broker load 作业状态不为 CANCELLED 或 FINISHED 时，可以被用户手动取消。取消时需要指定待取消导入任务的 Label
。取消导入命令语法可执行 [CANCEL
LOAD](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/CANCEL-LOAD)
查看。
例如：撤销数据库 demo 上， label 为 broker_load_2022_03_23 的导入作业
@@ -298,7 +298,7 @@ CANCEL LOAD FROM demo WHERE LABEL =
"broker_load_2022_03_23";
### Broker 参数
-Broker Load 需要借助 Broker 进程访问远端存储，不同的 Broker 需要提供不同的参数，具体请参阅
[Broker文档](../../../advanced/broker.md) 。
+Broker Load 需要借助 Broker 进程访问远端存储，不同的 Broker 需要提供不同的参数，具体请参阅
[Broker文档](../../../advanced/broker) 。
### FE 配置
@@ -399,7 +399,7 @@ FE 的配置参数 `async_loading_load_task_pool_size` 用于限制同时运行
可以在提交 LOAD 作业前，先执行 `set enable_profile=true` 打开会话变量。然后提交导入作业。待导入作业完成后，可以在 FE 的
web 页面的 `Queris` 标签中查看到导入作业的 Profile。
-可以查看 [SHOW LOAD
PROFILE](../../../sql-manual/sql-reference/Show-Statements/SHOW-LOAD-PROFILE.md)
帮助文档，获取更多使用帮助信息。
+可以查看 [SHOW LOAD
PROFILE](../../../sql-manual/sql-reference/Show-Statements/SHOW-LOAD-PROFILE)
帮助文档，获取更多使用帮助信息。
这个 Profile 可以帮助分析导入作业的运行状态。
@@ -442,4 +442,4 @@ FE 的配置参数 `async_loading_load_task_pool_size` 用于限制同时运行
## 更多帮助
-关于 Broker Load 使用的更多详细语法及最佳实践，请参阅 [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md)
命令手册，你也可以在 MySql 客户端命令行下输入 `HELP BROKER LOAD` 获取更多帮助信息。
+关于 Broker Load 使用的更多详细语法及最佳实践，请参阅 [Broker
Load](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD)
命令手册，你也可以在 MySql 客户端命令行下输入 `HELP BROKER LOAD` 获取更多帮助信息。
diff --git a/docs/zh-CN/docs/data-operate/update-delete/batch-delete-manual.md
b/docs/zh-CN/docs/data-operate/update-delete/batch-delete-manual.md
index 62a5e869bfa..237a50b6cdf 100644
--- a/docs/zh-CN/docs/data-operate/update-delete/batch-delete-manual.md
+++ b/docs/zh-CN/docs/data-operate/update-delete/batch-delete-manual.md
@@ -26,7 +26,7 @@ under the License.
# 批量删除
-目前Doris 支持 [Broker Load](../import/import-way/broker-load-manual.md)，[Routine
Load](../import/import-way/routine-load-manual.md)， [Stream
Load](../import/import-way/stream-load-manual.md)
等多种导入方式，对于数据的删除目前只能通过delete语句进行删除，使用delete 语句的方式删除时，每执行一次delete
都会生成一个新的数据版本，如果频繁删除会严重影响查询性能，并且在使用delete方式删除时，是通过生成一个空的rowset来记录删除条件实现，每次读取都要对删除条件进行过滤，同样在条件较多时会对性能造成影响。对比其他的系统，greenplum
的实现方式更像是传统数据库产品，snowflake 通过merge 语法实现。
+目前Doris 支持 [Broker Load](../import/import-way/broker-load-manual.md)，[Routine
Load](../import/import-way/routine-load-manual)， [Stream
Load](../import/import-way/stream-load-manual)
等多种导入方式，对于数据的删除目前只能通过delete语句进行删除，使用delete 语句的方式删除时，每执行一次delete
都会生成一个新的数据版本，如果频繁删除会严重影响查询性能，并且在使用delete方式删除时，是通过生成一个空的rowset来记录删除条件实现，每次读取都要对删除条件进行过滤，同样在条件较多时会对性能造成影响。对比其他的系统，greenplum
的实现方式更像是传统数据库产品，snowflake 通过merge 语法实现。
对于类似于cdc数据导入的场景，数据中insert和delete一般是穿插出现的，面对这种场景我们目前的导入方式也无法满足，即使我们能够分离出insert和delete虽然可以解决导入的问题，但是仍然解决不了删除的问题。使用批量删除功能可以解决这些个别场景的需求。数据导入有三种合并方式：
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
