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 2245f14efd4 [doc](table-temp-partition) address comments and translate
en doc by LLM (#1785)
2245f14efd4 is described below
commit 2245f14efd4fa08634573559ffcaba31e5ee242a
Author: zhannngchen <zhangc...@selectdb.com>
AuthorDate: Wed Jan 15 15:00:50 2025 +0800
[doc](table-temp-partition) address comments and translate en doc by LLM
(#1785)
## Versions
- [x] dev
- [x] 3.0
- [ ] 2.1
- [ ] 2.0
## Languages
- [ ] Chinese
- [ ] English
## Docs Checklist
- [ ] Checked by AI
- [ ] Test Cases Built
---
docs/data-operate/delete/table-temp-partition.md | 144 +++++++++------------
.../data-operate/delete/table-temp-partition.md | 107 ++++++---------
.../data-operate/delete/table-temp-partition.md | 107 ++++++---------
.../data-operate/delete/table-temp-partition.md | 107 ++++++---------
.../data-operate/delete/table-temp-partition.md | 144 +++++++++------------
.../data-operate/delete/table-temp-partition.md | 144 +++++++++------------
6 files changed, 312 insertions(+), 441 deletions(-)
diff --git a/docs/data-operate/delete/table-temp-partition.md
b/docs/data-operate/delete/table-temp-partition.md
index 0a7aad869da..0f548e18b5b 100644
--- a/docs/data-operate/delete/table-temp-partition.md
+++ b/docs/data-operate/delete/table-temp-partition.md
@@ -24,31 +24,25 @@ specific language governing permissions and limitations
under the License.
-->
-Doris supports adding temporary partitions to partitioned tables. Temporary
partitions differ from formal partitions in that they are not queried by formal
queries, but only by special query statements.
+Doris supports adding temporary partitions to partitioned tables. Temporary
partitions differ from regular partitions in that they are not retrieved by
regular queries and can only be queried through special query statements.
-- The partition columns of the temporary partition are the same as the formal
partition and cannot be modified.
+- The partition columns of temporary partitions are the same as those of
regular partitions and cannot be modified.
-- The partition ranges of all temporary partitions of a table cannot overlap,
but the ranges of temporary partitions and formal partitions can overlap.
+- The partition ranges of all temporary partitions cannot overlap, but the
ranges of temporary partitions and regular partitions can overlap.
-- The partition name of the temporary partition cannot be the same as the
formal partitions and other temporary partitions.
+- The names of temporary partitions cannot duplicate those of regular
partitions or other temporary partitions.
-Temporary Partitions are mainly used in the following scenarios:
+**Main application scenarios for temporary partitions:**
-- Atomic overwrite write operations
+- **Atomic overwrite operation**: Users can rewrite the data of a partition
without data loss between deleting old data and importing new data. In this
case, a temporary partition can be created, new data can be imported into the
temporary partition, and then the original partition can be atomically replaced
through a replace operation. For atomic overwrite operations on non-partitioned
tables, refer to the [replace table
documentation](../../data-operate/delete/atomicity-replace).
-In some cases, users want to rewrite the data of a certain partition, but if
they do it by deleting and then importing, there will be a period of time in
the middle when they cannot view the data. In this case, the user can create a
corresponding Temporary Partition first, and after importing the new data into
the Temporary Partition, replace the original partition atomically through the
Replace operation to achieve the purpose. For the atomic overwrite write
operation of non-partitioned [...]
+- **Modify the number of buckets**: If an inappropriate number of buckets was
used when creating a partition, a new temporary partition can be created with
the specified new number of buckets. Then, the data of the regular partition
can be imported into the temporary partition using the `INSERT INTO` command,
and the original partition can be atomically replaced through a replace
operation.
-- Modifying the number of buckets
-
-In some cases, users use an inappropriate bucket number when creating
partitions. Then the user can first create a Temporary Partition corresponding
to the partition range and specify the new bucket number. Then import the data
of the formal partition into the Temporary Partition through the `INSERT INTO`
command, and replace the original partition atomically through the Replace
operation to achieve the purpose.
-
-- Merge or split partition
-
-In some cases, users want to modify the scope of partitions, such as merging
two partitions, or splitting a large partition into several small partitions.
You can first create a Temporary Partition corresponding to the scope of the
merged or partitioned partition, and then import the data of the official
partition into the Temporary Partition through the `INSERT INTO` command, and
then replace the original partition atomically through the Replacement
operation, in order to achieve the purpose.
+- **Merge or split partitions**: Users can modify the partition range, such as
merging two partitions or splitting a large partition into multiple smaller
partitions. A new temporary partition can be created, the data of the regular
partition can be imported into the temporary partition using the `INSERT INTO`
command, and the original partition can be atomically replaced through a
replace operation.
## Add Temporary Partition
-You can add temporary partitions to a table with the `ALTER TABLE ADD
TEMPORARY PARTITION` statement:
+Use the `ALTER TABLE ADD TEMPORARY PARTITION` statement to add a temporary
partition:
```sql
ALTER TABLE tbl1 ADD TEMPORARY PARTITION tp1 VALUES LESS THAN("2020-02-01");
@@ -68,31 +62,17 @@ ALTER TABLE tbl3 ADD TEMPORARY PARTITION tp1 VALUES IN
("Beijing", "Shanghai")
DISTRIBUTED BY HASH(k1) BUCKETS 5;
```
-See `HELP ALTER TABLE;` for more help and examples.
-
-Some instructions for adding operations:
+## Drop Temporary Partition
-- Adding a temporary partition is similar to adding a formal partition. The
partition range of the temporary partition is independent of the formal
partition.
+Use the `ALTER TABLE DROP TEMPORARY PARTITION` statement to drop a temporary
partition:
-- Temporary partition can independently specify some attributes. Includes
information such as the number of buckets, the number of replicas, or the
storage medium.
-
-### Delete Temporary Partition
-
-A table's temporary partition can be dropped with the `ALTER TABLE DROP
TEMPORARY PARTITION` statement:
-
-```Plain
+```sql
ALTER TABLE tbl1 DROP TEMPORARY PARTITION tp1;
```
-See `HELP ALTER TABLE;` for more help and examples.
+## Replace Regular Partition
-Some instructions for the DELETE:
-
-- Deleting the temporary partition will not affect the data of the formal
partition.
-
-### Replace Partition
-
-You can replace formal partitions of a table with temporary partitions with
the `ALTER TABLE REPLACE PARTITION` statement.
+Use the `ALTER TABLE REPLACE PARTITION` statement to replace a regular
partition with a temporary partition:
```sql
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
@@ -101,76 +81,76 @@ ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY
PARTITION (tp1, tp2,
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1, tp2)
PROPERTIES (
- "strict_range" = "false",
- "use_temp_partition_name" = "true"
+ "strict_range" = "false",
+ "use_temp_partition_name" = "true"
);
```
-See `HELP ALTER TABLE;` for more help and examples.
-
-The replace operation has two special optional parameters:
+There are two special optional parameters for the replace operation:
**1. `strict_range`**
-The default is true.
+Default is true.
-For Range partition, When this parameter is true, the range union of all
formal partitions to be replaced needs to be the same as the range union of the
temporary partitions to be replaced. When set to false, you only need to ensure
that the range between the new formal partitions does not overlap after
replacement.
+For Range partitions, when this parameter is true, the union of the ranges of
all replaced regular partitions must be exactly the same as the union of the
ranges of the replacing temporary partitions. When set to false, it only needs
to ensure that the ranges of the new regular partitions do not overlap after
replacement.
-For List partition, this parameter is always true, and the enumeration values
of all full partitions to be replaced must be identical to the enumeration
values of the temporary partitions to be replaced.
+For List partitions, this parameter is always true. The enumeration values of
all replaced regular partitions must be exactly the same as the enumeration
values of the replacing temporary partitions.
**Example 1**
```sql
--- Range of partitions p1, p2, p3 to be replaced (=> union):
-(10, 20), [20, 30), [40, 50) => [10, 30), [40, 50)
+-- The range of partitions p1, p2, p3 to be replaced (=> union):
+[10, 20), [20, 30), [40, 50) => [10, 30), [40, 50)
---Replace the range of partitions tp1, tp2 (=> union):
-(10, 30), [40, 45), [45, 50) => [10, 30), [40, 50)
+-- The range of replacing partitions tp1, tp2 (=> union):
+[10, 30), [40, 45), [45, 50) => [10, 30), [40, 50)
---The union of ranges is the same, so you can use tp1 and tp2 to replace p1,
p2, p3.
+-- The union of ranges is the same, so tp1 and tp2 can replace p1, p2, p3.
```
**Example 2**
```sql
---Range of partition p1 to be replaced (=> union):
+-- The range of partition p1 to be replaced (=> union):
[10, 50) => [10, 50)
---Replace the range of partitions tp1, tp2 (=> union):
+-- The range of replacing partitions tp1, tp2 (=> union):
[10, 30), [40, 50) => [10, 30), [40, 50)
---The union of ranges is not the same. If strict_range is true, you cannot use
tp1 and tp2 to replace p1. If false, and the two partition ranges [10, 30),
[40, 50) and the other formal partitions do not overlap, they can be replaced.
+-- The union of ranges is not the same. If strict_range is true, tp1 and tp2
cannot replace p1. If it is false, and the ranges of the two partitions after
replacement [10, 30), [40, 50) do not overlap with other regular partitions,
they can replace p1.
```
**Example 3**
```sql
---Enumerated values of partitions p1, p2 to be replaced (=> union).
+-- The enumeration values of partitions p1, p2 to be replaced (=> union):
(1, 2, 3), (4, 5, 6) => (1, 2, 3, 4, 5, 6)
---Replace the enumerated values of partitions tp1, tp2, tp3 (=> union).
+
+-- The enumeration values of replacing partitions tp1, tp2, tp3 (=> union):
(1, 2, 3), (4), (5, 6) => (1, 2, 3, 4, 5, 6)
---The enumeration values are the same, you can use tp1, tp2, tp3 to replace
p1, p2
+
+-- The union of enumeration values is the same, so tp1, tp2, tp3 can replace
p1, p2.
```
**Example 4**
```sql
---Enumerated values of partitions p1, p2, p3 to be replaced (=> union).
+-- The enumeration values of partitions p1, p2, p3 to be replaced (=> union):
(("1","beijing"), ("1", "shanghai")), (("2","beijing"), ("2", "shanghai")),
(("3","beijing"), ("3", "shanghai")) => (("1","beijing"), ("1", "shanghai"),
("2","beijing"), ("2", "shanghai"), ("3","beijing"), ("3", "shanghai"))
---Replace the enumerated values of partitions tp1, tp2 (=> union).
+-- The enumeration values of replacing partitions tp1, tp2 (=> union):
(("1","beijing"), ("1", "shanghai")), (("2","beijing"), ("2", "shanghai"),
("3","beijing"), ("3", "shanghai")) => (("1","beijing"), ("1", "shanghai"),
("2","beijing"), ("2", "shanghai"), ("3","beijing"), ("3", "shanghai"))
---The enumeration values are the same, you can use tp1, tp2 to replace p1, p2,
p3
+-- The union of enumeration values is the same, so tp1, tp2 can replace p1,
p2, p3.
```
**2. `use_temp_partition_name`**
-The default is false.
+Default is false.
-When this parameter is false, and the number of partitions to be replaced is
the same as the number of replacement partitions, the name of the formal
partition after the replacement remains unchanged.
+When this parameter is false, and the number of partitions to be replaced is
the same as the number of replacing partitions, the names of the partitions
remain unchanged after replacement.
-If true, after replacement, the name of the formal partition is the name of
the replacement partition. Here are some examples:
+If it is true, the names of the partitions after replacement will be the names
of the replacing partitions. Examples are as follows:
**Example 1**
@@ -178,27 +158,26 @@ If true, after replacement, the name of the formal
partition is the name of the
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
```
-`use_temp_partition_name` is **false** by default. After replacement, the
partition name is still p1, but the related data and attributes are replaced
with tp1.
-
-If `use_temp_partition_name` is **true** by default, the name of the partition
is tp1 after replacement. The p1 partition no longer exists.
+- `use_temp_partition_name` defaults to false, so after replacement, the
partition name remains p1, but the data and properties are replaced with those
of tp1.
+- If `use_temp_partition_name` is true, after replacement, the partition name
is tp1, and p1 no longer exists.
**Example 2**
-```Plain
+```sql
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1);
```
-`use_temp_partition_name` is **false** by default, but this parameter is
invalid because the number of partitions to be replaced and the number of
replacement partitions are different. After the replacement, the partition name
is tp1, and p1 and p2 no longer exist.
+- `use_temp_partition_name` defaults to false, but since the number of
partitions to be replaced is different from the number of replacing partitions,
this parameter is invalid. After replacement, the partition name is tp1, and p1
and p2 no longer exist.
-:::tip Tip
-**Some instructions for the replacement operation:**
+:::tip
+**Explanation of the replace operation:**
-After the partition is replaced successfully, the replaced partition will be
deleted and cannot be recovered.
+After the partition replacement is successful, the replaced partitions will be
deleted and cannot be recovered.
:::
-## Importing Temporary Partitions
+## Import Temporary Partition
-Depending on the import method, the syntax for specifying the import of
Temporary Partitions is slightly different. Here is a brief explanation with an
example:
+The syntax for specifying the import of temporary partitions varies slightly
depending on the import method. Examples are as follows:
```sql
INSERT INTO tbl TEMPORARY PARTITION(tp1, tp2, ...) SELECT ....
@@ -221,7 +200,7 @@ FROM KAFKA
(...);
```
-## Query Temporary Partitions
+## Query Temporary Partition
```sql
SELECT ... FROM
@@ -232,26 +211,27 @@ ON ...
WHERE ...;
```
-## Relationship to Other Operations
+## Relationship with Other Operations
-### DROP
+**DROP**
-- After using the `DROP` operation to directly drop the database or table, you
can recover the database or table (within a limited time) through the `RECOVER`
command, but the temporary partition will not be recovered.
+- After using the Drop operation to directly delete a database or table, the
database or table can be recovered using the Recover command (within a limited
time), but temporary partitions will not be recovered.
-- After the formal partition is dropped using the `ALTER` command, the
partition can be recovered by the `RECOVER` command (within a limited time).
Operating a formal partition is not related to a temporary partition.
+- After using the Alter command to delete a regular partition, the partition
can be recovered using the Recover command (within a limited time). This
operation is unrelated to temporary partitions.
-- After the temporary partition is dropped using the `ALTER` command, the
temporary partition cannot be recovered through the `RECOVER` command.
+- After using the Alter command to delete a temporary partition, the temporary
partition cannot be recovered using the Recover command.
-### TRUNCATE
+**TRUNCATE**
-- Use the `TRUNCATE` command to empty the table. The temporary partition of
the table will be deleted and cannot be recovered.
+- Using the Truncate command to empty a table will delete the table's
temporary partitions, and they cannot be recovered.
-- When using `TRUNCATE` command to empty the formal partition, it will not
affect the temporary partition.
+- Using the Truncate command to empty a regular partition does not affect
temporary partitions.
-- You cannot use the `TRUNCATE` command to empty the temporary partition.
+- The Truncate command cannot be used to empty temporary partitions.
-### ALTER
+**ALTER**
-- When the table has a temporary partition, you cannot use the `ALTER` command
to perform Schema Change, Rollup, etc. on the table.
+- When a table has temporary partitions, the Alter command cannot be used to
perform Schema Change, Rollup, or other change operations on the table.
-- You cannot add temporary partitions to a table while the table is undergoing
a alter operation.
\ No newline at end of file
+- When a table is undergoing change operations, temporary partitions cannot be
added to the table.
+```
\ No newline at end of file
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/table-temp-partition.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/table-temp-partition.md
index d71d402fe3e..07149f097da 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/table-temp-partition.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/table-temp-partition.md
@@ -24,31 +24,25 @@ specific language governing permissions and limitations
under the License.
-->
-Doris 支持在分区表中添加临时分区，临时分区和正式分区不同的是，临时分区不会被正式查询查询到，只有通过特殊的查询语句才能查询。
+Doris 支持在分区表中添加临时分区。临时分区与正式分区不同，临时分区不会被常规查询检索到，只有通过特殊查询语句才能查询。
-- 临时分区的分区列和正式分区相同，且不可修改。
+- 临时分区的分区列与正式分区相同且不可修改。
-- 一张表所有临时分区之间的分区范围不可重叠，但临时分区的范围和正式分区范围可以重叠。
+- 所有临时分区之间的分区范围不可重叠，但临时分区与正式分区的范围可以重叠。
-- 临时分区的分区名称不能和正式分区以及其他临时分区重复。
+- 临时分区的名称不能与正式分区或其他临时分区重复。
-**临时分区主要用到如下场景：**
+**临时分区的主要应用场景：**
-- 原子的覆盖写操作
+-
**原子覆盖写操作**：用户希望重写某一分区的数据，但不希望在删除旧数据和导入新数据之间有数据缺失。此时，可以创建一个临时分区，将新数据导入临时分区后，通过替换操作原子性地替换原有分区。对于非分区表的原子覆盖写操作，请参阅[替换表文档](../../data-operate/delete/atomicity-replace)。
-
某些情况下，用户希望能够重写某一分区的数据，但如果采用先删除再导入的方式进行，在中间会有一段时间无法查看数据。这时，用户可以先创建一个对应的临时分区，将新的数据导入到临时分区后，通过替换操作，原子的替换原有分区，以达到目的。对于非分区表的原子覆盖写操作，请参阅[替换表文档](../../data-operate/delete/atomicity-replace)。
+- **修改分桶数**：用户在创建分区时使用了不合适的分桶数，可以创建一个新的临时分区并指定新的分桶数，然后通过 `INSERT INTO`
命令将正式分区的数据导入临时分区，再通过替换操作原子性地替换原有分区。
-- 修改分桶数
-
- 某些情况下，用户在创建分区时使用了不合适的分桶数。则用户可以先创建一个对应分区范围的临时分区，并指定新的分桶数。然后通过 `INSERT INTO`
命令将正式分区的数据导入到临时分区中，通过替换操作，原子的替换原有分区，以达到目的。
-
-- 合并或分割分区
-
- 某些情况下，用户希望对分区的范围进行修改，比如合并两个分区，或将一个大分区分割成多个小分区。则用户可以先建立对应合并或分割后范围的临时分区，然后通过
`INSERT INTO` 命令将正式分区的数据导入到临时分区中，通过替换操作，原子的替换原有分区，以达到目的。
+- **合并或分割分区**：用户希望修改分区范围，如合并两个分区或将一个大分区分割成多个小分区。可以先建立新的临时分区，然后通过 `INSERT INTO`
命令将正式分区的数据导入临时分区，再通过替换操作原子性地替换原有分区。
## 添加临时分区
-可以通过 `ALTER TABLE ADD TEMPORARY PARTITION` 语句对一个表添加临时分区：
+使用 `ALTER TABLE ADD TEMPORARY PARTITION` 语句添加临时分区：
```sql
ALTER TABLE tbl1 ADD TEMPORARY PARTITION tp1 VALUES LESS THAN("2020-02-01");
@@ -68,111 +62,95 @@ ALTER TABLE tbl3 ADD TEMPORARY PARTITION tp1 VALUES IN
("Beijing", "Shanghai")
DISTRIBUTED BY HASH(k1) BUCKETS 5;
```
-通过 `HELP ALTER TABLE;` 查看更多帮助和示例。
-
-添加操作的一些说明：
-
-- 临时分区的添加和正式分区的添加操作相似。临时分区的分区范围独立于正式分区。
-
-- 临时分区可以独立指定一些属性。包括分桶数、副本数、存储介质等信息。
## 删除临时分区
-可以通过 `ALTER TABLE DROP TEMPORARY PARTITION` 语句删除一个表的临时分区：
+使用 `ALTER TABLE DROP TEMPORARY PARTITION` 语句删除临时分区：
-```Plain
+```sql
ALTER TABLE tbl1 DROP TEMPORARY PARTITION tp1;
```
-通过 `HELP ALTER TABLE;` 查看更多帮助和示例。
-
-删除操作的一些说明：
-
-- 删除临时分区，不影响正式分区的数据。
-
## 替换正式分区
-可以通过 `ALTER TABLE REPLACE PARTITION` 语句将一个表的正式分区替换为临时分区。
+使用 `ALTER TABLE REPLACE PARTITION` 语句将正式分区替换为临时分区：
-```Plain
+```sql
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1,
tp2, tp3);
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1, tp2)
PROPERTIES (
- "strict_range" = "false",
- "use_temp_partition_name" = "true"
+ "strict_range" = "false",
+ "use_temp_partition_name" = "true"
);
```
-
-通过 `HELP ALTER TABLE;` 查看更多帮助和示例。
-
替换操作有两个特殊的可选参数：
**1. `strict_range`**
默认为 true。
-对于 Range 分区，当该参数为 true 时，表示要被替换的所有正式分区的范围并集需要和替换的临时分区的范围并集完全相同。当置为 false
时，只需要保证替换后，新的正式分区间的范围不重叠即可。
+对于 Range 分区，当该参数为 true 时，所有被替换的正式分区的范围并集需要与替换的临时分区的范围并集完全相同。当置为 false
时，只需保证替换后新的正式分区间的范围不重叠即可。
-对于 List 分区，该参数恒为 true。要被替换的所有正式分区的枚举值必须和替换的临时分区枚举值完全相同。
+对于 List 分区，该参数恒为 true。所有被替换的正式分区的枚举值必须与替换的临时分区枚举值完全相同。
**示例 1**
-```Plain
-待替换的分区 p1, p2, p3 的范围 (=> 并集)：
+```sql
+-- 待替换的分区 p1, p2, p3 的范围 (=> 并集)：
[10, 20), [20, 30), [40, 50) => [10, 30), [40, 50)
-替换分区 tp1, tp2 的范围(=> 并集)：
+-- 替换分区 tp1, tp2 的范围(=> 并集)：
[10, 30), [40, 45), [45, 50) => [10, 30), [40, 50)
-范围并集相同，则可以使用 tp1 和 tp2 替换 p1, p2, p3。
+--范围并集相同，则可以使用 tp1 和 tp2 替换 p1, p2, p3。
```
**示例 2**
```sql
-待替换的分区 p1 的范围 (=> 并集)：
+-- 待替换的分区 p1 的范围 (=> 并集)：
[10, 50) => [10, 50)
-替换分区 tp1, tp2 的范围(=> 并集)：
+-- 替换分区 tp1, tp2 的范围(=> 并集)：
[10, 30), [40, 50) => [10, 30), [40, 50)
-范围并集不相同，如果 strict_range 为 true，则不可以使用 tp1 和 tp2 替换 p1。如果为 false，且替换后的两个分区范围
[10, 30), [40, 50) 和其他正式分区不重叠，则可以替换。
+-- 范围并集不相同，如果 strict_range 为 true，则不可以使用 tp1 和 tp2 替换 p1。如果为 false，且替换后的两个分区范围
[10, 30), [40, 50) 和其他正式分区不重叠，则可以替换。
```
**示例 3**
-```Plain
-待替换的分区 p1, p2 的枚举值(=> 并集)：
+```sql
+-- 待替换的分区 p1, p2 的枚举值(=> 并集)：
(1, 2, 3), (4, 5, 6) => (1, 2, 3, 4, 5, 6)
-替换分区 tp1, tp2, tp3 的枚举值(=> 并集)：
+-- 替换分区 tp1, tp2, tp3 的枚举值(=> 并集)：
(1, 2, 3), (4), (5, 6) => (1, 2, 3, 4, 5, 6)
-枚举值并集相同，可以使用 tp1，tp2，tp3 替换 p1，p2
+-- 枚举值并集相同，可以使用 tp1，tp2，tp3 替换 p1，p2
```
**示例 4**
-```Plain
-待替换的分区 p1, p2，p3 的枚举值(=> 并集)：
+```sql
+-- 待替换的分区 p1, p2，p3 的枚举值(=> 并集)：
(("1","beijing"), ("1", "shanghai")), (("2","beijing"), ("2", "shanghai")),
(("3","beijing"), ("3", "shanghai")) => (("1","beijing"), ("1", "shanghai"),
("2","beijing"), ("2", "shanghai"), ("3","beijing"), ("3", "shanghai"))
-替换分区 tp1, tp2 的枚举值(=> 并集)：
+-- 替换分区 tp1, tp2 的枚举值(=> 并集)：
(("1","beijing"), ("1", "shanghai")), (("2","beijing"), ("2", "shanghai"),
("3","beijing"), ("3", "shanghai")) => (("1","beijing"), ("1", "shanghai"),
("2","beijing"), ("2", "shanghai"), ("3","beijing"), ("3", "shanghai"))
-枚举值并集相同，可以使用 tp1，tp2 替换 p1，p2，p3
+-- 枚举值并集相同，可以使用 tp1，tp2 替换 p1，p2，p3
```
**2. `use_temp_partition_name`**
默认为 false。
-当该参数为 false，并且待替换的分区和替换分区的个数相同时，则替换后的正式分区名称维持不变。
+当该参数为 false，并且待替换的分区和替换分区的个数相同时，替换后的正式分区名称维持不变。
-如果为 true，则替换后，正式分区的名称为替换分区的名称。下面举例说明：
+如果为 true，替换后正式分区的名称为替换分区的名称。示例如下：
**示例 1**
@@ -180,9 +158,8 @@ PROPERTIES (
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
```
-- `use_temp_partition_name` 默认为 false，则在替换后，分区的名称依然为 p1，但是相关的数据和属性都替换为 tp1 的。
-
-- 如果 `use_temp_partition_name` 默认为 true，则在替换后，分区的名称为 tp1。p1 分区不再存在。
+- `use_temp_partition_name` 默认为 false，则在替换后，分区的名称依然为 p1，但相关的数据和属性都替换为 tp1 的。
+- 如果 `use_temp_partition_name` 为 true，则在替换后，分区的名称为 tp1，p1 分区不再存在。
**示例 2**
@@ -190,19 +167,19 @@ ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY
PARTITION (tp1);
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1);
```
-- `use_temp_partition_name` 默认为 false，但因为待替换分区的个数和替换分区的个数不同，则该参数无效。替换后，分区名称为
tp1，p1 和 p2 不再存在。
+- `use_temp_partition_name` 默认为 false，但因待替换分区的个数与替换分区的个数不同，该参数无效。替换后，分区名称为
tp1，p1 和 p2 不再存在。
:::tip
-**替换操作的一些说明：**
+**替换操作说明：**
分区替换成功后，被替换的分区将被删除且不可恢复。
:::
## 导入临时分区
-根据导入方式的不同，指定导入临时分区的语法稍有差别。这里通过示例进行简单说明
+根据导入方式的不同，指定导入临时分区的语法稍有差别。示例如下：
-```Plain
+```sql
INSERT INTO tbl TEMPORARY PARTITION(tp1, tp2, ...) SELECT ....
curl --location-trusted -u root: -H "label:123" -H "temporary_partitions: tp1,
tp2, ..." -T testData http://host:port/api/testDb/testTbl/_stream_load
LOAD LABEL example_db.label1
@@ -225,7 +202,7 @@ FROM KAFKA
## 查询临时分区
-```Plain
+```sql
SELECT ... FROM
tbl1 TEMPORARY PARTITION(tp1, tp2, ...)
JOIN
@@ -234,7 +211,7 @@ ON ...
WHERE ...;
```
-## 和其他操作的关系
+## 与其他操作的关系
**DROP**
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/delete/table-temp-partition.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/delete/table-temp-partition.md
index d71d402fe3e..07149f097da 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/delete/table-temp-partition.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/delete/table-temp-partition.md
@@ -24,31 +24,25 @@ specific language governing permissions and limitations
under the License.
-->
-Doris 支持在分区表中添加临时分区，临时分区和正式分区不同的是，临时分区不会被正式查询查询到，只有通过特殊的查询语句才能查询。
+Doris 支持在分区表中添加临时分区。临时分区与正式分区不同，临时分区不会被常规查询检索到，只有通过特殊查询语句才能查询。
-- 临时分区的分区列和正式分区相同，且不可修改。
+- 临时分区的分区列与正式分区相同且不可修改。
-- 一张表所有临时分区之间的分区范围不可重叠，但临时分区的范围和正式分区范围可以重叠。
+- 所有临时分区之间的分区范围不可重叠，但临时分区与正式分区的范围可以重叠。
-- 临时分区的分区名称不能和正式分区以及其他临时分区重复。
+- 临时分区的名称不能与正式分区或其他临时分区重复。
-**临时分区主要用到如下场景：**
+**临时分区的主要应用场景：**
-- 原子的覆盖写操作
+-
**原子覆盖写操作**：用户希望重写某一分区的数据，但不希望在删除旧数据和导入新数据之间有数据缺失。此时，可以创建一个临时分区，将新数据导入临时分区后，通过替换操作原子性地替换原有分区。对于非分区表的原子覆盖写操作，请参阅[替换表文档](../../data-operate/delete/atomicity-replace)。
-
某些情况下，用户希望能够重写某一分区的数据，但如果采用先删除再导入的方式进行，在中间会有一段时间无法查看数据。这时，用户可以先创建一个对应的临时分区，将新的数据导入到临时分区后，通过替换操作，原子的替换原有分区，以达到目的。对于非分区表的原子覆盖写操作，请参阅[替换表文档](../../data-operate/delete/atomicity-replace)。
+- **修改分桶数**：用户在创建分区时使用了不合适的分桶数，可以创建一个新的临时分区并指定新的分桶数，然后通过 `INSERT INTO`
命令将正式分区的数据导入临时分区，再通过替换操作原子性地替换原有分区。
-- 修改分桶数
-
- 某些情况下，用户在创建分区时使用了不合适的分桶数。则用户可以先创建一个对应分区范围的临时分区，并指定新的分桶数。然后通过 `INSERT INTO`
命令将正式分区的数据导入到临时分区中，通过替换操作，原子的替换原有分区，以达到目的。
-
-- 合并或分割分区
-
- 某些情况下，用户希望对分区的范围进行修改，比如合并两个分区，或将一个大分区分割成多个小分区。则用户可以先建立对应合并或分割后范围的临时分区，然后通过
`INSERT INTO` 命令将正式分区的数据导入到临时分区中，通过替换操作，原子的替换原有分区，以达到目的。
+- **合并或分割分区**：用户希望修改分区范围，如合并两个分区或将一个大分区分割成多个小分区。可以先建立新的临时分区，然后通过 `INSERT INTO`
命令将正式分区的数据导入临时分区，再通过替换操作原子性地替换原有分区。
## 添加临时分区
-可以通过 `ALTER TABLE ADD TEMPORARY PARTITION` 语句对一个表添加临时分区：
+使用 `ALTER TABLE ADD TEMPORARY PARTITION` 语句添加临时分区：
```sql
ALTER TABLE tbl1 ADD TEMPORARY PARTITION tp1 VALUES LESS THAN("2020-02-01");
@@ -68,111 +62,95 @@ ALTER TABLE tbl3 ADD TEMPORARY PARTITION tp1 VALUES IN
("Beijing", "Shanghai")
DISTRIBUTED BY HASH(k1) BUCKETS 5;
```
-通过 `HELP ALTER TABLE;` 查看更多帮助和示例。
-
-添加操作的一些说明：
-
-- 临时分区的添加和正式分区的添加操作相似。临时分区的分区范围独立于正式分区。
-
-- 临时分区可以独立指定一些属性。包括分桶数、副本数、存储介质等信息。
## 删除临时分区
-可以通过 `ALTER TABLE DROP TEMPORARY PARTITION` 语句删除一个表的临时分区：
+使用 `ALTER TABLE DROP TEMPORARY PARTITION` 语句删除临时分区：
-```Plain
+```sql
ALTER TABLE tbl1 DROP TEMPORARY PARTITION tp1;
```
-通过 `HELP ALTER TABLE;` 查看更多帮助和示例。
-
-删除操作的一些说明：
-
-- 删除临时分区，不影响正式分区的数据。
-
## 替换正式分区
-可以通过 `ALTER TABLE REPLACE PARTITION` 语句将一个表的正式分区替换为临时分区。
+使用 `ALTER TABLE REPLACE PARTITION` 语句将正式分区替换为临时分区：
-```Plain
+```sql
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1,
tp2, tp3);
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1, tp2)
PROPERTIES (
- "strict_range" = "false",
- "use_temp_partition_name" = "true"
+ "strict_range" = "false",
+ "use_temp_partition_name" = "true"
);
```
-
-通过 `HELP ALTER TABLE;` 查看更多帮助和示例。
-
替换操作有两个特殊的可选参数：
**1. `strict_range`**
默认为 true。
-对于 Range 分区，当该参数为 true 时，表示要被替换的所有正式分区的范围并集需要和替换的临时分区的范围并集完全相同。当置为 false
时，只需要保证替换后，新的正式分区间的范围不重叠即可。
+对于 Range 分区，当该参数为 true 时，所有被替换的正式分区的范围并集需要与替换的临时分区的范围并集完全相同。当置为 false
时，只需保证替换后新的正式分区间的范围不重叠即可。
-对于 List 分区，该参数恒为 true。要被替换的所有正式分区的枚举值必须和替换的临时分区枚举值完全相同。
+对于 List 分区，该参数恒为 true。所有被替换的正式分区的枚举值必须与替换的临时分区枚举值完全相同。
**示例 1**
-```Plain
-待替换的分区 p1, p2, p3 的范围 (=> 并集)：
+```sql
+-- 待替换的分区 p1, p2, p3 的范围 (=> 并集)：
[10, 20), [20, 30), [40, 50) => [10, 30), [40, 50)
-替换分区 tp1, tp2 的范围(=> 并集)：
+-- 替换分区 tp1, tp2 的范围(=> 并集)：
[10, 30), [40, 45), [45, 50) => [10, 30), [40, 50)
-范围并集相同，则可以使用 tp1 和 tp2 替换 p1, p2, p3。
+--范围并集相同，则可以使用 tp1 和 tp2 替换 p1, p2, p3。
```
**示例 2**
```sql
-待替换的分区 p1 的范围 (=> 并集)：
+-- 待替换的分区 p1 的范围 (=> 并集)：
[10, 50) => [10, 50)
-替换分区 tp1, tp2 的范围(=> 并集)：
+-- 替换分区 tp1, tp2 的范围(=> 并集)：
[10, 30), [40, 50) => [10, 30), [40, 50)
-范围并集不相同，如果 strict_range 为 true，则不可以使用 tp1 和 tp2 替换 p1。如果为 false，且替换后的两个分区范围
[10, 30), [40, 50) 和其他正式分区不重叠，则可以替换。
+-- 范围并集不相同，如果 strict_range 为 true，则不可以使用 tp1 和 tp2 替换 p1。如果为 false，且替换后的两个分区范围
[10, 30), [40, 50) 和其他正式分区不重叠，则可以替换。
```
**示例 3**
-```Plain
-待替换的分区 p1, p2 的枚举值(=> 并集)：
+```sql
+-- 待替换的分区 p1, p2 的枚举值(=> 并集)：
(1, 2, 3), (4, 5, 6) => (1, 2, 3, 4, 5, 6)
-替换分区 tp1, tp2, tp3 的枚举值(=> 并集)：
+-- 替换分区 tp1, tp2, tp3 的枚举值(=> 并集)：
(1, 2, 3), (4), (5, 6) => (1, 2, 3, 4, 5, 6)
-枚举值并集相同，可以使用 tp1，tp2，tp3 替换 p1，p2
+-- 枚举值并集相同，可以使用 tp1，tp2，tp3 替换 p1，p2
```
**示例 4**
-```Plain
-待替换的分区 p1, p2，p3 的枚举值(=> 并集)：
+```sql
+-- 待替换的分区 p1, p2，p3 的枚举值(=> 并集)：
(("1","beijing"), ("1", "shanghai")), (("2","beijing"), ("2", "shanghai")),
(("3","beijing"), ("3", "shanghai")) => (("1","beijing"), ("1", "shanghai"),
("2","beijing"), ("2", "shanghai"), ("3","beijing"), ("3", "shanghai"))
-替换分区 tp1, tp2 的枚举值(=> 并集)：
+-- 替换分区 tp1, tp2 的枚举值(=> 并集)：
(("1","beijing"), ("1", "shanghai")), (("2","beijing"), ("2", "shanghai"),
("3","beijing"), ("3", "shanghai")) => (("1","beijing"), ("1", "shanghai"),
("2","beijing"), ("2", "shanghai"), ("3","beijing"), ("3", "shanghai"))
-枚举值并集相同，可以使用 tp1，tp2 替换 p1，p2，p3
+-- 枚举值并集相同，可以使用 tp1，tp2 替换 p1，p2，p3
```
**2. `use_temp_partition_name`**
默认为 false。
-当该参数为 false，并且待替换的分区和替换分区的个数相同时，则替换后的正式分区名称维持不变。
+当该参数为 false，并且待替换的分区和替换分区的个数相同时，替换后的正式分区名称维持不变。
-如果为 true，则替换后，正式分区的名称为替换分区的名称。下面举例说明：
+如果为 true，替换后正式分区的名称为替换分区的名称。示例如下：
**示例 1**
@@ -180,9 +158,8 @@ PROPERTIES (
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
```
-- `use_temp_partition_name` 默认为 false，则在替换后，分区的名称依然为 p1，但是相关的数据和属性都替换为 tp1 的。
-
-- 如果 `use_temp_partition_name` 默认为 true，则在替换后，分区的名称为 tp1。p1 分区不再存在。
+- `use_temp_partition_name` 默认为 false，则在替换后，分区的名称依然为 p1，但相关的数据和属性都替换为 tp1 的。
+- 如果 `use_temp_partition_name` 为 true，则在替换后，分区的名称为 tp1，p1 分区不再存在。
**示例 2**
@@ -190,19 +167,19 @@ ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY
PARTITION (tp1);
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1);
```
-- `use_temp_partition_name` 默认为 false，但因为待替换分区的个数和替换分区的个数不同，则该参数无效。替换后，分区名称为
tp1，p1 和 p2 不再存在。
+- `use_temp_partition_name` 默认为 false，但因待替换分区的个数与替换分区的个数不同，该参数无效。替换后，分区名称为
tp1，p1 和 p2 不再存在。
:::tip
-**替换操作的一些说明：**
+**替换操作说明：**
分区替换成功后，被替换的分区将被删除且不可恢复。
:::
## 导入临时分区
-根据导入方式的不同，指定导入临时分区的语法稍有差别。这里通过示例进行简单说明
+根据导入方式的不同，指定导入临时分区的语法稍有差别。示例如下：
-```Plain
+```sql
INSERT INTO tbl TEMPORARY PARTITION(tp1, tp2, ...) SELECT ....
curl --location-trusted -u root: -H "label:123" -H "temporary_partitions: tp1,
tp2, ..." -T testData http://host:port/api/testDb/testTbl/_stream_load
LOAD LABEL example_db.label1
@@ -225,7 +202,7 @@ FROM KAFKA
## 查询临时分区
-```Plain
+```sql
SELECT ... FROM
tbl1 TEMPORARY PARTITION(tp1, tp2, ...)
JOIN
@@ -234,7 +211,7 @@ ON ...
WHERE ...;
```
-## 和其他操作的关系
+## 与其他操作的关系
**DROP**
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/delete/table-temp-partition.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/delete/table-temp-partition.md
index d71d402fe3e..07149f097da 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/delete/table-temp-partition.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/delete/table-temp-partition.md
@@ -24,31 +24,25 @@ specific language governing permissions and limitations
under the License.
-->
-Doris 支持在分区表中添加临时分区，临时分区和正式分区不同的是，临时分区不会被正式查询查询到，只有通过特殊的查询语句才能查询。
+Doris 支持在分区表中添加临时分区。临时分区与正式分区不同，临时分区不会被常规查询检索到，只有通过特殊查询语句才能查询。
-- 临时分区的分区列和正式分区相同，且不可修改。
+- 临时分区的分区列与正式分区相同且不可修改。
-- 一张表所有临时分区之间的分区范围不可重叠，但临时分区的范围和正式分区范围可以重叠。
+- 所有临时分区之间的分区范围不可重叠，但临时分区与正式分区的范围可以重叠。
-- 临时分区的分区名称不能和正式分区以及其他临时分区重复。
+- 临时分区的名称不能与正式分区或其他临时分区重复。
-**临时分区主要用到如下场景：**
+**临时分区的主要应用场景：**
-- 原子的覆盖写操作
+-
**原子覆盖写操作**：用户希望重写某一分区的数据，但不希望在删除旧数据和导入新数据之间有数据缺失。此时，可以创建一个临时分区，将新数据导入临时分区后，通过替换操作原子性地替换原有分区。对于非分区表的原子覆盖写操作，请参阅[替换表文档](../../data-operate/delete/atomicity-replace)。
-
某些情况下，用户希望能够重写某一分区的数据，但如果采用先删除再导入的方式进行，在中间会有一段时间无法查看数据。这时，用户可以先创建一个对应的临时分区，将新的数据导入到临时分区后，通过替换操作，原子的替换原有分区，以达到目的。对于非分区表的原子覆盖写操作，请参阅[替换表文档](../../data-operate/delete/atomicity-replace)。
+- **修改分桶数**：用户在创建分区时使用了不合适的分桶数，可以创建一个新的临时分区并指定新的分桶数，然后通过 `INSERT INTO`
命令将正式分区的数据导入临时分区，再通过替换操作原子性地替换原有分区。
-- 修改分桶数
-
- 某些情况下，用户在创建分区时使用了不合适的分桶数。则用户可以先创建一个对应分区范围的临时分区，并指定新的分桶数。然后通过 `INSERT INTO`
命令将正式分区的数据导入到临时分区中，通过替换操作，原子的替换原有分区，以达到目的。
-
-- 合并或分割分区
-
- 某些情况下，用户希望对分区的范围进行修改，比如合并两个分区，或将一个大分区分割成多个小分区。则用户可以先建立对应合并或分割后范围的临时分区，然后通过
`INSERT INTO` 命令将正式分区的数据导入到临时分区中，通过替换操作，原子的替换原有分区，以达到目的。
+- **合并或分割分区**：用户希望修改分区范围，如合并两个分区或将一个大分区分割成多个小分区。可以先建立新的临时分区，然后通过 `INSERT INTO`
命令将正式分区的数据导入临时分区，再通过替换操作原子性地替换原有分区。
## 添加临时分区
-可以通过 `ALTER TABLE ADD TEMPORARY PARTITION` 语句对一个表添加临时分区：
+使用 `ALTER TABLE ADD TEMPORARY PARTITION` 语句添加临时分区：
```sql
ALTER TABLE tbl1 ADD TEMPORARY PARTITION tp1 VALUES LESS THAN("2020-02-01");
@@ -68,111 +62,95 @@ ALTER TABLE tbl3 ADD TEMPORARY PARTITION tp1 VALUES IN
("Beijing", "Shanghai")
DISTRIBUTED BY HASH(k1) BUCKETS 5;
```
-通过 `HELP ALTER TABLE;` 查看更多帮助和示例。
-
-添加操作的一些说明：
-
-- 临时分区的添加和正式分区的添加操作相似。临时分区的分区范围独立于正式分区。
-
-- 临时分区可以独立指定一些属性。包括分桶数、副本数、存储介质等信息。
## 删除临时分区
-可以通过 `ALTER TABLE DROP TEMPORARY PARTITION` 语句删除一个表的临时分区：
+使用 `ALTER TABLE DROP TEMPORARY PARTITION` 语句删除临时分区：
-```Plain
+```sql
ALTER TABLE tbl1 DROP TEMPORARY PARTITION tp1;
```
-通过 `HELP ALTER TABLE;` 查看更多帮助和示例。
-
-删除操作的一些说明：
-
-- 删除临时分区，不影响正式分区的数据。
-
## 替换正式分区
-可以通过 `ALTER TABLE REPLACE PARTITION` 语句将一个表的正式分区替换为临时分区。
+使用 `ALTER TABLE REPLACE PARTITION` 语句将正式分区替换为临时分区：
-```Plain
+```sql
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1,
tp2, tp3);
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1, tp2)
PROPERTIES (
- "strict_range" = "false",
- "use_temp_partition_name" = "true"
+ "strict_range" = "false",
+ "use_temp_partition_name" = "true"
);
```
-
-通过 `HELP ALTER TABLE;` 查看更多帮助和示例。
-
替换操作有两个特殊的可选参数：
**1. `strict_range`**
默认为 true。
-对于 Range 分区，当该参数为 true 时，表示要被替换的所有正式分区的范围并集需要和替换的临时分区的范围并集完全相同。当置为 false
时，只需要保证替换后，新的正式分区间的范围不重叠即可。
+对于 Range 分区，当该参数为 true 时，所有被替换的正式分区的范围并集需要与替换的临时分区的范围并集完全相同。当置为 false
时，只需保证替换后新的正式分区间的范围不重叠即可。
-对于 List 分区，该参数恒为 true。要被替换的所有正式分区的枚举值必须和替换的临时分区枚举值完全相同。
+对于 List 分区，该参数恒为 true。所有被替换的正式分区的枚举值必须与替换的临时分区枚举值完全相同。
**示例 1**
-```Plain
-待替换的分区 p1, p2, p3 的范围 (=> 并集)：
+```sql
+-- 待替换的分区 p1, p2, p3 的范围 (=> 并集)：
[10, 20), [20, 30), [40, 50) => [10, 30), [40, 50)
-替换分区 tp1, tp2 的范围(=> 并集)：
+-- 替换分区 tp1, tp2 的范围(=> 并集)：
[10, 30), [40, 45), [45, 50) => [10, 30), [40, 50)
-范围并集相同，则可以使用 tp1 和 tp2 替换 p1, p2, p3。
+--范围并集相同，则可以使用 tp1 和 tp2 替换 p1, p2, p3。
```
**示例 2**
```sql
-待替换的分区 p1 的范围 (=> 并集)：
+-- 待替换的分区 p1 的范围 (=> 并集)：
[10, 50) => [10, 50)
-替换分区 tp1, tp2 的范围(=> 并集)：
+-- 替换分区 tp1, tp2 的范围(=> 并集)：
[10, 30), [40, 50) => [10, 30), [40, 50)
-范围并集不相同，如果 strict_range 为 true，则不可以使用 tp1 和 tp2 替换 p1。如果为 false，且替换后的两个分区范围
[10, 30), [40, 50) 和其他正式分区不重叠，则可以替换。
+-- 范围并集不相同，如果 strict_range 为 true，则不可以使用 tp1 和 tp2 替换 p1。如果为 false，且替换后的两个分区范围
[10, 30), [40, 50) 和其他正式分区不重叠，则可以替换。
```
**示例 3**
-```Plain
-待替换的分区 p1, p2 的枚举值(=> 并集)：
+```sql
+-- 待替换的分区 p1, p2 的枚举值(=> 并集)：
(1, 2, 3), (4, 5, 6) => (1, 2, 3, 4, 5, 6)
-替换分区 tp1, tp2, tp3 的枚举值(=> 并集)：
+-- 替换分区 tp1, tp2, tp3 的枚举值(=> 并集)：
(1, 2, 3), (4), (5, 6) => (1, 2, 3, 4, 5, 6)
-枚举值并集相同，可以使用 tp1，tp2，tp3 替换 p1，p2
+-- 枚举值并集相同，可以使用 tp1，tp2，tp3 替换 p1，p2
```
**示例 4**
-```Plain
-待替换的分区 p1, p2，p3 的枚举值(=> 并集)：
+```sql
+-- 待替换的分区 p1, p2，p3 的枚举值(=> 并集)：
(("1","beijing"), ("1", "shanghai")), (("2","beijing"), ("2", "shanghai")),
(("3","beijing"), ("3", "shanghai")) => (("1","beijing"), ("1", "shanghai"),
("2","beijing"), ("2", "shanghai"), ("3","beijing"), ("3", "shanghai"))
-替换分区 tp1, tp2 的枚举值(=> 并集)：
+-- 替换分区 tp1, tp2 的枚举值(=> 并集)：
(("1","beijing"), ("1", "shanghai")), (("2","beijing"), ("2", "shanghai"),
("3","beijing"), ("3", "shanghai")) => (("1","beijing"), ("1", "shanghai"),
("2","beijing"), ("2", "shanghai"), ("3","beijing"), ("3", "shanghai"))
-枚举值并集相同，可以使用 tp1，tp2 替换 p1，p2，p3
+-- 枚举值并集相同，可以使用 tp1，tp2 替换 p1，p2，p3
```
**2. `use_temp_partition_name`**
默认为 false。
-当该参数为 false，并且待替换的分区和替换分区的个数相同时，则替换后的正式分区名称维持不变。
+当该参数为 false，并且待替换的分区和替换分区的个数相同时，替换后的正式分区名称维持不变。
-如果为 true，则替换后，正式分区的名称为替换分区的名称。下面举例说明：
+如果为 true，替换后正式分区的名称为替换分区的名称。示例如下：
**示例 1**
@@ -180,9 +158,8 @@ PROPERTIES (
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
```
-- `use_temp_partition_name` 默认为 false，则在替换后，分区的名称依然为 p1，但是相关的数据和属性都替换为 tp1 的。
-
-- 如果 `use_temp_partition_name` 默认为 true，则在替换后，分区的名称为 tp1。p1 分区不再存在。
+- `use_temp_partition_name` 默认为 false，则在替换后，分区的名称依然为 p1，但相关的数据和属性都替换为 tp1 的。
+- 如果 `use_temp_partition_name` 为 true，则在替换后，分区的名称为 tp1，p1 分区不再存在。
**示例 2**
@@ -190,19 +167,19 @@ ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY
PARTITION (tp1);
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1);
```
-- `use_temp_partition_name` 默认为 false，但因为待替换分区的个数和替换分区的个数不同，则该参数无效。替换后，分区名称为
tp1，p1 和 p2 不再存在。
+- `use_temp_partition_name` 默认为 false，但因待替换分区的个数与替换分区的个数不同，该参数无效。替换后，分区名称为
tp1，p1 和 p2 不再存在。
:::tip
-**替换操作的一些说明：**
+**替换操作说明：**
分区替换成功后，被替换的分区将被删除且不可恢复。
:::
## 导入临时分区
-根据导入方式的不同，指定导入临时分区的语法稍有差别。这里通过示例进行简单说明
+根据导入方式的不同，指定导入临时分区的语法稍有差别。示例如下：
-```Plain
+```sql
INSERT INTO tbl TEMPORARY PARTITION(tp1, tp2, ...) SELECT ....
curl --location-trusted -u root: -H "label:123" -H "temporary_partitions: tp1,
tp2, ..." -T testData http://host:port/api/testDb/testTbl/_stream_load
LOAD LABEL example_db.label1
@@ -225,7 +202,7 @@ FROM KAFKA
## 查询临时分区
-```Plain
+```sql
SELECT ... FROM
tbl1 TEMPORARY PARTITION(tp1, tp2, ...)
JOIN
@@ -234,7 +211,7 @@ ON ...
WHERE ...;
```
-## 和其他操作的关系
+## 与其他操作的关系
**DROP**
diff --git
a/versioned_docs/version-2.1/data-operate/delete/table-temp-partition.md
b/versioned_docs/version-2.1/data-operate/delete/table-temp-partition.md
index 0a7aad869da..0f548e18b5b 100644
--- a/versioned_docs/version-2.1/data-operate/delete/table-temp-partition.md
+++ b/versioned_docs/version-2.1/data-operate/delete/table-temp-partition.md
@@ -24,31 +24,25 @@ specific language governing permissions and limitations
under the License.
-->
-Doris supports adding temporary partitions to partitioned tables. Temporary
partitions differ from formal partitions in that they are not queried by formal
queries, but only by special query statements.
+Doris supports adding temporary partitions to partitioned tables. Temporary
partitions differ from regular partitions in that they are not retrieved by
regular queries and can only be queried through special query statements.
-- The partition columns of the temporary partition are the same as the formal
partition and cannot be modified.
+- The partition columns of temporary partitions are the same as those of
regular partitions and cannot be modified.
-- The partition ranges of all temporary partitions of a table cannot overlap,
but the ranges of temporary partitions and formal partitions can overlap.
+- The partition ranges of all temporary partitions cannot overlap, but the
ranges of temporary partitions and regular partitions can overlap.
-- The partition name of the temporary partition cannot be the same as the
formal partitions and other temporary partitions.
+- The names of temporary partitions cannot duplicate those of regular
partitions or other temporary partitions.
-Temporary Partitions are mainly used in the following scenarios:
+**Main application scenarios for temporary partitions:**
-- Atomic overwrite write operations
+- **Atomic overwrite operation**: Users can rewrite the data of a partition
without data loss between deleting old data and importing new data. In this
case, a temporary partition can be created, new data can be imported into the
temporary partition, and then the original partition can be atomically replaced
through a replace operation. For atomic overwrite operations on non-partitioned
tables, refer to the [replace table
documentation](../../data-operate/delete/atomicity-replace).
-In some cases, users want to rewrite the data of a certain partition, but if
they do it by deleting and then importing, there will be a period of time in
the middle when they cannot view the data. In this case, the user can create a
corresponding Temporary Partition first, and after importing the new data into
the Temporary Partition, replace the original partition atomically through the
Replace operation to achieve the purpose. For the atomic overwrite write
operation of non-partitioned [...]
+- **Modify the number of buckets**: If an inappropriate number of buckets was
used when creating a partition, a new temporary partition can be created with
the specified new number of buckets. Then, the data of the regular partition
can be imported into the temporary partition using the `INSERT INTO` command,
and the original partition can be atomically replaced through a replace
operation.
-- Modifying the number of buckets
-
-In some cases, users use an inappropriate bucket number when creating
partitions. Then the user can first create a Temporary Partition corresponding
to the partition range and specify the new bucket number. Then import the data
of the formal partition into the Temporary Partition through the `INSERT INTO`
command, and replace the original partition atomically through the Replace
operation to achieve the purpose.
-
-- Merge or split partition
-
-In some cases, users want to modify the scope of partitions, such as merging
two partitions, or splitting a large partition into several small partitions.
You can first create a Temporary Partition corresponding to the scope of the
merged or partitioned partition, and then import the data of the official
partition into the Temporary Partition through the `INSERT INTO` command, and
then replace the original partition atomically through the Replacement
operation, in order to achieve the purpose.
+- **Merge or split partitions**: Users can modify the partition range, such as
merging two partitions or splitting a large partition into multiple smaller
partitions. A new temporary partition can be created, the data of the regular
partition can be imported into the temporary partition using the `INSERT INTO`
command, and the original partition can be atomically replaced through a
replace operation.
## Add Temporary Partition
-You can add temporary partitions to a table with the `ALTER TABLE ADD
TEMPORARY PARTITION` statement:
+Use the `ALTER TABLE ADD TEMPORARY PARTITION` statement to add a temporary
partition:
```sql
ALTER TABLE tbl1 ADD TEMPORARY PARTITION tp1 VALUES LESS THAN("2020-02-01");
@@ -68,31 +62,17 @@ ALTER TABLE tbl3 ADD TEMPORARY PARTITION tp1 VALUES IN
("Beijing", "Shanghai")
DISTRIBUTED BY HASH(k1) BUCKETS 5;
```
-See `HELP ALTER TABLE;` for more help and examples.
-
-Some instructions for adding operations:
+## Drop Temporary Partition
-- Adding a temporary partition is similar to adding a formal partition. The
partition range of the temporary partition is independent of the formal
partition.
+Use the `ALTER TABLE DROP TEMPORARY PARTITION` statement to drop a temporary
partition:
-- Temporary partition can independently specify some attributes. Includes
information such as the number of buckets, the number of replicas, or the
storage medium.
-
-### Delete Temporary Partition
-
-A table's temporary partition can be dropped with the `ALTER TABLE DROP
TEMPORARY PARTITION` statement:
-
-```Plain
+```sql
ALTER TABLE tbl1 DROP TEMPORARY PARTITION tp1;
```
-See `HELP ALTER TABLE;` for more help and examples.
+## Replace Regular Partition
-Some instructions for the DELETE:
-
-- Deleting the temporary partition will not affect the data of the formal
partition.
-
-### Replace Partition
-
-You can replace formal partitions of a table with temporary partitions with
the `ALTER TABLE REPLACE PARTITION` statement.
+Use the `ALTER TABLE REPLACE PARTITION` statement to replace a regular
partition with a temporary partition:
```sql
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
@@ -101,76 +81,76 @@ ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY
PARTITION (tp1, tp2,
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1, tp2)
PROPERTIES (
- "strict_range" = "false",
- "use_temp_partition_name" = "true"
+ "strict_range" = "false",
+ "use_temp_partition_name" = "true"
);
```
-See `HELP ALTER TABLE;` for more help and examples.
-
-The replace operation has two special optional parameters:
+There are two special optional parameters for the replace operation:
**1. `strict_range`**
-The default is true.
+Default is true.
-For Range partition, When this parameter is true, the range union of all
formal partitions to be replaced needs to be the same as the range union of the
temporary partitions to be replaced. When set to false, you only need to ensure
that the range between the new formal partitions does not overlap after
replacement.
+For Range partitions, when this parameter is true, the union of the ranges of
all replaced regular partitions must be exactly the same as the union of the
ranges of the replacing temporary partitions. When set to false, it only needs
to ensure that the ranges of the new regular partitions do not overlap after
replacement.
-For List partition, this parameter is always true, and the enumeration values
of all full partitions to be replaced must be identical to the enumeration
values of the temporary partitions to be replaced.
+For List partitions, this parameter is always true. The enumeration values of
all replaced regular partitions must be exactly the same as the enumeration
values of the replacing temporary partitions.
**Example 1**
```sql
--- Range of partitions p1, p2, p3 to be replaced (=> union):
-(10, 20), [20, 30), [40, 50) => [10, 30), [40, 50)
+-- The range of partitions p1, p2, p3 to be replaced (=> union):
+[10, 20), [20, 30), [40, 50) => [10, 30), [40, 50)
---Replace the range of partitions tp1, tp2 (=> union):
-(10, 30), [40, 45), [45, 50) => [10, 30), [40, 50)
+-- The range of replacing partitions tp1, tp2 (=> union):
+[10, 30), [40, 45), [45, 50) => [10, 30), [40, 50)
---The union of ranges is the same, so you can use tp1 and tp2 to replace p1,
p2, p3.
+-- The union of ranges is the same, so tp1 and tp2 can replace p1, p2, p3.
```
**Example 2**
```sql
---Range of partition p1 to be replaced (=> union):
+-- The range of partition p1 to be replaced (=> union):
[10, 50) => [10, 50)
---Replace the range of partitions tp1, tp2 (=> union):
+-- The range of replacing partitions tp1, tp2 (=> union):
[10, 30), [40, 50) => [10, 30), [40, 50)
---The union of ranges is not the same. If strict_range is true, you cannot use
tp1 and tp2 to replace p1. If false, and the two partition ranges [10, 30),
[40, 50) and the other formal partitions do not overlap, they can be replaced.
+-- The union of ranges is not the same. If strict_range is true, tp1 and tp2
cannot replace p1. If it is false, and the ranges of the two partitions after
replacement [10, 30), [40, 50) do not overlap with other regular partitions,
they can replace p1.
```
**Example 3**
```sql
---Enumerated values of partitions p1, p2 to be replaced (=> union).
+-- The enumeration values of partitions p1, p2 to be replaced (=> union):
(1, 2, 3), (4, 5, 6) => (1, 2, 3, 4, 5, 6)
---Replace the enumerated values of partitions tp1, tp2, tp3 (=> union).
+
+-- The enumeration values of replacing partitions tp1, tp2, tp3 (=> union):
(1, 2, 3), (4), (5, 6) => (1, 2, 3, 4, 5, 6)
---The enumeration values are the same, you can use tp1, tp2, tp3 to replace
p1, p2
+
+-- The union of enumeration values is the same, so tp1, tp2, tp3 can replace
p1, p2.
```
**Example 4**
```sql
---Enumerated values of partitions p1, p2, p3 to be replaced (=> union).
+-- The enumeration values of partitions p1, p2, p3 to be replaced (=> union):
(("1","beijing"), ("1", "shanghai")), (("2","beijing"), ("2", "shanghai")),
(("3","beijing"), ("3", "shanghai")) => (("1","beijing"), ("1", "shanghai"),
("2","beijing"), ("2", "shanghai"), ("3","beijing"), ("3", "shanghai"))
---Replace the enumerated values of partitions tp1, tp2 (=> union).
+-- The enumeration values of replacing partitions tp1, tp2 (=> union):
(("1","beijing"), ("1", "shanghai")), (("2","beijing"), ("2", "shanghai"),
("3","beijing"), ("3", "shanghai")) => (("1","beijing"), ("1", "shanghai"),
("2","beijing"), ("2", "shanghai"), ("3","beijing"), ("3", "shanghai"))
---The enumeration values are the same, you can use tp1, tp2 to replace p1, p2,
p3
+-- The union of enumeration values is the same, so tp1, tp2 can replace p1,
p2, p3.
```
**2. `use_temp_partition_name`**
-The default is false.
+Default is false.
-When this parameter is false, and the number of partitions to be replaced is
the same as the number of replacement partitions, the name of the formal
partition after the replacement remains unchanged.
+When this parameter is false, and the number of partitions to be replaced is
the same as the number of replacing partitions, the names of the partitions
remain unchanged after replacement.
-If true, after replacement, the name of the formal partition is the name of
the replacement partition. Here are some examples:
+If it is true, the names of the partitions after replacement will be the names
of the replacing partitions. Examples are as follows:
**Example 1**
@@ -178,27 +158,26 @@ If true, after replacement, the name of the formal
partition is the name of the
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
```
-`use_temp_partition_name` is **false** by default. After replacement, the
partition name is still p1, but the related data and attributes are replaced
with tp1.
-
-If `use_temp_partition_name` is **true** by default, the name of the partition
is tp1 after replacement. The p1 partition no longer exists.
+- `use_temp_partition_name` defaults to false, so after replacement, the
partition name remains p1, but the data and properties are replaced with those
of tp1.
+- If `use_temp_partition_name` is true, after replacement, the partition name
is tp1, and p1 no longer exists.
**Example 2**
-```Plain
+```sql
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1);
```
-`use_temp_partition_name` is **false** by default, but this parameter is
invalid because the number of partitions to be replaced and the number of
replacement partitions are different. After the replacement, the partition name
is tp1, and p1 and p2 no longer exist.
+- `use_temp_partition_name` defaults to false, but since the number of
partitions to be replaced is different from the number of replacing partitions,
this parameter is invalid. After replacement, the partition name is tp1, and p1
and p2 no longer exist.
-:::tip Tip
-**Some instructions for the replacement operation:**
+:::tip
+**Explanation of the replace operation:**
-After the partition is replaced successfully, the replaced partition will be
deleted and cannot be recovered.
+After the partition replacement is successful, the replaced partitions will be
deleted and cannot be recovered.
:::
-## Importing Temporary Partitions
+## Import Temporary Partition
-Depending on the import method, the syntax for specifying the import of
Temporary Partitions is slightly different. Here is a brief explanation with an
example:
+The syntax for specifying the import of temporary partitions varies slightly
depending on the import method. Examples are as follows:
```sql
INSERT INTO tbl TEMPORARY PARTITION(tp1, tp2, ...) SELECT ....
@@ -221,7 +200,7 @@ FROM KAFKA
(...);
```
-## Query Temporary Partitions
+## Query Temporary Partition
```sql
SELECT ... FROM
@@ -232,26 +211,27 @@ ON ...
WHERE ...;
```
-## Relationship to Other Operations
+## Relationship with Other Operations
-### DROP
+**DROP**
-- After using the `DROP` operation to directly drop the database or table, you
can recover the database or table (within a limited time) through the `RECOVER`
command, but the temporary partition will not be recovered.
+- After using the Drop operation to directly delete a database or table, the
database or table can be recovered using the Recover command (within a limited
time), but temporary partitions will not be recovered.
-- After the formal partition is dropped using the `ALTER` command, the
partition can be recovered by the `RECOVER` command (within a limited time).
Operating a formal partition is not related to a temporary partition.
+- After using the Alter command to delete a regular partition, the partition
can be recovered using the Recover command (within a limited time). This
operation is unrelated to temporary partitions.
-- After the temporary partition is dropped using the `ALTER` command, the
temporary partition cannot be recovered through the `RECOVER` command.
+- After using the Alter command to delete a temporary partition, the temporary
partition cannot be recovered using the Recover command.
-### TRUNCATE
+**TRUNCATE**
-- Use the `TRUNCATE` command to empty the table. The temporary partition of
the table will be deleted and cannot be recovered.
+- Using the Truncate command to empty a table will delete the table's
temporary partitions, and they cannot be recovered.
-- When using `TRUNCATE` command to empty the formal partition, it will not
affect the temporary partition.
+- Using the Truncate command to empty a regular partition does not affect
temporary partitions.
-- You cannot use the `TRUNCATE` command to empty the temporary partition.
+- The Truncate command cannot be used to empty temporary partitions.
-### ALTER
+**ALTER**
-- When the table has a temporary partition, you cannot use the `ALTER` command
to perform Schema Change, Rollup, etc. on the table.
+- When a table has temporary partitions, the Alter command cannot be used to
perform Schema Change, Rollup, or other change operations on the table.
-- You cannot add temporary partitions to a table while the table is undergoing
a alter operation.
\ No newline at end of file
+- When a table is undergoing change operations, temporary partitions cannot be
added to the table.
+```
\ No newline at end of file
diff --git
a/versioned_docs/version-3.0/data-operate/delete/table-temp-partition.md
b/versioned_docs/version-3.0/data-operate/delete/table-temp-partition.md
index 0a7aad869da..0f548e18b5b 100644
--- a/versioned_docs/version-3.0/data-operate/delete/table-temp-partition.md
+++ b/versioned_docs/version-3.0/data-operate/delete/table-temp-partition.md
@@ -24,31 +24,25 @@ specific language governing permissions and limitations
under the License.
-->
-Doris supports adding temporary partitions to partitioned tables. Temporary
partitions differ from formal partitions in that they are not queried by formal
queries, but only by special query statements.
+Doris supports adding temporary partitions to partitioned tables. Temporary
partitions differ from regular partitions in that they are not retrieved by
regular queries and can only be queried through special query statements.
-- The partition columns of the temporary partition are the same as the formal
partition and cannot be modified.
+- The partition columns of temporary partitions are the same as those of
regular partitions and cannot be modified.
-- The partition ranges of all temporary partitions of a table cannot overlap,
but the ranges of temporary partitions and formal partitions can overlap.
+- The partition ranges of all temporary partitions cannot overlap, but the
ranges of temporary partitions and regular partitions can overlap.
-- The partition name of the temporary partition cannot be the same as the
formal partitions and other temporary partitions.
+- The names of temporary partitions cannot duplicate those of regular
partitions or other temporary partitions.
-Temporary Partitions are mainly used in the following scenarios:
+**Main application scenarios for temporary partitions:**
-- Atomic overwrite write operations
+- **Atomic overwrite operation**: Users can rewrite the data of a partition
without data loss between deleting old data and importing new data. In this
case, a temporary partition can be created, new data can be imported into the
temporary partition, and then the original partition can be atomically replaced
through a replace operation. For atomic overwrite operations on non-partitioned
tables, refer to the [replace table
documentation](../../data-operate/delete/atomicity-replace).
-In some cases, users want to rewrite the data of a certain partition, but if
they do it by deleting and then importing, there will be a period of time in
the middle when they cannot view the data. In this case, the user can create a
corresponding Temporary Partition first, and after importing the new data into
the Temporary Partition, replace the original partition atomically through the
Replace operation to achieve the purpose. For the atomic overwrite write
operation of non-partitioned [...]
+- **Modify the number of buckets**: If an inappropriate number of buckets was
used when creating a partition, a new temporary partition can be created with
the specified new number of buckets. Then, the data of the regular partition
can be imported into the temporary partition using the `INSERT INTO` command,
and the original partition can be atomically replaced through a replace
operation.
-- Modifying the number of buckets
-
-In some cases, users use an inappropriate bucket number when creating
partitions. Then the user can first create a Temporary Partition corresponding
to the partition range and specify the new bucket number. Then import the data
of the formal partition into the Temporary Partition through the `INSERT INTO`
command, and replace the original partition atomically through the Replace
operation to achieve the purpose.
-
-- Merge or split partition
-
-In some cases, users want to modify the scope of partitions, such as merging
two partitions, or splitting a large partition into several small partitions.
You can first create a Temporary Partition corresponding to the scope of the
merged or partitioned partition, and then import the data of the official
partition into the Temporary Partition through the `INSERT INTO` command, and
then replace the original partition atomically through the Replacement
operation, in order to achieve the purpose.
+- **Merge or split partitions**: Users can modify the partition range, such as
merging two partitions or splitting a large partition into multiple smaller
partitions. A new temporary partition can be created, the data of the regular
partition can be imported into the temporary partition using the `INSERT INTO`
command, and the original partition can be atomically replaced through a
replace operation.
## Add Temporary Partition
-You can add temporary partitions to a table with the `ALTER TABLE ADD
TEMPORARY PARTITION` statement:
+Use the `ALTER TABLE ADD TEMPORARY PARTITION` statement to add a temporary
partition:
```sql
ALTER TABLE tbl1 ADD TEMPORARY PARTITION tp1 VALUES LESS THAN("2020-02-01");
@@ -68,31 +62,17 @@ ALTER TABLE tbl3 ADD TEMPORARY PARTITION tp1 VALUES IN
("Beijing", "Shanghai")
DISTRIBUTED BY HASH(k1) BUCKETS 5;
```
-See `HELP ALTER TABLE;` for more help and examples.
-
-Some instructions for adding operations:
+## Drop Temporary Partition
-- Adding a temporary partition is similar to adding a formal partition. The
partition range of the temporary partition is independent of the formal
partition.
+Use the `ALTER TABLE DROP TEMPORARY PARTITION` statement to drop a temporary
partition:
-- Temporary partition can independently specify some attributes. Includes
information such as the number of buckets, the number of replicas, or the
storage medium.
-
-### Delete Temporary Partition
-
-A table's temporary partition can be dropped with the `ALTER TABLE DROP
TEMPORARY PARTITION` statement:
-
-```Plain
+```sql
ALTER TABLE tbl1 DROP TEMPORARY PARTITION tp1;
```
-See `HELP ALTER TABLE;` for more help and examples.
+## Replace Regular Partition
-Some instructions for the DELETE:
-
-- Deleting the temporary partition will not affect the data of the formal
partition.
-
-### Replace Partition
-
-You can replace formal partitions of a table with temporary partitions with
the `ALTER TABLE REPLACE PARTITION` statement.
+Use the `ALTER TABLE REPLACE PARTITION` statement to replace a regular
partition with a temporary partition:
```sql
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
@@ -101,76 +81,76 @@ ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY
PARTITION (tp1, tp2,
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1, tp2)
PROPERTIES (
- "strict_range" = "false",
- "use_temp_partition_name" = "true"
+ "strict_range" = "false",
+ "use_temp_partition_name" = "true"
);
```
-See `HELP ALTER TABLE;` for more help and examples.
-
-The replace operation has two special optional parameters:
+There are two special optional parameters for the replace operation:
**1. `strict_range`**
-The default is true.
+Default is true.
-For Range partition, When this parameter is true, the range union of all
formal partitions to be replaced needs to be the same as the range union of the
temporary partitions to be replaced. When set to false, you only need to ensure
that the range between the new formal partitions does not overlap after
replacement.
+For Range partitions, when this parameter is true, the union of the ranges of
all replaced regular partitions must be exactly the same as the union of the
ranges of the replacing temporary partitions. When set to false, it only needs
to ensure that the ranges of the new regular partitions do not overlap after
replacement.
-For List partition, this parameter is always true, and the enumeration values
of all full partitions to be replaced must be identical to the enumeration
values of the temporary partitions to be replaced.
+For List partitions, this parameter is always true. The enumeration values of
all replaced regular partitions must be exactly the same as the enumeration
values of the replacing temporary partitions.
**Example 1**
```sql
--- Range of partitions p1, p2, p3 to be replaced (=> union):
-(10, 20), [20, 30), [40, 50) => [10, 30), [40, 50)
+-- The range of partitions p1, p2, p3 to be replaced (=> union):
+[10, 20), [20, 30), [40, 50) => [10, 30), [40, 50)
---Replace the range of partitions tp1, tp2 (=> union):
-(10, 30), [40, 45), [45, 50) => [10, 30), [40, 50)
+-- The range of replacing partitions tp1, tp2 (=> union):
+[10, 30), [40, 45), [45, 50) => [10, 30), [40, 50)
---The union of ranges is the same, so you can use tp1 and tp2 to replace p1,
p2, p3.
+-- The union of ranges is the same, so tp1 and tp2 can replace p1, p2, p3.
```
**Example 2**
```sql
---Range of partition p1 to be replaced (=> union):
+-- The range of partition p1 to be replaced (=> union):
[10, 50) => [10, 50)
---Replace the range of partitions tp1, tp2 (=> union):
+-- The range of replacing partitions tp1, tp2 (=> union):
[10, 30), [40, 50) => [10, 30), [40, 50)
---The union of ranges is not the same. If strict_range is true, you cannot use
tp1 and tp2 to replace p1. If false, and the two partition ranges [10, 30),
[40, 50) and the other formal partitions do not overlap, they can be replaced.
+-- The union of ranges is not the same. If strict_range is true, tp1 and tp2
cannot replace p1. If it is false, and the ranges of the two partitions after
replacement [10, 30), [40, 50) do not overlap with other regular partitions,
they can replace p1.
```
**Example 3**
```sql
---Enumerated values of partitions p1, p2 to be replaced (=> union).
+-- The enumeration values of partitions p1, p2 to be replaced (=> union):
(1, 2, 3), (4, 5, 6) => (1, 2, 3, 4, 5, 6)
---Replace the enumerated values of partitions tp1, tp2, tp3 (=> union).
+
+-- The enumeration values of replacing partitions tp1, tp2, tp3 (=> union):
(1, 2, 3), (4), (5, 6) => (1, 2, 3, 4, 5, 6)
---The enumeration values are the same, you can use tp1, tp2, tp3 to replace
p1, p2
+
+-- The union of enumeration values is the same, so tp1, tp2, tp3 can replace
p1, p2.
```
**Example 4**
```sql
---Enumerated values of partitions p1, p2, p3 to be replaced (=> union).
+-- The enumeration values of partitions p1, p2, p3 to be replaced (=> union):
(("1","beijing"), ("1", "shanghai")), (("2","beijing"), ("2", "shanghai")),
(("3","beijing"), ("3", "shanghai")) => (("1","beijing"), ("1", "shanghai"),
("2","beijing"), ("2", "shanghai"), ("3","beijing"), ("3", "shanghai"))
---Replace the enumerated values of partitions tp1, tp2 (=> union).
+-- The enumeration values of replacing partitions tp1, tp2 (=> union):
(("1","beijing"), ("1", "shanghai")), (("2","beijing"), ("2", "shanghai"),
("3","beijing"), ("3", "shanghai")) => (("1","beijing"), ("1", "shanghai"),
("2","beijing"), ("2", "shanghai"), ("3","beijing"), ("3", "shanghai"))
---The enumeration values are the same, you can use tp1, tp2 to replace p1, p2,
p3
+-- The union of enumeration values is the same, so tp1, tp2 can replace p1,
p2, p3.
```
**2. `use_temp_partition_name`**
-The default is false.
+Default is false.
-When this parameter is false, and the number of partitions to be replaced is
the same as the number of replacement partitions, the name of the formal
partition after the replacement remains unchanged.
+When this parameter is false, and the number of partitions to be replaced is
the same as the number of replacing partitions, the names of the partitions
remain unchanged after replacement.
-If true, after replacement, the name of the formal partition is the name of
the replacement partition. Here are some examples:
+If it is true, the names of the partitions after replacement will be the names
of the replacing partitions. Examples are as follows:
**Example 1**
@@ -178,27 +158,26 @@ If true, after replacement, the name of the formal
partition is the name of the
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
```
-`use_temp_partition_name` is **false** by default. After replacement, the
partition name is still p1, but the related data and attributes are replaced
with tp1.
-
-If `use_temp_partition_name` is **true** by default, the name of the partition
is tp1 after replacement. The p1 partition no longer exists.
+- `use_temp_partition_name` defaults to false, so after replacement, the
partition name remains p1, but the data and properties are replaced with those
of tp1.
+- If `use_temp_partition_name` is true, after replacement, the partition name
is tp1, and p1 no longer exists.
**Example 2**
-```Plain
+```sql
ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1);
```
-`use_temp_partition_name` is **false** by default, but this parameter is
invalid because the number of partitions to be replaced and the number of
replacement partitions are different. After the replacement, the partition name
is tp1, and p1 and p2 no longer exist.
+- `use_temp_partition_name` defaults to false, but since the number of
partitions to be replaced is different from the number of replacing partitions,
this parameter is invalid. After replacement, the partition name is tp1, and p1
and p2 no longer exist.
-:::tip Tip
-**Some instructions for the replacement operation:**
+:::tip
+**Explanation of the replace operation:**
-After the partition is replaced successfully, the replaced partition will be
deleted and cannot be recovered.
+After the partition replacement is successful, the replaced partitions will be
deleted and cannot be recovered.
:::
-## Importing Temporary Partitions
+## Import Temporary Partition
-Depending on the import method, the syntax for specifying the import of
Temporary Partitions is slightly different. Here is a brief explanation with an
example:
+The syntax for specifying the import of temporary partitions varies slightly
depending on the import method. Examples are as follows:
```sql
INSERT INTO tbl TEMPORARY PARTITION(tp1, tp2, ...) SELECT ....
@@ -221,7 +200,7 @@ FROM KAFKA
(...);
```
-## Query Temporary Partitions
+## Query Temporary Partition
```sql
SELECT ... FROM
@@ -232,26 +211,27 @@ ON ...
WHERE ...;
```
-## Relationship to Other Operations
+## Relationship with Other Operations
-### DROP
+**DROP**
-- After using the `DROP` operation to directly drop the database or table, you
can recover the database or table (within a limited time) through the `RECOVER`
command, but the temporary partition will not be recovered.
+- After using the Drop operation to directly delete a database or table, the
database or table can be recovered using the Recover command (within a limited
time), but temporary partitions will not be recovered.
-- After the formal partition is dropped using the `ALTER` command, the
partition can be recovered by the `RECOVER` command (within a limited time).
Operating a formal partition is not related to a temporary partition.
+- After using the Alter command to delete a regular partition, the partition
can be recovered using the Recover command (within a limited time). This
operation is unrelated to temporary partitions.
-- After the temporary partition is dropped using the `ALTER` command, the
temporary partition cannot be recovered through the `RECOVER` command.
+- After using the Alter command to delete a temporary partition, the temporary
partition cannot be recovered using the Recover command.
-### TRUNCATE
+**TRUNCATE**
-- Use the `TRUNCATE` command to empty the table. The temporary partition of
the table will be deleted and cannot be recovered.
+- Using the Truncate command to empty a table will delete the table's
temporary partitions, and they cannot be recovered.
-- When using `TRUNCATE` command to empty the formal partition, it will not
affect the temporary partition.
+- Using the Truncate command to empty a regular partition does not affect
temporary partitions.
-- You cannot use the `TRUNCATE` command to empty the temporary partition.
+- The Truncate command cannot be used to empty temporary partitions.
-### ALTER
+**ALTER**
-- When the table has a temporary partition, you cannot use the `ALTER` command
to perform Schema Change, Rollup, etc. on the table.
+- When a table has temporary partitions, the Alter command cannot be used to
perform Schema Change, Rollup, or other change operations on the table.
-- You cannot add temporary partitions to a table while the table is undergoing
a alter operation.
\ No newline at end of file
+- When a table is undergoing change operations, temporary partitions cannot be
added to the table.
+```
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
