This is an automated email from the ASF dual-hosted git repository.
yiguolei 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 5e595254480 [docs] fix typo (#3132)
5e595254480 is described below
commit 5e59525448022ac2d8c725bbeac0adb717c911a2
Author: curiosity-hyf <[email protected]>
AuthorDate: Mon Dec 8 10:33:03 2025 +0800
[docs] fix typo (#3132)
## Versions
- [x] dev
- [x] 4.x
- [x] 3.x
- [x] 2.1
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [ ] Checked by AI
- [ ] Test Cases Built
---------
Signed-off-by: curiosity-hyf <[email protected]>
---
docs/table-design/data-model/aggregate.md | 2 +-
.../current/table-design/data-model/aggregate.md | 2 +-
.../current/table-design/data-model/unique.md | 2 +-
.../version-2.1/table-design/data-model/aggregate.md | 2 +-
.../version-2.1/table-design/data-model/unique.md | 2 +-
.../version-3.x/table-design/data-model/aggregate.md | 2 +-
.../version-3.x/table-design/data-model/unique.md | 2 +-
.../version-4.x/table-design/data-model/aggregate.md | 2 +-
.../version-4.x/table-design/data-model/unique.md | 2 +-
versioned_docs/version-2.0/table-design/data-model/aggregate.md | 2 +-
versioned_docs/version-2.1/table-design/data-model/aggregate.md | 2 +-
versioned_docs/version-3.x/table-design/data-model/aggregate.md | 2 +-
versioned_docs/version-4.x/table-design/data-model/aggregate.md | 2 +-
13 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/docs/table-design/data-model/aggregate.md
b/docs/table-design/data-model/aggregate.md
index f38a58ce552..7552f825d44 100644
--- a/docs/table-design/data-model/aggregate.md
+++ b/docs/table-design/data-model/aggregate.md
@@ -54,7 +54,7 @@ AGGREGATE KEY(user_id, load_dt, city)
DISTRIBUTED BY HASH(user_id) BUCKETS 10;
```
-In the example above, a fact table for user information and access behavior is
defined, where `user_id`, `load_date`, `city`, and `age` are used as Key
columns for aggregation. During data import, the Key columns are aggregated
into one row, and the Value columns are aggregated according to the specified
aggregation types.
+In the example above, a fact table for user information and access behavior is
defined, where `user_id`, `load_dt`, and `city` are used as Key columns for
aggregation. During data import, the Key columns are aggregated into one row,
and the Value columns are aggregated according to the specified aggregation
types.
The following types of dimension aggregation are supported in the Aggregate
Key Table:
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-model/aggregate.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-model/aggregate.md
index b11b52afd41..82a269a2911 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-model/aggregate.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-model/aggregate.md
@@ -41,7 +41,7 @@ AGGREGATE KEY(user_id, load_dt, city)
DISTRIBUTED BY HASH(user_id) BUCKETS 10;
```
-上例中定义了用户信息和访问行为表，将 `user_id`、`load_date`、`city` 及 `age` 作为 Key 列进行聚合。数据导入时，Key
列会聚合成一行，Value 列会按照指定的聚合类型进行维度聚合。
+上例中定义了用户信息和访问行为表，将 `user_id`、`load_dt` 及 `city` 作为 Key 列进行聚合。数据导入时，Key
列会聚合成一行，Value 列会按照指定的聚合类型进行维度聚合。
在聚合表中支持以下类型的维度聚合：
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-model/unique.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-model/unique.md
index 23c10487364..e832049099d 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-model/unique.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-model/unique.md
@@ -29,7 +29,7 @@
* **写时合并**（merge-on-write）：自 1.2 版本起，Doris 默认使用写时合并模式，数据在写入时立即合并相同 Key
的记录，确保存储的始终是最新数据。写时合并兼顾查询和写入性能，避免多个版本的数据合并，并支持谓词下推到存储层。大多数场景推荐使用此模式；
-* **读时合并**（merge-on-read）：在 1.2 版本前，Doris
中的主键模型默认使用读时合并模式，数据在写入时并不进行合并，以增量的方式被追加存储，在 Doris 内保留多个版本。查询或 Compaction
时，会对数据进行相同 Key 的版本合并。读时合并适合写多读少的场景，在查询是需要进行多个版本合并，谓词无法下推，可能会影响到查询速度。
+* **读时合并**（merge-on-read）：在 1.2 版本前，Doris
中的主键模型默认使用读时合并模式，数据在写入时并不进行合并，以增量的方式被追加存储，在 Doris 内保留多个版本。查询或 Compaction
时，会对数据进行相同 Key 的版本合并。读时合并适合写多读少的场景，在查询时需要进行多个版本合并，谓词无法下推，可能会影响到查询速度。
在 Doris 中基于主键模型更新有两种语义：
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/data-model/aggregate.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/data-model/aggregate.md
index fb1d1104494..573faeb5d59 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/data-model/aggregate.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/data-model/aggregate.md
@@ -41,7 +41,7 @@ AGGREGATE KEY(user_id, load_dt, city)
DISTRIBUTED BY HASH(user_id) BUCKETS 10;
```
-上例中定义了用户信息和访问行为表，将 `user_id`、`load_date`、`city` 及 `age` 作为 Key 列进行聚合。数据导入时，Key
列会聚合成一行，Value 列会按照指定的聚合类型进行维度聚合。
+上例中定义了用户信息和访问行为表，将 `user_id`、`load_dt` 及 `city` 作为 Key 列进行聚合。数据导入时，Key
列会聚合成一行，Value 列会按照指定的聚合类型进行维度聚合。
在聚合表中支持以下类型的维度聚合：
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/data-model/unique.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/data-model/unique.md
index 9f750719107..64588820814 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/data-model/unique.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/data-model/unique.md
@@ -29,7 +29,7 @@
* **写时合并**（merge-on-write）：自 1.2 版本起，Doris 默认使用写时合并模式，数据在写入时立即合并相同 Key
的记录，确保存储的始终是最新数据。写时合并兼顾查询和写入性能，避免多个版本的数据合并，并支持谓词下推到存储层。大多数场景推荐使用此模式；
-* **读时合并**（merge-on-read）：在 1.2 版本前，Doris
中的主键模型默认使用读时合并模式，数据在写入时并不进行合并，以增量的方式被追加存储，在 Doris 内保留多个版本。查询或 Compaction
时，会对数据进行相同 Key 的版本合并。读时合并适合写多读少的场景，在查询是需要进行多个版本合并，谓词无法下推，可能会影响到查询速度。
+* **读时合并**（merge-on-read）：在 1.2 版本前，Doris
中的主键模型默认使用读时合并模式，数据在写入时并不进行合并，以增量的方式被追加存储，在 Doris 内保留多个版本。查询或 Compaction
时，会对数据进行相同 Key 的版本合并。读时合并适合写多读少的场景，在查询时需要进行多个版本合并，谓词无法下推，可能会影响到查询速度。
在 Doris 中基于主键模型更新有两种语义：
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/data-model/aggregate.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/data-model/aggregate.md
index 80cf661e3fd..f0bf44f9992 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/data-model/aggregate.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/data-model/aggregate.md
@@ -42,7 +42,7 @@ DISTRIBUTED BY HASH(user_id) BUCKETS 10;
```
-上例中定义了用户信息和访问的行为事实表，将 `user_id`、`load_dt`、`city`作为 Key 列进行聚合操作。数据导入时，Key
列会聚合成一行，Value 列会按照指定的聚合类型进行维度聚合。
+上例中定义了用户信息和访问的行为事实表，将 `user_id`、`load_dt` 及 `city` 作为 Key 列进行聚合操作。数据导入时，Key
列会聚合成一行，Value 列会按照指定的聚合类型进行维度聚合。
在聚合表中支持以下类型的维度聚合：
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/data-model/unique.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/data-model/unique.md
index 0d84e5bca16..806a20fd2c0 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/data-model/unique.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/data-model/unique.md
@@ -29,7 +29,7 @@
* **写时合并**（merge-on-write）：自 1.2 版本起，Doris 默认使用写时合并模式，数据在写入时立即合并相同 Key
的记录，确保存储的始终是最新数据。写时合并兼顾查询和写入性能，避免多个版本的数据合并，并支持谓词下推到存储层。大多数场景推荐使用此模式；
-* **读时合并**（merge-on-read）：在 1.2 版本前，Doris
中的主键表默认使用读时合并模式，数据在写入时并不进行合并，以增量的方式被追加存储，在 Doris 内保留多个版本。查询或 Compaction
时，会对数据进行相同 Key 的版本合并。读时合并适合写多读少的场景，在查询是需要进行多个版本合并，谓词无法下推，可能会影响到查询速度。
+* **读时合并**（merge-on-read）：在 1.2 版本前，Doris
中的主键表默认使用读时合并模式，数据在写入时并不进行合并，以增量的方式被追加存储，在 Doris 内保留多个版本。查询或 Compaction
时，会对数据进行相同 Key 的版本合并。读时合并适合写多读少的场景，在查询时需要进行多个版本合并，谓词无法下推，可能会影响到查询速度。
在 Doris 中基于主键表更新有两种语义：
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-model/aggregate.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-model/aggregate.md
index b11b52afd41..82a269a2911 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-model/aggregate.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-model/aggregate.md
@@ -41,7 +41,7 @@ AGGREGATE KEY(user_id, load_dt, city)
DISTRIBUTED BY HASH(user_id) BUCKETS 10;
```
-上例中定义了用户信息和访问行为表，将 `user_id`、`load_date`、`city` 及 `age` 作为 Key 列进行聚合。数据导入时，Key
列会聚合成一行，Value 列会按照指定的聚合类型进行维度聚合。
+上例中定义了用户信息和访问行为表，将 `user_id`、`load_dt` 及 `city` 作为 Key 列进行聚合。数据导入时，Key
列会聚合成一行，Value 列会按照指定的聚合类型进行维度聚合。
在聚合表中支持以下类型的维度聚合：
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-model/unique.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-model/unique.md
index 23c10487364..e832049099d 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-model/unique.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-model/unique.md
@@ -29,7 +29,7 @@
* **写时合并**（merge-on-write）：自 1.2 版本起，Doris 默认使用写时合并模式，数据在写入时立即合并相同 Key
的记录，确保存储的始终是最新数据。写时合并兼顾查询和写入性能，避免多个版本的数据合并，并支持谓词下推到存储层。大多数场景推荐使用此模式；
-* **读时合并**（merge-on-read）：在 1.2 版本前，Doris
中的主键模型默认使用读时合并模式，数据在写入时并不进行合并，以增量的方式被追加存储，在 Doris 内保留多个版本。查询或 Compaction
时，会对数据进行相同 Key 的版本合并。读时合并适合写多读少的场景，在查询是需要进行多个版本合并，谓词无法下推，可能会影响到查询速度。
+* **读时合并**（merge-on-read）：在 1.2 版本前，Doris
中的主键模型默认使用读时合并模式，数据在写入时并不进行合并，以增量的方式被追加存储，在 Doris 内保留多个版本。查询或 Compaction
时，会对数据进行相同 Key 的版本合并。读时合并适合写多读少的场景，在查询时需要进行多个版本合并，谓词无法下推，可能会影响到查询速度。
在 Doris 中基于主键模型更新有两种语义：
diff --git a/versioned_docs/version-2.0/table-design/data-model/aggregate.md
b/versioned_docs/version-2.0/table-design/data-model/aggregate.md
index 2f3f68e0671..f3192f17523 100644
--- a/versioned_docs/version-2.0/table-design/data-model/aggregate.md
+++ b/versioned_docs/version-2.0/table-design/data-model/aggregate.md
@@ -54,7 +54,7 @@ AGGREGATE KEY(user_id, load_dt, city)
DISTRIBUTED BY HASH(user_id) BUCKETS 10;
```
-In the example above, a fact table for user information and access behavior is
defined, where `user_id`, `load_date`, `city`, and `age` are used as Key
columns for aggregation. During data import, the Key columns are aggregated
into one row, and the Value columns are aggregated according to the specified
aggregation types.
+In the example above, a fact table for user information and access behavior is
defined, where `user_id`, `load_dt`, and `city` are used as Key columns for
aggregation. During data import, the Key columns are aggregated into one row,
and the Value columns are aggregated according to the specified aggregation
types.
The following types of dimension aggregation are supported in the Aggregate
Key Model:
diff --git a/versioned_docs/version-2.1/table-design/data-model/aggregate.md
b/versioned_docs/version-2.1/table-design/data-model/aggregate.md
index d2bd91e7463..aa07ed97de7 100644
--- a/versioned_docs/version-2.1/table-design/data-model/aggregate.md
+++ b/versioned_docs/version-2.1/table-design/data-model/aggregate.md
@@ -54,7 +54,7 @@ AGGREGATE KEY(user_id, load_dt, city)
DISTRIBUTED BY HASH(user_id) BUCKETS 10;
```
-In the example above, a fact table for user information and access behavior is
defined, where `user_id`, `load_date`, `city`, and `age` are used as Key
columns for aggregation. During data import, the Key columns are aggregated
into one row, and the Value columns are aggregated according to the specified
aggregation types.
+In the example above, a fact table for user information and access behavior is
defined, where `user_id`, `load_dt`, and `city` are used as Key columns for
aggregation. During data import, the Key columns are aggregated into one row,
and the Value columns are aggregated according to the specified aggregation
types.
The following types of dimension aggregation are supported in the Aggregate
Key Model:
diff --git a/versioned_docs/version-3.x/table-design/data-model/aggregate.md
b/versioned_docs/version-3.x/table-design/data-model/aggregate.md
index 49facbe6b90..cb62bc02df5 100644
--- a/versioned_docs/version-3.x/table-design/data-model/aggregate.md
+++ b/versioned_docs/version-3.x/table-design/data-model/aggregate.md
@@ -54,7 +54,7 @@ AGGREGATE KEY(user_id, load_dt, city)
DISTRIBUTED BY HASH(user_id) BUCKETS 10;
```
-In the example above, a fact table for user information and access behavior is
defined, where `user_id`, `load_date`, `city`, and `age` are used as Key
columns for aggregation. During data import, the Key columns are aggregated
into one row, and the Value columns are aggregated according to the specified
aggregation types.
+In the example above, a fact table for user information and access behavior is
defined, where `user_id`, `load_dt`, and `city` are used as Key columns for
aggregation. During data import, the Key columns are aggregated into one row,
and the Value columns are aggregated according to the specified aggregation
types.
The following types of dimension aggregation are supported in the Aggregate
Key Table:
diff --git a/versioned_docs/version-4.x/table-design/data-model/aggregate.md
b/versioned_docs/version-4.x/table-design/data-model/aggregate.md
index f38a58ce552..7552f825d44 100644
--- a/versioned_docs/version-4.x/table-design/data-model/aggregate.md
+++ b/versioned_docs/version-4.x/table-design/data-model/aggregate.md
@@ -54,7 +54,7 @@ AGGREGATE KEY(user_id, load_dt, city)
DISTRIBUTED BY HASH(user_id) BUCKETS 10;
```
-In the example above, a fact table for user information and access behavior is
defined, where `user_id`, `load_date`, `city`, and `age` are used as Key
columns for aggregation. During data import, the Key columns are aggregated
into one row, and the Value columns are aggregated according to the specified
aggregation types.
+In the example above, a fact table for user information and access behavior is
defined, where `user_id`, `load_dt`, and `city` are used as Key columns for
aggregation. During data import, the Key columns are aggregated into one row,
and the Value columns are aggregated according to the specified aggregation
types.
The following types of dimension aggregation are supported in the Aggregate
Key Table:
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
