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 4d814b8acb4 (doc)[fix] BROKER-LOAD.md Hyber Link 404 fixed (#164)
4d814b8acb4 is described below

commit 4d814b8acb4ddd45077c492231e1a795da43b478
Author: DingGeGe <109070189+dinggege1...@users.noreply.github.com>
AuthorDate: Tue Nov 22 20:05:51 2022 +0800

    (doc)[fix] BROKER-LOAD.md Hyber Link 404 fixed (#164)
---
 .../Load/BROKER-LOAD.md                            | 22 +++++++++++-----------
 .../Load/BROKER-LOAD.md                            | 22 +++++++++++-----------
 2 files changed, 22 insertions(+), 22 deletions(-)

diff --git 
a/docs/sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md
 
b/docs/sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md
index df065e9a409..a4a612c327b 100644
--- 
a/docs/sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md
+++ 
b/docs/sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md
@@ -100,7 +100,7 @@ WITH BROKER broker_name
 
   - `column list`
 
-    Used to specify the column order in the original file. For a detailed 
introduction to this part, please refer to the [Column Mapping, Conversion and 
Filtering](../../../../../data-operate/import/import-scenes/load-data-convert) 
document.
+    Used to specify the column order in the original file. For a detailed 
introduction to this part, please refer to the [Column Mapping, Conversion and 
Filtering](../../../../data-operate/import/import-scenes/load-data-convert.md) 
document.
 
     `(k1, k2, tmpk1)`
 
@@ -110,7 +110,7 @@ WITH BROKER broker_name
 
   - `PRECEDING FILTER predicate`
 
-    Pre-filter conditions. The data is first concatenated into raw data rows 
in order according to `column list` and `COLUMNS FROM PATH AS`. Then filter 
according to the pre-filter conditions. For a detailed introduction to this 
part, please refer to the [Column Mapping, Conversion and 
Filtering](../../../../../data-operate/import/import-scenes/load-data-convert) 
document.
+    Pre-filter conditions. The data is first concatenated into raw data rows 
in order according to `column list` and `COLUMNS FROM PATH AS`. Then filter 
according to the pre-filter conditions. For a detailed introduction to this 
part, please refer to the [Column Mapping, Conversion and 
Filtering](../../../../data-operate/import/import-scenes/load-data-convert.md) 
document.
 
   - `SET (column_mapping)`
 
@@ -118,7 +118,7 @@ WITH BROKER broker_name
 
   - `WHERE predicate`
 
-    Filter imported data based on conditions. For a detailed introduction to 
this part, please refer to the [Column Mapping, Conversion and 
Filtering](../../../../../data-operate/import/import-scenes/load-data-convert) 
document.
+    Filter imported data based on conditions. For a detailed introduction to 
this part, please refer to the [Column Mapping, Conversion and 
Filtering](../../../../data-operate/import/import-scenes/load-data-convert.md) 
document.
 
   - `DELETE ON expr`
 
@@ -134,7 +134,7 @@ WITH BROKER broker_name
 
 - `broker_properties`
 
-  Specifies the information required by the broker. This information is 
usually used by the broker to be able to access remote storage systems. Such as 
BOS or HDFS. See the [Broker](../../../../../advanced/broker) documentation for 
specific information.
+  Specifies the information required by the broker. This information is 
usually used by the broker to be able to access remote storage systems. Such as 
BOS or HDFS. See the [Broker](../../../../advanced/broker.md) documentation for 
specific information.
 
   ````text
   (
@@ -166,7 +166,7 @@ WITH BROKER broker_name
 
   - `timezone`
 
-    Specify the time zone for some functions that are affected by time zones, 
such as `strftime/alignment_timestamp/from_unixtime`, etc. Please refer to the 
[timezone](../../../../../advanced/time-zone) documentation for details. If not 
specified, the "Asia/Shanghai" timezone is used
+    Specify the time zone for some functions that are affected by time zones, 
such as `strftime/alignment_timestamp/from_unixtime`, etc. Please refer to the 
[timezone](../../../../advanced/time-zone.md) documentation for details. If not 
specified, the "Asia/Shanghai" timezone is used
     
   - `send_batch_parallelism` : 
   
@@ -409,29 +409,29 @@ WITH BROKER broker_name
 
 1. Check the import task status
 
-   Broker Load is an asynchronous import process. The successful execution of 
the statement only means that the import task is submitted successfully, and 
does not mean that the data import is successful. The import status needs to be 
viewed through the [SHOW LOAD](../../../Show-Statements/SHOW-LOAD) command.
+   Broker Load is an asynchronous import process. The successful execution of 
the statement only means that the import task is submitted successfully, and 
does not mean that the data import is successful. The import status needs to be 
viewed through the [SHOW LOAD](../../Show-Statements/SHOW-LOAD.md) command.
 
 2. Cancel the import task
 
-   Import tasks that have been submitted but not yet completed can be canceled 
by the [CANCEL LOAD](../CANCEL-LOAD) command. After cancellation, the written 
data will also be rolled back and will not take effect.
+   Import tasks that have been submitted but not yet completed can be canceled 
by the [CANCEL LOAD](CANCEL-LOAD.md) command. After cancellation, the written 
data will also be rolled back and will not take effect.
 
 3. Label, import transaction, multi-table atomicity
 
-   All import tasks in Doris are atomic. And the import of multiple tables in 
the same import task can also guarantee atomicity. At the same time, Doris can 
also use the Label mechanism to ensure that the data imported is not lost or 
heavy. For details, see the [Import Transactions and 
Atomicity](../../../../../data-operate/import/import-scenes/load-atomicity) 
documentation.
+   All import tasks in Doris are atomic. And the import of multiple tables in 
the same import task can also guarantee atomicity. At the same time, Doris can 
also use the Label mechanism to ensure that the data imported is not lost or 
heavy. For details, see the [Import Transactions and 
Atomicity](../../../../data-operate/import/import-scenes/load-atomicity.md) 
documentation.
 
 4. Column mapping, derived columns and filtering
 
-   Doris can support very rich column transformation and filtering operations 
in import statements. Most built-in functions and UDFs are supported. For how 
to use this function correctly, please refer to the [Column Mapping, Conversion 
and 
Filtering](../../../../../data-operate/import/import-scenes/load-data-convert) 
document.
+   Doris can support very rich column transformation and filtering operations 
in import statements. Most built-in functions and UDFs are supported. For how 
to use this function correctly, please refer to the [Column Mapping, Conversion 
and 
Filtering](../../../../data-operate/import/import-scenes/load-data-convert.md) 
document.
 
 5. Error data filtering
 
    Doris' import tasks can tolerate a portion of malformed data. Tolerated via 
`max_filter_ratio` setting. The default is 0, which means that the entire 
import task will fail when there is an error data. If the user wants to ignore 
some problematic data rows, the secondary parameter can be set to a value 
between 0 and 1, and Doris will automatically skip the rows with incorrect data 
format.
 
-   For some calculation methods of the tolerance rate, please refer to the 
[Column Mapping, Conversion and 
Filtering](../../../../../data-operate/import/import-scenes/load-data-convert) 
document.
+   For some calculation methods of the tolerance rate, please refer to the 
[Column Mapping, Conversion and 
Filtering](../../../../data-operate/import/import-scenes/load-data-convert.md) 
document.
 
 6. Strict Mode
 
-   The `strict_mode` attribute is used to set whether the import task runs in 
strict mode. The format affects the results of column mapping, transformation, 
and filtering. For a detailed description of strict mode, see the [strict 
mode](../../../../../data-operate/import/import-scenes/load-strict-mode) 
documentation.
+   The `strict_mode` attribute is used to set whether the import task runs in 
strict mode. The format affects the results of column mapping, transformation, 
and filtering. For a detailed description of strict mode, see the [strict 
mode](../../../../data-operate/import/import-scenes/load-strict-mode.md) 
documentation.
 
 7. Timeout
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md
index b55b83dfc14..8ec65e997ae 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Manipulation-Statements/Load/BROKER-LOAD.md
@@ -100,7 +100,7 @@ WITH BROKER broker_name
 
   - `column list`
 
-    用于指定原始文件中的列顺序。关于这部分详细介绍,可以参阅 
[列的映射,转换与过滤](../../../../../data-operate/import/import-scenes/load-data-convert.md)
 文档。
+    用于指定原始文件中的列顺序。关于这部分详细介绍,可以参阅 
[列的映射,转换与过滤](../../../../data-operate/import/import-scenes/load-data-convert.md)
 文档。
 
     `(k1, k2, tmpk1)`
 
@@ -110,7 +110,7 @@ WITH BROKER broker_name
 
   - `PRECEDING FILTER predicate`
 
-    前置过滤条件。数据首先根据 `column list` 和 `COLUMNS FROM PATH AS` 
按顺序拼接成原始数据行。然后按照前置过滤条件进行过滤。关于这部分详细介绍,可以参阅 
[列的映射,转换与过滤](../../../../../data-operate/import/import-scenes/load-data-convert.md)
 文档。
+    前置过滤条件。数据首先根据 `column list` 和 `COLUMNS FROM PATH AS` 
按顺序拼接成原始数据行。然后按照前置过滤条件进行过滤。关于这部分详细介绍,可以参阅 
[列的映射,转换与过滤](../../../../data-operate/import/import-scenes/load-data-convert.md)
 文档。
 
   - `SET (column_mapping)`
 
@@ -118,7 +118,7 @@ WITH BROKER broker_name
 
   - `WHERE predicate`
 
-    根据条件对导入的数据进行过滤。关于这部分详细介绍,可以参阅 
[列的映射,转换与过滤](../../../../../data-operate/import/import-scenes/load-data-convert.md)
 文档。
+    根据条件对导入的数据进行过滤。关于这部分详细介绍,可以参阅 
[列的映射,转换与过滤](../../../../data-operate/import/import-scenes/load-data-convert.md)
 文档。
 
   - `DELETE ON expr`
 
@@ -134,7 +134,7 @@ WITH BROKER broker_name
 
 - `broker_properties`
 
-  指定 broker 所需的信息。这些信息通常被用于 Broker 能够访问远端存储系统。如 BOS 或 HDFS。关于具体信息,可参阅 
[Broker](../../../../../advanced/broker.md) 文档。
+  指定 broker 所需的信息。这些信息通常被用于 Broker 能够访问远端存储系统。如 BOS 或 HDFS。关于具体信息,可参阅 
[Broker](../../../../advanced/broker.md) 文档。
 
   ```text
   (
@@ -166,7 +166,7 @@ WITH BROKER broker_name
 
   - `timezone`
 
-    指定某些受时区影响的函数的时区,如 `strftime/alignment_timestamp/from_unixtime` 等等,具体请查阅 
[时区](../../../../../advanced/time-zone.md) 文档。如果不指定,则使用 "Asia/Shanghai" 时区
+    指定某些受时区影响的函数的时区,如 `strftime/alignment_timestamp/from_unixtime` 等等,具体请查阅 
[时区](../../../../advanced/time-zone.md) 文档。如果不指定,则使用 "Asia/Shanghai" 时区
     
   - send_batch_parallelism: 用于设置发送批处理数据的并行度,如果并行度的值超过 BE 配置中的 
`max_send_batch_parallelism_per_job`,那么作为协调点的 BE 将使用 
`max_send_batch_parallelism_per_job` 的值。
   
@@ -406,29 +406,29 @@ WITH BROKER broker_name
 
 1. 查看导入任务状态
 
-   Broker Load 是一个异步导入过程,语句执行成功仅代表导入任务提交成功,并不代表数据导入成功。导入状态需要通过 [SHOW 
LOAD](../../../Show-Statements/SHOW-LOAD) 命令查看。
+   Broker Load 是一个异步导入过程,语句执行成功仅代表导入任务提交成功,并不代表数据导入成功。导入状态需要通过 [SHOW 
LOAD](../../Show-Statements/SHOW-LOAD.md) 命令查看。
 
 2. 取消导入任务
 
-   已提交切尚未结束的导入任务可以通过 [CANCEL LOAD](../CANCEL-LOAD) 命令取消。取消后,已写入的数据也会回滚,不会生效。
+   已提交切尚未结束的导入任务可以通过 [CANCEL LOAD](CANCEL-LOAD.md) 命令取消。取消后,已写入的数据也会回滚,不会生效。
 
 3. Label、导入事务、多表原子性
 
-   Doris 中所有导入任务都是原子生效的。并且在同一个导入任务中对多张表的导入也能够保证原子性。同时,Doris 还可以通过 Label 
的机制来保证数据导入的不丢不重。具体说明可以参阅 
[导入事务和原子性](../../../.../../ddata-operate/import/import-scenes/load-atomicity) 
文档。
+   Doris 中所有导入任务都是原子生效的。并且在同一个导入任务中对多张表的导入也能够保证原子性。同时,Doris 还可以通过 Label 
的机制来保证数据导入的不丢不重。具体说明可以参阅 
[导入事务和原子性](../../../../../current/data-operate/import/import-scenes/load-atomicity.md)
 文档。
 
 4. 列映射、衍生列和过滤
 
-   Doris 可以在导入语句中支持非常丰富的列转换和过滤操作。支持绝大多数内置函数和 UDF。关于如何正确的使用这个功能,可参阅 
[列的映射,转换与过滤](../../../.../../data-operate/import/import-scenes/load-data-convert)
 文档。
+   Doris 可以在导入语句中支持非常丰富的列转换和过滤操作。支持绝大多数内置函数和 UDF。关于如何正确的使用这个功能,可参阅 
[列的映射,转换与过滤](../../../../data-operate/import/import-scenes/load-data-convert.md)
 文档。
 
 5. 错误数据过滤
 
    Doris 的导入任务可以容忍一部分格式错误的数据。容忍了通过 `max_filter_ratio` 
设置。默认为0,即表示当有一条错误数据时,整个导入任务将会失败。如果用户希望忽略部分有问题的数据行,可以将次参数设置为 0~1 之间的数值,Doris 
会自动跳过哪些数据格式不正确的行。
 
-   关于容忍率的一些计算方式,可以参阅 
[列的映射,转换与过滤](../../../.../../ddata-operate/import/import-scenes/load-data-convert)
 文档。
+   关于容忍率的一些计算方式,可以参阅 
[列的映射,转换与过滤](../../../../data-operate/import/import-scenes/load-data-convert.md)
 文档。
 
 6. 严格模式
 
-   `strict_mode` 属性用于设置导入任务是否运行在严格模式下。该格式会对列映射、转换和过滤的结果产生影响。关于严格模式的具体说明,可参阅 
[严格模式](../../../.../../ddata-operate/import/import-scenes/load-strict-mode) 文档。
+   `strict_mode` 属性用于设置导入任务是否运行在严格模式下。该格式会对列映射、转换和过滤的结果产生影响。关于严格模式的具体说明,可参阅 
[严格模式](../../../../data-operate/import/import-scenes/load-strict-mode.md) 文档。
 
 7. 超时时间
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org

Reply via email to