This is an automated email from the ASF dual-hosted git repository.
zclll 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 da075fa9e5b Clarify auto partition lifecycle (#3087)
da075fa9e5b is described below
commit da075fa9e5b53de828d91c4c726f423201850089
Author: zclllyybb <[email protected]>
AuthorDate: Thu Nov 13 15:26:49 2025 +0800
Clarify auto partition lifecycle (#3087)
## Versions
- [x] dev
- [x] 4.x
- [ ] 3.x
- [ ] 2.1
## Languages
- [x] Chinese
- [x] English
---
.../table-design/data-partitioning/auto-partitioning.md | 8 +++++---
.../data-partitioning/dynamic-partitioning.md | 7 +------
.../table-design/data-partitioning/auto-partitioning.md | 4 +++-
.../data-partitioning/dynamic-partitioning.md | 3 +--
.../table-design/data-partitioning/auto-partitioning.md | 4 +++-
.../data-partitioning/dynamic-partitioning.md | 3 +--
static/images/blogs/auto-partition-lifetime1.png | Bin 0 -> 55871 bytes
.../table-design/data-partitioning/auto-partitioning.md | 8 +++++---
.../data-partitioning/dynamic-partitioning.md | 7 +------
9 files changed, 20 insertions(+), 24 deletions(-)
diff --git a/docs/table-design/data-partitioning/auto-partitioning.md
b/docs/table-design/data-partitioning/auto-partitioning.md
index 0ac96d7f00c..d98a8ad6ea7 100644
--- a/docs/table-design/data-partitioning/auto-partitioning.md
+++ b/docs/table-design/data-partitioning/auto-partitioning.md
@@ -255,12 +255,14 @@ properties(
);
```
-This represents keeping only the top 3 partitions with the largest date values
in the history. Assuming the current date is `2025-10-21`, and inserting data
for each day from `2025-10-16` to `2025-10-23`, after one recycling, the
remaining partitions are as follows:
+This represents keeping only the top 3 partitions with the largest date values
in the history. Assuming the current date is `2025-10-21`, and inserting data
for each day from `2025-10-16` to `2025-10-23`, after one recycling, as shown
in the figure, the remaining partitions are as follows:
+
+
- p20251018000000
- p20251019000000
-- p20251020000000 (The following partition and above: Only keep three
historical partitions)
-- p20251021000000 (The following partition and below: The current and future
partitions are not affected)
+- p20251020000000 (This partition and above: Only keep three historical
partitions)
+- p20251021000000 (This partition and below: The current and future partitions
are not affected)
- p20251022000000
- p20251023000000
diff --git a/docs/table-design/data-partitioning/dynamic-partitioning.md
b/docs/table-design/data-partitioning/dynamic-partitioning.md
index df3081f2131..3cdcbf76991 100644
--- a/docs/table-design/data-partitioning/dynamic-partitioning.md
+++ b/docs/table-design/data-partitioning/dynamic-partitioning.md
@@ -1,6 +1,6 @@
---
{
- "title": "Dynamic Partitioning",
+ "title": "Dynamic Partitioning(Outdated)",
"language": "zh-CN"
}
---
@@ -15,7 +15,6 @@ The diagram below illustrates lifecycle management using
dynamic partitioning, w
According to the above rules, as time progresses, a total of 4 partitions will
always be retained: the partition from the past day, the current day partition,
and the partitions for the next two days.
-
## Usage Restrictions
@@ -30,7 +29,6 @@ When using dynamic partitioning, the following rules must be
followed:
When creating a table, you can create a dynamic partitioned table by
specifying the `dynamic_partition` property.
-
```sql
CREATE TABLE test_dynamic_partition(
order_id BIGINT,
@@ -208,6 +206,3 @@ PROPERTIES (
"dynamic_partition.reserved_history_periods"="[2020-06-01,2020-06-20],[2020-10-31,2020-11-15]"
);
```
-
-
-
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/auto-partitioning.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/auto-partitioning.md
index db479c72b70..f9c1e964903 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/auto-partitioning.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/auto-partitioning.md
@@ -244,7 +244,9 @@ properties(
);
```
-这代表只保留历史分区日期值最大的 3 个分区。假设当前日期为 `2025-10-21`，插入 `2025-10-16` 至 `2025-10-23`
中每一天的数据。则经过一次回收，剩余如下 6 个分区：
+这代表只保留历史分区日期值最大的 3 个分区。假设当前日期为 `2025-10-21`，插入 `2025-10-16` 至 `2025-10-23`
中每一天的数据。则经过一次回收，如图所示，剩余如下 6 个分区：
+
+
- p20251018000000
- p20251019000000
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/dynamic-partitioning.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/dynamic-partitioning.md
index eced1153f51..4d72410c262 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/dynamic-partitioning.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/dynamic-partitioning.md
@@ -1,6 +1,6 @@
---
{
- "title": "动态分区",
+ "title": "动态分区（不推荐）",
"language": "zh-CN"
}
---
@@ -211,4 +211,3 @@ PROPERTIES (
"dynamic_partition.reserved_history_periods"="[2020-06-01,2020-06-20],[2020-10-31,2020-11-15]"
);
```
-
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-partitioning/auto-partitioning.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-partitioning/auto-partitioning.md
index db479c72b70..f9c1e964903 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-partitioning/auto-partitioning.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-partitioning/auto-partitioning.md
@@ -244,7 +244,9 @@ properties(
);
```
-这代表只保留历史分区日期值最大的 3 个分区。假设当前日期为 `2025-10-21`，插入 `2025-10-16` 至 `2025-10-23`
中每一天的数据。则经过一次回收，剩余如下 6 个分区：
+这代表只保留历史分区日期值最大的 3 个分区。假设当前日期为 `2025-10-21`，插入 `2025-10-16` 至 `2025-10-23`
中每一天的数据。则经过一次回收，如图所示，剩余如下 6 个分区：
+
+
- p20251018000000
- p20251019000000
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
index eced1153f51..4d72410c262 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
@@ -1,6 +1,6 @@
---
{
- "title": "动态分区",
+ "title": "动态分区（不推荐）",
"language": "zh-CN"
}
---
@@ -211,4 +211,3 @@ PROPERTIES (
"dynamic_partition.reserved_history_periods"="[2020-06-01,2020-06-20],[2020-10-31,2020-11-15]"
);
```
-
diff --git a/static/images/blogs/auto-partition-lifetime1.png
b/static/images/blogs/auto-partition-lifetime1.png
new file mode 100644
index 00000000000..712435e0519
Binary files /dev/null and b/static/images/blogs/auto-partition-lifetime1.png
differ
diff --git
a/versioned_docs/version-4.x/table-design/data-partitioning/auto-partitioning.md
b/versioned_docs/version-4.x/table-design/data-partitioning/auto-partitioning.md
index 0ac96d7f00c..d98a8ad6ea7 100644
---
a/versioned_docs/version-4.x/table-design/data-partitioning/auto-partitioning.md
+++
b/versioned_docs/version-4.x/table-design/data-partitioning/auto-partitioning.md
@@ -255,12 +255,14 @@ properties(
);
```
-This represents keeping only the top 3 partitions with the largest date values
in the history. Assuming the current date is `2025-10-21`, and inserting data
for each day from `2025-10-16` to `2025-10-23`, after one recycling, the
remaining partitions are as follows:
+This represents keeping only the top 3 partitions with the largest date values
in the history. Assuming the current date is `2025-10-21`, and inserting data
for each day from `2025-10-16` to `2025-10-23`, after one recycling, as shown
in the figure, the remaining partitions are as follows:
+
+
- p20251018000000
- p20251019000000
-- p20251020000000 (The following partition and above: Only keep three
historical partitions)
-- p20251021000000 (The following partition and below: The current and future
partitions are not affected)
+- p20251020000000 (This partition and above: Only keep three historical
partitions)
+- p20251021000000 (This partition and below: The current and future partitions
are not affected)
- p20251022000000
- p20251023000000
diff --git
a/versioned_docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
b/versioned_docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
index df3081f2131..3cdcbf76991 100644
---
a/versioned_docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
+++
b/versioned_docs/version-4.x/table-design/data-partitioning/dynamic-partitioning.md
@@ -1,6 +1,6 @@
---
{
- "title": "Dynamic Partitioning",
+ "title": "Dynamic Partitioning(Outdated)",
"language": "zh-CN"
}
---
@@ -15,7 +15,6 @@ The diagram below illustrates lifecycle management using
dynamic partitioning, w
According to the above rules, as time progresses, a total of 4 partitions will
always be retained: the partition from the past day, the current day partition,
and the partitions for the next two days.
-
## Usage Restrictions
@@ -30,7 +29,6 @@ When using dynamic partitioning, the following rules must be
followed:
When creating a table, you can create a dynamic partitioned table by
specifying the `dynamic_partition` property.
-
```sql
CREATE TABLE test_dynamic_partition(
order_id BIGINT,
@@ -208,6 +206,3 @@ PROPERTIES (
"dynamic_partition.reserved_history_periods"="[2020-06-01,2020-06-20],[2020-10-31,2020-11-15]"
);
```
-
-
-
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
