This is an automated email from the ASF dual-hosted git repository.
morningman pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new fc04b2c271e typo(docs): fix some docs problem (#2227)
fc04b2c271e is described below
commit fc04b2c271ecb29ad859d71bd6b797d229d36d2a
Author: LGD.HuaFEEng <[email protected]>
AuthorDate: Sat Oct 17 05:41:17 2026 +0800
typo(docs): fix some docs problem (#2227)
## Summary
Rebase the historical documentation corrections on current master and
retain the fixes that are still needed in dev and 4.x.
- Fix the dynamic-partition conversion example: create `test_partition`
with RANGE partitioning before altering that same table.
- Use a table name in `SHOW INDEX FROM`, including the dev/4.x English
and Chinese NGram BloomFilter examples.
- Remove duplicate Chinese punctuation in Memory Tracker and
CREATE/ALTER USER descriptions. Their English counterparts already
express the correct meaning.
- Preserve master deletions and rewrites rather than restoring obsolete
connection, inverted-index, or aggregate-state pages.
The author's existing changes for older versions remain; this audit and
the counterpart additions focus on dev and 4.x.
## Validation
- Checked SHOW INDEX grammar and dynamic-partition validation in Doris
master and branch-4.0.
- Compared every original dev/current change with the current
documentation to remove obsolete hunks.
- `git diff --check` passes.
- Docusaurus Markdown/MDX compilation passes for the 14 changed dev/4.x
pages.
- Documentation governance checks introduce no errors or warnings in the
requested scope.
---------
Co-authored-by: morningman <[email protected]>
---
.../data-partitioning/dynamic-partitioning.md | 3 +-
docs/table-design/index/ngram-bloomfilter-index.md | 2 +-
.../memory-feature/memory-tracker.md | 2 +-
.../account-management/ALTER-USER.md | 2 +-
.../account-management/CREATE-USER.md | 2 +-
.../data-partitioning/dynamic-partitioning.md | 3 +-
.../table-design/index/ngram-bloomfilter-index.md | 2 +-
.../version-1.2/ecosystem/beats.md | 2 +-
.../version-2.0/ecosystem/beats.md | 2 +-
.../cluster-deployment/standard-deployment.md | 70 ++++++++++++----------
.../version-2.0/table-design/best-practice.md | 2 +-
.../table-design/index/inverted-index.md | 16 ++---
.../table-design/index/ngram-bloomfilter-index.md | 2 +-
.../version-2.0/table-design/index/prefix-index.md | 2 +-
.../version-2.0/table-design/schema-change.md | 2 +-
.../auth/authentication-and-authorization.md | 6 +-
.../memory-feature/memory-tracker.md | 2 +-
.../db-connect/arrow-flight-sql-connect.md | 4 +-
.../version-2.1/ecosystem/observability/beats.md | 2 +-
.../string-functions/regexp-extract-all.md | 2 +-
.../string-functions/regexp-extract.md | 2 +-
.../account-management/ALTER-USER.md | 2 +-
.../account-management/CREATE-USER.md | 2 +-
.../version-2.1/table-design/best-practice.md | 2 +-
.../data-partitioning/dynamic-partitioning.md | 3 +-
.../table-design/index/inverted-index.md | 16 ++---
.../table-design/index/ngram-bloomfilter-index.md | 2 +-
.../version-2.1/table-design/schema-change.md | 4 +-
.../table-design/tiered-storage/remote-storage.md | 2 +-
.../auth/authentication-and-authorization.md | 6 +-
.../db-connect/arrow-flight-sql-connect.md | 4 +-
.../version-3.x/ecosystem/observability/beats.md | 2 +-
.../account-management/ALTER-USER.md | 2 +-
.../account-management/CREATE-USER.md | 2 +-
.../version-3.x/table-design/best-practice.md | 2 +-
.../data-partitioning/dynamic-partitioning.md | 3 +-
.../table-design/index/ngram-bloomfilter-index.md | 2 +-
.../version-3.x/table-design/schema-change.md | 4 +-
.../table-design/tiered-storage/remote-storage.m | 2 +-
.../table-design/tiered-storage/remote-storage.md | 2 +-
.../memory-feature/memory-tracker.md | 2 +-
.../account-management/ALTER-USER.md | 2 +-
.../account-management/CREATE-USER.md | 2 +-
.../data-partitioning/dynamic-partitioning.md | 3 +-
.../table-design/index/ngram-bloomfilter-index.md | 2 +-
.../cluster-deployment/standard-deployment.md | 43 +++++++------
.../table-design/index/inverted-index.md | 4 +-
.../table-design/index/ngram-bloomfilter-index.md | 2 +-
.../version-2.0/table-design/schema-change.md | 2 +-
.../db-connect/arrow-flight-sql-connect.md | 4 +-
.../data-partitioning/dynamic-partitioning.md | 3 +-
.../table-design/index/inverted-index.md | 4 +-
.../table-design/index/ngram-bloomfilter-index.md | 2 +-
.../version-2.1/table-design/schema-change.md | 2 +-
.../table-design/tiered-storage/remote-storage.md | 2 +-
.../db-connect/arrow-flight-sql-connect.md | 4 +-
.../data-partitioning/dynamic-partitioning.md | 3 +-
.../table-design/index/inverted-index.md | 4 +-
.../table-design/index/ngram-bloomfilter-index.md | 2 +-
.../version-3.x/table-design/schema-change.md | 2 +-
.../table-design/tiered-storage/remote-storage.md | 2 +-
.../data-partitioning/dynamic-partitioning.md | 3 +-
.../table-design/index/ngram-bloomfilter-index.md | 2 +-
63 files changed, 163 insertions(+), 134 deletions(-)
diff --git a/docs/table-design/data-partitioning/dynamic-partitioning.md
b/docs/table-design/data-partitioning/dynamic-partitioning.md
index 5dba1f2b4cb..fcc451afa40 100644
--- a/docs/table-design/data-partitioning/dynamic-partitioning.md
+++ b/docs/table-design/data-partitioning/dynamic-partitioning.md
@@ -80,12 +80,13 @@ Modifying dynamic partitions with the `ALTER TABLE`
statement does not take effe
The following example uses an `ALTER TABLE` statement to convert a non-dynamic
partitioned table into a dynamic partitioned table:
```sql
-CREATE TABLE test_dynamic_partition(
+CREATE TABLE test_partition(
order_id BIGINT,
create_dt DATE,
username VARCHAR(20)
)
DUPLICATE KEY(order_id)
+PARTITION BY RANGE(create_dt) ()
DISTRIBUTED BY HASH(order_id) BUCKETS 10;
ALTER TABLE test_partition SET (
diff --git a/docs/table-design/index/ngram-bloomfilter-index.md
b/docs/table-design/index/ngram-bloomfilter-index.md
index 38aa923b90c..75a7d7d4658 100644
--- a/docs/table-design/index/ngram-bloomfilter-index.md
+++ b/docs/table-design/index/ngram-bloomfilter-index.md
@@ -97,7 +97,7 @@ It is recommended to prefix index names with `idx_`, for
example `idx_review_bod
SHOW CREATE TABLE table_name;
-- Method 2: An IndexType of NGRAM_BF marks an NGram BloomFilter index
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
```
### Drop an Index
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/memory-feature/memory-tracker.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/memory-feature/memory-tracker.md
index 5f5c103fbfc..cc5757409c1 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/memory-feature/memory-tracker.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/memory-feature/memory-tracker.md
@@ -80,7 +80,7 @@ Orphan Memory Tracker 是默认 Memory Tracker，值为正数或负数都意味
- 如果线程开始时 TLS 中没有绑定 Memory Tracker，那么 Doris Allocator 会默认将内存记录到 Orphan Memory
Tracker 中，意味着这部分内存不知所属，有关 Doris Allocator 记录内存的原理参考上文 [内存跟踪原理]。
-- Query 或 Load 等任务 Memory Tracker 析构时如果值不等于 0，，通常意味着这部分内存没有释放，将把这部分剩余的内存记录到
Orphan Memory Tracker 中，相当于将剩余内存交由 Orphan Memory Tracker 继续跟踪。从而保证 Orphan
Memory Tracker 和其他 Memory Tracker 之和等于 Doris Allocator 分配出去的所有内存。
+- Query 或 Load 等任务 Memory Tracker 析构时如果值不等于 0，通常意味着这部分内存没有释放，将把这部分剩余的内存记录到
Orphan Memory Tracker 中，相当于将剩余内存交由 Orphan Memory Tracker 继续跟踪。从而保证 Orphan
Memory Tracker 和其他 Memory Tracker 之和等于 Doris Allocator 分配出去的所有内存。
理想情况下，期望 Orphan Memory Tracker 的值接近 0。所以我们希望所有线程开始时都 Attach 一个 Orphan 之外的
Memory Tracker，比如 Query 或 Load Memory Tracker。并且所有 Query 或 Load Memory Tracker
析构时都等于 0，这意味着 Query 或 Load 执行过程中使用的内存在析构时都已经被释放。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/ALTER-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/ALTER-USER.md
index f677c410f25..0b4252cc30e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/ALTER-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/ALTER-USER.md
@@ -31,7 +31,7 @@ password_policy:
> 一个用户的唯一标识，语法为：'user_name'@'host'
> `user_identity` 由两部分组成，user_name 和 host，其中 username 为用户名。host
> 标识用户端连接所在的主机地址。host 部分可以使用 % 进行模糊匹配。如果不指定 host，默认为 '%'，即表示该用户可以从任意 host 连接到
> Doris。
-> host 部分也可指定为 domain，，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
+> host 部分也可指定为 domain，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
## 可选参数
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/CREATE-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/CREATE-USER.md
index cc676e31018..125296b02d3 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/CREATE-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/account-management/CREATE-USER.md
@@ -31,7 +31,7 @@ password_policy:
> 一个用户的唯一标识，语法为：'user_name'@'host'
> `user_identity` 由两部分组成，user_name 和 host，其中 username 为用户名。host
> 标识用户端连接所在的主机地址。host 部分可以使用 % 进行模糊匹配。如果不指定 host，默认为 '%'，即表示该用户可以从任意 host 连接到
> Doris。
-> host 部分也可指定为 domain，，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
+> host 部分也可指定为 domain，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
## 可选参数
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/dynamic-partitioning.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/dynamic-partitioning.md
index 1271269b870..bab63e5771f 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/dynamic-partitioning.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/dynamic-partitioning.md
@@ -80,12 +80,13 @@ PROPERTIES(
下例通过 ALTER TABLE 语句将非动态分区表修改为动态分区表：
```sql
-CREATE TABLE test_dynamic_partition(
+CREATE TABLE test_partition(
order_id BIGINT,
create_dt DATE,
username VARCHAR(20)
)
DUPLICATE KEY(order_id)
+PARTITION BY RANGE(create_dt) ()
DISTRIBUTED BY HASH(order_id) BUCKETS 10;
ALTER TABLE test_partition SET (
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/index/ngram-bloomfilter-index.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/index/ngram-bloomfilter-index.md
index c018ce91a11..06dd06e96ae 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/index/ngram-bloomfilter-index.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/index/ngram-bloomfilter-index.md
@@ -97,7 +97,7 @@ COMMENT 'username ngram_bf index'
SHOW CREATE TABLE table_name;
-- 方式 2：IndexType 为 NGRAM_BF 标识为 NGram BloomFilter 索引
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
```
### 删除索引
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.2/ecosystem/beats.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.2/ecosystem/beats.md
index f2cb3e70207..19c9671d730 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.2/ecosystem/beats.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.2/ecosystem/beats.md
@@ -170,7 +170,7 @@ queue.mem:
flush.timeout: 10s
# 4. output 部分负责数据输出
-# doris output 将数据输出到 Doris，使用的是 Stream Load HTTP 接口。通过 headers 参数指定了 Stream
Load 的数据格式为 JSON，通过 codec_format_string 参数用类似 printf 的方式格式化输出到 Doris
的数据。比如下面的例子基于 filebeat 内部的字段 format 出一个 JSON，这些字段可以是 filebeat 内置字段如
agent.hostname，也可以是 processor 比如 dissect 生产的字段如 day，通过 %{[a][b]} 的方式引用，，Stream
Load 会自动将 JSON 字段写入对应的 Doris 表的字段。
+# doris output 将数据输出到 Doris，使用的是 Stream Load HTTP 接口。通过 headers 参数指定了 Stream
Load 的数据格式为 JSON，通过 codec_format_string 参数用类似 printf 的方式格式化输出到 Doris
的数据。比如下面的例子基于 filebeat 内部的字段 format 出一个 JSON，这些字段可以是 filebeat 内置字段如
agent.hostname，也可以是 processor 比如 dissect 生产的字段如 day，通过 %{[a][b]} 的方式引用，Stream
Load 会自动将 JSON 字段写入对应的 Doris 表的字段。
output.doris:
fenodes: [ "http://fehost1:http_port";, "http://fehost2:http_port";,
"http://fehost3:http_port"; ]
user: "your_username"
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/ecosystem/beats.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/ecosystem/beats.md
index fdb33f084b7..95c0d80d9b8 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/ecosystem/beats.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/ecosystem/beats.md
@@ -170,7 +170,7 @@ queue.mem:
flush.timeout: 10s
# 4. output 部分负责数据输出
-# doris output 将数据输出到 Doris，使用的是 Stream Load HTTP 接口。通过 headers 参数指定了 Stream
Load 的数据格式为 JSON，通过 codec_format_string 参数用类似 printf 的方式格式化输出到 Doris
的数据。比如下面的例子基于 filebeat 内部的字段 format 出一个 JSON，这些字段可以是 filebeat 内置字段如
agent.hostname，也可以是 processor 比如 dissect 生产的字段如 day，通过 %{[a][b]} 的方式引用，，Stream
Load 会自动将 JSON 字段写入对应的 Doris 表的字段。
+# doris output 将数据输出到 Doris，使用的是 Stream Load HTTP 接口。通过 headers 参数指定了 Stream
Load 的数据格式为 JSON，通过 codec_format_string 参数用类似 printf 的方式格式化输出到 Doris
的数据。比如下面的例子基于 filebeat 内部的字段 format 出一个 JSON，这些字段可以是 filebeat 内置字段如
agent.hostname，也可以是 processor 比如 dissect 生产的字段如 day，通过 %{[a][b]} 的方式引用，Stream
Load 会自动将 JSON 字段写入对应的 Doris 表的字段。
output.doris:
fenodes: [ "http://fehost1:http_port";, "http://fehost2:http_port";,
"http://fehost3:http_port"; ]
user: "your_username"
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/install/cluster-deployment/standard-deployment.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/install/cluster-deployment/standard-deployment.md
index c99415b098e..bd21c4ac073 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/install/cluster-deployment/standard-deployment.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/install/cluster-deployment/standard-deployment.md
@@ -7,15 +7,15 @@
手动部署 Doris 集群，通常要进行四步规划：
-1. 软硬件环境检查：检查用户的硬件资源情况及操作系统兼容性
+1. 软硬件环境检查：检查用户的硬件资源情况及操作系统兼容性
-2. 操作系统检查：检查操作系统参数及配置
+2. 操作系统检查：检查操作系统参数及配置
-3. 集群规划：规划集群的 FE、BE 节点，预估使用资源情况
+3. 集群规划：规划集群的 FE、BE 节点，预估使用资源情况
-4. 集群部署：根据部署规划进行集群部署操作
+4. 集群部署：根据部署规划进行集群部署操作
-5. 部署验证：登录并验证集群正确性
+5. 部署验证：登录并验证集群正确性
## 1 软硬件环境检查
@@ -43,9 +43,9 @@ Doris 部署时数据可以存放在 SSD 或 HDD 硬盘或者对象存储中。
在以下几种场景中建议使用 SSD 作为数据存储：
-- 大规模数据量下的高并发点查场景
+- 大规模数据量下的高并发点查场景
-- 大规模数据量下的高频数据更新场景
+- 大规模数据量下的高频数据更新场景
**文件系统**
@@ -69,15 +69,16 @@ Doris 支持运行和部署在 x86-64 架构的服务器平台或 ARM64 架构
:::tip
说明
-- 在验证测试环境中，可以将 FE 与 BE 部署在同一台服务器上
+- 在验证测试环境中，可以将 FE 与 BE 部署在同一台服务器上
-- 一台机器上一般**只建议部署一个 BE 实例**，同时**只能部署一个 FE**
+- 一台机器上一般**只建议部署一个 BE 实例**，同时**只能部署一个 FE**
-- 如果需要 3 副本数据，那么至少需要 3 台机器各部署一个 BE 实例，而不是 1 台机器部署 3 个 BE 实例
+- 如果需要 3 副本数据，那么至少需要 3 台机器各部署一个 BE 实例，而不是 1 台机器部署 3 个 BE 实例
-- **多个 FE 所在服务器的时钟必须保持一致，最多允许 5 秒的时钟偏差**
+- **多个 FE 所在服务器的时钟必须保持一致，最多允许 5 秒的时钟偏差**
+
+- 测试环境也可以仅使用一个 BE 进行测试。实际生产环境，BE 实例数量直接决定了整体查询延迟。
-- 测试环境也可以仅使用一个 BE 进行测试。实际生产环境，BE 实例数量直接决定了整体查询延迟。
:::
**生产环境**
@@ -90,11 +91,12 @@ Doris 支持运行和部署在 x86-64 架构的服务器平台或 ARM64 架构
:::tip
说明
-- 在生产环境中，如果 FE 与 BE 混布，需要注意资源争用问题，建议元数据存储与数据存储分盘存放
+- 在生产环境中，如果 FE 与 BE 混布，需要注意资源争用问题，建议元数据存储与数据存储分盘存放
+
+- BE 节点可以配置多块硬盘存储，在一个 BE 实例上绑定多块 HDD 或 SSD 盘
-- BE 节点可以配置多块硬盘存储，在一个 BE 实例上绑定多块 HDD 或 SSD 盘
+- 集群的性能与 BE 节点的资源有关，BE 节点越多，Doris 性能越好。通常情况下在 10 - 100 台机器上可以充分发挥 Doris 的性能
-- 集群的性能与 BE 节点的资源有关，BE 节点越多，Doris 性能越好。通常情况下在 10 - 100 台机器上可以充分发挥 Doris 的性能
:::
### 硬盘空间计算
@@ -221,9 +223,9 @@ FE 节点主要负责用户请求的接入、查询解析规划、元数据的
对于生产集群，一般至少需要部署 3 节点 FE 的高可用环境。FE 节点分为两种角色：
-- Follower 节点参与选举操作，当 Master 节点宕机后，会选择一个可用的 Follower 节点成为新的 Master；
+- Follower 节点参与选举操作，当 Master 节点宕机后，会选择一个可用的 Follower 节点成为新的 Master；
-- Observer 节点仅从 Leader 节点同步元数据，不参与选举。可以横向扩展以提供元数据的读服务的扩展性。
+- Observer 节点仅从 Leader 节点同步元数据，不参与选举。可以横向扩展以提供元数据的读服务的扩展性。
通常情况下，建议部署 3 个 Follower 节点。在高并发的场景中，可以通过扩展 Observer 节点提高集群的连接数。
@@ -248,7 +250,8 @@ FE 元数据通常不超过 10GB，建议与 BE 节点数据存储在不同的
mkdir -p <doris_meta_created>
## 创建 FE 的元数据目录软连接
-ln -s <doris_meta_original> <doris_meta_created>
+rm -rf <doris_meta_original>
+ln -s <doris_meta_created> <doris_meta_original>
```
**修改 FE 配置文件**
@@ -303,11 +306,11 @@ mysql -uroot -P<fe_query_port> -h<fe_ip_address>
链接到 Doris 集群后，可以通过 `show frontends` 命令查看 FE 的状态，通常要确认以下几项
-- Alive 为 true 表示节点存活
+- Alive 为 true 表示节点存活
-- Join 为 true 表示节点加入到集群中，但不代表当前还在集群内（可能已失联）
+- Join 为 true 表示节点加入到集群中，但不代表当前还在集群内（可能已失联）
-- IsMaster 为 true 表示当前节点为 Master 节点
+- IsMaster 为 true 表示当前节点为 Master 节点
### 部署 FE 集群（可选）
@@ -345,11 +348,12 @@ ALTER SYSTEM ADD OBSERVER
"<fe_ip_address>:<fe_edit_log_port>"
:::caution
注意
-1. FE Follower（包括 Master）节点的数量建议为奇数，建议部署 3 个组成高可用模式。
+1. FE Follower（包括 Master）节点的数量建议为奇数，建议部署 3 个组成高可用模式。
+
+2. 当 FE 处于高可用部署时（1 个 Master，2 个 Follower），我们建议通过增加 Observer FE 来扩展 FE 的读服务能力
-2. 当 FE 处于高可用部署时（1 个 Master，2 个 Follower），我们建议通过增加 Observer FE 来扩展 FE 的读服务能力
+3. 通常一个 FE 节点可以应对 10-20 台 BE 节点。建议总的 FE 节点数量在 10 个以下
-3. 通常一个 FE 节点可以应对 10-20 台 BE 节点。建议总的 FE 节点数量在 10 个以下
:::
**启动 FE Follower 节点**
@@ -366,7 +370,7 @@ bin/start_fe.sh --helper <helper_fe_ip>:<fe_edit_log_port>
--daemon
与判断 FE master 节点状态的方式相同，添加注册 FE follower 节点后需要通过 `show frontends` 命令查看 FE
节点状态。与 Master 状态不同，`IsMaster` 的状态应为 false。
-### 部署 BE
+### 部署 BE
**创建数据目录**
@@ -381,7 +385,7 @@ mkdir -p <be_storage_root_path>
BE 的配置文件在 BE 部署路径下的 conf 目录中，启动 FE 节点前需要修改 `conf/be.conf`。
-1. 配置 Java 环境
+1. 配置 Java 环境
从 1.2 版本开始 Doris 支持 Java UDF 函数，BE 依赖于 Java 环境。需要预先配置操作系统 `JAVA_HOME` 环境变量，或者在
BE 配置文件中指定 Java 环境变量。
@@ -412,15 +416,15 @@
storage_root_path=/home/disk1/doris,medium:HDD;/home/disk2/doris,medium:SSD
:::caution
**注意：**
-1. 当指定存储路径的存储类型时，至少设置一个路径的存储类型为 HDD；
+1. 当指定存储路径的存储类型时，至少设置一个路径的存储类型为 HDD；
-2. 如未显示声明存储路径的存储类型，则默认全部为 HDD；
+2. 如未显示声明存储路径的存储类型，则默认全部为 HDD；
-3. 指定 HDD 或 SSD 存储类型与物理存储介质无关，只为区分存储路径的存储类型，即可以在 HDD 介质的盘上标记某个目录为 SSD；
+3. 指定 HDD 或 SSD 存储类型与物理存储介质无关，只为区分存储路径的存储类型，即可以在 HDD 介质的盘上标记某个目录为 SSD；
-4. 存储类型 HDD 和 SSD 关键字须大写。
-:::
+4. 存储类型 HDD 和 SSD 关键字须大写。
+:::
3. 绑定集群 IP
@@ -468,9 +472,9 @@ show backends;
通常情况下需要注意以下几项状态：
-- Alive 为 true 表示节点存活
+- Alive 为 true 表示节点存活
-- TabletNum 表示该节点上的分片数量，新加入的节点会进行数据均衡，TabletNum 逐渐趋于平均
+- TabletNum 表示该节点上的分片数量，新加入的节点会进行数据均衡，TabletNum 逐渐趋于平均
### 验证集群正确性
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/best-practice.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/best-practice.md
index ad274eaaf33..e59330143af 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/best-practice.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/best-practice.md
@@ -302,7 +302,7 @@ DISTRIBUTED BY HASH(`siteid`) BUCKETS 10;
4. 亿级别以上数据，如果有模糊匹配，使用倒排索引或者是 NGram Bloomfilter
:::
-### 2.6 Bitmap 索引
+### 6 Bitmap 索引
为了加速数据查询，Doris 支持用户为某些字段添加 Bitmap 索引，适合在基数较低的列上进行等值查询或范围查询的场景。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/index/inverted-index.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/index/inverted-index.md
index 85e3adee10e..4b267a99bb5 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/index/inverted-index.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/index/inverted-index.md
@@ -108,7 +108,7 @@ table_properties;
**用于指定分词的模式，目前 parser = chinese 时支持如下几种模式：**
<p>- fine_grained：细粒度模式，倾向于分出比较短、较多的词，比如 '武汉市长江大桥' 会分成 '武汉', '武汉市', '市长',
'长江', '长江大桥', '大桥' 6 个词</p>
- <p>- coarse_grained：粗粒度模式，倾向于分出比较长、较少的词，，比如 '武汉市长江大桥' 会分成 '武汉市' '长江大桥' 2
个词</p>
+ <p>- coarse_grained：粗粒度模式，倾向于分出比较长、较少的词，比如 '武汉市长江大桥' 会分成 '武汉市' '长江大桥' 2
个词</p>
<p>- 默认 coarse_grained</p>
</details>
@@ -131,7 +131,7 @@ table_properties;
**用于指定在分词前对文本进行预处理，通常用于影响分词行为**
- <p>char_filter_type：指定使用不同功能的 char_filter（目前仅支持 char_replace）</p>
+ <p>- char_filter_type：指定使用不同功能的 char_filter（目前仅支持 char_replace）</p>
<p>char_replace 将 pattern 中每个 char 替换为一个 replacement 中的 char</p>
<p>- char_filter_pattern：需要被替换掉的字符数</p>
@@ -157,7 +157,7 @@ table_properties;
<summary>lower_case</summary>
**是否将分词进行小写转换，从而在匹配的时候实现忽略大小写**
- <p>- true: 转换小写</p>
+ <p>- true：转换小写</p>
<p>- false：不转换小写</p>
<p>- 从 2.0.7 版本开始默认为 true，自动转小写，之前的版本默认为 false</p>
</details>
@@ -167,7 +167,7 @@ table_properties;
**指明使用的停用词表，会影响分词器的行为**
<p>默认的内置停用词表包含一些无意义的词：'is'、'the'、'a' 等。在写入或者查询时，分词器会忽略停用词表中的词。</p>
- <p>- none: 使用空的停用词表</p>
+ <p>- none：使用空的停用词表</p>
</details>
**4. `COMMENT` 是可选的，用于指定索引注释**
@@ -210,7 +210,7 @@ SHOW BUILD INDEX where TableName = "table1";
通过 `CANCEL BUILD INDEX` 取消 `BUILD INDEX`：
```sql
CANCEL BUILD INDEX ON table_name;
-CANCEL BUILD INDEX ON table_name (job_id1,jobid_2,...);
+CANCEL BUILD INDEX ON table_name (job_id1,job_id2,...);
```
:::tip
@@ -248,7 +248,7 @@ ALTER TABLE table_name DROP INDEX idx_name;
SHOW CREATE TABLE table_name;
-- 语法 2，IndexType 为 INVERTED 的是倒排索引
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
```
@@ -274,7 +274,7 @@ SELECT * FROM table_name WHERE content MATCH_ALL 'keyword1
keyword2';
-- 2.1 content 列中同时包含 keyword1 和 keyword2 的行，而且 keyword2 必须紧跟在 keyword1 后面
-- 'keyword1 keyword2'，'wordx keyword1 keyword2'，'wordx keyword1 keyword2
wordy' 能匹配，因为他们都包含 keyword1 keyword2，而且 keyword2 紧跟在 keyword1 后面
-- 'keyword1 wordx keyword2' 不能匹配，因为 keyword1 keyword2 之间隔了一个词 wordx
--- 'keyword2 keyword1'，因为 keyword1 keyword2 的顺序反了
+-- 'keyword2 keyword1' 不能匹配，因为 keyword1 keyword2 的顺序反了
SELECT * FROM table_name WHERE content MATCH_PHRASE 'keyword1 keyword2';
-- 2.2 content 列中同时包含 keyword1 和 keyword2 的行，而且 keyword1 keyword2 的
`词距`（slop）不超过 3
@@ -414,7 +414,7 @@ PROPERTIES ("replication_num" = "1");
```
wget
https://qa-build.oss-cn-beijing.aliyuncs.com/regression/index/hacknernews_1m.csv.gz
-curl --location-trusted -u root: -H "compress_type:gz" -T
hacknernews_1m.csv.gz
http://127.0.0.1:8030/api/test_inverted_index/hackernews_1m/_stream_load
+curl --location-trusted -u root: -H "compress_type:gz" -T
hacknernews_1m.csv.gz -XPUT
http://127.0.0.1:8030/api/test_inverted_index/hackernews_1m/_stream_load
{
"TxnId": 2,
"Label": "a8a3e802-2329-49e8-912b-04c800a461a6",
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/index/ngram-bloomfilter-index.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/index/ngram-bloomfilter-index.md
index b69519bcf11..1633351f50f 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/index/ngram-bloomfilter-index.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/index/ngram-bloomfilter-index.md
@@ -60,7 +60,7 @@ NGram BloomFilter 索引只能加速字符串 LIKE 查询，而且 LIKE pattern
SHOW CREATE TABLE table_name;
-- 语法 2，IndexType 为 NGRAM_BF 的是倒排索引
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
```
### 删除 NGram BloomFilter 索引
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/index/prefix-index.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/index/prefix-index.md
index 62821ad19f9..a3dbe9e8e18 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/index/prefix-index.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/index/prefix-index.md
@@ -33,7 +33,7 @@ Doris 的数据存储在类似 SSTable（Sorted String Table）的数据结构
因为一个表的 Key 定义是唯一的，所以一个表只有一组前缀索引，因此设计表结构时选择合适的前缀索引很重要，可以参考下面的建议：
1. 选择查询中最常用于 WHERE 过滤条件的字段作为 Key。
-2. 约常用的字段越放在前面，因为前缀索引只对 WHERE 条件中字段在 Key 的前缀中才有效。
+2. 越常用的字段越放在前面，因为前缀索引只对 WHERE 条件中字段在 Key 的前缀中才有效。
使用其他不能命中前缀索引的列作为条件进行的查询来说，效率上可能无法满足需求，有两种解决方案：
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/schema-change.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/schema-change.md
index 43a8b12e0ad..5ca2dd248bf 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/schema-change.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/table-design/schema-change.md
@@ -267,7 +267,7 @@ MODIFY COLUMN col1 BIGINT KEY DEFAULT "1" AFTER col2;
注意：无论是修改 Key 列还是 Value 列都需要声明完整的 Column 信息
-**2. 修改 Base Index 的 val1 列最大长度。原 val1 为 (val1 VARCHAR(32) REPLACE DEFAULT
"abc")**
+**2. 修改 Base Index 的 val5 列最大长度。原 val5 为 (val5 VARCHAR(32) REPLACE DEFAULT
"abc")**
```sql
ALTER TABLE example_db.my_table
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/auth/authentication-and-authorization.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/auth/authentication-and-authorization.md
index f782fa6d7c0..d1ac58a28b2 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/auth/authentication-and-authorization.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/auth/authentication-and-authorization.md
@@ -111,9 +111,9 @@ Doris 支持以下密码策略，可以帮助用户更好的进行密码管理
- 设置用户属性：[SET
PROPERTY](../../sql-manual/sql-statements/account-management/SET-PROPERTY)
- 查看用户属性：[SHOW
PROPERTY](../../sql-manual/sql-statements/account-management/SHOW-PROPERTY)
- 修改密码：[SET
PASSWORD](../../sql-manual/sql-statements/account-management/SET-PASSWORD)
-- 查看支持的所有权限项：[SHOW PRIVILEGES]
-- 查看行权限策略 [SHOW ROW POLICY]
-- 创建行权限策略 [CREATE ROW POLICY]
+- 查看支持的所有权限项：[SHOW
PRIVILEGES](../../../../sql-manual/sql-statements/account-management/SHOW-PRIVILEGES)
+- 查看行权限策略：[SHOW ROW
POLICY](../../../../sql-manual/sql-statements/data-governance/SHOW-ROW-POLICY)
+- 创建行权限策略：[CREATE ROW
POLICY](../../../../sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY)
### 权限类型
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/trouble-shooting/memory-management/memory-feature/memory-tracker.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/trouble-shooting/memory-management/memory-feature/memory-tracker.md
index 5f5c103fbfc..cc5757409c1 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/trouble-shooting/memory-management/memory-feature/memory-tracker.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/trouble-shooting/memory-management/memory-feature/memory-tracker.md
@@ -80,7 +80,7 @@ Orphan Memory Tracker 是默认 Memory Tracker，值为正数或负数都意味
- 如果线程开始时 TLS 中没有绑定 Memory Tracker，那么 Doris Allocator 会默认将内存记录到 Orphan Memory
Tracker 中，意味着这部分内存不知所属，有关 Doris Allocator 记录内存的原理参考上文 [内存跟踪原理]。
-- Query 或 Load 等任务 Memory Tracker 析构时如果值不等于 0，，通常意味着这部分内存没有释放，将把这部分剩余的内存记录到
Orphan Memory Tracker 中，相当于将剩余内存交由 Orphan Memory Tracker 继续跟踪。从而保证 Orphan
Memory Tracker 和其他 Memory Tracker 之和等于 Doris Allocator 分配出去的所有内存。
+- Query 或 Load 等任务 Memory Tracker 析构时如果值不等于 0，通常意味着这部分内存没有释放，将把这部分剩余的内存记录到
Orphan Memory Tracker 中，相当于将剩余内存交由 Orphan Memory Tracker 继续跟踪。从而保证 Orphan
Memory Tracker 和其他 Memory Tracker 之和等于 Doris Allocator 分配出去的所有内存。
理想情况下，期望 Orphan Memory Tracker 的值接近 0。所以我们希望所有线程开始时都 Attach 一个 Orphan 之外的
Memory Tracker，比如 Query 或 Load Memory Tracker。并且所有 Query 或 Load Memory Tracker
析构时都等于 0，这意味着 Query 或 Load 执行过程中使用的内存在析构时都已经被释放。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/db-connect/arrow-flight-sql-connect.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/db-connect/arrow-flight-sql-connect.md
index db9936361f3..d5eb7f71040 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/db-connect/arrow-flight-sql-connect.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/db-connect/arrow-flight-sql-connect.md
@@ -16,7 +16,6 @@
安装 Apache Arrow 你可以去官方文档 [Apache Arrow](https://arrow.apache.org/install/)
找到详细的安装教程。更多关于 Doris 实现 Arrow Flight 协议的原理可以参考 [Doris support Arrow Flight SQL
protocol](https://github.com/apache/doris/issues/25514)。
-
## Python 使用方法
使用 Python 的 ADBC Driver 连接 Doris 实现数据的极速读取，下面的步骤使用 Python（版本 >= 3.9）的 ADBC
Driver 执行一系列常见的数据库语法操作，包括 DDL、DML、设置 Session 变量以及 Show 语句等。
@@ -34,6 +33,7 @@ pip install adbc_driver_flightsql
```Python
import adbc_driver_manager
+import adbc_driver_flightsql
import adbc_driver_flightsql.dbapi as flight_sql
>>> print(adbc_driver_manager.__version__)
@@ -265,6 +265,7 @@ cursor.close()
Arrow Flight SQL 协议的开源 JDBC 驱动兼容标准的 JDBC API，可用于大多数 BI 工具通过 JDBC 访问
Doris，并支持高速传输 Apache Arrow 数据。使用方法与通过 MySQL 协议的 JDBC 驱动连接 Doris 类似，只需将链接 URL 中的
jdbc:mysql 协议换成 jdbc:arrow-flight-sql 协议，查询返回的结果依然是 JDBC 的 ResultSet 数据结构。
POM dependency:
+
```Java
<properties>
<arrow.version>17.0.0</arrow.version>
@@ -322,6 +323,7 @@ conn.close();
除了使用 JDBC，与 Python 类似，Java 也可以创建 Driver 读取 Doris 并返回 Arrow 格式的数据，下面分别是使用
AdbcDriver 和 JdbcDriver 连接 Doris Arrow Flight Server。
POM dependency:
+
```Java
<properties>
<adbc.version>0.15.0</adbc.version>
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/ecosystem/observability/beats.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/ecosystem/observability/beats.md
index aa46440b132..1fd73885c37 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/ecosystem/observability/beats.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/ecosystem/observability/beats.md
@@ -171,7 +171,7 @@ queue.mem:
flush.timeout: 10s
# 4. output 部分负责数据输出
-# doris output 将数据输出到 Doris，使用的是 Stream Load HTTP 接口。通过 headers 参数指定了 Stream
Load 的数据格式为 JSON，通过 codec_format_string 参数用类似 printf 的方式格式化输出到 Doris
的数据。比如下面的例子基于 filebeat 内部的字段 format 出一个 JSON，这些字段可以是 filebeat 内置字段如
agent.hostname，也可以是 processor 比如 dissect 生产的字段如 day，通过 %{[a][b]} 的方式引用，，Stream
Load 会自动将 JSON 字段写入对应的 Doris 表的字段。
+# doris output 将数据输出到 Doris，使用的是 Stream Load HTTP 接口。通过 headers 参数指定了 Stream
Load 的数据格式为 JSON，通过 codec_format_string 参数用类似 printf 的方式格式化输出到 Doris
的数据。比如下面的例子基于 filebeat 内部的字段 format 出一个 JSON，这些字段可以是 filebeat 内置字段如
agent.hostname，也可以是 processor 比如 dissect 生产的字段如 day，通过 %{[a][b]} 的方式引用，Stream
Load 会自动将 JSON 字段写入对应的 Doris 表的字段。
output.doris:
fenodes: [ "http://fehost1:http_port";, "http://fehost2:http_port";,
"http://fehost3:http_port"; ]
user: "your_username"
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/string-functions/regexp-extract-all.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/string-functions/regexp-extract-all.md
index 13e6ae559ac..08089c7b319 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/string-functions/regexp-extract-all.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/string-functions/regexp-extract-all.md
@@ -183,4 +183,4 @@ SELECT regexp_extract_all('hello (world) 123',
'([[:alpha:]+');
```text
ERROR 1105 (HY000): errCode = 2, detailMessage =
(10.16.10.2)[INVALID_ARGUMENT]Could not compile regexp pattern: ([[:alpha:]+
Error: missing ]: [[:alpha:]+
-```
\ No newline at end of file
+```
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/string-functions/regexp-extract.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/string-functions/regexp-extract.md
index 48bca4470ed..22f1cf65a49 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/string-functions/regexp-extract.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/string-functions/regexp-extract.md
@@ -183,4 +183,4 @@ SELECT regexp_extract('AbCdE', '([[:digit:]]+', 1);
```text
ERROR 1105 (HY000): errCode = 2, detailMessage =
(10.16.10.2)[INVALID_ARGUMENT]Could not compile regexp pattern: ([[:digit:]]+
Error: missing ): ([[:digit:]]+
-```
\ No newline at end of file
+```
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/ALTER-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/ALTER-USER.md
index f949568fbfd..ea8028778dd 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/ALTER-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/ALTER-USER.md
@@ -31,7 +31,7 @@ password_policy:
> 一个用户的唯一标识，语法为：'user_name'@'host'
> `user_identity` 由两部分组成，user_name 和 host，其中 username 为用户名。host
> 标识用户端连接所在的主机地址。host 部分可以使用 % 进行模糊匹配。如果不指定 host，默认为 '%'，即表示该用户可以从任意 host 连接到
> Doris。
-> host 部分也可指定为 domain，，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
+> host 部分也可指定为 domain，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
## 可选参数
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/CREATE-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/CREATE-USER.md
index 2827a59d1a2..b87b6732ce7 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/CREATE-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/account-management/CREATE-USER.md
@@ -31,7 +31,7 @@ password_policy:
> 一个用户的唯一标识，语法为：'user_name'@'host'
> `user_identity` 由两部分组成，user_name 和 host，其中 username 为用户名。host
> 标识用户端连接所在的主机地址。host 部分可以使用 % 进行模糊匹配。如果不指定 host，默认为 '%'，即表示该用户可以从任意 host 连接到
> Doris。
-> host 部分也可指定为 domain，，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
+> host 部分也可指定为 domain，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
## 可选参数
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/best-practice.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/best-practice.md
index a530944039c..f42cf4a27fc 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/best-practice.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/best-practice.md
@@ -303,7 +303,7 @@ DISTRIBUTED BY HASH(`siteid`) BUCKETS 10;
4. 亿级别以上数据，如果有模糊匹配，使用倒排索引或者是 NGram Bloomfilter
:::
-### 2.6 Bitmap 索引
+### 06 Bitmap 索引
为了加速数据查询，Doris 支持用户为某些字段添加 Bitmap 索引，适合在基数较低的列上进行等值查询或范围查询的场景。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/data-partitioning/dynamic-partitioning.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/data-partitioning/dynamic-partitioning.md
index dab22939a2c..b8887a6216c 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/data-partitioning/dynamic-partitioning.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/data-partitioning/dynamic-partitioning.md
@@ -70,12 +70,13 @@ PROPERTIES(
下例中通过 ALTER TABLE 语句，将非动态分区表修改为动态分区：
```sql
-CREATE TABLE test_dynamic_partition(
+CREATE TABLE test_partition(
order_id BIGINT,
create_dt DATE,
username VARCHAR(20)
)
DUPLICATE KEY(order_id)
+PARTITION BY RANGE(create_dt) ()
DISTRIBUTED BY HASH(order_id) BUCKETS 10;
ALTER TABLE test_partition SET (
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/index/inverted-index.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/index/inverted-index.md
index 080f1c1f7de..a94ff5037ae 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/index/inverted-index.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/index/inverted-index.md
@@ -109,7 +109,7 @@ table_properties;
**用于指定分词的模式，目前 parser = chinese 时支持如下几种模式：**
<p>- fine_grained：细粒度模式，倾向于分出比较短、较多的词，比如 '武汉市长江大桥' 会分成 '武汉', '武汉市', '市长',
'长江', '长江大桥', '大桥' 6 个词</p>
- <p>- coarse_grained：粗粒度模式，倾向于分出比较长、较少的词，，比如 '武汉市长江大桥' 会分成 '武汉市' '长江大桥' 2
个词</p>
+ <p>- coarse_grained：粗粒度模式，倾向于分出比较长、较少的词，比如 '武汉市长江大桥' 会分成 '武汉市' '长江大桥' 2
个词</p>
<p>- 默认 coarse_grained</p>
</details>
@@ -132,7 +132,7 @@ table_properties;
**用于指定在分词前对文本进行预处理，通常用于影响分词行为**
- <p>char_filter_type：指定使用不同功能的 char_filter（目前仅支持 char_replace）</p>
+ <p>- char_filter_type：指定使用不同功能的 char_filter（目前仅支持 char_replace）</p>
<p>char_replace 将 pattern 中每个 char 替换为一个 replacement 中的 char</p>
<p>- char_filter_pattern：需要被替换掉的字符数</p>
@@ -158,7 +158,7 @@ table_properties;
<summary>lower_case</summary>
**是否将分词进行小写转换，从而在匹配的时候实现忽略大小写**
- <p>- true: 转换小写</p>
+ <p>- true：转换小写</p>
<p>- false：不转换小写</p>
<p>- 从 2.0.7 和 2.1.2 版本开始默认为 true，自动转小写，之前的版本默认为 false</p>
</details>
@@ -168,7 +168,7 @@ table_properties;
**指明使用的停用词表，会影响分词器的行为**
<p>默认的内置停用词表包含一些无意义的词：'is'、'the'、'a' 等。在写入或者查询时，分词器会忽略停用词表中的词。</p>
- <p>- none: 使用空的停用词表</p>
+ <p>- none：使用空的停用词表</p>
</details>
**4. `COMMENT` 是可选的，用于指定索引注释**
@@ -249,7 +249,7 @@ ALTER TABLE table_name DROP INDEX idx_name;
SHOW CREATE TABLE table_name;
-- 语法 2，IndexType 为 INVERTED 的是倒排索引
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
```
@@ -275,8 +275,8 @@ SELECT * FROM table_name WHERE content MATCH_ALL 'keyword1
keyword2';
-- 2.1 content 列中同时包含 keyword1 和 keyword2 的行，而且 keyword2 必须紧跟在 keyword1 后面
-- 'keyword1 keyword2'，'wordx keyword1 keyword2'，'wordx keyword1 keyword2
wordy' 能匹配，因为他们都包含 keyword1 keyword2，而且 keyword2 紧跟在 keyword1 后面
-- 'keyword1 wordx keyword2' 不能匹配，因为 keyword1 keyword2 之间隔了一个词 wordx
--- 'keyword2 keyword1'，因为 keyword1 keyword2 的顺序反了
--- 使用 MATCH_PHRASE 需要再 PROPERTIES 中开启 "support_phrase" = "true"
+-- 'keyword2 keyword1' 不能匹配，因为 keyword1 keyword2 的顺序反了
+-- 使用 MATCH_PHRASE 需要在 PROPERTIES 中开启 "support_phrase" = "true"
SELECT * FROM table_name WHERE content MATCH_PHRASE 'keyword1 keyword2';
-- 2.2 content 列中同时包含 keyword1 和 keyword2 的行，而且 keyword1 keyword2 的
`词距`（slop）不超过 3
@@ -435,7 +435,7 @@ PROPERTIES ("replication_num" = "1");
```
wget
https://qa-build.oss-cn-beijing.aliyuncs.com/regression/index/hacknernews_1m.csv.gz
-curl --location-trusted -u root: -H "compress_type:gz" -T
hacknernews_1m.csv.gz
http://127.0.0.1:8030/api/test_inverted_index/hackernews_1m/_stream_load
+curl --location-trusted -u root: -H "compress_type:gz" -T
hacknernews_1m.csv.gz -XPUT
http://127.0.0.1:8030/api/test_inverted_index/hackernews_1m/_stream_load
{
"TxnId": 2,
"Label": "a8a3e802-2329-49e8-912b-04c800a461a6",
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/index/ngram-bloomfilter-index.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/index/ngram-bloomfilter-index.md
index b87f8d4e7e0..0fb2aa666c2 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/index/ngram-bloomfilter-index.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/index/ngram-bloomfilter-index.md
@@ -61,7 +61,7 @@ NGram BloomFilter 索引只能加速字符串 LIKE 查询，而且 LIKE pattern
SHOW CREATE TABLE table_name;
-- 语法 2，IndexType 为 NGRAM_BF 的是倒排索引
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
```
### 删除 NGram BloomFilter 索引
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/schema-change.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/schema-change.md
index 1845457be76..70a21ba60a1 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/schema-change.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/schema-change.md
@@ -187,7 +187,7 @@ CREATE TABLE IF NOT EXISTS example_db.my_table(
DISTRIBUTED BY HASH(col1) BUCKETS 10;
```
-2. 从 `example_db.my_table` 删除`col3`列
+2. 从 `example_db.my_table` 删除`col4`列
```sql
ALTER TABLE example_db.my_table DROP COLUMN col4;
@@ -249,7 +249,7 @@ MODIFY COLUMN col1 BIGINT KEY DEFAULT "1" AFTER col2;
注意：无论是修改 Key 列还是 Value 列都需要声明完整的 Column 信息
-2. 修改 Base Table 的 val1 列最大长度。原 val1 为 (val1 VARCHAR(32) REPLACE DEFAULT "abc")
+2. 修改 Base Table 的 val5 列最大长度。原 val5 为 (val5 VARCHAR(32) REPLACE DEFAULT "abc")
```sql
ALTER TABLE example_db.my_table
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/tiered-storage/remote-storage.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/tiered-storage/remote-storage.md
index 23002a2e37e..fcd5b563760 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/tiered-storage/remote-storage.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/tiered-storage/remote-storage.md
@@ -190,7 +190,7 @@ ALTER TABLE create_table_partition MODIFY PARTITION (*)
SET("storage_policy"="te
- Cache 是通过 LRU 管理的，不支持 TTL。
-具体配置请参考 (../../lakehouse/data-cache)。
+具体配置请参考 [数据缓存](../../lakehouse/filecache)。
## 常见问题
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/auth/authentication-and-authorization.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/auth/authentication-and-authorization.md
index f782fa6d7c0..d1ac58a28b2 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/auth/authentication-and-authorization.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/auth/authentication-and-authorization.md
@@ -111,9 +111,9 @@ Doris 支持以下密码策略，可以帮助用户更好的进行密码管理
- 设置用户属性：[SET
PROPERTY](../../sql-manual/sql-statements/account-management/SET-PROPERTY)
- 查看用户属性：[SHOW
PROPERTY](../../sql-manual/sql-statements/account-management/SHOW-PROPERTY)
- 修改密码：[SET
PASSWORD](../../sql-manual/sql-statements/account-management/SET-PASSWORD)
-- 查看支持的所有权限项：[SHOW PRIVILEGES]
-- 查看行权限策略 [SHOW ROW POLICY]
-- 创建行权限策略 [CREATE ROW POLICY]
+- 查看支持的所有权限项：[SHOW
PRIVILEGES](../../../../sql-manual/sql-statements/account-management/SHOW-PRIVILEGES)
+- 查看行权限策略：[SHOW ROW
POLICY](../../../../sql-manual/sql-statements/data-governance/SHOW-ROW-POLICY)
+- 创建行权限策略：[CREATE ROW
POLICY](../../../../sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY)
### 权限类型
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/db-connect/arrow-flight-sql-connect.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/db-connect/arrow-flight-sql-connect.md
index db9936361f3..d5eb7f71040 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/db-connect/arrow-flight-sql-connect.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/db-connect/arrow-flight-sql-connect.md
@@ -16,7 +16,6 @@
安装 Apache Arrow 你可以去官方文档 [Apache Arrow](https://arrow.apache.org/install/)
找到详细的安装教程。更多关于 Doris 实现 Arrow Flight 协议的原理可以参考 [Doris support Arrow Flight SQL
protocol](https://github.com/apache/doris/issues/25514)。
-
## Python 使用方法
使用 Python 的 ADBC Driver 连接 Doris 实现数据的极速读取，下面的步骤使用 Python（版本 >= 3.9）的 ADBC
Driver 执行一系列常见的数据库语法操作，包括 DDL、DML、设置 Session 变量以及 Show 语句等。
@@ -34,6 +33,7 @@ pip install adbc_driver_flightsql
```Python
import adbc_driver_manager
+import adbc_driver_flightsql
import adbc_driver_flightsql.dbapi as flight_sql
>>> print(adbc_driver_manager.__version__)
@@ -265,6 +265,7 @@ cursor.close()
Arrow Flight SQL 协议的开源 JDBC 驱动兼容标准的 JDBC API，可用于大多数 BI 工具通过 JDBC 访问
Doris，并支持高速传输 Apache Arrow 数据。使用方法与通过 MySQL 协议的 JDBC 驱动连接 Doris 类似，只需将链接 URL 中的
jdbc:mysql 协议换成 jdbc:arrow-flight-sql 协议，查询返回的结果依然是 JDBC 的 ResultSet 数据结构。
POM dependency:
+
```Java
<properties>
<arrow.version>17.0.0</arrow.version>
@@ -322,6 +323,7 @@ conn.close();
除了使用 JDBC，与 Python 类似，Java 也可以创建 Driver 读取 Doris 并返回 Arrow 格式的数据，下面分别是使用
AdbcDriver 和 JdbcDriver 连接 Doris Arrow Flight Server。
POM dependency:
+
```Java
<properties>
<adbc.version>0.15.0</adbc.version>
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/ecosystem/observability/beats.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/ecosystem/observability/beats.md
index aa46440b132..1fd73885c37 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/ecosystem/observability/beats.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/ecosystem/observability/beats.md
@@ -171,7 +171,7 @@ queue.mem:
flush.timeout: 10s
# 4. output 部分负责数据输出
-# doris output 将数据输出到 Doris，使用的是 Stream Load HTTP 接口。通过 headers 参数指定了 Stream
Load 的数据格式为 JSON，通过 codec_format_string 参数用类似 printf 的方式格式化输出到 Doris
的数据。比如下面的例子基于 filebeat 内部的字段 format 出一个 JSON，这些字段可以是 filebeat 内置字段如
agent.hostname，也可以是 processor 比如 dissect 生产的字段如 day，通过 %{[a][b]} 的方式引用，，Stream
Load 会自动将 JSON 字段写入对应的 Doris 表的字段。
+# doris output 将数据输出到 Doris，使用的是 Stream Load HTTP 接口。通过 headers 参数指定了 Stream
Load 的数据格式为 JSON，通过 codec_format_string 参数用类似 printf 的方式格式化输出到 Doris
的数据。比如下面的例子基于 filebeat 内部的字段 format 出一个 JSON，这些字段可以是 filebeat 内置字段如
agent.hostname，也可以是 processor 比如 dissect 生产的字段如 day，通过 %{[a][b]} 的方式引用，Stream
Load 会自动将 JSON 字段写入对应的 Doris 表的字段。
output.doris:
fenodes: [ "http://fehost1:http_port";, "http://fehost2:http_port";,
"http://fehost3:http_port"; ]
user: "your_username"
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/ALTER-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/ALTER-USER.md
index be89d848997..6d281210a02 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/ALTER-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/ALTER-USER.md
@@ -35,7 +35,7 @@ password_policy:
> 一个用户的唯一标识，语法为：'user_name'@'host'
> `user_identity` 由两部分组成，user_name 和 host，其中 username 为用户名。host
> 标识用户端连接所在的主机地址。host 部分可以使用 % 进行模糊匹配。如果不指定 host，默认为 '%'，即表示该用户可以从任意 host 连接到
> Doris。
-> host 部分也可指定为 domain，，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
+> host 部分也可指定为 domain，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
## 可选参数
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/CREATE-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/CREATE-USER.md
index 21312b631e2..46dfa712da1 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/CREATE-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-statements/account-management/CREATE-USER.md
@@ -31,7 +31,7 @@ password_policy:
> 一个用户的唯一标识，语法为：'user_name'@'host'
> `user_identity` 由两部分组成，user_name 和 host，其中 username 为用户名。host
> 标识用户端连接所在的主机地址。host 部分可以使用 % 进行模糊匹配。如果不指定 host，默认为 '%'，即表示该用户可以从任意 host 连接到
> Doris。
-> host 部分也可指定为 domain，，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
+> host 部分也可指定为 domain，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
## 可选参数
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/best-practice.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/best-practice.md
index 625bfc6e829..9850d4c4664 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/best-practice.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/best-practice.md
@@ -303,7 +303,7 @@ DISTRIBUTED BY HASH(`siteid`) BUCKETS 10;
4. 亿级别以上数据，如果有模糊匹配，使用倒排索引或者是 NGram Bloomfilter
:::
-### 2.6 Bitmap 索引
+### 6 Bitmap 索引
为了加速数据查询，Doris 支持用户为某些字段添加 Bitmap 索引，适合在基数较低的列上进行等值查询或范围查询的场景。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/data-partitioning/dynamic-partitioning.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/data-partitioning/dynamic-partitioning.md
index 395a09bbf2c..c65a3b3b24d 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/data-partitioning/dynamic-partitioning.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/data-partitioning/dynamic-partitioning.md
@@ -69,12 +69,13 @@ PROPERTIES(
下例中通过 ALTER TABLE 语句，将非动态分区表修改为动态分区：
```sql
-CREATE TABLE test_dynamic_partition(
+CREATE TABLE test_partition(
order_id BIGINT,
create_dt DATE,
username VARCHAR(20)
)
DUPLICATE KEY(order_id)
+PARTITION BY RANGE(create_dt) ()
DISTRIBUTED BY HASH(order_id) BUCKETS 10;
ALTER TABLE test_partition SET (
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/index/ngram-bloomfilter-index.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/index/ngram-bloomfilter-index.md
index 1223ba85cc9..4f841e7b4d9 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/index/ngram-bloomfilter-index.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/index/ngram-bloomfilter-index.md
@@ -61,7 +61,7 @@ NGram BloomFilter 索引只能加速字符串 LIKE 查询，而且 LIKE pattern
SHOW CREATE TABLE table_name;
-- 语法 2，IndexType 为 NGRAM_BF 的是倒排索引
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
```
### 删除 NGram BloomFilter 索引
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/schema-change.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/schema-change.md
index 5b0fcc0623c..015230f7d90 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/schema-change.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/schema-change.md
@@ -188,7 +188,7 @@ CREATE TABLE IF NOT EXISTS example_db.my_table(
DISTRIBUTED BY HASH(col1) BUCKETS 10;
```
-2. 从 `example_db.my_table` 删除`col3`列
+2. 从 `example_db.my_table` 删除`col4`列
```sql
ALTER TABLE example_db.my_table DROP COLUMN col4;
@@ -252,7 +252,7 @@ MODIFY COLUMN col1 BIGINT KEY DEFAULT "1" AFTER col2;
注意：无论是修改 Key 列还是 Value 列都需要声明完整的 Column 信息
-2. 修改 Base Table 的 val1 列最大长度。原 val1 为 (val1 VARCHAR(32) REPLACE DEFAULT "abc")
+2. 修改 Base Table 的 val5 列最大长度。原 val5 为 (val5 VARCHAR(32) REPLACE DEFAULT "abc")
```sql
ALTER TABLE example_db.my_table
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/tiered-storage/remote-storage.m
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/tiered-storage/remote-storage.m
index 23b373fea9f..38aff3587ab 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/tiered-storage/remote-storage.m
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/tiered-storage/remote-storage.m
@@ -206,7 +206,7 @@ ALTER TABLE create_table_partition MODIFY PARTITION (*)
SET("storage_policy"="te
- Cache 是通过 LRU 管理的，不支持 TTL。
-具体配置请参考(../../lakehouse/data-cache)。
+具体配置请参考 [数据缓存](../../lakehouse/filecache)。
## 常见问题
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/tiered-storage/remote-storage.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/tiered-storage/remote-storage.md
index 23002a2e37e..fcd5b563760 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/tiered-storage/remote-storage.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/tiered-storage/remote-storage.md
@@ -190,7 +190,7 @@ ALTER TABLE create_table_partition MODIFY PARTITION (*)
SET("storage_policy"="te
- Cache 是通过 LRU 管理的，不支持 TTL。
-具体配置请参考 (../../lakehouse/data-cache)。
+具体配置请参考 [数据缓存](../../lakehouse/filecache)。
## 常见问题
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-feature/memory-tracker.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-feature/memory-tracker.md
index 5f5c103fbfc..cc5757409c1 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-feature/memory-tracker.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-feature/memory-tracker.md
@@ -80,7 +80,7 @@ Orphan Memory Tracker 是默认 Memory Tracker，值为正数或负数都意味
- 如果线程开始时 TLS 中没有绑定 Memory Tracker，那么 Doris Allocator 会默认将内存记录到 Orphan Memory
Tracker 中，意味着这部分内存不知所属，有关 Doris Allocator 记录内存的原理参考上文 [内存跟踪原理]。
-- Query 或 Load 等任务 Memory Tracker 析构时如果值不等于 0，，通常意味着这部分内存没有释放，将把这部分剩余的内存记录到
Orphan Memory Tracker 中，相当于将剩余内存交由 Orphan Memory Tracker 继续跟踪。从而保证 Orphan
Memory Tracker 和其他 Memory Tracker 之和等于 Doris Allocator 分配出去的所有内存。
+- Query 或 Load 等任务 Memory Tracker 析构时如果值不等于 0，通常意味着这部分内存没有释放，将把这部分剩余的内存记录到
Orphan Memory Tracker 中，相当于将剩余内存交由 Orphan Memory Tracker 继续跟踪。从而保证 Orphan
Memory Tracker 和其他 Memory Tracker 之和等于 Doris Allocator 分配出去的所有内存。
理想情况下，期望 Orphan Memory Tracker 的值接近 0。所以我们希望所有线程开始时都 Attach 一个 Orphan 之外的
Memory Tracker，比如 Query 或 Load Memory Tracker。并且所有 Query 或 Load Memory Tracker
析构时都等于 0，这意味着 Query 或 Load 执行过程中使用的内存在析构时都已经被释放。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/ALTER-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/ALTER-USER.md
index f677c410f25..0b4252cc30e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/ALTER-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/ALTER-USER.md
@@ -31,7 +31,7 @@ password_policy:
> 一个用户的唯一标识，语法为：'user_name'@'host'
> `user_identity` 由两部分组成，user_name 和 host，其中 username 为用户名。host
> 标识用户端连接所在的主机地址。host 部分可以使用 % 进行模糊匹配。如果不指定 host，默认为 '%'，即表示该用户可以从任意 host 连接到
> Doris。
-> host 部分也可指定为 domain，，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
+> host 部分也可指定为 domain，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
## 可选参数
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/CREATE-USER.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/CREATE-USER.md
index cc676e31018..125296b02d3 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/CREATE-USER.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/account-management/CREATE-USER.md
@@ -31,7 +31,7 @@ password_policy:
> 一个用户的唯一标识，语法为：'user_name'@'host'
> `user_identity` 由两部分组成，user_name 和 host，其中 username 为用户名。host
> 标识用户端连接所在的主机地址。host 部分可以使用 % 进行模糊匹配。如果不指定 host，默认为 '%'，即表示该用户可以从任意 host 连接到
> Doris。
-> host 部分也可指定为 domain，，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
+> host 部分也可指定为 domain，即使用中括号包围，则 Doris 会认为这个是一个 domain，并尝试解析其 ip 地址。
## 可选参数
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
index 2589c631f8b..9df2baad3a4 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
@@ -80,12 +80,13 @@ PROPERTIES(
下例通过 ALTER TABLE 语句将非动态分区表修改为动态分区表：
```sql
-CREATE TABLE test_dynamic_partition(
+CREATE TABLE test_partition(
order_id BIGINT,
create_dt DATE,
username VARCHAR(20)
)
DUPLICATE KEY(order_id)
+PARTITION BY RANGE(create_dt) ()
DISTRIBUTED BY HASH(order_id) BUCKETS 10;
ALTER TABLE test_partition SET (
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/index/ngram-bloomfilter-index.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/index/ngram-bloomfilter-index.md
index c018ce91a11..06dd06e96ae 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/index/ngram-bloomfilter-index.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/index/ngram-bloomfilter-index.md
@@ -97,7 +97,7 @@ COMMENT 'username ngram_bf index'
SHOW CREATE TABLE table_name;
-- 方式 2：IndexType 为 NGRAM_BF 标识为 NGram BloomFilter 索引
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
```
### 删除索引
diff --git
a/versioned_docs/version-2.0/install/cluster-deployment/standard-deployment.md
b/versioned_docs/version-2.0/install/cluster-deployment/standard-deployment.md
index 3ec61b06e0d..6c418933b98 100644
---
a/versioned_docs/version-2.0/install/cluster-deployment/standard-deployment.md
+++
b/versioned_docs/version-2.0/install/cluster-deployment/standard-deployment.md
@@ -19,7 +19,7 @@ Manually deploying a Doris cluster typically involves four
steps:
**CPU**
-When installing Doris, it is recommended to use machines that support the AVX2
instruction set to leverage its vectorization capabilities for query
acceleration.
+When installing Doris, it is recommended to use machines that support the AVX2
instruction set to leverage its vectorization capabilities for query
acceleration.
Run the following command. If a result is returned, that means the machine
supports the AVX2 instruction set.
@@ -61,13 +61,15 @@ Doris can run on servers with x86-64 architecture or ARM64
architecture.
| Frontend | 8+ Cores | 8+ GB | SSD or SATA, 10+ GB | 1 or 10 GbE | 1
|
| Backend | 8+ Cores | 16+ GB | SSD or SATA, 50+ GB | 1 or 10 GbE | 1
|
-:::tip
+:::tip
Description:
+
- In a validation testing environment, you can deploy the FE and BE on the
same server.
- It is generally recommended to deploy only **one BE instance on a single
machine**. Meanwhile, you can only deploy **one** **FE** **on one machine**.
- If you need three replicas of data, you will need at least three machines
and deploy one BE instance on each of them, instead of deploying three BE
instances on one single machine.
- **The clocks of multiple servers hosting FEs must be synchronized, allowing
a maximum clock deviation of 5 seconds.**
- In a testing environment, you can also perform tests with just one BE. In
the actual production environment, the number of BE instances directly affects
the overall query latency.
+
:::
**Production environment**
@@ -77,11 +79,13 @@ Description:
| Frontend | 16+ Cores | 64+ GB | SSD or RAID, 100+ GB | 10 GbE | 1
|
| Backend | 16+ Cores | 64+ GB | SSD or SATA, 100+ GB | 10 GbE | 3
|
-:::tip
+:::tip
Description:
+
- In a production environment, if the FE and BE are co-located, be mindful of
resource contention issues. It is recommended to store metadata and data on
separate disks.
- BE nodes can be configured with multiple disks for storage. You can bind
multiple HDDs or SSDs to a single BE instance.
- The performance of the cluster is dependent on the resources of the BE
nodes. The more BE nodes there are, the better the performance of Doris.
Typically, Doris can fully leverage its performance potential with 10 to 100
machines.
+
:::
### Hard disk space calculation
@@ -125,8 +129,8 @@ tmpfs /tmp tmpfs nodev,nosuid
0 0
/dev/sda3 /home ext4 defaults,noatime 0 2
```
-:::caution
-It is not recommended to disable swap by setting vm.swappiness = 0 because
this parameter has different semantics in different Linux kernel versions. In
many cases, this will not completely disable swap.
+:::caution
+It is not recommended to disable swap by setting vm.swappiness = 0 because
this parameter has different semantics in different Linux kernel versions. In
many cases, this will not completely disable swap.
:::
### Check and disable system firewall
@@ -140,7 +144,7 @@ sudo systemctl disable firewalld.service
### Configure NTP service
-Doris metadata requires a time precision of less than 5000ms, so clock
synchronization is required for all machines in the cluster. This prevents
metadata inconsistency from causing service abnormalities.
+Doris metadata requires a time precision of less than 5000ms, so clock
synchronization is required for all machines in the cluster. This prevents
metadata inconsistency from causing service abnormalities.
Typically, you can ensure clock synchronization across nodes by NTP service
configuration.
@@ -159,8 +163,8 @@ vi /etc/security/limits.conf
* hard nofile 1000000
```
-:::caution
-For the changes to take effect, the current user needs to log out of the
current session and log back in.
+:::caution
+For the changes to take effect, the current user needs to log out of the
current session and log back in.
:::
### Modify the number of virtual memory areas
@@ -232,7 +236,8 @@ After extracting the installation package, there is usually
a default doris-meta
mkdir -p <doris_meta_created>
## Create a symbolic link to the FE metadata directory.
-ln -s <doris_meta_original> <doris_meta_created>
+rm -rf <doris_meta_original>
+ln -s <doris_meta_created> <doris_meta_original>
```
**Modify FE configuration file**
@@ -318,9 +323,11 @@ ALTER SYSTEM ADD OBSERVER
"<fe_ip_address>:<fe_edit_log_port>"
```
:::note
+
1. It is recommended to have an odd number of FE Follower nodes (including the
Master node), with a suggested number of three to achieve high availability.
2. When FE is deployed in a high availability mode (1 Master node, 2 Follower
nodes), it is advisable to increase the scalability of the FE read services by
adding an Observer FE.
3. Typically, one FE node can handle around 10-20 BE nodes. It is recommended
to keep the total number of FE nodes below 10.
+
:::
**Start** **FE** **Follower node**
@@ -337,7 +344,7 @@ bin/start_fe.sh --helper <helper_fe_ip>:<fe_edit_log_port>
--daemon
To check the status of a Follower node, follow the same method of checking the
status of the FE Master node. After registering the FE Follower node, use the
`show frontends` command to view the FE node status. Unlike the Master node,
the `IsMaster` status should be false for the Follower node.
-### Deploy BE
+### Deploy BE
**Create directory**
@@ -379,10 +386,12 @@
storage_root_path=/home/disk1/doris,medium:HDD;/home/disk2/doris,medium:SSD
```
:::note
+
1. When specifying the storage type for the storage path, at least one path
should have the storage type set as HDD.
2. If the storage type for a storage path is not explicitly declared, it
defaults to HDD.
3. Specifying the storage type as HDD or SSD is to differentiate the storage
types for the paths. It is independent of the physical storage medium. For
example, you can designate a directory on an HDD disk as SSD.
4. The keywords for storage types, HDD and SSD, must be capitalized.
+
:::
6. Bind cluster IP
@@ -419,7 +428,7 @@ After BE process is started, it runs in the background. The
log files are stored
**Check BE status**
-After connecting to the Doris cluster, you can use the `show backends` command
to check the status of the BE nodes.
+After connecting to the Doris cluster, you can use the `show backends` command
to check the status of the BE nodes.
```SQL
## Connect to Doris cluster
@@ -526,20 +535,20 @@ Doris processes listen to network segments represented in
CIDR format for IP add
This parameter is mainly used to help the system select the correct network
card IP as its listening IP. For example, if the required listening IP is
192.168.0.1, you can set `priority_networks=192.168.0.0/24`. The system will
automatically scan all IPs on the machine, and only those matching the
192.168.0.0/24 network segment will be used as service listening addresses. You
can also configure multiple CIDR network segments in this parameter, such as
`priority_networks = 10.10.0.0/16; 19 [...]
-:::tip
+:::tip
**Why use priority_networks to configure listening address segments instead of
directly setting the listening IP address in the configuration file?**
-The main reason is that Doris is a distributed cluster, and the same
configuration file will be deployed on multiple nodes. To facilitate
deployment, updates, and maintenance, it is desirable to keep all nodes'
configuration files consistent. By configuring the listening address segment
and then starting the system, the appropriate listening IP can be found based
on this network segment, thus each machine can use a single value in this
configuration.
+The main reason is that Doris is a distributed cluster, and the same
configuration file will be deployed on multiple nodes. To facilitate
deployment, updates, and maintenance, it is desirable to keep all nodes'
configuration files consistent. By configuring the listening address segment
and then starting the system, the appropriate listening IP can be found based
on this network segment, thus each machine can use a single value in this
configuration.
:::
### Why do new BE nodes need to be manually added to the cluster?
After the BE node is started, you need to send a command to the FE through the
MySQL protocol or the built-in web console to join the BE node to the cluster.
-:::tip
+:::tip
**How does the FE know which BE nodes constitute the cluster?**
-As a distributed database, Doris generally has many BE nodes. Doris adds BE
nodes to the cluster by sending commands to the FE. This is different from the
way how BE nodes know the addresses of FE nodes and then actively report
connections. The way of manual adding and having the FE actively connect to BE
nodes is beneficial to cluster management in many aspects. For example, it can
determine which nodes constitute the cluster and it can proactively shut down a
BE node that cannot be con [...]
+As a distributed database, Doris generally has many BE nodes. Doris adds BE
nodes to the cluster by sending commands to the FE. This is different from the
way how BE nodes know the addresses of FE nodes and then actively report
connections. The way of manual adding and having the FE actively connect to BE
nodes is beneficial to cluster management in many aspects. For example, it can
determine which nodes constitute the cluster and it can proactively shut down a
BE node that cannot be con [...]
:::
### How to quickly detect whether the FE has started successfully?
@@ -570,8 +579,8 @@ ALTER SYSTEM ADD BACKEND
"be_host_ip:heartbeat_service_port";
-:::tip
-For successful execution of statements that are not related to specific
databases/tables in the Playground, it is necessary to randomly select a
database from the left-hand database panel. This limitation will be removed
later.
+:::tip
+For successful execution of statements that are not related to specific
databases/tables in the Playground, it is necessary to randomly select a
database from the left-hand database panel. This limitation will be removed
later.
:::
### Why can't I change the root password via the Web UI?
diff --git a/versioned_docs/version-2.0/table-design/index/inverted-index.md
b/versioned_docs/version-2.0/table-design/index/inverted-index.md
index 0b33436a4c9..f22279d8b7c 100644
--- a/versioned_docs/version-2.0/table-design/index/inverted-index.md
+++ b/versioned_docs/version-2.0/table-design/index/inverted-index.md
@@ -244,7 +244,7 @@ ALTER TABLE table_name DROP INDEX idx_name;
SHOW CREATE TABLE table_name;
-- Syntax 2: IndexType as INVERTED indicates an inverted index
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
## Using Indexes
@@ -377,7 +377,7 @@ PROPERTIES ("replication_num" = "1");
```
wget
https://qa-build.oss-cn-beijing.aliyuncs.com/regression/index/hacknernews_1m.csv.gz
-curl --location-trusted -u root: -H "compress_type:gz" -T
hacknernews_1m.csv.gz
http://127.0.0.1:8030/api/test_inverted_index/hackernews_1m/_stream_load
+curl --location-trusted -u root: -H "compress_type:gz" -T
hacknernews_1m.csv.gz -XPUT
http://127.0.0.1:8030/api/test_inverted_index/hackernews_1m/_stream_load
{
"TxnId": 2,
"Label": "a8a3e802-2329-49e8-912b-04c800a461a6",
diff --git
a/versioned_docs/version-2.0/table-design/index/ngram-bloomfilter-index.md
b/versioned_docs/version-2.0/table-design/index/ngram-bloomfilter-index.md
index c5654c8d217..8ea9f23faf7 100644
--- a/versioned_docs/version-2.0/table-design/index/ngram-bloomfilter-index.md
+++ b/versioned_docs/version-2.0/table-design/index/ngram-bloomfilter-index.md
@@ -54,7 +54,7 @@ SHOW CREATE TABLE table_name;
-- Syntax 2: IndexType as NGRAM_BF indicates an inverted index
```sql
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
```
### Deleting an NGram BloomFilter Index
diff --git a/versioned_docs/version-2.0/table-design/schema-change.md
b/versioned_docs/version-2.0/table-design/schema-change.md
index 672e0ea3861..58acaa13d38 100644
--- a/versioned_docs/version-2.0/table-design/schema-change.md
+++ b/versioned_docs/version-2.0/table-design/schema-change.md
@@ -267,7 +267,7 @@ MODIFY COLUMN col1 BIGINT KEY DEFAULT "1" AFTER col2;
Note: whether modifying a key column or a value column, the complete column
information needs to be declared.
-**2. Modifying the maximum length of column val1 in the Base Index. The
original val1 is (val1 VARCHAR(32) REPLACE DEFAULT "abc")**
+**2. Modifying the maximum length of column val5 in the Base Index. The
original val5 is (val5 VARCHAR(32) REPLACE DEFAULT "abc")**
```sql
ALTER TABLE example_db.my_table
diff --git a/versioned_docs/version-2.1/db-connect/arrow-flight-sql-connect.md
b/versioned_docs/version-2.1/db-connect/arrow-flight-sql-connect.md
index ae25f177c19..52f60c783b5 100644
--- a/versioned_docs/version-2.1/db-connect/arrow-flight-sql-connect.md
+++ b/versioned_docs/version-2.1/db-connect/arrow-flight-sql-connect.md
@@ -16,7 +16,6 @@ In Doris, query results are organized in columnar format as
Blocks. In versions
To install Apache Arrow, you can find detailed installation instructions in
the official documentation [Apache Arrow](https://arrow.apache.org/install/).
For more information on how Doris implements the Arrow Flight protocol, you can
refer to [Doris support Arrow Flight SQL
protocol](https://github.com/apache/doris/issues/25514).
-
## Python Usage
Use Python's ADBC Driver to connect to Doris to achieve extremely fast data
reading. The following steps use Python (version >= 3.9) ADBC Driver to
perform a series of common database syntax operations, including DDL, DML,
setting Session variables, and Show statements.
@@ -34,6 +33,7 @@ Import the following modules/libraries in the code to use the
installed Library:
```Python
import adbc_driver_manager
+import adbc_driver_flightsql
import adbc_driver_flightsql.dbapi as flight_sql
>>> print(adbc_driver_manager.__version__)
@@ -265,6 +265,7 @@ cursor.close()
The open source JDBC driver of Arrow Flight SQL protocol is compatible with
the standard JDBC API, which can be used by most BI tools to access Doris
through JDBC and supports high-speed transmission of Apache Arrow data. The
usage is similar to connecting to Doris through the JDBC driver of MySQL
protocol. You only need to replace the jdbc:mysql protocol in the link URL with
the jdbc:arrow-flight-sql protocol. The query results are still returned in the
JDBC ResultSet data structure.
POM dependency:
+
```Java
<properties>
<arrow.version>17.0.0</arrow.version>
@@ -322,6 +323,7 @@ conn.close();
In addition to using JDBC, similar to Python, JAVA can also create a Driver to
read Doris and return data in Arrow format. The following are how to use
AdbcDriver and JdbcDriver to connect to Doris Arrow Flight Server.
POM dependency:
+
```Java
<properties>
<adbc.version>0.15.0</adbc.version>
diff --git
a/versioned_docs/version-2.1/table-design/data-partitioning/dynamic-partitioning.md
b/versioned_docs/version-2.1/table-design/data-partitioning/dynamic-partitioning.md
index 728162d2af9..0bea7e09cb7 100644
---
a/versioned_docs/version-2.1/table-design/data-partitioning/dynamic-partitioning.md
+++
b/versioned_docs/version-2.1/table-design/data-partitioning/dynamic-partitioning.md
@@ -68,12 +68,13 @@ When using the ALTER TABLE statement to modify dynamic
partitioning, the changes
In the example below, the ALTER TABLE statement is used to modify a
non-dynamic partitioned table to a dynamic partitioned table:
```sql
-CREATE TABLE test_dynamic_partition(
+CREATE TABLE test_partition(
order_id BIGINT,
create_dt DATE,
username VARCHAR(20)
)
DUPLICATE KEY(order_id)
+PARTITION BY RANGE(create_dt) ()
DISTRIBUTED BY HASH(order_id) BUCKETS 10;
ALTER TABLE test_partition SET (
diff --git a/versioned_docs/version-2.1/table-design/index/inverted-index.md
b/versioned_docs/version-2.1/table-design/index/inverted-index.md
index cbd2ed8e245..1285e45ada3 100644
--- a/versioned_docs/version-2.1/table-design/index/inverted-index.md
+++ b/versioned_docs/version-2.1/table-design/index/inverted-index.md
@@ -242,7 +242,7 @@ ALTER TABLE table_name DROP INDEX idx_name;
SHOW CREATE TABLE table_name;
-- Syntax 2: IndexType as INVERTED indicates an inverted index
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
## Using Indexes
@@ -393,7 +393,7 @@ PROPERTIES ("replication_num" = "1");
```
wget
https://qa-build.oss-cn-beijing.aliyuncs.com/regression/index/hacknernews_1m.csv.gz
-curl --location-trusted -u root: -H "compress_type:gz" -T
hacknernews_1m.csv.gz
http://127.0.0.1:8030/api/test_inverted_index/hackernews_1m/_stream_load
+curl --location-trusted -u root: -H "compress_type:gz" -T
hacknernews_1m.csv.gz -XPUT
http://127.0.0.1:8030/api/test_inverted_index/hackernews_1m/_stream_load
{
"TxnId": 2,
"Label": "a8a3e802-2329-49e8-912b-04c800a461a6",
diff --git
a/versioned_docs/version-2.1/table-design/index/ngram-bloomfilter-index.md
b/versioned_docs/version-2.1/table-design/index/ngram-bloomfilter-index.md
index 9303c1f0306..790ec089e73 100644
--- a/versioned_docs/version-2.1/table-design/index/ngram-bloomfilter-index.md
+++ b/versioned_docs/version-2.1/table-design/index/ngram-bloomfilter-index.md
@@ -55,7 +55,7 @@ SHOW CREATE TABLE table_name;
-- Syntax 2: IndexType as NGRAM_BF indicates an inverted index
```sql
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
```
### Deleting an NGram BloomFilter Index
diff --git a/versioned_docs/version-2.1/table-design/schema-change.md
b/versioned_docs/version-2.1/table-design/schema-change.md
index 1ebd840a9e3..c3dd66f4921 100644
--- a/versioned_docs/version-2.1/table-design/schema-change.md
+++ b/versioned_docs/version-2.1/table-design/schema-change.md
@@ -247,7 +247,7 @@ MODIFY COLUMN col1 BIGINT KEY DEFAULT "1" AFTER col2;
Note: Whether modifying a key column or a value column, the complete column
information must be declared.
-3. Modify the maximum length of the `val1` column in the base table. The
original `val1` was (val1 VARCHAR(32) REPLACE DEFAULT "abc")
+3. Modify the maximum length of the `val5` column in the base table. The
original `val5` was (val5 VARCHAR(32) REPLACE DEFAULT "abc")
```sql
ALTER TABLE example_db.my_table
diff --git
a/versioned_docs/version-2.1/table-design/tiered-storage/remote-storage.md
b/versioned_docs/version-2.1/table-design/tiered-storage/remote-storage.md
index 7330a5c3031..4ca0ea49e2b 100644
--- a/versioned_docs/version-2.1/table-design/tiered-storage/remote-storage.md
+++ b/versioned_docs/version-2.1/table-design/tiered-storage/remote-storage.md
@@ -190,7 +190,7 @@ To optimize query performance and save object storage
resources, local Cache has
- The Cache is managed through LRU and does not support TTL.
-For specific configurations, please refer to (../../lakehouse/data-cache).
+For specific configurations, please refer to [Data
Cache](../../lakehouse/filecache).
## FAQ
diff --git a/versioned_docs/version-3.x/db-connect/arrow-flight-sql-connect.md
b/versioned_docs/version-3.x/db-connect/arrow-flight-sql-connect.md
index ae25f177c19..52f60c783b5 100644
--- a/versioned_docs/version-3.x/db-connect/arrow-flight-sql-connect.md
+++ b/versioned_docs/version-3.x/db-connect/arrow-flight-sql-connect.md
@@ -16,7 +16,6 @@ In Doris, query results are organized in columnar format as
Blocks. In versions
To install Apache Arrow, you can find detailed installation instructions in
the official documentation [Apache Arrow](https://arrow.apache.org/install/).
For more information on how Doris implements the Arrow Flight protocol, you can
refer to [Doris support Arrow Flight SQL
protocol](https://github.com/apache/doris/issues/25514).
-
## Python Usage
Use Python's ADBC Driver to connect to Doris to achieve extremely fast data
reading. The following steps use Python (version >= 3.9) ADBC Driver to
perform a series of common database syntax operations, including DDL, DML,
setting Session variables, and Show statements.
@@ -34,6 +33,7 @@ Import the following modules/libraries in the code to use the
installed Library:
```Python
import adbc_driver_manager
+import adbc_driver_flightsql
import adbc_driver_flightsql.dbapi as flight_sql
>>> print(adbc_driver_manager.__version__)
@@ -265,6 +265,7 @@ cursor.close()
The open source JDBC driver of Arrow Flight SQL protocol is compatible with
the standard JDBC API, which can be used by most BI tools to access Doris
through JDBC and supports high-speed transmission of Apache Arrow data. The
usage is similar to connecting to Doris through the JDBC driver of MySQL
protocol. You only need to replace the jdbc:mysql protocol in the link URL with
the jdbc:arrow-flight-sql protocol. The query results are still returned in the
JDBC ResultSet data structure.
POM dependency:
+
```Java
<properties>
<arrow.version>17.0.0</arrow.version>
@@ -322,6 +323,7 @@ conn.close();
In addition to using JDBC, similar to Python, JAVA can also create a Driver to
read Doris and return data in Arrow format. The following are how to use
AdbcDriver and JdbcDriver to connect to Doris Arrow Flight Server.
POM dependency:
+
```Java
<properties>
<adbc.version>0.15.0</adbc.version>
diff --git
a/versioned_docs/version-3.x/table-design/data-partitioning/dynamic-partitioning.md
b/versioned_docs/version-3.x/table-design/data-partitioning/dynamic-partitioning.md
index b8a154d7b0c..743173a5c50 100644
---
a/versioned_docs/version-3.x/table-design/data-partitioning/dynamic-partitioning.md
+++
b/versioned_docs/version-3.x/table-design/data-partitioning/dynamic-partitioning.md
@@ -67,12 +67,13 @@ When using the ALTER TABLE statement to modify dynamic
partitioning, the changes
In the example below, the ALTER TABLE statement is used to modify a
non-dynamic partitioned table to a dynamic partitioned table:
```sql
-CREATE TABLE test_dynamic_partition(
+CREATE TABLE test_partition(
order_id BIGINT,
create_dt DATE,
username VARCHAR(20)
)
DUPLICATE KEY(order_id)
+PARTITION BY RANGE(create_dt) ()
DISTRIBUTED BY HASH(order_id) BUCKETS 10;
ALTER TABLE test_partition SET (
diff --git a/versioned_docs/version-3.x/table-design/index/inverted-index.md
b/versioned_docs/version-3.x/table-design/index/inverted-index.md
index 18e62af11d5..5ecf59e3c91 100644
--- a/versioned_docs/version-3.x/table-design/index/inverted-index.md
+++ b/versioned_docs/version-3.x/table-design/index/inverted-index.md
@@ -284,7 +284,7 @@ ALTER TABLE table_name DROP INDEX idx_name;
SHOW CREATE TABLE table_name;
-- Syntax 2: IndexType as INVERTED indicates an inverted index
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
## Using Indexes
@@ -479,7 +479,7 @@ PROPERTIES ("replication_num" = "1");
```
wget
https://qa-build.oss-cn-beijing.aliyuncs.com/regression/index/hacknernews_1m.csv.gz
-curl --location-trusted -u root: -H "compress_type:gz" -T
hacknernews_1m.csv.gz
http://127.0.0.1:8030/api/test_inverted_index/hackernews_1m/_stream_load
+curl --location-trusted -u root: -H "compress_type:gz" -T
hacknernews_1m.csv.gz -XPUT
http://127.0.0.1:8030/api/test_inverted_index/hackernews_1m/_stream_load
{
"TxnId": 2,
"Label": "a8a3e802-2329-49e8-912b-04c800a461a6",
diff --git
a/versioned_docs/version-3.x/table-design/index/ngram-bloomfilter-index.md
b/versioned_docs/version-3.x/table-design/index/ngram-bloomfilter-index.md
index 9303c1f0306..790ec089e73 100644
--- a/versioned_docs/version-3.x/table-design/index/ngram-bloomfilter-index.md
+++ b/versioned_docs/version-3.x/table-design/index/ngram-bloomfilter-index.md
@@ -55,7 +55,7 @@ SHOW CREATE TABLE table_name;
-- Syntax 2: IndexType as NGRAM_BF indicates an inverted index
```sql
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
```
### Deleting an NGram BloomFilter Index
diff --git a/versioned_docs/version-3.x/table-design/schema-change.md
b/versioned_docs/version-3.x/table-design/schema-change.md
index 1b276e3f6fe..80bcff54a92 100644
--- a/versioned_docs/version-3.x/table-design/schema-change.md
+++ b/versioned_docs/version-3.x/table-design/schema-change.md
@@ -251,7 +251,7 @@ MODIFY COLUMN col1 BIGINT KEY DEFAULT "1" AFTER col2;
Note: Whether modifying a key column or a value column, the complete column
information must be declared.
-3. Modify the maximum length of the `val1` column in the base table. The
original `val1` was (val1 VARCHAR(32) REPLACE DEFAULT "abc")
+3. Modify the maximum length of the `val5` column in the base table. The
original `val5` was (val5 VARCHAR(32) REPLACE DEFAULT "abc")
```sql
ALTER TABLE example_db.my_table
diff --git
a/versioned_docs/version-3.x/table-design/tiered-storage/remote-storage.md
b/versioned_docs/version-3.x/table-design/tiered-storage/remote-storage.md
index efeba59de61..358c9db94d6 100644
--- a/versioned_docs/version-3.x/table-design/tiered-storage/remote-storage.md
+++ b/versioned_docs/version-3.x/table-design/tiered-storage/remote-storage.md
@@ -190,7 +190,7 @@ To optimize query performance and save object storage
resources, local Cache has
- The Cache is managed through LRU and does not support TTL.
-For specific configurations, please refer to (../../lakehouse/data-cache).
+For specific configurations, please refer to [Data
Cache](../../lakehouse/filecache).
## FAQ
diff --git
a/versioned_docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
b/versioned_docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
index 6d7d456efef..bcb7f00915b 100644
---
a/versioned_docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
+++
b/versioned_docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
@@ -80,12 +80,13 @@ Modifying dynamic partitions with the `ALTER TABLE`
statement does not take effe
The following example uses an `ALTER TABLE` statement to convert a non-dynamic
partitioned table into a dynamic partitioned table:
```sql
-CREATE TABLE test_dynamic_partition(
+CREATE TABLE test_partition(
order_id BIGINT,
create_dt DATE,
username VARCHAR(20)
)
DUPLICATE KEY(order_id)
+PARTITION BY RANGE(create_dt) ()
DISTRIBUTED BY HASH(order_id) BUCKETS 10;
ALTER TABLE test_partition SET (
diff --git
a/versioned_docs/version-4.x/table-design/index/ngram-bloomfilter-index.md
b/versioned_docs/version-4.x/table-design/index/ngram-bloomfilter-index.md
index 38aa923b90c..75a7d7d4658 100644
--- a/versioned_docs/version-4.x/table-design/index/ngram-bloomfilter-index.md
+++ b/versioned_docs/version-4.x/table-design/index/ngram-bloomfilter-index.md
@@ -97,7 +97,7 @@ It is recommended to prefix index names with `idx_`, for
example `idx_review_bod
SHOW CREATE TABLE table_name;
-- Method 2: An IndexType of NGRAM_BF marks an NGram BloomFilter index
-SHOW INDEX FROM idx_name;
+SHOW INDEX FROM table_name;
```
### Drop an Index
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
