This is an automated email from the ASF dual-hosted git repository.
zhangchen 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 0f232e7154c [Fix](delete) Fix delete without partition docs (#1987)
0f232e7154c is described below
commit 0f232e7154cdf729d802dc06143fe332602d2de6
Author: bobhan1 <bao...@selectdb.com>
AuthorDate: Wed Mar 12 15:38:49 2025 +0800
[Fix](delete) Fix delete without partition docs (#1987)
## Versions
- [x] dev
- [x] 3.0
- [x] 2.1
- [ ] 2.0
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [x] Checked by AI
- [x] Test Cases Built
---
docs/data-operate/delete/delete-manual.md | 2 +-
docs/sql-manual/sql-statements/data-modification/DML/DELETE.md | 2 +-
.../current/data-operate/delete/delete-manual.md | 2 +-
.../current/sql-manual/sql-statements/data-modification/DML/DELETE.md | 2 +-
.../version-2.1/data-operate/delete/delete-manual.md | 2 +-
.../sql-manual/sql-statements/data-modification/DML/DELETE.md | 2 +-
.../version-3.0/data-operate/delete/delete-manual.md | 2 +-
.../sql-manual/sql-statements/data-modification/DML/DELETE.md | 2 +-
versioned_docs/version-2.1/data-operate/delete/delete-manual.md | 2 +-
.../sql-manual/sql-statements/data-modification/DML/DELETE.md | 2 +-
versioned_docs/version-3.0/data-operate/delete/delete-manual.md | 2 +-
.../sql-manual/sql-statements/data-modification/DML/DELETE.md | 2 +-
12 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/docs/data-operate/delete/delete-manual.md
b/docs/data-operate/delete/delete-manual.md
index 0b33a5b8baf..0c707603b83 100644
--- a/docs/data-operate/delete/delete-manual.md
+++ b/docs/data-operate/delete/delete-manual.md
@@ -60,7 +60,7 @@ DELETE FROM table_name [table_alias]
1. The conditions do not include partition columns.
2. The `op` of the partition column is `not in`.
- - When the partitioned table does not specify a partition or cannot infer
the partition from the conditions, the session variable
`delete_without_partition` needs to be set to `true`, and the delete operation
will apply to all partitions.
+ - When the partitioned table is not a Unique table, and it does not specify
a partition or cannot infer the partition from the conditions, the session
variable `delete_without_partition` needs to be set to `true`, and the delete
operation will apply to all partitions.
### Examples
diff --git a/docs/sql-manual/sql-statements/data-modification/DML/DELETE.md
b/docs/sql-manual/sql-statements/data-modification/DML/DELETE.md
index dfa89978495..c10c4e5eb9e 100644
--- a/docs/sql-manual/sql-statements/data-modification/DML/DELETE.md
+++ b/docs/sql-manual/sql-statements/data-modification/DML/DELETE.md
@@ -72,7 +72,7 @@ DELETE FROM table_name
1. Only conditions on the key column can be specified when using AGGREGATE
(UNIQUE) model.
2. When the selected key column does not exist in a rollup, delete cannot be
performed.
3. Wheny you use syntax 1, conditions can only have an "and" relationship. If
you want to achieve an "or" relationship, you need to write the conditions in
two DELETE statements.
-4. In syntax 1, if it is a partitioned table, you can specify a partition. If
not specified, Doris will infer partition from the given conditions. In two
cases, Doris cannot infer the partition from conditions: 1) the conditions do
not contain partition columns; 2) The operator of the partition column is not
in. When a partition table does not specify the partition, or the partition
cannot be inferred from the conditions, the session variable
delete_without_partition needs to be true to [...]
+4. In syntax 1, if it is a partitioned table, you can specify a partition. If
not specified, Doris will infer partition from the given conditions. In two
cases, Doris cannot infer the partition from conditions: 1) the conditions do
not contain partition columns; 2) The operator of the partition column is not
in. When the partitioned table is not a Unique table, and it does not specify
the partition, or the partition cannot be inferred from the conditions, the
session variable delete_with [...]
:::tip Tips
This feature is supported since the Apache Doris 1.2 version
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/delete-manual.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/delete-manual.md
index 1a2688744da..127a27a5bb1 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/delete-manual.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/delete-manual.md
@@ -61,7 +61,7 @@ DELETE FROM table_name [table_alias]
1. 条件中不包含分区列
2. 分区列的 `op` 为 `not in`
- - 当分区表未指定分区，或无法从条件中推断分区时，需要设置会话变量 `delete_without_partition` 为
`true`，此时删除操作会应用到所有分区。
+ - 如果分区表不是 Unique 表，当分区表未指定分区，或无法从条件中推断分区时，需要设置会话变量
`delete_without_partition` 为 `true`，此时删除操作会应用到所有分区。
### 示例
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/data-modification/DML/DELETE.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/data-modification/DML/DELETE.md
index 98ee646b702..c2ddf36bcd3 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/data-modification/DML/DELETE.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/data-modification/DML/DELETE.md
@@ -70,7 +70,7 @@ DELETE FROM table_name [table_alias]
1. 使用聚合类的表模型（AGGREGATE、UNIQUE）只能指定 key 列上的条件。
2. 当选定的 key 列不存在于某个 rollup 中时，无法进行 delete。
3. 语法一中，条件之间只能是“与”的关系。若希望达成“或”的关系，需要将条件分写在两个 DELETE 语句中。
-4. 语法一中，如果为分区表，需要指定分区，如果不指定，doris 会从条件中推断出分区。两种情况下，doris 无法从条件中推断出分区：1)
条件中不包含分区列；2) 分区列的 op 为 not in。当分区表未指定分区，或者无法从条件中推断分区的时候，需要设置会话变量
delete_without_partition 为 true，此时 delete 会应用到所有分区。
+4. 语法一中，如果为分区表，需要指定分区，如果不指定，doris 会从条件中推断出分区。两种情况下，doris 无法从条件中推断出分区：1)
条件中不包含分区列；2) 分区列的 op 为 not in。如果分区表不是 Unique
表，当分区表未指定分区，或者无法从条件中推断分区的时候，需要设置会话变量 delete_without_partition 为 true，此时 delete
会应用到所有分区。
5. 该语句可能会降低执行后一段时间内的查询效率。影响程度取决于语句中指定的删除条件的数量。指定的条件越多，影响越大。
## 示例
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/delete/delete-manual.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/delete/delete-manual.md
index 6a8d17d78f5..77830628e5d 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/delete/delete-manual.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/delete/delete-manual.md
@@ -55,7 +55,7 @@ DELETE FROM table_name [table_alias]
- 两种情况下，Doris 无法从条件中推断分区：
1. 条件中不包含分区列
2. 分区列的 `op` 为 `not in`
- - 当分区表未指定分区，或无法从条件中推断分区时，需要设置会话变量 `delete_without_partition` 为
`true`，此时删除操作会应用到所有分区。
+ - 如果分区表不是 Unique 表，当分区表未指定分区，或无法从条件中推断分区时，需要设置会话变量
`delete_without_partition` 为 `true`，此时删除操作会应用到所有分区。
### 示例
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/data-modification/DML/DELETE.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/data-modification/DML/DELETE.md
index 1d01b8c419b..87f7fb331de 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/data-modification/DML/DELETE.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-statements/data-modification/DML/DELETE.md
@@ -72,7 +72,7 @@ DELETE FROM table_name [table_alias]
1. 使用聚合类的表模型（AGGREGATE、UNIQUE）只能指定 key 列上的条件。
2. 当选定的 key 列不存在于某个 rollup 中时，无法进行 delete。
3. 语法一中，条件之间只能是“与”的关系。若希望达成“或”的关系，需要将条件分写在两个 DELETE 语句中。
-4. 语法一中，如果为分区表，需要指定分区，如果不指定，doris 会从条件中推断出分区。两种情况下，doris 无法从条件中推断出分区：1)
条件中不包含分区列；2) 分区列的 op 为 not in。当分区表未指定分区，或者无法从条件中推断分区的时候，需要设置会话变量
delete_without_partition 为 true，此时 delete 会应用到所有分区。该功能自 Apache Doris 1.2 版本起支持
+4. 语法一中，如果为分区表，需要指定分区，如果不指定，doris 会从条件中推断出分区。两种情况下，doris 无法从条件中推断出分区：1)
条件中不包含分区列；2) 分区列的 op 为 not in。如果分区表不是 Unique
表，当分区表未指定分区，或者无法从条件中推断分区的时候，需要设置会话变量 delete_without_partition 为 true，此时 delete
会应用到所有分区。该功能自 Apache Doris 1.2 版本起支持
5. 该语句可能会降低执行后一段时间内的查询效率。影响程度取决于语句中指定的删除条件的数量。指定的条件越多，影响越大。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/delete/delete-manual.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/delete/delete-manual.md
index 6a8d17d78f5..77830628e5d 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/delete/delete-manual.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/delete/delete-manual.md
@@ -55,7 +55,7 @@ DELETE FROM table_name [table_alias]
- 两种情况下，Doris 无法从条件中推断分区：
1. 条件中不包含分区列
2. 分区列的 `op` 为 `not in`
- - 当分区表未指定分区，或无法从条件中推断分区时，需要设置会话变量 `delete_without_partition` 为
`true`，此时删除操作会应用到所有分区。
+ - 如果分区表不是 Unique 表，当分区表未指定分区，或无法从条件中推断分区时，需要设置会话变量
`delete_without_partition` 为 `true`，此时删除操作会应用到所有分区。
### 示例
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/sql-manual/sql-statements/data-modification/DML/DELETE.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/sql-manual/sql-statements/data-modification/DML/DELETE.md
index 98ee646b702..c2ddf36bcd3 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/sql-manual/sql-statements/data-modification/DML/DELETE.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/sql-manual/sql-statements/data-modification/DML/DELETE.md
@@ -70,7 +70,7 @@ DELETE FROM table_name [table_alias]
1. 使用聚合类的表模型（AGGREGATE、UNIQUE）只能指定 key 列上的条件。
2. 当选定的 key 列不存在于某个 rollup 中时，无法进行 delete。
3. 语法一中，条件之间只能是“与”的关系。若希望达成“或”的关系，需要将条件分写在两个 DELETE 语句中。
-4. 语法一中，如果为分区表，需要指定分区，如果不指定，doris 会从条件中推断出分区。两种情况下，doris 无法从条件中推断出分区：1)
条件中不包含分区列；2) 分区列的 op 为 not in。当分区表未指定分区，或者无法从条件中推断分区的时候，需要设置会话变量
delete_without_partition 为 true，此时 delete 会应用到所有分区。
+4. 语法一中，如果为分区表，需要指定分区，如果不指定，doris 会从条件中推断出分区。两种情况下，doris 无法从条件中推断出分区：1)
条件中不包含分区列；2) 分区列的 op 为 not in。如果分区表不是 Unique
表，当分区表未指定分区，或者无法从条件中推断分区的时候，需要设置会话变量 delete_without_partition 为 true，此时 delete
会应用到所有分区。
5. 该语句可能会降低执行后一段时间内的查询效率。影响程度取决于语句中指定的删除条件的数量。指定的条件越多，影响越大。
## 示例
diff --git a/versioned_docs/version-2.1/data-operate/delete/delete-manual.md
b/versioned_docs/version-2.1/data-operate/delete/delete-manual.md
index 0b33a5b8baf..0c707603b83 100644
--- a/versioned_docs/version-2.1/data-operate/delete/delete-manual.md
+++ b/versioned_docs/version-2.1/data-operate/delete/delete-manual.md
@@ -60,7 +60,7 @@ DELETE FROM table_name [table_alias]
1. The conditions do not include partition columns.
2. The `op` of the partition column is `not in`.
- - When the partitioned table does not specify a partition or cannot infer
the partition from the conditions, the session variable
`delete_without_partition` needs to be set to `true`, and the delete operation
will apply to all partitions.
+ - When the partitioned table is not a Unique table, and it does not specify
a partition or cannot infer the partition from the conditions, the session
variable `delete_without_partition` needs to be set to `true`, and the delete
operation will apply to all partitions.
### Examples
diff --git
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/DML/DELETE.md
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/DML/DELETE.md
index b68b20f537d..103102fc865 100644
---
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/DML/DELETE.md
+++
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/DML/DELETE.md
@@ -72,7 +72,7 @@ DELETE FROM table_name
1. Only conditions on the key column can be specified when using AGGREGATE
(UNIQUE) model.
2. When the selected key column does not exist in a rollup, delete cannot be
performed.
3. Wheny you use syntax 1, conditions can only have an "and" relationship. If
you want to achieve an "or" relationship, you need to write the conditions in
two DELETE statements.
-4. In syntax 1, if it is a partitioned table, you can specify a partition. If
not specified, Doris will infer partition from the given conditions. In two
cases, Doris cannot infer the partition from conditions: 1) the conditions do
not contain partition columns; 2) The operator of the partition column is not
in. When a partition table does not specify the partition, or the partition
cannot be inferred from the conditions, the session variable
delete_without_partition needs to be true to [...]
+4. In syntax 1, if it is a partitioned table, you can specify a partition. If
not specified, Doris will infer partition from the given conditions. In two
cases, Doris cannot infer the partition from conditions: 1) the conditions do
not contain partition columns; 2) The operator of the partition column is not
in. When the partitioned table is not a Unique table, and it does not specify
the partition, or the partition cannot be inferred from the conditions, the
session variable delete_with [...]
:::tip Tips
This feature is supported since the Apache Doris 1.2 version
diff --git a/versioned_docs/version-3.0/data-operate/delete/delete-manual.md
b/versioned_docs/version-3.0/data-operate/delete/delete-manual.md
index 0b33a5b8baf..0c707603b83 100644
--- a/versioned_docs/version-3.0/data-operate/delete/delete-manual.md
+++ b/versioned_docs/version-3.0/data-operate/delete/delete-manual.md
@@ -60,7 +60,7 @@ DELETE FROM table_name [table_alias]
1. The conditions do not include partition columns.
2. The `op` of the partition column is `not in`.
- - When the partitioned table does not specify a partition or cannot infer
the partition from the conditions, the session variable
`delete_without_partition` needs to be set to `true`, and the delete operation
will apply to all partitions.
+ - When the partitioned table is not a Unique table, and it does not specify
a partition or cannot infer the partition from the conditions, the session
variable `delete_without_partition` needs to be set to `true`, and the delete
operation will apply to all partitions.
### Examples
diff --git
a/versioned_docs/version-3.0/sql-manual/sql-statements/data-modification/DML/DELETE.md
b/versioned_docs/version-3.0/sql-manual/sql-statements/data-modification/DML/DELETE.md
index dfa89978495..c10c4e5eb9e 100644
---
a/versioned_docs/version-3.0/sql-manual/sql-statements/data-modification/DML/DELETE.md
+++
b/versioned_docs/version-3.0/sql-manual/sql-statements/data-modification/DML/DELETE.md
@@ -72,7 +72,7 @@ DELETE FROM table_name
1. Only conditions on the key column can be specified when using AGGREGATE
(UNIQUE) model.
2. When the selected key column does not exist in a rollup, delete cannot be
performed.
3. Wheny you use syntax 1, conditions can only have an "and" relationship. If
you want to achieve an "or" relationship, you need to write the conditions in
two DELETE statements.
-4. In syntax 1, if it is a partitioned table, you can specify a partition. If
not specified, Doris will infer partition from the given conditions. In two
cases, Doris cannot infer the partition from conditions: 1) the conditions do
not contain partition columns; 2) The operator of the partition column is not
in. When a partition table does not specify the partition, or the partition
cannot be inferred from the conditions, the session variable
delete_without_partition needs to be true to [...]
+4. In syntax 1, if it is a partitioned table, you can specify a partition. If
not specified, Doris will infer partition from the given conditions. In two
cases, Doris cannot infer the partition from conditions: 1) the conditions do
not contain partition columns; 2) The operator of the partition column is not
in. When the partitioned table is not a Unique table, and it does not specify
the partition, or the partition cannot be inferred from the conditions, the
session variable delete_with [...]
:::tip Tips
This feature is supported since the Apache Doris 1.2 version
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
