This is an automated email from the ASF dual-hosted git repository.
dataroaring 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 c7a7df1a0d [doc](unique key) fix reference doc (#1300)
c7a7df1a0d is described below
commit c7a7df1a0d3dbcd011acc52be88da1993ddc00d8
Author: zhannngchen <[email protected]>
AuthorDate: Wed Nov 6 19:28:16 2024 +0800
[doc](unique key) fix reference doc (#1300)
# Versions
- [x] dev
- [x] 3.0
- [x] 2.1
- [ ] 2.0
# Languages
- [x] Chinese
- [x] English
Co-authored-by: Chen Zhang <[email protected]>
---
docs/table-design/data-model/unique.md | 2 +-
.../current/table-design/data-model/unique.md | 2 +-
.../version-2.1/table-design/data-model/unique.md | 2 +-
.../version-3.0/table-design/data-model/unique.md | 2 +-
versioned_docs/version-2.1/table-design/data-model/unique.md | 2 +-
versioned_docs/version-3.0/table-design/data-model/unique.md | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/table-design/data-model/unique.md
b/docs/table-design/data-model/unique.md
index 1ee9737e01..3f9d16345b 100644
--- a/docs/table-design/data-model/unique.md
+++ b/docs/table-design/data-model/unique.md
@@ -36,7 +36,7 @@ The Unique data model provides two implementation methods:
The default update semantics of the Unique model is a **full-row UPSERT**,
which stands for UPDATE OR INSERT. If the key of the row data exists, an update
will be performed; if it does not exist, new data will be inserted. Under the
full-row UPSERT semantics, even if the user uses INSERT INTO to specify partial
columns for writing, Doris will fill the unprovided columns with NULL values or
default values in the Planner.
-If a user wishes to update partial fields, they need to use the merge-on-write
implementation and enable support for partial column updates through specific
parameters. Please refer to the Data Operate/Data Update section for more
details.
+If a user wishes to update partial fields, they need to use the merge-on-write
implementation and enable support for partial column updates through specific
parameters. Please refer to the documentation [partial column
updates](../../data-operate/update/update-of-unique-model) for more details.
Let's look at how to create a Unique model table with merge-on-read and
merge-on-write using a typical user basic information table as an example. This
table does not have aggregation requirements and only needs to ensure the
uniqueness of the primary key (The primary key is user_id + username).
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 045a89fa25..832256b6db 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
@@ -37,7 +37,7 @@ under the License.
- Unique 模型默认的更新语义为**整行`UPSERT`**，即 UPDATE OR INSERT，该行数据的 key
如果存在，则进行更新，如果不存在，则进行新数据插入。在整行`UPSERT`语义下，即使用户使用 insert into 指定部分列进行写入，Doris 也会在
Planner 中将未提供的列使用 NULL 值或者默认值进行填充。
-- 部分列更新。如果用户希望更新部分字段，需要使用写时合并实现，并通过特定的参数来开启部分列更新的支持。请查阅数据操作/数据更新部分。
+-
部分列更新。如果用户希望更新部分字段，需要使用写时合并实现，并通过特定的参数来开启部分列更新的支持。请查阅文档[部分列更新](../../data-operate/update/update-of-unique-model)。
下面以一个典型的用户基础信息表，来看看如何建立读时合并和写时合并的主键模型表。这个表数据没有聚合需求，只需保证主键唯一性。（这里的主键为 user_id +
username）。
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 a15d4c7463..4e34dadc34 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
@@ -37,7 +37,7 @@ under the License.
- Unique 模型默认的更新语义为**整行`UPSERT`**，即 UPDATE OR INSERT，该行数据的 key
如果存在，则进行更新，如果不存在，则进行新数据插入。在整行`UPSERT`语义下，即使用户使用 insert into 指定部分列进行写入，Doris 也会在
Planner 中将未提供的列使用 NULL 值或者默认值进行填充。
-- 部分列更新。如果用户希望更新部分字段，需要使用写时合并实现，并通过特定的参数来开启部分列更新的支持。请查阅数据操作/数据更新部分。
+-
部分列更新。如果用户希望更新部分字段，需要使用写时合并实现，并通过特定的参数来开启部分列更新的支持。请查阅文档[部分列更新](../../data-operate/update/update-of-unique-model)。
下面以一个典型的用户基础信息表，来看看如何建立读时合并和写时合并的主键模型表。这个表数据没有聚合需求，只需保证主键唯一性。（这里的主键为 user_id +
username）。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/table-design/data-model/unique.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/table-design/data-model/unique.md
index a15d4c7463..4e34dadc34 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/table-design/data-model/unique.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/table-design/data-model/unique.md
@@ -37,7 +37,7 @@ under the License.
- Unique 模型默认的更新语义为**整行`UPSERT`**，即 UPDATE OR INSERT，该行数据的 key
如果存在，则进行更新，如果不存在，则进行新数据插入。在整行`UPSERT`语义下，即使用户使用 insert into 指定部分列进行写入，Doris 也会在
Planner 中将未提供的列使用 NULL 值或者默认值进行填充。
-- 部分列更新。如果用户希望更新部分字段，需要使用写时合并实现，并通过特定的参数来开启部分列更新的支持。请查阅数据操作/数据更新部分。
+-
部分列更新。如果用户希望更新部分字段，需要使用写时合并实现，并通过特定的参数来开启部分列更新的支持。请查阅文档[部分列更新](../../data-operate/update/update-of-unique-model)。
下面以一个典型的用户基础信息表，来看看如何建立读时合并和写时合并的主键模型表。这个表数据没有聚合需求，只需保证主键唯一性。（这里的主键为 user_id +
username）。
diff --git a/versioned_docs/version-2.1/table-design/data-model/unique.md
b/versioned_docs/version-2.1/table-design/data-model/unique.md
index 1ee9737e01..3f9d16345b 100644
--- a/versioned_docs/version-2.1/table-design/data-model/unique.md
+++ b/versioned_docs/version-2.1/table-design/data-model/unique.md
@@ -36,7 +36,7 @@ The Unique data model provides two implementation methods:
The default update semantics of the Unique model is a **full-row UPSERT**,
which stands for UPDATE OR INSERT. If the key of the row data exists, an update
will be performed; if it does not exist, new data will be inserted. Under the
full-row UPSERT semantics, even if the user uses INSERT INTO to specify partial
columns for writing, Doris will fill the unprovided columns with NULL values or
default values in the Planner.
-If a user wishes to update partial fields, they need to use the merge-on-write
implementation and enable support for partial column updates through specific
parameters. Please refer to the Data Operate/Data Update section for more
details.
+If a user wishes to update partial fields, they need to use the merge-on-write
implementation and enable support for partial column updates through specific
parameters. Please refer to the documentation [partial column
updates](../../data-operate/update/update-of-unique-model) for more details.
Let's look at how to create a Unique model table with merge-on-read and
merge-on-write using a typical user basic information table as an example. This
table does not have aggregation requirements and only needs to ensure the
uniqueness of the primary key (The primary key is user_id + username).
diff --git a/versioned_docs/version-3.0/table-design/data-model/unique.md
b/versioned_docs/version-3.0/table-design/data-model/unique.md
index 1ee9737e01..3f9d16345b 100644
--- a/versioned_docs/version-3.0/table-design/data-model/unique.md
+++ b/versioned_docs/version-3.0/table-design/data-model/unique.md
@@ -36,7 +36,7 @@ The Unique data model provides two implementation methods:
The default update semantics of the Unique model is a **full-row UPSERT**,
which stands for UPDATE OR INSERT. If the key of the row data exists, an update
will be performed; if it does not exist, new data will be inserted. Under the
full-row UPSERT semantics, even if the user uses INSERT INTO to specify partial
columns for writing, Doris will fill the unprovided columns with NULL values or
default values in the Planner.
-If a user wishes to update partial fields, they need to use the merge-on-write
implementation and enable support for partial column updates through specific
parameters. Please refer to the Data Operate/Data Update section for more
details.
+If a user wishes to update partial fields, they need to use the merge-on-write
implementation and enable support for partial column updates through specific
parameters. Please refer to the documentation [partial column
updates](../../data-operate/update/update-of-unique-model) for more details.
Let's look at how to create a Unique model table with merge-on-read and
merge-on-write using a typical user basic information table as an example. This
table does not have aggregation requirements and only needs to ensure the
uniqueness of the primary key (The primary key is user_id + username).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
