diff --git a/docs/sql-manual/basic-element/sql-data-types/uuid.md b/docs/sql-manual/basic-element/sql-data-types/uuid.md index 7edd4a7c936ed..afdd8db2b8169 100644 --- a/docs/sql-manual/basic-element/sql-data-types/uuid.md +++ b/docs/sql-manual/basic-element/sql-data-types/uuid.md @@ -97,7 +97,8 @@ The existing `IS_UUID()` accepts some text, such as canonical UUIDs enclosed in ## Table design and restrictions -- UUID columns can be keys in Duplicate, Unique, and Aggregate tables, hash distribution columns, and manual RANGE or LIST partition columns. Specify partition boundaries as quoted UUID text. Numeric-step batch range creation does not apply to UUID. +- UUID columns can be keys in Duplicate, Unique, and Aggregate tables and hash distribution columns. +- UUID columns cannot be RANGE or LIST partition columns, including in multi-column partitions or `AUTO PARTITION BY LIST`. Dynamic partitioning on UUID columns is also unsupported. - UUID values support comparison, `IN`, sorting, grouping, joins, `MIN`, `MAX`, and `COUNT(DISTINCT ...)`. UUID is not a numeric type: arithmetic and numeric aggregates such as `SUM` and `AVG` are not supported. - Aggregate-table UUID value columns support `MIN`, `MAX`, `REPLACE`, and `REPLACE_IF_NOT_NULL`. - UUID can be an ARRAY element, a MAP key or value, or a STRUCT field. The existing constraints on the outer complex type still apply. diff --git a/docs/table-design/data-partitioning/manual-partitioning.md b/docs/table-design/data-partitioning/manual-partitioning.md index 5b8d907524dd4..ca99c1afc9787 100644 --- a/docs/table-design/data-partitioning/manual-partitioning.md +++ b/docs/table-design/data-partitioning/manual-partitioning.md @@ -25,9 +25,7 @@ Before using manual partitioning, you need to understand the general rules for p Range partitioning divides data into different partitions based on the value range of the partition column. The partition column is typically a time column, which makes it easy to manage old and new data. -**Supported column types:** `DATE`, `DATETIME`, `TIMESTAMP_NS`, `TIMESTAMPTZ`, `TINYINT`, `SMALLINT`, `INT`, `BIGINT`, `LARGEINT`, `UUID`. - -UUID partition boundaries accept quoted canonical or compact hexadecimal text. Numeric-step batch RANGE creation does not apply to UUID. +**Supported column types:** `DATE`, `DATETIME`, `TIMESTAMP_NS`, `TIMESTAMPTZ`, `TINYINT`, `SMALLINT`, `INT`, `BIGINT`, `LARGEINT`. Range partitioning supports the following four forms, suitable for different scenarios: @@ -143,9 +141,7 @@ PARTITION BY RANGE(col) List partitioning divides data into different partitions based on the enumerated values of the partition column. A row is routed to a partition only if its value matches one of the enumerated values defined for that partition. -**Supported column types:** `BOOLEAN`, `TINYINT`, `SMALLINT`, `INT`, `BIGINT`, `LARGEINT`, `DATE`, `DATETIME`, `TIMESTAMP_NS`, `TIMESTAMPTZ`, `CHAR`, `VARCHAR`, `UUID`. - -UUID partition values accept quoted canonical or compact hexadecimal text. Different letter cases or hyphen formats of the same UUID represent the same partition value. +**Supported column types:** `BOOLEAN`, `TINYINT`, `SMALLINT`, `INT`, `BIGINT`, `LARGEINT`, `DATE`, `DATETIME`, `TIMESTAMP_NS`, `TIMESTAMPTZ`, `CHAR`, `VARCHAR`. **Syntax keyword:** Use `VALUES IN (...)` to specify the enumerated values contained in each partition. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/uuid.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/uuid.md index 8f279545b823e..525c6909a11e2 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/uuid.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/uuid.md @@ -97,7 +97,8 @@ WHERE event_id = CAST('550e8400-e29b-41d4-a716-446655440000' AS UUID); ## 表设计和限制 -- UUID 列可作为 Duplicate、Unique 和 Aggregate 表的 Key 列、Hash 分桶列以及手动 RANGE 或 LIST 分区列。分区边界使用带引号的 UUID 文本。基于数值步长批量创建 RANGE 分区的方式不适用于 UUID。 +- UUID 列可作为 Duplicate、Unique 和 Aggregate 表的 Key 列以及 Hash 分桶列。 +- UUID 列不能作为 RANGE 或 LIST 分区列，包括多列分区和 `AUTO PARTITION BY LIST`，也不支持基于 UUID 列进行动态分区。 - UUID 值支持比较、`IN`、排序、分组、关联、`MIN`、`MAX` 和 `COUNT(DISTINCT ...)`。UUID 不是数值类型，不支持算术运算以及 `SUM`、`AVG` 等数值聚合。 - Aggregate 表的 UUID Value 列支持 `MIN`、`MAX`、`REPLACE` 和 `REPLACE_IF_NOT_NULL`。 - UUID 可用作 ARRAY 元素、MAP 的键或值以及 STRUCT 字段；外层复杂类型的原有限制仍然适用。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/manual-partitioning.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/manual-partitioning.md index caf5d7f0d5517..70929aac9350a 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/manual-partitioning.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/data-partitioning/manual-partitioning.md @@ -25,9 +25,7 @@ Range 分区按照分区列的取值范围将数据划分到不同分区。分区列通常为时间列，便于管理新旧数据。 -**支持的列类型：** `DATE`、`DATETIME`、`TIMESTAMP_NS`、`TIMESTAMPTZ`、`TINYINT`、`SMALLINT`、`INT`、`BIGINT`、`LARGEINT`、`UUID`。 - -UUID 分区边界接受带引号的标准格式或紧凑十六进制文本。不支持为 UUID 按数值步长批量创建 RANGE 分区。 +**支持的列类型：** `DATE`、`DATETIME`、`TIMESTAMP_NS`、`TIMESTAMPTZ`、`TINYINT`、`SMALLINT`、`INT`、`BIGINT`、`LARGEINT`。 Range 分区支持以下四种写法，适用于不同场景： @@ -143,9 +141,7 @@ PARTITION BY RANGE(col) List 分区按照分区列的枚举值将数据划分到不同分区。只有当数据为目标分区枚举值其中之一时，才可以命中分区。 -**支持的列类型：** `BOOLEAN`、`TINYINT`、`SMALLINT`、`INT`、`BIGINT`、`LARGEINT`、`DATE`、`DATETIME`、`TIMESTAMP_NS`、`TIMESTAMPTZ`、`CHAR`、`VARCHAR`、`UUID`。 - -UUID 分区值接受带引号的标准格式或紧凑十六进制文本。同一个 UUID 的大小写或连字符格式不同，仍表示相同的分区值。 +**支持的列类型：** `BOOLEAN`、`TINYINT`、`SMALLINT`、`INT`、`BIGINT`、`LARGEINT`、`DATE`、`DATETIME`、`TIMESTAMP_NS`、`TIMESTAMPTZ`、`CHAR`、`VARCHAR`。 **语法关键字：** 通过 `VALUES IN (...)` 指定每个分区包含的枚举值。