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 8e47a9294cf fix
8e47a9294cf is described below
commit 8e47a9294cf95871020eb025dc5b5efe7eb7c6d0
Author: jiafeng.zhang <zhang...@gmail.com>
AuthorDate: Tue Oct 25 18:05:56 2022 +0800
fix
---
blog/Annoucing.md | 2 +-
.../cluster-management/elastic-expansion.md | 4 ++--
docs/advanced/alter-table/replace-table.md | 4 ++--
.../import/import-scenes/external-storage-load.md | 2 +-
docs/data-operate/import/import-scenes/jdbc-load.md | 4 ++--
docs/data-table/basic-usage.md | 14 +++++++-------
docs/data-table/hit-the-rollup.md | 4 ++--
.../Alter/ALTER-TABLE-REPLACE.md | 2 +-
.../Alter/ALTER-TABLE-ROLLUP.md | 4 ++--
.../Data-Definition-Statements/Drop/DROP-DATABASE.md | 2 +-
.../Data-Manipulation-Statements/Load/BROKER-LOAD.md | 4 ++--
.../SHOW-ALTER-TABLE-MATERIALIZED-VIEW.md | 2 +-
i18n/zh-CN/docusaurus-plugin-content-blog/Annoucing.md | 2 +-
.../cluster-management/elastic-expansion.md | 4 ++--
.../current/advanced/alter-table/replace-table.md | 2 +-
.../import/import-scenes/external-storage-load.md | 8 ++++----
.../data-operate/import/import-scenes/jdbc-load.md | 4 ++--
.../current/data-table/basic-usage.md | 18 +++++++++---------
.../current/data-table/hit-the-rollup.md | 2 +-
.../Alter/ALTER-TABLE-REPLACE.md | 2 +-
.../Alter/ALTER-TABLE-ROLLUP.md | 4 ++--
.../Data-Definition-Statements/Drop/DROP-DATABASE.md | 2 +-
.../SHOW-ALTER-TABLE-MATERIALIZED-VIEW.md | 2 +-
.../best-practices/star-schema-benchmark.md | 4 ++--
.../extending-doris/udf/user-defined-function.md | 2 +-
.../best-practices/star-schema-benchmark.md | 4 ++--
.../extending-doris/udf/user-defined-function.md | 2 +-
27 files changed, 55 insertions(+), 55 deletions(-)
diff --git a/blog/Annoucing.md b/blog/Annoucing.md
index 77bef3a0853..7ce634eb78d 100644
--- a/blog/Annoucing.md
+++ b/blog/Annoucing.md
@@ -52,4 +52,4 @@ Once again, we sincerely thank all contributors who
participated in the construc
**See How to subscribe:**
-[https://doris.apache.org/zh-CN/community/subscribe-mail-list](https://doris.apache.org/zh-CN/community/subscribe-mail-list)
+[https://doris.apache.org/community/subscribe-mail-list](https://doris.apache.org/community/subscribe-mail-list/)
diff --git a/docs/admin-manual/cluster-management/elastic-expansion.md
b/docs/admin-manual/cluster-management/elastic-expansion.md
index 17cb9111553..ea821f69bbb 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.md).
+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
@@ -140,7 +140,7 @@ DECOMMISSION clause:
> ```CANCEL ALTER SYSTEM DECOMMISSION BACKEND
> "be_host:be_heartbeat_service_port";```
> The order was cancelled. When cancelled, the data on the BE will
> maintain the current amount of data remaining. Follow-up Doris re-load
> balancing
-**For expansion and scaling of BE nodes in multi-tenant deployment
environments, please refer to the [Multi-tenant Design
Document](../multi-tenant.md).**
+**For expansion and scaling of BE nodes in multi-tenant deployment
environments, please refer to the [Multi-tenant Design
Document](../multi-tenant).**
## Broker Expansion and Shrinkage
diff --git a/docs/advanced/alter-table/replace-table.md
b/docs/advanced/alter-table/replace-table.md
index 9aa755710f0..13ad8d5cc4d 100644
--- a/docs/advanced/alter-table/replace-table.md
+++ b/docs/advanced/alter-table/replace-table.md
@@ -29,7 +29,7 @@ under the License.
In version 0.14, Doris supports atomic replacement of two tables.
This operation only applies to OLAP tables.
-For partition level replacement operations, please refer to [Temporary
Partition Document](../../partition/table-temp-partition)
+For partition level replacement operations, please refer to [Temporary
Partition Document](../partition/table-temp-partition.md)
## Syntax
@@ -69,4 +69,4 @@ If `swap` is `false`, the operation is as follows:
1. Atomic Overwrite Operation
- In some cases, the user wants to be able to rewrite the data of a certain
table, but if it is dropped and then imported, there will be a period of time
in which the data cannot be viewed. At this time, the user can first use the
`CREATE TABLE LIKE` statement to create a new table with the same structure,
import the new data into the new table, and replace the old table atomically
through the replacement operation to achieve the goal. For partition level
atomic overwrite operation, pl [...]
+ In some cases, the user wants to be able to rewrite the data of a certain
table, but if it is dropped and then imported, there will be a period of time
in which the data cannot be viewed. At this time, the user can first use the
`CREATE TABLE LIKE` statement to create a new table with the same structure,
import the new data into the new table, and replace the old table atomically
through the replacement operation to achieve the goal. For partition level
atomic overwrite operation, pl [...]
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 221a45c1f8c..f2ebd53e3af 100644
--- a/docs/data-operate/import/import-scenes/external-storage-load.md
+++ b/docs/data-operate/import/import-scenes/external-storage-load.md
@@ -82,7 +82,7 @@ Hdfs load creates an import statement. The import method is
basically the same a
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) 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;
diff --git a/docs/data-operate/import/import-scenes/jdbc-load.md
b/docs/data-operate/import/import-scenes/jdbc-load.md
index 27cc9cfe28e..b84ce15e81b 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)
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.md)
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), 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.md)
document.
diff --git a/docs/data-table/basic-usage.md b/docs/data-table/basic-usage.md
index 8022c39aacf..f4bf29cfb27 100644
--- a/docs/data-table/basic-usage.md
+++ b/docs/data-table/basic-usage.md
@@ -107,7 +107,7 @@ CREATE DATABASE example_db;
>
> 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).
+After the database is created, you can view the database information through
[SHOW DATABASES](../sql-manual/sql-reference/Show-Statements/SHOW-DATABASES.md).
```sql
MySQL> SHOW DATABASES;
@@ -142,7 +142,7 @@ mysql> USE example_db;
Database changed
```
-Doris supports [composite partition and single partition](../data-partition)
two table building methods. The following takes the aggregation model as an
example to demonstrate how to create two partitioned data tables.
+Doris supports [composite partition and single partition](./data-partition.md)
two table building methods. The following takes the aggregation model as an
example to demonstrate how to create two partitioned data tables.
#### Single partition
@@ -406,7 +406,7 @@ MySQL> SELECT SUM(pv) FROM table2 WHERE siteid IN (SELECT
siteid FROM table1 WHE
## Table Structure Change
-Use the [ALTER TABLE
COLUMN](../sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-COLUMN)
command to modify the table Schema, including the following changes.
+Use the [ALTER TABLE
COLUMN](../sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-COLUMN.md)
command to modify the table Schema, including the following changes.
- Adding columns
- Deleting columns
@@ -470,7 +470,7 @@ For more help, see ``HELP ALTER TABLE``.
Rollup can be understood as a materialized index structure for a Table.
**Materialized** because its data is physically stored independently, and
**Indexed** in the sense that Rollup can reorder columns to increase the hit
rate of prefix indexes, and can reduce key columns to increase the aggregation
of data.
-Use [ALTER TABLE
ROLLUP](../sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP)
to perform various changes to Rollup.
+Use [ALTER TABLE
ROLLUP](../sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP.md)
to perform various changes to Rollup.
The following examples are given
@@ -539,7 +539,7 @@ Materialized views are a space-for-time data analysis
acceleration technique, an
At the same time, Doris can automatically ensure data consistency between
materialized views and base tables, and automatically match the appropriate
materialized view at query time, greatly reducing the cost of data maintenance
for users and providing a consistent and transparent query acceleration
experience for users.
-For more information about materialized views, see [Materialized
Views](../advanced/materialized-view)
+For more information about materialized views, see [Materialized
Views](../advanced/materialized-view.md)
## Data table queries
@@ -656,7 +656,7 @@ mysql> select sum(table1.pv) from table1 join [shuffle]
table2 where table1.site
When deploying multiple FE nodes, you can deploy a load balancing layer on top
of multiple FEs to achieve high availability of Doris.
-Please refer to [Load Balancing](...) for details on installation, deployment,
and usage. /admin-manual/cluster-management/load-balancing)
+Please refer to [Load
Balancing](../admin-manual/cluster-management/load-balancing)
## Data update and deletion
@@ -664,4 +664,4 @@ Doris supports deleting imported data in two ways. One way
is to delete data by
The other deletion method is for the Unique primary key unique model only,
where the primary key rows to be deleted are imported by importing the data,
and the final physical deletion of the data is performed internally by Doris
using the delete tag bit. This deletion method is suitable for deleting data in
a real-time manner.
-For specific instructions on delete and update operations, see [Data
Update](...). /data-operate/update-delete/update) documentation.
+For specific instructions on delete and update operations, see [Data
Update](../data-operate/update-delete/update.md) documentation.
diff --git a/docs/data-table/hit-the-rollup.md
b/docs/data-table/hit-the-rollup.md
index 85cac8c0df3..90bedf68085 100644
--- a/docs/data-table/hit-the-rollup.md
+++ b/docs/data-table/hit-the-rollup.md
@@ -44,7 +44,7 @@ Because Uniq is only a special case of the Aggregate model,
we do not distinguis
Example 1: Get the total consumption per user
-Following [Data Model Aggregate Model](../data-model.md) in the **Aggregate
Model** section, the Base table structure is as follows:
+Following [Data Model Aggregate Model](./data-model.md) in the **Aggregate
Model** section, the Base table structure is as follows:
| ColumnName | Type | AggregationType | Comment
|
|-------------------| ------------ | --------------- |
-------------------------------------- |
@@ -185,7 +185,7 @@ However, in order to hit Rollup, certain conditions need to
be met, and the valu
### Index
-Doris's prefix index has been introduced in the previous query practice, that
is, Doris will generate the first 36 bytes in the Base/Rollup table separately
in the underlying storage engine (with varchar type, the prefix index may be
less than 36 bytes, varchar will truncate the prefix index, and use up to 20
bytes of varchar). A sorted sparse index data (data is also sorted, positioned
by index, and then searched by dichotomy in the data), and then matched each
Base/Rollup prefix index [...]
+The prefix index was described earlier in
[prefix-index](./index/prefix-index.md), Doris takes the first 36 bytes of the
Base/Rollup table (a varchar type may result in a prefix index of less than 36
bytes; a varchar truncates the prefix index and uses up to 20 bytes of the
varchar ) generates a separate sorted sparse indexed data in the underlying
storage engine (the data is also sorted, indexed, and then does a dichotomous
lookup in the data), and then matches the prefix index of each [...]
```
---> matching from left to right
diff --git
a/docs/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-REPLACE.md
b/docs/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-REPLACE.md
index e14188172b2..98df98892e8 100644
---
a/docs/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-REPLACE.md
+++
b/docs/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-REPLACE.md
@@ -83,4 +83,4 @@ ALTER, TABLE, REPLACE, ALTER TABLE
### Best Practice
1. Atomic overlay write operations
- In some cases, the user wants to be able to rewrite the data of a table,
but if the deletion and then import method is used, the data cannot be viewed
for a period of time. In this case, you can use the `CREATE TABLE LIKE`
statement to CREATE a new TABLE with the same structure. After importing the
new data into the new TABLE, you can replace the old TABLE atomic to achieve
the purpose.
+ In some cases, the user wants to be able to rewrite the data of a certain
table, but if this is done by deleting first and then importing, there will be
a period of time in between when the data cannot be viewed. In this case, the
user can first use the `CREATE TABLE LIKE` statement to create a new table with
the same structure, import the new data into the new table, and then replace
the old table atomically through a replace operation to achieve the goal. For
partition-level atomic o [...]
\ No newline at end of file
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 d8660a1424e..e5d35e18758 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](../../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](/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](/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
3. Delete rollup index
diff --git
a/docs/sql-manual/sql-reference/Data-Definition-Statements/Drop/DROP-DATABASE.md
b/docs/sql-manual/sql-reference/Data-Definition-Statements/Drop/DROP-DATABASE.md
index a5d329e7fa6..d44bc3f25e3 100644
---
a/docs/sql-manual/sql-reference/Data-Definition-Statements/Drop/DROP-DATABASE.md
+++
b/docs/sql-manual/sql-reference/Data-Definition-Statements/Drop/DROP-DATABASE.md
@@ -41,7 +41,7 @@ DROP DATABASE [IF EXISTS] db_name [FORCE];
illustrate:
-- During the execution of DROP DATABASE, the deleted database can be recovered
through the RECOVER statement. See the
[RECOVER](../../../sql-manual/sql-reference/Database-Administration-Statements/RECOVER)
statement for details
+- During the execution of DROP DATABASE, the deleted database can be recovered
through the RECOVER statement. See the
[RECOVER](../../../../sql-manual/sql-reference/Database-Administration-Statements/RECOVER.md)
statement for details
- If you execute DROP DATABASE FORCE, the system will not check the database
for unfinished transactions, the database will be deleted directly and cannot
be recovered, this operation is generally not recommended
### Example
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 41d42c71a78..df065e9a409 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
@@ -427,11 +427,11 @@ WITH BROKER broker_name
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)
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)
documentation.
7. Timeout
diff --git
a/docs/sql-manual/sql-reference/Show-Statements/SHOW-ALTER-TABLE-MATERIALIZED-VIEW.md
b/docs/sql-manual/sql-reference/Show-Statements/SHOW-ALTER-TABLE-MATERIALIZED-VIEW.md
index cfa1c922810..020935ae990 100644
---
a/docs/sql-manual/sql-reference/Show-Statements/SHOW-ALTER-TABLE-MATERIALIZED-VIEW.md
+++
b/docs/sql-manual/sql-reference/Show-Statements/SHOW-ALTER-TABLE-MATERIALIZED-VIEW.md
@@ -32,7 +32,7 @@ SHOW ALTER TABLE MATERIALIZED VIEW
### Description
-This command is used to view the execution of the Create Materialized View job
submitted through the
[CREATE-MATERIALIZED-VIEW](../../../sql-reference/Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW)
statement.
+This command is used to view the execution of the Create Materialized View job
submitted through the
[CREATE-MATERIALIZED-VIEW](../../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW)
statement.
> This statement is equivalent to `SHOW ALTER TABLE ROLLUP`;
diff --git a/i18n/zh-CN/docusaurus-plugin-content-blog/Annoucing.md
b/i18n/zh-CN/docusaurus-plugin-content-blog/Annoucing.md
index bb777b21b41..29e78a6902c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-blog/Annoucing.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-blog/Annoucing.md
@@ -71,4 +71,4 @@ Apache Doris 后续将开展更多富有挑战且有意义的工作，包括新
**See How to subscribe:**
-[http://doris.apache.org/community/subscribe-mail-list.html](http://doris.apache.org/community/subscribe-mail-list.html)
+[https://doris.apache.org/zh-CN/community/subscribe-mail-list](https://doris.apache.org/zh-CN/community/subscribe-mail-list/)
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 66f1abb994c..6e2c03c5cef 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.md)。
+BE
节点的扩容和缩容过程，不影响当前系统运行以及正在执行的任务，并且不会影响当前系统的性能。数据均衡会自动进行。根据集群现有数据量的大小，集群会在几个小时到1天不等的时间内，恢复到负载均衡的状态。集群负载情况，可以参见
[Tablet 负载均衡文档](../maint-monitor/tablet-repair-and-balance)。
### 增加 BE 节点
@@ -134,7 +134,7 @@ DECOMMISSION 语句如下：
> ```CANCEL DECOMMISSION BACKEND
"be_host:be_heartbeat_service_port";```
> 命令取消。取消后，该 BE 上的数据将维持当前剩余的数据量。后续 Doris 重新进行负载均衡
-**对于多租户部署环境下，BE 节点的扩容和缩容，请参阅 [多租户设计文档](../multi-tenant.md)。**
+**对于多租户部署环境下，BE 节点的扩容和缩容，请参阅 [多租户设计文档](../multi-tenant)。**
## Broker 扩容缩容
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced/alter-table/replace-table.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced/alter-table/replace-table.md
index 216350e2bb2..fb79f6de7e6 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced/alter-table/replace-table.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced/alter-table/replace-table.md
@@ -28,7 +28,7 @@ under the License.
在 0.14 版本中，Doris 支持对两个表进行原子的替换操作。 该操作仅适用于 OLAP 表。
-分区级别的替换操作，请参阅 [临时分区文档](../../partition/table-temp-partition)
+分区级别的替换操作，请参阅 [临时分区文档](../partition/table-temp-partition.md)
## 语法说明
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-scenes/external-storage-load.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-scenes/external-storage-load.md
index 88c5a271e71..a0b28959e2f 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-scenes/external-storage-load.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-scenes/external-storage-load.md
@@ -49,7 +49,7 @@ Hdfs load 创建导入语句，导入方式和[Broker Load](../../../data-operat
1. 创建一张表
- 通过 `CREATE TABLE` 命令在`demo`创建一张表用于存储待导入的数据。具体的导入方式请查阅 [CREATE
TABLE](../../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE.md)
命令手册。示例如下：
+ 通过 `CREATE TABLE` 命令在`demo`创建一张表用于存储待导入的数据。具体的导入方式请查阅 [CREATE
TABLE](../../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
命令手册。示例如下：
```sql
CREATE TABLE IF NOT EXISTS load_hdfs_file_test
@@ -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)命令查看
+ 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-scenes/jdbc-load.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-scenes/jdbc-load.md
index ada0d26ddce..6843249ccdf 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-scenes/jdbc-load.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-scenes/jdbc-load.md
@@ -35,7 +35,7 @@ INSERT 语句的使用方式和 MySQL 等数据库中 INSERT 语句的使用方
* INSERT INTO table VALUES(...)
```
-这里我们仅介绍第二种方式。关于 INSERT 命令的详细说明，请参阅
[INSERT](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Manipulation/INSERT)
命令文档。
+这里我们仅介绍第二种方式。关于 INSERT 命令的详细说明，请参阅
[INSERT](../../sql-manual/sql-reference/Data-Manipulation-Statements/Manipulation/INSERT.md)
命令文档。
## 单次写入
@@ -160,4 +160,4 @@ public class DorisJDBCDemo {
前面提到，我们建议在使用 INSERT 导入数据时，采用 ”批“ 的方式进行导入，而不是单条插入。
- 同时，我们可以为每次 INSERT 操作设置一个 Label。通过 [Label 机制](../load-atomicity)
可以保证操作的幂等性和原子性，最终做到数据的不丢不重。关于 INSERT 中 Label 的具体用法，可以参阅
[INSERT](../../../sql-manual/sql-reference/Data-Manipulation-Statements/Manipulation/INSERT)
文档。
+ 同时，我们可以为每次 INSERT 操作设置一个 Label。通过 [Label 机制](./load-atomicity.md)
可以保证操作的幂等性和原子性，最终做到数据的不丢不重。关于 INSERT 中 Label 的具体用法，可以参阅
[INSERT](../../sql-manual/sql-reference/Data-Manipulation-Statements/Manipulation/INSERT.md)
文档。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-table/basic-usage.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-table/basic-usage.md
index 51d52d998b5..faa1c22b842 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-table/basic-usage.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-table/basic-usage.md
@@ -42,7 +42,7 @@ Doris 内置 root，密码默认为空。
>
>root 用户默认拥有集群所有权限。同时拥有 Grant_priv 和 Node_priv 的用户，可以将该权限赋予其他用户，拥有节点变更权限，包括
>FE、BE、BROKER 节点的添加、删除、下线等操作。
>
->关于权限这块的具体说明可以参照[权限管理](/docs/admin-manual/privilege-ldap/user-privilege)
+>关于权限这块的具体说明可以参照[权限管理](/docs/admin-manual/privilege-ldap/user-privilege.md)
启动完 Doris 程序之后，可以通过 root 或 admin 用户连接到 Doris 集群。 使用下面命令即可登录
Doris，登录后进入到Doris对应的Mysql命令行操作界面：
@@ -130,7 +130,7 @@ CREATE DATABASE example_db;
> SHOW CREATE ROUTINE LOAD
> ```
-数据库创建完成之后，可以通过 [SHOW
DATABASES](../sql-manual/sql-reference/Show-Statements/SHOW-DATABASES) 查看数据库信息。
+数据库创建完成之后，可以通过 [SHOW
DATABASES](../sql-manual/sql-reference/Show-Statements/SHOW-DATABASES.md)
查看数据库信息。
```sql
mysql> SHOW DATABASES;
@@ -165,7 +165,7 @@ mysql> USE example_db;
Database changed
```
-Doris支持[复合分区和单分区](../data-partition)两种建表方式。下面以聚合模型为例，分别演示如何创建两种分区的数据表。
+Doris支持[复合分区和单分区](./data-partition.md)两种建表方式。下面以聚合模型为例，分别演示如何创建两种分区的数据表。
#### 单分区
@@ -328,7 +328,7 @@ curl --location-trusted -u test:test -H
"label:table2_20170707" -H "column_separ
> 注意事项：
>
> 1. 采用流式导入建议文件大小限制在 10GB 以内，过大的文件会导致失败重试代价变大。
-> 2. label：Label 的主要作用是唯一标识一个导入任务，并且能够保证相同的 Label 仅会被成功导入一次，具体可以查看 [数据导入事务及原子性
](../data-operate/import/import-scenes/load-atomicity)。
+> 2. label：Label 的主要作用是唯一标识一个导入任务，并且能够保证相同的 Label 仅会被成功导入一次，具体可以查看 [数据导入事务及原子性
](../data-operate/import/import-scenes/load-atomicity.md)。
> 3. 流式导入是同步命令。命令返回成功则表示数据已经导入，返回失败表示这批数据没有导入。
#### Broker 导入
@@ -431,7 +431,7 @@ mysql> SELECT SUM(pv) FROM table2 WHERE siteid IN (SELECT
siteid FROM table1 WHE
## 表结构变更
-使用 [ALTER TABLE
COLUMN](../sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-COLUMN)
命令可以修改表的 Schema，包括如下修改：
+使用 [ALTER TABLE
COLUMN](../sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-COLUMN.md)
命令可以修改表的 Schema，包括如下修改：
- 增加列
- 删除列
@@ -495,7 +495,7 @@ CANCEL ALTER TABLE COLUMN FROM table1;
Rollup 可以理解为 Table 的一个物化索引结构。**物化** 是因为其数据在物理上独立存储，而 **索引**
的意思是，Rollup可以调整列顺序以增加前缀索引的命中率，也可以减少key列以增加数据的聚合度。
-使用[ALTER TABLE
ROLLUP](../sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP)可以进行Rollup的各种变更操作。
+使用[ALTER TABLE
ROLLUP](../sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-ROLLUP.md)可以进行Rollup的各种变更操作。
以下举例说明
@@ -562,7 +562,7 @@ Rollup 建立之后，查询不需要指定 Rollup 进行查询。还是指定
同时，Doris
能够自动保证物化视图和基础表的数据一致性，并且在查询时自动匹配合适的物化视图，极大降低用户的数据维护成本，为用户提供一个一致且透明的查询加速体验。
-关于物化视图的具体介绍，可参阅 [物化视图](../advanced/materialized-view)
+关于物化视图的具体介绍，可参阅 [物化视图](../advanced/materialized-view.md)
## 数据表的查询
@@ -679,7 +679,7 @@ mysql> select sum(table1.pv) from table1 join [shuffle]
table2 where table1.site
当部署多个 FE 节点时，用户可以在多个 FE 之上部署负载均衡层来实现 Doris 的高可用。
-具体安装部署及使用方式请参照 [负载均衡](../admin-manual/cluster-management/load-balancing)
+具体安装部署及使用方式请参照 [负载均衡](../admin-manual/cluster-management/load-balancing.md)
## 数据更新和删除
@@ -687,4 +687,4 @@ Doris 支持通过两种方式对已导入的数据进行删除。一种是通
另一种删除方式仅针对 Unique 主键唯一模型，通过导入数据的方式将需要删除的主键行数据进行导入。Doris
内部会通过删除标记位对数据进行最终的物理删除。这种删除方式适合以实时的方式对数据进行删除。
-关于删除和更新操作的具体说明，可参阅 [数据更新](../data-operate/update-delete/update) 相关文档。
+关于删除和更新操作的具体说明，可参阅 [数据更新](../data-operate/update-delete/update.md) 相关文档。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-table/hit-the-rollup.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-table/hit-the-rollup.md
index 335a8380d37..288b850d80c 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-table/hit-the-rollup.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-table/hit-the-rollup.md
@@ -44,7 +44,7 @@ ROLLUP 表的基本作用，在于在 Base 表的基础上，获得更粗粒度
1. 示例1：获得每个用户的总消费
-接 **[数据模型Aggregate 模型](../data-model)**小节的**示例2**，Base 表结构如下：
+接 **[数据模型Aggregate 模型](./data-model.md)**小节的**示例2**，Base 表结构如下：
| ColumnName | Type | AggregationType | Comment |
| --------------- | ----------- | --------------- | ---------------------- |
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-REPLACE.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-REPLACE.md
index 3c23fbb5dcb..88b54538fbd 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-REPLACE.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Alter/ALTER-TABLE-REPLACE.md
@@ -83,4 +83,4 @@ ALTER, TABLE, REPLACE, ALTER TABLE
### Best Practice
1. 原子的覆盖写操作
- 某些情况下，用户希望能够重写某张表的数据，但如果采用先删除再导入的方式进行，在中间会有一段时间无法查看数据。这时，用户可以先使用 `CREATE
TABLE LIKE` 语句创建一个相同结构的新表，将新的数据导入到新表后，通过替换操作，原子的替换旧表，以达到目的。分区级别的原子覆盖写操作，请参阅
[临时分区文档](../../../../../advanced/partition/table-temp-partition)。
+ 某些情况下，用户希望能够重写某张表的数据，但如果采用先删除再导入的方式进行，在中间会有一段时间无法查看数据。这时，用户可以先使用 `CREATE
TABLE LIKE` 语句创建一个相同结构的新表，将新的数据导入到新表后，通过替换操作，原子的替换旧表，以达到目的。分区级别的原子覆盖写操作，请参阅
[临时分区文档](../../../../advanced/partition/table-temp-partition.md)。
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 1f74ab95d23..dabd7a87681 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](../../Show-Statements/SHOW-ALTER) 命令查看进度。
+该语句用于对已有 table 进行 rollup 进行修改操作。rollup 是异步操作，任务提交成功则返回，之后可使用[SHOW
ALTER](/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](/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-TABLE)
3. 删除 rollup index
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Drop/DROP-DATABASE.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Drop/DROP-DATABASE.md
index 2919dbc2770..783a0822b87 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Drop/DROP-DATABASE.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Drop/DROP-DATABASE.md
@@ -41,7 +41,7 @@ DROP DATABASE [IF EXISTS] db_name [FORCE];
说明：
-- 执行 DROP DATABASE 一段时间内，可以通过 RECOVER 语句恢复被删除的数据库。详见
[RECOVER](../../../sql-manual/sql-reference/Database-Administration-Statements/RECOVER)
语句
+- 执行 DROP DATABASE 一段时间内，可以通过 RECOVER 语句恢复被删除的数据库。详见
[RECOVER](../../../../sql-manual/sql-reference/Database-Administration-Statements/RECOVER.md)
语句
- 如果执行 DROP DATABASE FORCE，则系统不会检查该数据库是否存在未完成的事务，数据库将直接被删除并且不能被恢复，一般不建议执行此操作
### Example
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Show-Statements/SHOW-ALTER-TABLE-MATERIALIZED-VIEW.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Show-Statements/SHOW-ALTER-TABLE-MATERIALIZED-VIEW.md
index c9574bb0165..fb4171d69ff 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Show-Statements/SHOW-ALTER-TABLE-MATERIALIZED-VIEW.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Show-Statements/SHOW-ALTER-TABLE-MATERIALIZED-VIEW.md
@@ -32,7 +32,7 @@ SHOW ALTER TABLE MATERIALIZED VIEW
### Description
-该命令用于查看通过
[CREATE-MATERIALIZED-VIEW](../../../sql-reference/Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW)
语句提交的创建物化视图作业的执行情况。
+该命令用于查看通过
[CREATE-MATERIALIZED-VIEW](../../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW)
语句提交的创建物化视图作业的执行情况。
> 该语句等同于 `SHOW ALTER TABLE ROLLUP`;
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.15/best-practices/star-schema-benchmark.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.15/best-practices/star-schema-benchmark.md
index 0df33cf5c5e..99d10e8b18a 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.15/best-practices/star-schema-benchmark.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.15/best-practices/star-schema-benchmark.md
@@ -36,7 +36,7 @@ under the License.
## 环境准备
-请先参照 [官方文档](../installing/install-deploy.html) 进行 Doris 的安装部署，以获得一个正常运行中的
Doris 集群（至少包含 1 FE，1 BE）。
+请先参照 [官方文档](https://doris.apache.org/docs/0.15/installing/install-deploy/) 进行
Doris 的安装部署，以获得一个正常运行中的 Doris 集群（至少包含 1 FE，1 BE）。
以下文档中涉及的的脚本都存放在 Doris 代码库的 `tools/ssb-tools/` 下。
@@ -162,5 +162,5 @@ SSB 测试集共 4 组 14 个 SQL。查询语句在 [queries/](https://github.c
>
> 注4：Parallelism 表示查询并发度，通过 `set parallel_fragment_exec_instance_num=8` 设置。
>
- > 注5：Runtime Filter Mode 是 Runtime Filter 的类型，通过 `set
runtime_filter_type="BLOOM_FILTER"` 设置。（[Runtime
Filter](../administrator-guide/runtime-filter/) 功能对 SSB 测试集效果显著。因为该测试集中，Join
算子右表的数据可以对左表起到很好的过滤作用。你可以尝试通过 `set runtime_filter_mode=off` 关闭该功能，看看查询延迟的变化。）
+ > 注5：Runtime Filter Mode 是 Runtime Filter 的类型，通过 `set
runtime_filter_type="BLOOM_FILTER"` 设置。（[Runtime
Filter](https://doris.apache.org/zh-CN/docs/0.15/administrator-guide/runtime-filter/)
功能对 SSB 测试集效果显著。因为该测试集中，Join 算子右表的数据可以对左表起到很好的过滤作用。你可以尝试通过 `set
runtime_filter_mode=off` 关闭该功能，看看查询延迟的变化。）
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.15/extending-doris/udf/user-defined-function.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.15/extending-doris/udf/user-defined-function.md
index d4c8c7b8c47..1822172bf49 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.15/extending-doris/udf/user-defined-function.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.15/extending-doris/udf/user-defined-function.md
@@ -35,7 +35,7 @@ UDF 能满足的分析需求分为两种：UDF 和 UDAF。本文中的 UDF 指
这篇文档主要讲述了，如何编写自定义的 UDF 函数，以及如何在 Doris 中使用它。
-如果用户使用 UDF 功能并扩展了 Doris 的函数分析，并且希望将自己实现的 UDF 函数贡献回 Doris 社区给其他用户使用，这时候请看文档
[Contribute UDF](./contribute_udf.md)。
+如果用户使用 UDF 功能并扩展了 Doris 的函数分析，并且希望将自己实现的 UDF 函数贡献回 Doris 社区给其他用户使用，这时候请看文档
[Contribute
UDF](https://doris.apache.org/zh-CN/docs/0.15/extending-doris/udf/contribute-udf)。
## 编写 UDF 函数
diff --git
a/versioned_docs/version-0.15/best-practices/star-schema-benchmark.md
b/versioned_docs/version-0.15/best-practices/star-schema-benchmark.md
index aacb08635d7..ec9b0715bf5 100644
--- a/versioned_docs/version-0.15/best-practices/star-schema-benchmark.md
+++ b/versioned_docs/version-0.15/best-practices/star-schema-benchmark.md
@@ -36,7 +36,7 @@ This document mainly introduces how to pass the preliminary
performance test of
## Environmental preparation
-Please refer to the [official document](../installing/install-deploy) to
install and deploy Doris to obtain a normal running Doris cluster ( Contain at
least 1 FE, 1 BE).
+Please refer to the [official
document](https://doris.apache.org/zh-CN/docs/0.15/installing/install-deploy/)
to install and deploy Doris to obtain a normal running Doris cluster ( Contain
at least 1 FE, 1 BE).
The scripts involved in the following documents are all stored under
`tools/ssb-tools/` in the Doris code base.
@@ -162,4 +162,4 @@ The following test report is based on Doris
[branch-0.15](https://github.com/apa
>
> Note 4: Parallelism means query concurrency, which is set by `set
parallel_fragment_exec_instance_num=8`.
>
- > Note 5: Runtime Filter Mode is the type of Runtime Filter, set by `set
runtime_filter_type="BLOOM_FILTER"`. ([Runtime
Filter](../administrator-guide/runtime-filter/) function has a significant
effect on the SSB test set. Because in this test set, The data from the right
table of Join can filter the left table very well. You can try to turn off this
function through `set runtime_filter_mode=off` to see the change in query
latency.)
+ > Note 5: Runtime Filter Mode is the type of Runtime Filter, set by `set
runtime_filter_type="BLOOM_FILTER"`. ([Runtime
Filter](https://doris.apache.org/docs/0.15/administrator-guide/runtime-filter/)
function has a significant effect on the SSB test set. Because in this test
set, The data from the right table of Join can filter the left table very well.
You can try to turn off this function through `set runtime_filter_mode=off` to
see the change in query latency.)
diff --git
a/versioned_docs/version-0.15/extending-doris/udf/user-defined-function.md
b/versioned_docs/version-0.15/extending-doris/udf/user-defined-function.md
index 304760b40b4..34d1c0d49f1 100644
--- a/versioned_docs/version-0.15/extending-doris/udf/user-defined-function.md
+++ b/versioned_docs/version-0.15/extending-doris/udf/user-defined-function.md
@@ -34,7 +34,7 @@ There are two types of analysis requirements that UDF can
meet: UDF and UDAF. UD
This document mainly describes how to write a custom UDF function and how to
use it in Doris.
-If users use the UDF function and extend Doris' function analysis, and want to
contribute their own UDF functions back to the Doris community for other users,
please see the document [Contribute UDF](../contribute_udf).
+If users use the UDF function and extend Doris' function analysis, and want to
contribute their own UDF functions back to the Doris community for other users,
please see the document [Contribute
UDF](https://doris.apache.org/zh-CN/docs/0.15/extending-doris/udf/contribute-udf).
## Writing UDF functions
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
