This is an automated email from the ASF dual-hosted git repository.
jiafengzheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new 3fb3ade87c7 table_model_key_colume (#91)
3fb3ade87c7 is described below
commit 3fb3ade87c75d41e5c969ae0222d2368bc48de3a
Author: catpineapple <[email protected]>
AuthorDate: Fri Sep 9 18:40:12 2022 +0800
table_model_key_colume (#91)
table_model_key_colume
---
docs/data-table/data-model.md | 3 +++
.../docusaurus-plugin-content-docs/current/data-table/data-model.md | 3 +++
2 files changed, 6 insertions(+)
diff --git a/docs/data-table/data-model.md b/docs/data-table/data-model.md
index 9694c52cfb8..d27e6f6bce8 100644
--- a/docs/data-table/data-model.md
+++ b/docs/data-table/data-model.md
@@ -444,6 +444,9 @@ Another way is to **change the aggregation type of the
count column above to REP
Duplicate model has no limitation of aggregation model. Because the model does
not involve aggregate semantics, when doing count (*) query, we can get the
correct semantics by choosing a column of queries arbitrarily.
+### Key Columns
+For the Duplicate,Aggregate and Unique models,The key columns will be given
when the table created, but it is actually different: For the Duplicate model,
the key columns of the table can be regarded as just "sort columns", not an
unique identifier. In aggregate type tables such as Aggregate and Unique
models, the key columns are both "sort columns" and "unique identification
columns", which were the real "key columns".
+
## Suggestions for Choosing Data Model
Because the data model was established when the table was built, and **could
not be modified. Therefore, it is very important to select an appropriate data
model**.
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-table/data-model.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-table/data-model.md
index 87e83628930..3242fe9b78a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-table/data-model.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-table/data-model.md
@@ -453,6 +453,9 @@ SELECT COUNT(*) FROM table;
Duplicate 模型没有聚合模型的这个局限性。因为该模型不涉及聚合语意，在做 count(*) 查询时，任意选择一列查询，即可得到语意正确的结果。
+### key 列
+Duplicate、Aggregate、Unique 模型，都会在建表指定 key 列，然而实际上是有所区别的：对于 Duplicate
模型，表的key列，可以认为只是 “排序列”，并非起到唯一标识的作用。而 Aggregate、Unique 模型这种聚合类型的表，key 列是兼顾 “排序列”
和 “唯一标识列”，是真正意义上的“ key 列”。
+
## 数据模型的选择建议
因为数据模型在建表时就已经确定，且**无法修改**。所以，选择一个合适的数据模型**非常重要**。
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
