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

morningman pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 8cc301dfce65 [docs] Expand CREATE TABLE property reference for Dev and 
4.x (#4633)
8cc301dfce65 is described below

commit 8cc301dfce65d94b39ae134cc5de7707fee28e8e
Author: Mingyu Chen (Rayner) <[email protected]>
AuthorDate: Fri Nov 13 08:05:17 2026 +0800

    [docs] Expand CREATE TABLE property reference for Dev and 4.x (#4633)
    
    The CREATE TABLE reference omits table properties that users otherwise
    have to discover in feature pages or source. Add a
    type/default/constraints reference for 30 properties in Dev and 25 in
    4.x, in both English and Chinese. It covers prefix/Bloom indexes, row
    and column pages, storage policies and vaults, cache protection,
    bucketing, retention, compaction, Group Commit, and CCR.
    
    The version audit includes master, branch-4.1, branch-4.2, and
    4.2.0-rc03. SNII and `partition.inverted_index_storage_format` are
    available since 4.2.0 and appear in both documentation versions.
    Sequence mapping and row-level TTL remain Dev-only; TTL retains its
    5.0.0 experimental marker. The reference distinguishes ordinary table
    properties from index, VARIANT-column, and materialized-view properties,
    and directs `auto_analyze_policy` users to ALTER TABLE. Six existing
    Chinese parameter links are also repaired.
    
    Source verification: [master
    
PropertyAnalyzer](https://github.com/apache/doris/blob/172120cbaa46b0a2eff6c37d86fb438c3a307375/fe/fe-core/src/main/java/org/apache/doris/common/util/PropertyAnalyzer.java),
    [4.1 create
    
path](https://github.com/apache/doris/blob/df8ed67a8e5dbdc91f1065b50dae23d834117800/fe/fe-core/src/main/java/org/apache/doris/datasource/InternalCatalog.java),
    [4.2
    
PropertyAnalyzer](https://github.com/apache/doris/blob/7523405f6aa8e9df3d110eb432fed1ff6e1c3418/fe/fe-core/src/main/java/org/apache/doris/common/util/PropertyAnalyzer.java),
    and corresponding CreateTableInfo, CloudPropertyAnalyzer, BinlogConfig,
    and storage/load consumers. Rejected or internal constants were not
    inferred to be user-facing options.
    
    Validation: scoped link lint reports zero findings; all four
    Markdown/GFM pages compile; property-key sets match between locales and
    exist in the corresponding source snapshots; `git diff --check` passes.
    i18n sync reports only two informational 3.x candidates; the requested
    scope is Dev and 4.x. No full site build or SQL runtime tests were run.
    
    Fixes #1301
    
    Co-authored-by: morningman <[email protected]>
---
 .../table-and-view/table/CREATE-TABLE.md           | 39 ++++++++++++++++++++
 .../table-and-view/table/CREATE-TABLE.md           | 43 +++++++++++++++++++++-
 .../table-and-view/table/CREATE-TABLE.md           | 38 ++++++++++++++++++-
 .../table-and-view/table/CREATE-TABLE.md           | 34 +++++++++++++++++
 4 files changed, 150 insertions(+), 4 deletions(-)

diff --git 
a/docs/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md 
b/docs/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
index d3f9c7065976..067f4ee1b695 100644
--- a/docs/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
+++ b/docs/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
@@ -344,6 +344,8 @@ The functionality of creating synchronized materialized 
views with rollup is lim
 
 ### Table Property Related Parameters
 
+The following references apply to OLAP tables. Set property values as quoted 
strings in `PROPERTIES ("name" = "value", ...)`. Properties are optional unless 
a feature requires them; deployment-specific restrictions are stated in the 
descriptions.
+
 **<table_property>**
 
 | Property Name | Function |
@@ -377,6 +379,43 @@ The functionality of creating synchronized materialized 
views with rollup is lim
 | changelog.need_historical_value | Whether the changelog records the values 
before a change (the before image), default `false`. Only Unique Key 
Merge-on-Write tables can set it to `true`; `min_delta` / `detail` Table 
Streams depend on it. Cannot be changed after creation. |
 | changelog.ttl_seconds | Retention period of the change records in seconds, 
default `86400` (one day); must be greater than `0`. Can be changed with `ALTER 
TABLE`. |
 
+#### Additional OLAP Table Properties
+
+| Property | Value type | Default | Description |
+| --- | --- | --- | --- |
+| `short_key` | Integer | Automatically calculated | Number of leading sort 
columns used by the prefix index. Must be positive and no larger than the 
number of sort columns; a VARCHAR column can only be the last selected column. |
+| `bloom_filter_fpp` | Double | `0.05` | False-positive probability for 
`bloom_filter_columns`, in `[0.0001, 0.05]`. Effective only when Bloom Filter 
columns are configured. See [Bloom 
Filter](../../../../table-design/index/bloomfilter.md). |
+| `storage_type` | String | `COLUMN` | Storage organization. Only `COLUMN` is 
accepted. Enable an additional row-format copy with the row-store properties 
below. |
+| `storage_format` | String | `V2` | Segment storage format: `V2`, `V3`, or 
`default` (`V2`). `V3` is available since 4.1.0 and stores column metadata 
externally. See [Storage Format](../../../../table-design/storage-format.md). |
+| `inverted_index_storage_format` | String | FE configuration | Inverted index 
format: `V2`, `V3`, or `default`; `SNII` is also supported since 4.2.0. Omitted 
or `default` uses FE configuration `inverted_index_storage_format`. New V1 
indexes are rejected since 4.1.5. See [Inverted 
Index](../../../../table-design/index/inverted-index/overview.md). |
+| `store_row_column` | Boolean | `false` | Stores an additional row-format 
copy of all columns. Requires `light_schema_change = true`; Aggregate Key 
tables are unsupported. See [Row Store](../../../../table-design/row-store.md). 
|
+| `row_store_columns` | String | Unset | Comma-separated existing column 
names, for example `k,v1,v2`, to store in row format. Setting this list enables 
row store for those columns; Aggregate Key tables are unsupported. See [Row 
Store](../../../../table-design/row-store.md). |
+| `row_store_page_size` | Long | `16384` | Row-store page size in bytes. Must 
be positive; rounded up to a multiple of 4096 bytes. |
+| `storage_page_size` | Long | `65536` | Column data page size in bytes, from 
`4096` to `10485760`; rounded up to a multiple of 4096 bytes. |
+| `storage_dict_page_size` | Long | `262144` | Dictionary page size in bytes, 
from `0` to `104857600`; rounded up to a multiple of 4096 bytes. |
+| `storage_policy` | String | Unset | Existing remote-storage policy for a 
compute-storage coupled table. Unsupported for Unique Key Merge-on-Write 
tables; ignored in compute-storage decoupled mode. See [Remote 
Storage](../../../../table-design/tiered-storage/remote-storage.md). |
+| `storage_vault_name` | String | Database vault, then default vault | Storage 
Vault name in compute-storage decoupled mode. The vault must exist, and the 
user needs `USAGE` on it. Table configuration overrides the database and 
default vault. See [Managing Storage 
Vault](../../../../compute-storage-decoupled/managing-storage-vault.md). |
+| `file_cache_ttl_seconds` | Long | `0` | TTL cache protection duration in 
seconds in compute-storage decoupled mode. `0` uses ordinary caching. Since 
4.1.4, the validated range is `0` to `4611686018427387903`. This is not a data 
expiration setting. See [File 
Cache](../../../../compute-storage-decoupled/file-cache/file-cache.md). |
+| `estimate_partition_size` | String | Unset | Estimated uncompressed size of 
one partition, for example `10G`, used with `BUCKETS AUTO` to choose the 
initial bucket count. See 
[Bucketing](../../../../table-design/data-partitioning/data-bucketing.md). |
+| `mutable` | Boolean | `true` | Whether a partition accepts data loading. 
`false` makes it immutable. A table-level setting supplies the default for its 
partitions. |
+| `partition.retention_count` | Integer | Unset | Positive number of 
historical partitions to retain in an AUTO RANGE PARTITION table. Current and 
future partitions are retained. Cannot be combined with enabled dynamic 
partitioning since 4.1.4. See [Auto 
Partitioning](../../../../table-design/data-partitioning/auto-partitioning.md). 
|
+| `vertical_compaction_num_columns_per_group` | Integer | `5` | Number of 
columns per group during vertical compaction. Must be at least `1`. |
+| `time_series_compaction_empty_rowsets_threshold` | Long | `5` | Minimum 
number of consecutive empty rowsets for prioritized compaction. Must be at 
least `2`, and requires `compaction_policy = time_series`. |
+| `group_commit_mode` | String | `off_mode` | Default Group Commit mode for 
this table: `off_mode`, `sync_mode`, or `async_mode`. Supported since 4.1.0. A 
request or session setting takes precedence. See [Group 
Commit](../../../../data-operate/import/load-best-practices/group-commit-manual.md).
 |
+| `binlog.enable` | Boolean | `false` | Enables CCR binlog for this table. The 
FE must also enable `enable_feature_binlog`. |
+| `binlog.ttl_seconds` | Long | `86400` | CCR binlog retention threshold in 
seconds. |
+| `binlog.max_bytes` | Long | `9223372036854775807` | CCR binlog size 
threshold for garbage collection, in bytes. |
+| `binlog.max_history_nums` | Long | `9223372036854775807` | CCR binlog 
history-count threshold for garbage collection. |
+| `is_being_synced` | Boolean | `false` | Marks a CCR destination table as 
being synchronized. When `true`, Doris skips its dynamic partition scheduling 
and ignores colocate/storage-policy settings. Leave this to the CCR workflow. |
+| `partition.inverted_index_storage_format` | String | Unset | Since 4.2.0: 
format for newly created partitions in compute-storage decoupled mode: `V2`, 
`V3`, or `SNII`. Requires FE configuration 
`enable_partition_inverted_index_storage_format_rollout = true`; ignored when 
the switch is off. Does not convert existing partitions. |
+| `sequence_mapping.<sequence_col>` | String | Unset | Dev: comma-separated 
Value columns controlled by the named Sequence column. Requires a Unique Key 
Merge-on-Read table and `light_schema_change = true`. See [Multi-stream 
Update](../../../../data-operate/update/multi-stream-update-for-unique-model.md).
 |
+| `function_column.enable_row_ttl` | Boolean | `false` | Experimental, since 
5.0.0: enables row-level TTL at table creation. Aggregate Key tables and 
Sequence-column combinations are unsupported. See [Row-level 
TTL](../../../../data-operate/delete/row-ttl.md). |
+| `function_column.ttl_col` | String | Unset | Source Value column for 
row-level TTL. Must be set together with `function_column.ttl`, and row-level 
TTL must be enabled. See the source-column constraints in [Row-level 
TTL](../../../../data-operate/delete/row-ttl.md). |
+| `function_column.ttl` | String | Unset | Nonnegative retention duration for 
source-column TTL, for example `86400` or `1 day`. A value without a unit is in 
seconds. `0` means expiration at the source timestamp. |
+| `function_column.ttl_time_zone` | String | Depends on source type | Time 
zone for the TTL source column: `UTC`, `Z`, or a fixed offset from `-12:00` to 
`+14:00`. Required for DATE/DATETIME-family source columns; TIMESTAMPTZ 
defaults to `+00:00` and accepts only zero offset. |
+
+For feature-specific properties, also see [Dynamic 
Partitioning](../../../../table-design/data-partitioning/dynamic-partitioning.md).
 Index `PROPERTIES`, VARIANT column `PROPERTIES`, and asynchronous materialized 
view properties are separate from these table properties. For automatic 
statistics collection, set `auto_analyze_policy` with `ALTER TABLE` as 
described in 
[Statistics](../../../../query-acceleration/optimization-technology-principle/statistics.md).
+
 ## Access Control Requirements
 
 The [user](../../../../admin-manual/auth/authentication-and-authorization.md) 
executing this SQL command must have at least the following 
[privileges](../../../../admin-manual/auth/authentication-and-authorization.md):
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
index 5078f11f1864..8605920c46d8 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
@@ -231,7 +231,7 @@ CREATE TABLE <table_name> LIKE <source_table>
 
 **<distribute_cols> 和 <bucket_count>**
 
-> 分桶列和分桶数。明细模型的分桶列可以是任意的列,聚合模型和主键模型的分桶列必须和 key 
列保持一致。分桶数是任意的正整数。有关分桶的详细信息,请参阅[手动分桶](../../../../table-design/data-partitioning/data-bucketing#手动设置分桶数)和[自动分桶](../../../../table-design/data-partitioning/data-bucketing#自动设置分桶数)章节。
+> 分桶列和分桶数。明细模型的分桶列可以是任意的列,聚合模型和主键模型的分桶列必须和 key 
列保持一致。分桶数是任意的正整数。有关分桶的详细信息,请参阅[手动分桶](../../../../table-design/data-partitioning/data-bucketing#1-手动设置分桶数)和[自动分桶](../../../../table-design/data-partitioning/data-bucketing#2-自动设置分桶数)章节。
 
 ### 列的默认值相关参数
 
@@ -345,6 +345,8 @@ rollup 可以创建的同步物化视图功能有限。已不再推荐使用。
 
 ### 表属性相关参数
 
+以下属性参考适用于 OLAP 内表,在 `PROPERTIES ("name" = "value", ...)` 
中以字符串形式设置属性值。除特定功能要求外,属性均为可选项;部署模式限制见各项说明。
+
 **<table_property>**
 
 | 属性名                                        | 作用                              
                           |
@@ -373,10 +375,47 @@ rollup 可以创建的同步物化视图功能有限。已不再推荐使用。
 | group_commit_data_bytes                       | 配置这个表的 Group Commit 
攒批数据大小。单位为 bytes,默认值为 134217728,即 128MB。Group Commit 的下刷时机取决于 
`group_commit_interval_ms`以及`group_commit_data_bytes` 哪个先到设置的值。 |
 | enable_mow_light_delete                       | 是否在 Unique 表 Mow 上开启 Delete 
语句写 Delete predicate。若开启,会提升 Delete 语句的性能,但 Delete 
后进行部分列更新可能会出现部分数据错误的情况。若关闭,会降低 Delete 语句的性能来保证正确性。此属性的默认值为 `false`。此属性只能在 
Unique Merge-on-Write 表上开启。 |
 | 动态分区相关属性                              | 动态分区相关参考[数据划分 - 
动态分区](../../../../table-design/data-partitioning/dynamic-partitioning) |
-| enable_unique_key_skip_bitmap_column | 是否在 Unique Merge-on-Write 
表上开启[灵活列更新功能](../../../../data-operate/update/update-of-unique-model.md#灵活部分列更新)。此属性只能在
 Unique Merge-on-Write 表上开启。 |
+| enable_unique_key_skip_bitmap_column | 是否在 Unique Merge-on-Write 
表上开启[灵活列更新功能](../../../../data-operate/update/partial-column-update.md#灵活列更新)。此属性只能在
 Unique Merge-on-Write 表上开启。 |
 | changelog.enable | 为该表开启 
[Changelog](../../../../data-operate/incremental/changelog),记录行级变更,用于 Table 
Stream 增量消费和 `@incr` 增量查询。仅 Duplicate Key 表和 Unique Key Merge-on-Write 表(无 
cluster key)支持。只能在建表时开启,开启后不可关闭;不能与 `binlog.enable`(CCR)同时开启。需要 FE 开启 
`enable_feature_changelog = true`。5.0.0 版本起支持。 |
 | changelog.need_historical_value | 是否在 Changelog 中记录变更前的值(before 镜像),默认 
`false`。仅 Unique Key Merge-on-Write 表可设为 `true`;`min_delta` / `detail` 类型的 
Table Stream 依赖它。建表后不可修改。 |
 | changelog.ttl_seconds | 变更记录的保留时长(秒),默认 `86400`(一天),必须大于 `0`。可以通过 `ALTER 
TABLE` 修改。 |
+#### 其他 OLAP 表属性
+
+| 属性 | 值类型 | 默认值 | 说明 |
+| --- | --- | --- | --- |
+| `short_key` | 整数 | 自动计算 | 前缀索引包含的前导排序列数量。必须为正整数且不超过排序列数量;VARCHAR 
列只能是所选列中的最后一列。 |
+| `bloom_filter_fpp` | 浮点数 | `0.05` | `bloom_filter_columns` 的误判率,范围为 
`[0.0001, 0.05]`,仅在配置 Bloom Filter 列时生效。详见 [Bloom Filter 
索引](../../../../table-design/index/bloomfilter.md)。 |
+| `storage_type` | 字符串 | `COLUMN` | 存储组织方式,仅接受 `COLUMN`。如需额外存储行格式副本,使用下方的行存属性。 
|
+| `storage_format` | 字符串 | `V2` | Segment 存储格式,可选 `V2`、`V3` 或 `default`(即 
`V2`)。`V3` 自 4.1.0 
起支持,将列元数据存储在外部。详见[存储格式](../../../../table-design/storage-format.md)。 |
+| `inverted_index_storage_format` | 字符串 | FE 配置 | 倒排索引格式,可选 `V2`、`V3` 或 
`default`,自 4.2.0 起还支持 `SNII`。不设置或使用 `default` 时遵循 FE 配置 
`inverted_index_storage_format`。自 4.1.5 起不再允许新建 V1 
索引。详见[倒排索引](../../../../table-design/index/inverted-index/overview.md)。 |
+| `store_row_column` | 布尔值 | `false` | 额外以行格式存储全部列。要求 `light_schema_change = 
true`,不支持 Aggregate Key 表。详见[行存](../../../../table-design/row-store.md)。 |
+| `row_store_columns` | 字符串 | 不设置 | 以逗号分隔的已存在列名,例如 `k,v1,v2`。设置后为这些列启用行存,不支持 
Aggregate Key 表。详见[行存](../../../../table-design/row-store.md)。 |
+| `row_store_page_size` | 长整数 | `16384` | 行存页大小,单位为字节。必须为正数,向上取整到 4096 字节的整数倍。 
|
+| `storage_page_size` | 长整数 | `65536` | 列存数据页大小,单位为字节,范围为 `4096` 至 
`10485760`,向上取整到 4096 字节的整数倍。 |
+| `storage_dict_page_size` | 长整数 | `262144` | 字典页大小,单位为字节,范围为 `0` 至 
`104857600`,向上取整到 4096 字节的整数倍。 |
+| `storage_policy` | 字符串 | 不设置 | 存算一体表使用的已存在远程存储策略。不支持 Unique Key 
Merge-on-Write 
表,在存算分离模式中被忽略。详见[远程存储](../../../../table-design/tiered-storage/remote-storage.md)。
 |
+| `storage_vault_name` | 字符串 | 数据库的 Vault,其次为默认 Vault | 存算分离模式使用的 Storage 
Vault 名称。Vault 必须已存在,用户须拥有其 `USAGE` 权限。表级配置优先于数据库和默认 Vault。详见[管理 Storage 
Vault](../../../../compute-storage-decoupled/managing-storage-vault.md)。 |
+| `file_cache_ttl_seconds` | 长整数 | `0` | 存算分离模式下 TTL 缓存的保护时长,单位为秒。`0` 
表示使用普通缓存;自 4.1.4 起校验的取值范围为 `0` 至 
`4611686018427387903`。此属性不控制数据过期删除。详见[文件缓存](../../../../compute-storage-decoupled/file-cache/file-cache.md)。
 |
+| `estimate_partition_size` | 字符串 | 不设置 | 单个分区未压缩数据大小的预估值,例如 `10G`,与 `BUCKETS 
AUTO` 
一起用于确定初始分桶数。详见[数据分桶](../../../../table-design/data-partitioning/data-bucketing.md)。
 |
+| `mutable` | 布尔值 | `true` | 分区是否允许导入数据。`false` 将分区设为不可写;表级设置作为各分区的默认值。 |
+| `partition.retention_count` | 整数 | 不设置 | AUTO RANGE PARTITION 
表保留的历史分区数量,必须为正整数;当前和未来分区继续保留。自 4.1.4 
起不能与已启用的动态分区同时使用。详见[自动分区](../../../../table-design/data-partitioning/auto-partitioning.md)。
 |
+| `vertical_compaction_num_columns_per_group` | 整数 | `5` | 垂直 Compaction 
每组处理的列数,必须大于等于 `1`。 |
+| `time_series_compaction_empty_rowsets_threshold` | 长整数 | `5` | 优先合并连续空 
Rowset 的数量阈值,必须大于等于 `2`,要求 `compaction_policy = time_series`。 |
+| `group_commit_mode` | 字符串 | `off_mode` | 表的默认 Group Commit 模式,可选 
`off_mode`、`sync_mode` 或 `async_mode`,自 4.1.0 起支持。请求或会话中的设置优先。详见 [Group 
Commit](../../../../data-operate/import/load-best-practices/group-commit-manual.md)。
 |
+| `binlog.enable` | 布尔值 | `false` | 为表启用 CCR Binlog,FE 还须开启 
`enable_feature_binlog`。 |
+| `binlog.ttl_seconds` | 长整数 | `86400` | CCR Binlog 保留时长阈值,单位为秒。 |
+| `binlog.max_bytes` | 长整数 | `9223372036854775807` | CCR Binlog 
垃圾回收的大小阈值,单位为字节。 |
+| `binlog.max_history_nums` | 长整数 | `9223372036854775807` | CCR Binlog 
垃圾回收的历史记录数量阈值。 |
+| `is_being_synced` | 布尔值 | `false` | 标记 CCR 目标表正在同步。设为 `true` 
时跳过该表的动态分区调度,并忽略 Colocate 和存储策略设置,由 CCR 流程管理此属性。 |
+| `partition.inverted_index_storage_format` | 字符串 | 不设置 | 自 4.2.0 
起支持:存算分离模式下新建分区的索引格式,可选 `V2`、`V3` 或 `SNII`。须开启 FE 配置 
`enable_partition_inverted_index_storage_format_rollout = true`,否则忽略。不转换已有分区。 |
+| `sequence_mapping.<sequence_col>` | 字符串 | 不设置 | Dev:由指定 Sequence 列控制的 Value 
列列表,以逗号分隔。要求 Unique Key Merge-on-Read 表且 `light_schema_change = 
true`。详见[多流更新](../../../../data-operate/update/multi-stream-update-for-unique-model.md)。
 |
+| `function_column.enable_row_ttl` | 布尔值 | `false` | 实验性功能,5.0.0 起支持:建表时开启行级 
TTL。不支持 Aggregate Key 表,不能与 Sequence 列同时使用。详见[行级 
TTL](../../../../data-operate/delete/row-ttl.md)。 |
+| `function_column.ttl_col` | 字符串 | 不设置 | 行级 TTL 的源 Value 列,必须与 
`function_column.ttl` 一起设置且已开启行级 TTL。列类型等限制详见[行级 
TTL](../../../../data-operate/delete/row-ttl.md)。 |
+| `function_column.ttl` | 字符串 | 不设置 | 源列模式的非负保留时长,例如 `86400` 或 `1 
day`;无单位时按秒解释。`0` 表示在源列时间到达时过期。 |
+| `function_column.ttl_time_zone` | 字符串 | 取决于源列类型 | TTL 源列的时区,可选 `UTC`、`Z` 或 
`-12:00` 至 `+14:00` 的固定偏移。DATE/DATETIME 系列源列必须显式设置;TIMESTAMPTZ 默认 `+00:00` 
且只接受零偏移。 |
+
+特定功能的属性另见[动态分区](../../../../table-design/data-partitioning/dynamic-partitioning.md)。索引
 `PROPERTIES`、VARIANT 列的 `PROPERTIES` 
及异步物化视图属性与上述表属性分开配置。如需设置自动统计信息收集策略,请按照[统计信息](../../../../query-acceleration/optimization-technology-principle/statistics.md)中的说明,通过
 `ALTER TABLE` 设置 `auto_analyze_policy`。
+
 ## 权限控制
 
 执行此 SQL 
命令的[用户](../../../../admin-manual/auth/security-overview)必须至少具有以下[权限](../../../../admin-manual/auth/authorization/internal):
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
index bbf0d92109de..9f7e0e6ae5c8 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
@@ -231,7 +231,7 @@ CREATE TABLE <table_name> LIKE <source_table>
 
 **<distribute_cols> 和 <bucket_count>**
 
-> 分桶列和分桶数。明细模型的分桶列可以是任意的列,聚合模型和主键模型的分桶列必须和 key 
列保持一致。分桶数是任意的正整数。有关分桶的详细信息,请参阅[手动分桶](../../../../table-design/data-partitioning/data-bucketing#手动设置分桶数)和[自动分桶](../../../../table-design/data-partitioning/data-bucketing#自动设置分桶数)章节。
+> 分桶列和分桶数。明细模型的分桶列可以是任意的列,聚合模型和主键模型的分桶列必须和 key 
列保持一致。分桶数是任意的正整数。有关分桶的详细信息,请参阅[手动分桶](../../../../table-design/data-partitioning/data-bucketing#1-手动设置分桶数)和[自动分桶](../../../../table-design/data-partitioning/data-bucketing#2-自动设置分桶数)章节。
 
 ### 列的默认值相关参数
 
@@ -344,6 +344,8 @@ rollup 可以创建的同步物化视图功能有限。已不再推荐使用。
 
 ### 表属性相关参数
 
+以下属性参考适用于 OLAP 内表,在 `PROPERTIES ("name" = "value", ...)` 
中以字符串形式设置属性值。除特定功能要求外,属性均为可选项;部署模式限制见各项说明。
+
 **<table_property>**
 
 | 属性名                                        | 作用                              
                           |
@@ -372,7 +374,39 @@ rollup 可以创建的同步物化视图功能有限。已不再推荐使用。
 | group_commit_data_bytes                       | 配置这个表的 Group Commit 
攒批数据大小。单位为 bytes,默认值为 134217728,即 128MB。Group Commit 的下刷时机取决于 
`group_commit_interval_ms`以及`group_commit_data_bytes` 哪个先到设置的值。 |
 | enable_mow_light_delete                       | 是否在 Unique 表 Mow 上开启 Delete 
语句写 Delete predicate。若开启,会提升 Delete 语句的性能,但 Delete 
后进行部分列更新可能会出现部分数据错误的情况。若关闭,会降低 Delete 语句的性能来保证正确性。此属性的默认值为 `false`。此属性只能在 
Unique Merge-on-Write 表上开启。 |
 | 动态分区相关属性                              | 动态分区相关参考[数据划分 - 
动态分区](../../../../table-design/data-partitioning/dynamic-partitioning) |
-| enable_unique_key_skip_bitmap_column | 是否在 Unique Merge-on-Write 
表上开启[灵活列更新功能](../../../../data-operate/update/update-of-unique-model.md#灵活部分列更新)。此属性只能在
 Unique Merge-on-Write 表上开启。 |
+| enable_unique_key_skip_bitmap_column | 是否在 Unique Merge-on-Write 
表上开启[灵活列更新功能](../../../../data-operate/update/partial-column-update.md#灵活列更新)。此属性只能在
 Unique Merge-on-Write 表上开启。 |
+#### 其他 OLAP 表属性
+
+| 属性 | 值类型 | 默认值 | 说明 |
+| --- | --- | --- | --- |
+| `short_key` | 整数 | 自动计算 | 前缀索引包含的前导排序列数量。必须为正整数且不超过排序列数量;VARCHAR 
列只能是所选列中的最后一列。 |
+| `bloom_filter_fpp` | 浮点数 | `0.05` | `bloom_filter_columns` 的误判率,范围为 
`[0.0001, 0.05]`,仅在配置 Bloom Filter 列时生效。详见 [Bloom Filter 
索引](../../../../table-design/index/bloomfilter.md)。 |
+| `storage_type` | 字符串 | `COLUMN` | 存储组织方式,仅接受 `COLUMN`。如需额外存储行格式副本,使用下方的行存属性。 
|
+| `storage_format` | 字符串 | `V2` | Segment 存储格式,可选 `V2`、`V3` 或 `default`(即 
`V2`)。`V3` 自 4.1.0 
起支持,将列元数据存储在外部。详见[存储格式](../../../../table-design/storage-format.md)。 |
+| `inverted_index_storage_format` | 字符串 | FE 配置 | 倒排索引格式,可选 `V2`、`V3` 或 
`default`,自 4.2.0 起还支持 `SNII`。不设置或使用 `default` 时遵循 FE 配置 
`inverted_index_storage_format`。自 4.1.5 起不再允许新建 V1 
索引。详见[倒排索引](../../../../table-design/index/inverted-index/overview.md)。 |
+| `store_row_column` | 布尔值 | `false` | 额外以行格式存储全部列。要求 `light_schema_change = 
true`,不支持 Aggregate Key 表。详见[行存](../../../../table-design/row-store.md)。 |
+| `row_store_columns` | 字符串 | 不设置 | 以逗号分隔的已存在列名,例如 `k,v1,v2`。设置后为这些列启用行存,不支持 
Aggregate Key 表。详见[行存](../../../../table-design/row-store.md)。 |
+| `row_store_page_size` | 长整数 | `16384` | 行存页大小,单位为字节。必须为正数,向上取整到 4096 字节的整数倍。 
|
+| `storage_page_size` | 长整数 | `65536` | 列存数据页大小,单位为字节,范围为 `4096` 至 
`10485760`,向上取整到 4096 字节的整数倍。 |
+| `storage_dict_page_size` | 长整数 | `262144` | 字典页大小,单位为字节,范围为 `0` 至 
`104857600`,向上取整到 4096 字节的整数倍。 |
+| `storage_policy` | 字符串 | 不设置 | 存算一体表使用的已存在远程存储策略。不支持 Unique Key 
Merge-on-Write 
表,在存算分离模式中被忽略。详见[远程存储](../../../../table-design/tiered-storage/remote-storage.md)。
 |
+| `storage_vault_name` | 字符串 | 数据库的 Vault,其次为默认 Vault | 存算分离模式使用的 Storage 
Vault 名称。Vault 必须已存在,用户须拥有其 `USAGE` 权限。表级配置优先于数据库和默认 Vault。详见[管理 Storage 
Vault](../../../../compute-storage-decoupled/managing-storage-vault.md)。 |
+| `file_cache_ttl_seconds` | 长整数 | `0` | 存算分离模式下 TTL 缓存的保护时长,单位为秒。`0` 
表示使用普通缓存;自 4.1.4 起校验的取值范围为 `0` 至 
`4611686018427387903`。此属性不控制数据过期删除。详见[文件缓存](../../../../compute-storage-decoupled/file-cache/file-cache.md)。
 |
+| `estimate_partition_size` | 字符串 | 不设置 | 单个分区未压缩数据大小的预估值,例如 `10G`,与 `BUCKETS 
AUTO` 
一起用于确定初始分桶数。详见[数据分桶](../../../../table-design/data-partitioning/data-bucketing.md)。
 |
+| `mutable` | 布尔值 | `true` | 分区是否允许导入数据。`false` 将分区设为不可写;表级设置作为各分区的默认值。 |
+| `partition.retention_count` | 整数 | 不设置 | AUTO RANGE PARTITION 
表保留的历史分区数量,必须为正整数;当前和未来分区继续保留。自 4.1.4 
起不能与已启用的动态分区同时使用。详见[自动分区](../../../../table-design/data-partitioning/auto-partitioning.md)。
 |
+| `vertical_compaction_num_columns_per_group` | 整数 | `5` | 垂直 Compaction 
每组处理的列数,必须大于等于 `1`。 |
+| `time_series_compaction_empty_rowsets_threshold` | 长整数 | `5` | 优先合并连续空 
Rowset 的数量阈值,必须大于等于 `2`,要求 `compaction_policy = time_series`。 |
+| `group_commit_mode` | 字符串 | `off_mode` | 表的默认 Group Commit 模式,可选 
`off_mode`、`sync_mode` 或 `async_mode`,自 4.1.0 起支持。请求或会话中的设置优先。详见 [Group 
Commit](../../../../data-operate/import/load-best-practices/group-commit-manual.md)。
 |
+| `binlog.enable` | 布尔值 | `false` | 为表启用 CCR Binlog,FE 还须开启 
`enable_feature_binlog`。 |
+| `binlog.ttl_seconds` | 长整数 | `86400` | CCR Binlog 保留时长阈值,单位为秒。 |
+| `binlog.max_bytes` | 长整数 | `9223372036854775807` | CCR Binlog 
垃圾回收的大小阈值,单位为字节。 |
+| `binlog.max_history_nums` | 长整数 | `9223372036854775807` | CCR Binlog 
垃圾回收的历史记录数量阈值。 |
+| `is_being_synced` | 布尔值 | `false` | 标记 CCR 目标表正在同步。设为 `true` 
时跳过该表的动态分区调度,并忽略 Colocate 和存储策略设置,由 CCR 流程管理此属性。 |
+| `partition.inverted_index_storage_format` | 字符串 | 不设置 | 自 4.2.0 
起支持:存算分离模式下新建分区的索引格式,可选 `V2`、`V3` 或 `SNII`。须开启 FE 配置 
`enable_partition_inverted_index_storage_format_rollout = true`,否则忽略。不转换已有分区。 |
+
+特定功能的属性另见[动态分区](../../../../table-design/data-partitioning/dynamic-partitioning.md)。索引
 `PROPERTIES`、VARIANT 列的 `PROPERTIES` 
及异步物化视图属性与上述表属性分开配置。如需设置自动统计信息收集策略,请按照[统计信息](../../../../query-acceleration/optimization-technology-principle/statistics.md)中的说明,通过
 `ALTER TABLE` 设置 `auto_analyze_policy`。
+
 ## 权限控制
 
 执行此 SQL 
命令的[用户](../../../../admin-manual/auth/security-overview)必须至少具有以下[权限](../../../../admin-manual/auth/authorization/internal):
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
index 32c31b862364..c3f5420cba2a 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md
@@ -343,6 +343,8 @@ The functionality of creating synchronized materialized 
views with rollup is lim
 
 ### Table Property Related Parameters
 
+The following references apply to OLAP tables. Set property values as quoted 
strings in `PROPERTIES ("name" = "value", ...)`. Properties are optional unless 
a feature requires them; deployment-specific restrictions are stated in the 
descriptions.
+
 **<table_property>**
 
 | Property Name | Function |
@@ -373,6 +375,38 @@ The functionality of creating synchronized materialized 
views with rollup is lim
 | Dynamic Partitioning Related Properties | For dynamic partitioning, refer to 
[Data Partitioning - Dynamic 
Partitioning](../../../../table-design/data-partitioning/dynamic-partitioning) |
 | enable_unique_key_skip_bitmap_column | Whether to enable the [Flexible 
Column Update 
feature](../../../../data-operate/update/partial-column-update.md#flexible-column-update)
 on Unique Merge-on-Write tables. This property can only be enabled on Unique 
Merge-on-Write tables. |
 
+#### Additional OLAP Table Properties
+
+| Property | Value type | Default | Description |
+| --- | --- | --- | --- |
+| `short_key` | Integer | Automatically calculated | Number of leading sort 
columns used by the prefix index. Must be positive and no larger than the 
number of sort columns; a VARCHAR column can only be the last selected column. |
+| `bloom_filter_fpp` | Double | `0.05` | False-positive probability for 
`bloom_filter_columns`, in `[0.0001, 0.05]`. Effective only when Bloom Filter 
columns are configured. See [Bloom 
Filter](../../../../table-design/index/bloomfilter.md). |
+| `storage_type` | String | `COLUMN` | Storage organization. Only `COLUMN` is 
accepted. Enable an additional row-format copy with the row-store properties 
below. |
+| `storage_format` | String | `V2` | Segment storage format: `V2`, `V3`, or 
`default` (`V2`). `V3` is available since 4.1.0 and stores column metadata 
externally. See [Storage Format](../../../../table-design/storage-format.md). |
+| `inverted_index_storage_format` | String | FE configuration | Inverted index 
format: `V2`, `V3`, or `default`; `SNII` is also supported since 4.2.0. Omitted 
or `default` uses FE configuration `inverted_index_storage_format`. New V1 
indexes are rejected since 4.1.5. See [Inverted 
Index](../../../../table-design/index/inverted-index/overview.md). |
+| `store_row_column` | Boolean | `false` | Stores an additional row-format 
copy of all columns. Requires `light_schema_change = true`; Aggregate Key 
tables are unsupported. See [Row Store](../../../../table-design/row-store.md). 
|
+| `row_store_columns` | String | Unset | Comma-separated existing column 
names, for example `k,v1,v2`, to store in row format. Setting this list enables 
row store for those columns; Aggregate Key tables are unsupported. See [Row 
Store](../../../../table-design/row-store.md). |
+| `row_store_page_size` | Long | `16384` | Row-store page size in bytes. Must 
be positive; rounded up to a multiple of 4096 bytes. |
+| `storage_page_size` | Long | `65536` | Column data page size in bytes, from 
`4096` to `10485760`; rounded up to a multiple of 4096 bytes. |
+| `storage_dict_page_size` | Long | `262144` | Dictionary page size in bytes, 
from `0` to `104857600`; rounded up to a multiple of 4096 bytes. |
+| `storage_policy` | String | Unset | Existing remote-storage policy for a 
compute-storage coupled table. Unsupported for Unique Key Merge-on-Write 
tables; ignored in compute-storage decoupled mode. See [Remote 
Storage](../../../../table-design/tiered-storage/remote-storage.md). |
+| `storage_vault_name` | String | Database vault, then default vault | Storage 
Vault name in compute-storage decoupled mode. The vault must exist, and the 
user needs `USAGE` on it. Table configuration overrides the database and 
default vault. See [Managing Storage 
Vault](../../../../compute-storage-decoupled/managing-storage-vault.md). |
+| `file_cache_ttl_seconds` | Long | `0` | TTL cache protection duration in 
seconds in compute-storage decoupled mode. `0` uses ordinary caching. Since 
4.1.4, the validated range is `0` to `4611686018427387903`. This is not a data 
expiration setting. See [File 
Cache](../../../../compute-storage-decoupled/file-cache/file-cache.md). |
+| `estimate_partition_size` | String | Unset | Estimated uncompressed size of 
one partition, for example `10G`, used with `BUCKETS AUTO` to choose the 
initial bucket count. See 
[Bucketing](../../../../table-design/data-partitioning/data-bucketing.md). |
+| `mutable` | Boolean | `true` | Whether a partition accepts data loading. 
`false` makes it immutable. A table-level setting supplies the default for its 
partitions. |
+| `partition.retention_count` | Integer | Unset | Positive number of 
historical partitions to retain in an AUTO RANGE PARTITION table. Current and 
future partitions are retained. Cannot be combined with enabled dynamic 
partitioning since 4.1.4. See [Auto 
Partitioning](../../../../table-design/data-partitioning/auto-partitioning.md). 
|
+| `vertical_compaction_num_columns_per_group` | Integer | `5` | Number of 
columns per group during vertical compaction. Must be at least `1`. |
+| `time_series_compaction_empty_rowsets_threshold` | Long | `5` | Minimum 
number of consecutive empty rowsets for prioritized compaction. Must be at 
least `2`, and requires `compaction_policy = time_series`. |
+| `group_commit_mode` | String | `off_mode` | Default Group Commit mode for 
this table: `off_mode`, `sync_mode`, or `async_mode`. Supported since 4.1.0. A 
request or session setting takes precedence. See [Group 
Commit](../../../../data-operate/import/load-best-practices/group-commit-manual.md).
 |
+| `binlog.enable` | Boolean | `false` | Enables CCR binlog for this table. The 
FE must also enable `enable_feature_binlog`. |
+| `binlog.ttl_seconds` | Long | `86400` | CCR binlog retention threshold in 
seconds. |
+| `binlog.max_bytes` | Long | `9223372036854775807` | CCR binlog size 
threshold for garbage collection, in bytes. |
+| `binlog.max_history_nums` | Long | `9223372036854775807` | CCR binlog 
history-count threshold for garbage collection. |
+| `is_being_synced` | Boolean | `false` | Marks a CCR destination table as 
being synchronized. When `true`, Doris skips its dynamic partition scheduling 
and ignores colocate/storage-policy settings. Leave this to the CCR workflow. |
+| `partition.inverted_index_storage_format` | String | Unset | Since 4.2.0: 
format for newly created partitions in compute-storage decoupled mode: `V2`, 
`V3`, or `SNII`. Requires FE configuration 
`enable_partition_inverted_index_storage_format_rollout = true`; ignored when 
the switch is off. Does not convert existing partitions. |
+
+For feature-specific properties, also see [Dynamic 
Partitioning](../../../../table-design/data-partitioning/dynamic-partitioning.md).
 Index `PROPERTIES`, VARIANT column `PROPERTIES`, and asynchronous materialized 
view properties are separate from these table properties. For automatic 
statistics collection, set `auto_analyze_policy` with `ALTER TABLE` as 
described in 
[Statistics](../../../../query-acceleration/optimization-technology-principle/statistics.md).
+
 ## Access Control Requirements
 
 The [user](../../../../admin-manual/auth/authentication-and-authorization.md) 
executing this SQL command must have at least the following 
[privileges](../../../../admin-manual/auth/authentication-and-authorization.md):


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to