This is an automated email from the ASF dual-hosted git repository.
kassiez 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 3f56868e115 [doc] Enhanced unique-update-concurrent (#2178)
3f56868e115 is described below
commit 3f56868e115f6786183c50f33014e8219ffdc07f
Author: mklzl <36362816+mk...@users.noreply.github.com>
AuthorDate: Wed Apr 23 19:45:54 2025 +0800
[doc] Enhanced unique-update-concurrent (#2178)
## Versions
- [x] dev
- [x] 3.0
- [x] 2.1
- [ ] 2.0
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [ ] Checked by AI
- [ ] Test Cases Built
---
docs/data-operate/update/unique-update-concurrent-control.md | 10 ++++++++--
.../data-operate/update/unique-update-concurrent-control.md | 10 ++++++++--
.../data-operate/update/unique-update-concurrent-control.md | 10 ++++++++--
.../data-operate/update/unique-update-concurrent-control.md | 9 +++++++--
.../data-operate/update/unique-update-concurrent-control.md | 10 ++++++++--
.../data-operate/update/unique-update-concurrent-control.md | 10 ++++++++--
6 files changed, 47 insertions(+), 12 deletions(-)
diff --git a/docs/data-operate/update/unique-update-concurrent-control.md
b/docs/data-operate/update/unique-update-concurrent-control.md
index 781535794e9..d6df6414ef8 100644
--- a/docs/data-operate/update/unique-update-concurrent-control.md
+++ b/docs/data-operate/update/unique-update-concurrent-control.md
@@ -258,6 +258,12 @@ This time, the data in the table is replaced. In summary,
during the load proces
Table test_tbl has sequence column, need to specify the sequence column
```
-2. Since version 2.0, Doris supports partial column update capability for
Unique Key tables with Merge-on-Write implementation. In partial column update
loads, users can update only a portion of the columns each time, so it is not
necessary to include the sequence column. If the load task submitted by the
user includes the sequence column, the behavior is unaffected; if the load task
does not include the sequence column, Doris will use the sequence column from
the matching historical dat [...]
+2. When you use the Insert statement to insert data, you must display the
specified sequence column; otherwise, the preceding exception is reported. In
order to facilitate the use of Doris in some scenarios (table replication,
internal data migration, etc.), Doris can be controlled by the session
parameter to close the check constraint on the sequence column:
-3. During concurrent loads, Doris uses the MVCC mechanism to ensure data
correctness. If two batches of data loads update different columns of the same
key, the load task with the higher system version will use the data row written
by the lower version load task to fill in the same key after the lower version
load task succeeds.
+```sql
+set require_sequence_in_insert = false;
+```
+
+3. Since version 2.0, Doris supports partial column update capability for
Unique Key tables with Merge-on-Write implementation. In partial column update
loads, users can update only a portion of the columns each time, so it is not
necessary to include the sequence column. If the load task submitted by the
user includes the sequence column, the behavior is unaffected; if the load task
does not include the sequence column, Doris will use the sequence column from
the matching historical dat [...]
+
+4. During concurrent loads, Doris uses the MVCC mechanism to ensure data
correctness. If two batches of data loads update different columns of the same
key, the load task with the higher system version will use the data row written
by the lower version load task to fill in the same key after the lower version
load task succeeds.
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/update/unique-update-concurrent-control.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/update/unique-update-concurrent-control.md
index a087d512cfa..d4a87d64cf0 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/update/unique-update-concurrent-control.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/update/unique-update-concurrent-control.md
@@ -258,6 +258,12 @@ MySQL [test]> select * from test_table;
Table test_tbl has sequence column, need to specify the sequence column
```
-2. 自版本 2.0 起，Doris 对 Unique Key 表的 Merge-on-Write
实现支持了部分列更新能力，在部分列更新导入中，用户每次可以只更新一部分列，因此并不是必须要包含 sequence 列。若用户提交的导入任务中，包含
sequence 列，则行为无影响；若用户提交的导入任务不包含 sequence 列，Doris 会使用匹配的历史数据中的 sequence
列作为更新后该行的 sequence 列的值。如果历史数据中不存在相同 key 的列，则会自动用 null 或默认值填充。
+2. 在使用 Insert 语句插入数据时，由于用户必须显示指定 sequence
列，否则会报如上异常。为了方便用户在一些场景下（表复制，内部数据迁移等场景）使用，Doris 可以通过 session 参数控制，来关闭 sequence
列的检查约束：
-3. 当出现并发导入时，Doris 会利用 MVCC 机制来保证数据的正确性。如果两批数据导入都更新了一个相同 key
的不同列，则其中系统版本较高的导入任务会在版本较低的导入任务成功后，使用版本较低的导入任务写入的相同 key 的数据行重新进行补齐。
+```sql
+set require_sequence_in_insert = false;
+```
+
+3. 自版本 2.0 起，Doris 对 Unique Key 表的 Merge-on-Write
实现支持了部分列更新能力，在部分列更新导入中，用户每次可以只更新一部分列，因此并不是必须要包含 sequence 列。若用户提交的导入任务中，包含
sequence 列，则行为无影响；若用户提交的导入任务不包含 sequence 列，Doris 会使用匹配的历史数据中的 sequence
列作为更新后该行的 sequence 列的值。如果历史数据中不存在相同 key 的列，则会自动用 null 或默认值填充。
+
+4. 当出现并发导入时，Doris 会利用 MVCC 机制来保证数据的正确性。如果两批数据导入都更新了一个相同 key
的不同列，则其中系统版本较高的导入任务会在版本较低的导入任务成功后，使用版本较低的导入任务写入的相同 key 的数据行重新进行补齐。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/update/unique-update-concurrent-control.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/update/unique-update-concurrent-control.md
index a087d512cfa..d4a87d64cf0 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/update/unique-update-concurrent-control.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/update/unique-update-concurrent-control.md
@@ -258,6 +258,12 @@ MySQL [test]> select * from test_table;
Table test_tbl has sequence column, need to specify the sequence column
```
-2. 自版本 2.0 起，Doris 对 Unique Key 表的 Merge-on-Write
实现支持了部分列更新能力，在部分列更新导入中，用户每次可以只更新一部分列，因此并不是必须要包含 sequence 列。若用户提交的导入任务中，包含
sequence 列，则行为无影响；若用户提交的导入任务不包含 sequence 列，Doris 会使用匹配的历史数据中的 sequence
列作为更新后该行的 sequence 列的值。如果历史数据中不存在相同 key 的列，则会自动用 null 或默认值填充。
+2. 在使用 Insert 语句插入数据时，由于用户必须显示指定 sequence
列，否则会报如上异常。为了方便用户在一些场景下（表复制，内部数据迁移等场景）使用，Doris 可以通过 session 参数控制，来关闭 sequence
列的检查约束：
-3. 当出现并发导入时，Doris 会利用 MVCC 机制来保证数据的正确性。如果两批数据导入都更新了一个相同 key
的不同列，则其中系统版本较高的导入任务会在版本较低的导入任务成功后，使用版本较低的导入任务写入的相同 key 的数据行重新进行补齐。
+```sql
+set require_sequence_in_insert = false;
+```
+
+3. 自版本 2.0 起，Doris 对 Unique Key 表的 Merge-on-Write
实现支持了部分列更新能力，在部分列更新导入中，用户每次可以只更新一部分列，因此并不是必须要包含 sequence 列。若用户提交的导入任务中，包含
sequence 列，则行为无影响；若用户提交的导入任务不包含 sequence 列，Doris 会使用匹配的历史数据中的 sequence
列作为更新后该行的 sequence 列的值。如果历史数据中不存在相同 key 的列，则会自动用 null 或默认值填充。
+
+4. 当出现并发导入时，Doris 会利用 MVCC 机制来保证数据的正确性。如果两批数据导入都更新了一个相同 key
的不同列，则其中系统版本较高的导入任务会在版本较低的导入任务成功后，使用版本较低的导入任务写入的相同 key 的数据行重新进行补齐。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/update/unique-update-concurrent-control.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/update/unique-update-concurrent-control.md
index a087d512cfa..49bb4d84e5e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/update/unique-update-concurrent-control.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/update/unique-update-concurrent-control.md
@@ -257,7 +257,12 @@ MySQL [test]> select * from test_table;
```Plain
Table test_tbl has sequence column, need to specify the sequence column
```
+2. 在使用 Insert 语句插入数据时，由于用户必须显示指定 sequence
列，否则会报如上异常。为了方便用户在一些场景下（表复制，内部数据迁移等场景）使用，Doris 可以通过 session 参数控制，来关闭 sequence
列的检查约束：
-2. 自版本 2.0 起，Doris 对 Unique Key 表的 Merge-on-Write
实现支持了部分列更新能力，在部分列更新导入中，用户每次可以只更新一部分列，因此并不是必须要包含 sequence 列。若用户提交的导入任务中，包含
sequence 列，则行为无影响；若用户提交的导入任务不包含 sequence 列，Doris 会使用匹配的历史数据中的 sequence
列作为更新后该行的 sequence 列的值。如果历史数据中不存在相同 key 的列，则会自动用 null 或默认值填充。
+```sql
+set require_sequence_in_insert = false;
+```
+
+3. 自版本 2.0 起，Doris 对 Unique Key 表的 Merge-on-Write
实现支持了部分列更新能力，在部分列更新导入中，用户每次可以只更新一部分列，因此并不是必须要包含 sequence 列。若用户提交的导入任务中，包含
sequence 列，则行为无影响；若用户提交的导入任务不包含 sequence 列，Doris 会使用匹配的历史数据中的 sequence
列作为更新后该行的 sequence 列的值。如果历史数据中不存在相同 key 的列，则会自动用 null 或默认值填充。
-3. 当出现并发导入时，Doris 会利用 MVCC 机制来保证数据的正确性。如果两批数据导入都更新了一个相同 key
的不同列，则其中系统版本较高的导入任务会在版本较低的导入任务成功后，使用版本较低的导入任务写入的相同 key 的数据行重新进行补齐。
+4. 当出现并发导入时，Doris 会利用 MVCC 机制来保证数据的正确性。如果两批数据导入都更新了一个相同 key
的不同列，则其中系统版本较高的导入任务会在版本较低的导入任务成功后，使用版本较低的导入任务写入的相同 key 的数据行重新进行补齐。
diff --git
a/versioned_docs/version-2.1/data-operate/update/unique-update-concurrent-control.md
b/versioned_docs/version-2.1/data-operate/update/unique-update-concurrent-control.md
index 781535794e9..d6df6414ef8 100644
---
a/versioned_docs/version-2.1/data-operate/update/unique-update-concurrent-control.md
+++
b/versioned_docs/version-2.1/data-operate/update/unique-update-concurrent-control.md
@@ -258,6 +258,12 @@ This time, the data in the table is replaced. In summary,
during the load proces
Table test_tbl has sequence column, need to specify the sequence column
```
-2. Since version 2.0, Doris supports partial column update capability for
Unique Key tables with Merge-on-Write implementation. In partial column update
loads, users can update only a portion of the columns each time, so it is not
necessary to include the sequence column. If the load task submitted by the
user includes the sequence column, the behavior is unaffected; if the load task
does not include the sequence column, Doris will use the sequence column from
the matching historical dat [...]
+2. When you use the Insert statement to insert data, you must display the
specified sequence column; otherwise, the preceding exception is reported. In
order to facilitate the use of Doris in some scenarios (table replication,
internal data migration, etc.), Doris can be controlled by the session
parameter to close the check constraint on the sequence column:
-3. During concurrent loads, Doris uses the MVCC mechanism to ensure data
correctness. If two batches of data loads update different columns of the same
key, the load task with the higher system version will use the data row written
by the lower version load task to fill in the same key after the lower version
load task succeeds.
+```sql
+set require_sequence_in_insert = false;
+```
+
+3. Since version 2.0, Doris supports partial column update capability for
Unique Key tables with Merge-on-Write implementation. In partial column update
loads, users can update only a portion of the columns each time, so it is not
necessary to include the sequence column. If the load task submitted by the
user includes the sequence column, the behavior is unaffected; if the load task
does not include the sequence column, Doris will use the sequence column from
the matching historical dat [...]
+
+4. During concurrent loads, Doris uses the MVCC mechanism to ensure data
correctness. If two batches of data loads update different columns of the same
key, the load task with the higher system version will use the data row written
by the lower version load task to fill in the same key after the lower version
load task succeeds.
diff --git
a/versioned_docs/version-3.0/data-operate/update/unique-update-concurrent-control.md
b/versioned_docs/version-3.0/data-operate/update/unique-update-concurrent-control.md
index 781535794e9..d6df6414ef8 100644
---
a/versioned_docs/version-3.0/data-operate/update/unique-update-concurrent-control.md
+++
b/versioned_docs/version-3.0/data-operate/update/unique-update-concurrent-control.md
@@ -258,6 +258,12 @@ This time, the data in the table is replaced. In summary,
during the load proces
Table test_tbl has sequence column, need to specify the sequence column
```
-2. Since version 2.0, Doris supports partial column update capability for
Unique Key tables with Merge-on-Write implementation. In partial column update
loads, users can update only a portion of the columns each time, so it is not
necessary to include the sequence column. If the load task submitted by the
user includes the sequence column, the behavior is unaffected; if the load task
does not include the sequence column, Doris will use the sequence column from
the matching historical dat [...]
+2. When you use the Insert statement to insert data, you must display the
specified sequence column; otherwise, the preceding exception is reported. In
order to facilitate the use of Doris in some scenarios (table replication,
internal data migration, etc.), Doris can be controlled by the session
parameter to close the check constraint on the sequence column:
-3. During concurrent loads, Doris uses the MVCC mechanism to ensure data
correctness. If two batches of data loads update different columns of the same
key, the load task with the higher system version will use the data row written
by the lower version load task to fill in the same key after the lower version
load task succeeds.
+```sql
+set require_sequence_in_insert = false;
+```
+
+3. Since version 2.0, Doris supports partial column update capability for
Unique Key tables with Merge-on-Write implementation. In partial column update
loads, users can update only a portion of the columns each time, so it is not
necessary to include the sequence column. If the load task submitted by the
user includes the sequence column, the behavior is unaffected; if the load task
does not include the sequence column, Doris will use the sequence column from
the matching historical dat [...]
+
+4. During concurrent loads, Doris uses the MVCC mechanism to ensure data
correctness. If two batches of data loads update different columns of the same
key, the load task with the higher system version will use the data row written
by the lower version load task to fill in the same key after the lower version
load task succeeds.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
