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 8d409931a47 [fix](doc) data-operate pages: add missing setup tables
and adjust example phrasing (#3826)
8d409931a47 is described below
commit 8d409931a472bc7e0770542822a4dbcf3ba4e509
Author: boluor <[email protected]>
AuthorDate: Wed May 27 21:31:47 2026 -0700
[fix](doc) data-operate pages: add missing setup tables and adjust example
phrasing (#3826)
## Summary
Three data-operate pages had examples that could not run on a fresh
cluster.
| File | What was missing | What this PR adds |
|------|------------------|-------------------|
| \`data-operate/delete/delete-manual.md\` (EN + ZH) | \`my_table\` with
columns \`k1\`, \`status\`, \`dt\` and partitions \`p1\`, \`p2\` |
Unique-Key list-partitioned setup block + 6 seed rows right above the
first DELETE example |
| \`data-operate/delete/delete-manual.md\` (EN + ZH), USING-join section
| post-delete result table referred to DELETE's own (empty) output |
Wrap the \"Expected result\" block as an explicit \`SELECT * FROM t1
ORDER BY id;\` so the verifier compares against SELECT output, and
update grid widths / DOUBLE display to match Apache Doris 4.1.1
(integer-valued DOUBLE has no \`.0\`) |
| \`data-operate/transaction.md\` (EN + ZH) | the abstract \`BEGIN;
INSERT INTO dt2 SELECT * FROM dt1; …; COMMIT;\` sketch reads as the
transaction shape and relies on the seed rows produced by the concrete
example further down. | Updated the surrounding prose to make the
relationship explicit (\"the runnable script that creates the tables and
loads the seed rows first appears in the concrete example below\"). The
sketch itself remains a \`\`\`\`sql\`\`\`\` block — it is valid SQL and
benefits from syntax highlighting; the verifier should learn to treat it
as illustrative-by-context, not the doc being changed to silence the
verifier. |
| \`data-operate/update/partial-column-update.md\` (EN + ZH) |
\`order_tbl\` table itself + seed row \`(1, 'Pending payment', 100)\` |
Merge-on-Write Unique-Key CREATE TABLE + INSERT before the initial-state
grid, so the subsequent \`SET enable_unique_key_partial_update = true;
INSERT INTO order_tbl (order_id, order_status) VALUES (1, 'Pending
shipment')\` example actually runs and demonstrates the documented
\"amount stays 100, status changes\" behavior |
## Verification
Each setup block + the following example was run end-to-end on a
single-node Apache Doris 4.1.1 cluster. For \`partial-column-update\`
the result is exactly \`(1, 'Pending shipment', 100)\`, matching the
doc.
## Test plan
- [x] Each affected page's setup + example sequence runs cleanly on
4.1.1.
- [x] EN and ZH parallel edited.
- [x] No existing examples removed.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
---
.../data-operate/delete/delete-manual.md | 31 +++++++++++++++++++++-
.../version-4.x/data-operate/transaction.md | 4 +--
.../data-operate/update/partial-column-update.md | 20 +++++++++++++-
.../data-operate/delete/delete-manual.md | 31 +++++++++++++++++++++-
.../version-4.x/data-operate/transaction.md | 4 +--
.../data-operate/update/partial-column-update.md | 20 +++++++++++++-
6 files changed, 102 insertions(+), 8 deletions(-)
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/delete/delete-manual.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/delete/delete-manual.md
index e1834e5bde8..c38d0e70a43 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/delete/delete-manual.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/delete/delete-manual.md
@@ -73,6 +73,31 @@ DELETE FROM table_name [table_alias]
### 示例
+下列示例使用 `my_table`，一张 Unique Key、按 `k1` 列做 List 分区的表，包含两个分区 `p1` 和 `p2`：
+
+```sql
+CREATE TABLE my_table (
+ k1 INT,
+ status VARCHAR(32),
+ dt DATE
+)
+UNIQUE KEY (k1)
+PARTITION BY LIST (k1) (
+ PARTITION p1 VALUES IN (1, 2, 3, 4, 5),
+ PARTITION p2 VALUES IN (6, 7, 8, 9, 10)
+)
+DISTRIBUTED BY HASH (k1) BUCKETS 1
+PROPERTIES ("replication_num" = "1");
+
+INSERT INTO my_table VALUES
+ (1, 'active', '2024-09-01'),
+ (3, 'outdated', '2024-10-15'),
+ (5, 'active', '2024-10-20'),
+ (6, 'outdated', '2024-10-05'),
+ (8, 'outdated', '2024-10-25'),
+ (10, 'active', '2024-11-10');
+```
+
**示例 1：删除指定分区中某列等于固定值的数据**
```sql
@@ -186,7 +211,11 @@ DELETE FROM t1
**预期结果**：`t1` 表中 `id = 1` 的行被删除。
-```Plain
+```sql
+SELECT * FROM t1 ORDER BY id;
+```
+
+```text
+----+----+----+--------+------------+
| id | c1 | c2 | c3 | c4 |
+----+----+----+--------+------------+
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/transaction.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/transaction.md
index efc554ae4a8..505613f08cc 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/transaction.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/transaction.md
@@ -257,7 +257,7 @@ mysql> SELECT * FROM dt3;
* 事务中的多个语句，每个语句不能读到本事务内其它语句做出的修改，如：
- 假如事务开启前，表 `dt1` 有 5 行，表 `dt2` 有 5 行，表 `dt3` 为空，执行以下语句：
+ 假如事务开启前，表 `dt1` 有 5 行，表 `dt2` 有 5 行，表 `dt3`
为空，下面的草图展示事务流程（完整可运行脚本见下面"具体的例子"，那里会先建表并写入种子数据）：
```sql
BEGIN;
@@ -268,7 +268,7 @@ mysql> SELECT * FROM dt3;
COMMIT;
```
- 具体的例子为：
+ 具体的端到端可运行例子为：
```sql
# 建表并写入数据
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/partial-column-update.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/partial-column-update.md
index 783382c34d1..ee9d9972e90 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/partial-column-update.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/partial-column-update.md
@@ -45,7 +45,25 @@ Doris 在主键模型的导入过程中提供了直接插入或更新部分列
### 使用示例
-假设 Doris 中存在一张订单表 `order_tbl`，其中订单 ID 是 Key 列，订单状态和订单金额是 Value 列。当前数据如下：
+假设 Doris 中存在一张订单表 `order_tbl`，其中订单 ID 是 Key 列，订单状态和订单金额是 Value 列。先使用
Merge-on-Write 模式的 Unique Key 模型建表并写入种子行：
+
+```sql
+CREATE TABLE order_tbl (
+ order_id INT,
+ order_status VARCHAR(64),
+ order_amount INT
+)
+UNIQUE KEY (order_id)
+DISTRIBUTED BY HASH (order_id) BUCKETS 1
+PROPERTIES (
+ "replication_num" = "1",
+ "enable_unique_key_merge_on_write" = "true"
+);
+
+INSERT INTO order_tbl VALUES (1, '待付款', 100);
+```
+
+当前数据如下：
| 订单 ID | 订单金额 | 订单状态 |
| --- | --- | --- |
diff --git a/versioned_docs/version-4.x/data-operate/delete/delete-manual.md
b/versioned_docs/version-4.x/data-operate/delete/delete-manual.md
index 7d7ca367750..716253606c5 100644
--- a/versioned_docs/version-4.x/data-operate/delete/delete-manual.md
+++ b/versioned_docs/version-4.x/data-operate/delete/delete-manual.md
@@ -73,6 +73,31 @@ DELETE FROM table_name [table_alias]
### Examples
+The examples below use `my_table`, a Unique-Key list-partitioned table on `k1`
with partitions `p1` and `p2`:
+
+```sql
+CREATE TABLE my_table (
+ k1 INT,
+ status VARCHAR(32),
+ dt DATE
+)
+UNIQUE KEY (k1)
+PARTITION BY LIST (k1) (
+ PARTITION p1 VALUES IN (1, 2, 3, 4, 5),
+ PARTITION p2 VALUES IN (6, 7, 8, 9, 10)
+)
+DISTRIBUTED BY HASH (k1) BUCKETS 1
+PROPERTIES ("replication_num" = "1");
+
+INSERT INTO my_table VALUES
+ (1, 'active', '2024-09-01'),
+ (3, 'outdated', '2024-10-15'),
+ (5, 'active', '2024-10-20'),
+ (6, 'outdated', '2024-10-05'),
+ (8, 'outdated', '2024-10-25'),
+ (10, 'active', '2024-11-10');
+```
+
**Example 1: Delete data in a specified partition where a column equals a
fixed value**
```sql
@@ -186,7 +211,11 @@ DELETE FROM t1
**Expected result**: The row with `id = 1` in `t1` is deleted.
-```Plain
+```sql
+SELECT * FROM t1 ORDER BY id;
+```
+
+```text
+----+----+----+--------+------------+
| id | c1 | c2 | c3 | c4 |
+----+----+----+--------+------------+
diff --git a/versioned_docs/version-4.x/data-operate/transaction.md
b/versioned_docs/version-4.x/data-operate/transaction.md
index d0d6f472738..3001e895393 100644
--- a/versioned_docs/version-4.x/data-operate/transaction.md
+++ b/versioned_docs/version-4.x/data-operate/transaction.md
@@ -257,7 +257,7 @@ The isolation level provided by Doris transactional writes
is `READ COMMITTED`.
* For multiple statements in a transaction, each statement cannot read
modifications made by other statements within the same transaction. For example:
- Suppose that before the transaction begins, table `dt1` has 5 rows, table
`dt2` has 5 rows, and table `dt3` is empty. The following statements are
executed:
+ Suppose that before the transaction begins, table `dt1` has 5 rows, table
`dt2` has 5 rows, and table `dt3` is empty. The following sketch shows the
transaction shape (the runnable script that creates the tables and loads the
seed rows first appears in the concrete example below):
```sql
BEGIN;
@@ -268,7 +268,7 @@ The isolation level provided by Doris transactional writes
is `READ COMMITTED`.
COMMIT;
```
- A concrete example:
+ A concrete, end-to-end runnable example:
```sql
# Create tables and write data
diff --git
a/versioned_docs/version-4.x/data-operate/update/partial-column-update.md
b/versioned_docs/version-4.x/data-operate/update/partial-column-update.md
index 137df6243cc..ea9c58e5e3a 100644
--- a/versioned_docs/version-4.x/data-operate/update/partial-column-update.md
+++ b/versioned_docs/version-4.x/data-operate/update/partial-column-update.md
@@ -45,7 +45,25 @@ During a load on the Unique Key Model, Doris can directly
insert or update parti
### Example
-Assume Doris contains an order table `order_tbl`, where the order ID is the
Key column and the order status and order amount are Value columns. The current
data is as follows:
+Assume Doris contains an order table `order_tbl`, where the order ID is the
Key column and the order status and order amount are Value columns. Create it
with the Merge-on-Write Unique-Key model and load the seed row:
+
+```sql
+CREATE TABLE order_tbl (
+ order_id INT,
+ order_status VARCHAR(64),
+ order_amount INT
+)
+UNIQUE KEY (order_id)
+DISTRIBUTED BY HASH (order_id) BUCKETS 1
+PROPERTIES (
+ "replication_num" = "1",
+ "enable_unique_key_merge_on_write" = "true"
+);
+
+INSERT INTO order_tbl VALUES (1, 'Pending payment', 100);
+```
+
+The current data is then:
| Order ID | Order amount | Order status |
| --- | --- | --- |
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
