This is an automated email from the ASF dual-hosted git repository.

luoyuxia pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/fluss.git


The following commit(s) were added to refs/heads/main by this push:
     new 46f14cf2d [docs] Clarify auto partition retention alter support (#3339)
46f14cf2d is described below

commit 46f14cf2d12e168e4c7281c07be0802f8607baef
Author: yuxia Luo <[email protected]>
AuthorDate: Mon May 25 17:32:50 2026 +0800

    [docs] Clarify auto partition retention alter support (#3339)
---
 website/docs/table-design/data-distribution/partitioning.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/docs/table-design/data-distribution/partitioning.md 
b/website/docs/table-design/data-distribution/partitioning.md
index ffeef84f6..30460933d 100644
--- a/website/docs/table-design/data-distribution/partitioning.md
+++ b/website/docs/table-design/data-distribution/partitioning.md
@@ -30,7 +30,7 @@ For example, in an `Order` primary key table, the partition 
key can be defined a
 - The partition key must be a Fluss native data type and cannot be contained 
in a map or list.
 - For auto partition table, the partition keys can be one or more. If the 
table has only one partition key, it supports automatic creation and automatic 
expiration of partitions. Otherwise, only automatic expiration is allowed.
 - If the table is a primary key table, the partition key must be a subset of 
the primary key.
-- Auto-partitioning rules can only be configured at the time of creating the 
partitioned table; modifying the auto-partitioning rules after table creation 
is not supported.
+- Auto-partitioning rules can only be configured at the time of creating the 
partitioned table, except `table.auto-partition.num-retention`, which can be 
modified by `ALTER TABLE ... SET` after table creation.
 
 ## Auto Partitioning
 ### Example
@@ -61,7 +61,7 @@ In this case, when automatic partitioning occurs (Fluss will 
periodically operat
 | table.auto-partition.key           | String  | no       | (none)             
  | This configuration defines the time-based partition key to be used for 
auto-partitioning when a table is partitioned with multiple keys. 
Auto-partitioning utilizes a time-based partition key to handle partitions 
automatically, including creating new ones and removing outdated ones, by 
comparing the time value of the partition with the current system time. In the 
case of a table using multiple partition key [...]
 | table.auto-partition.time-unit     | ENUM    | no       | DAY                
  | The time granularity for auto created partitions. The default value is 
'DAY'. Valid values are 'HOUR', 'DAY', 'MONTH', 'QUARTER', 'YEAR'. If the value 
is 'HOUR', the partition format for auto created is yyyyMMddHH. If the value is 
'DAY', the partition format for auto created is yyyyMMdd. If the value is 
'MONTH', the partition format for auto created is yyyyMM. If the value is 
'QUARTER', the partition forma [...]
 | table.auto-partition.num-precreate | Integer | no       | 2                  
  | The number of partitions to pre-create for auto created partitions in each 
check for auto partition. For example, if the current check time is 2024-11-11 
and the value is configured as 3, then partitions 20241111, 20241112, 20241113 
will be pre-created. If any one partition exists, it'll skip creating the 
partition. The default value is 2, which means 2 partitions will be 
pre-created. If the 'table.auto-pa [...]
-| table.auto-partition.num-retention | Integer | no       | 7                  
  | The number of history partitions to retain for auto created partitions in 
each check for auto partition. For example, if the current check time is 
2024-11-11, time-unit is DAY, and the value is configured as 3, then the 
history partitions 20241108, 20241109, 20241110 will be retained. The 
partitions earlier than 20241108 will be deleted. The default value is 7.       
                                        [...]
+| table.auto-partition.num-retention | Integer | no       | 7                  
  | The number of history partitions to retain for auto created partitions in 
each check for auto partition. For example, if the current check time is 
2024-11-11, time-unit is DAY, and the value is configured as 3, then the 
history partitions 20241108, 20241109, 20241110 will be retained. The 
partitions earlier than 20241108 will be deleted. The default value is 7. This 
option can be modified after table creat [...]
 | table.auto-partition.time-zone     | String  | no       | the system time 
zone | The time zone for auto partitions, which is by default the same as the 
system time zone.                                                               
                                                                                
                                                                                
                                                                                
                   [...]
 
 ### Partition Generation Rules

Reply via email to