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 1e96706dc6d [doc](varbinary) update varbinary type in mv and
statistics (#3133)
1e96706dc6d is described below
commit 1e96706dc6d2163888a79667b393d1d2bc7eaaca
Author: zhangstar333 <[email protected]>
AuthorDate: Fri Dec 5 14:11:24 2025 +0800
[doc](varbinary) update varbinary type in mv and statistics (#3133)
## Versions
- [x] dev
- [x] 4.x
- [ ] 3.x
- [ ] 2.1
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [ ] Checked by AI
- [ ] Test Cases Built
---
.../materialized-view/async-materialized-view/overview.md | 1 +
docs/query-acceleration/materialized-view/sync-materialized-view.md | 2 ++
.../optimization-technology-principle/statistics.md | 4 ++--
docs/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md | 4 +++-
.../materialized-view/async-materialized-view/overview.md | 1 +
.../query-acceleration/materialized-view/sync-materialized-view.md | 2 ++
.../optimization-technology-principle/statistics.md | 4 ++--
.../sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md | 4 +++-
.../materialized-view/async-materialized-view/overview.md | 1 +
.../query-acceleration/materialized-view/sync-materialized-view.md | 2 ++
.../optimization-technology-principle/statistics.md | 4 ++--
.../sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md | 4 +++-
.../materialized-view/async-materialized-view/overview.md | 2 ++
.../query-acceleration/materialized-view/sync-materialized-view.md | 2 ++
.../optimization-technology-principle/statistics.md | 4 ++--
.../sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md | 4 +++-
16 files changed, 33 insertions(+), 12 deletions(-)
diff --git
a/docs/query-acceleration/materialized-view/async-materialized-view/overview.md
b/docs/query-acceleration/materialized-view/async-materialized-view/overview.md
index c5d93b4907e..03ee0d8e391 100644
---
a/docs/query-acceleration/materialized-view/async-materialized-view/overview.md
+++
b/docs/query-acceleration/materialized-view/async-materialized-view/overview.md
@@ -23,6 +23,7 @@ when query requests arrive, thus avoiding the overhead of
re-executing complex q
- **Support for Window Function Queries**: Currently, if a query contains
window functions, it is not supported to transparently rewrite that query to
utilize materialized views.
- **Materialized Views Joining More Tables than Query Tables**: If the number
of tables joined in the materialized view exceeds the number of tables involved
in the query (for example, if the query only involves t1 and t2, while the
materialized view includes t1, t2, and an additional t3), the system currently
does not support transparently rewriting that query to utilize the materialized
view.
- If the materialized view contains set operations such as UNION ALL, LIMIT,
ORDER BY, or CROSS JOIN, the materialized view can be built normally, but it
cannot be used for transparent rewriting.
+- When creating a materialized view, the VARBINARY type is not currently
supported.
## Principle Introduction
diff --git
a/docs/query-acceleration/materialized-view/sync-materialized-view.md
b/docs/query-acceleration/materialized-view/sync-materialized-view.md
index b0069b90ca7..29966d85a81 100644
--- a/docs/query-acceleration/materialized-view/sync-materialized-view.md
+++ b/docs/query-acceleration/materialized-view/sync-materialized-view.md
@@ -27,6 +27,8 @@ A synchronous materialized view is a special type of table in
Doris that stores
- The SELECT list cannot include auto-increment columns, constants, duplicate
expressions, or window functions.
+- The SELECT list cannot include VARBINARY type column.
+
- The column names in the select list of a sync materialized view must not be
the same as any existing columns in the base table, nor duplicate the column
names of other sync materialized views on the same base table. You can avoid
name conflicts by specifying aliases (e.g., col as xxx).
- If the SELECT list contains aggregation functions, these must be root
expressions (e.g., `sum(a + 1)` is supported, but `sum(a) + 1` is not), and no
non-aggregation function expressions can follow the aggregation function (e.g.,
`SELECT x, sum(a)` is allowed, but `SELECT sum(a), x` is not).
diff --git
a/docs/query-acceleration/optimization-technology-principle/statistics.md
b/docs/query-acceleration/optimization-technology-principle/statistics.md
index 16d3ff8734b..751952436c3 100644
--- a/docs/query-acceleration/optimization-technology-principle/statistics.md
+++ b/docs/query-acceleration/optimization-technology-principle/statistics.md
@@ -23,7 +23,7 @@ Doris enables the automatic sampling collection of internal
tables by default. T
Currently, the system only supports collecting statistics for columns of basic
data types, including BOOLEAN, TINYINT, SMALLINT, INT, BIGINT, LARGEINT, FLOAT,
DOUBLE, DATE, DATETIME, STRING, VARCHAR, TEXT, among others.
-Columns of complex types, such as JSONB, VARIANT, MAP, STRUCT, ARRAY, HLL,
BITMAP, TIME, TIMEV2, are skipped.
+Columns of complex types, such as JSONB, VARIANT, MAP, STRUCT, ARRAY, HLL,
BITMAP, TIME, TIMEV2, VARBINARY are skipped.
Statistics can be collected manually or automatically, and the results are
stored in the `internal.__internal_schema.column_statistics` table. The
following sections detail these two collection methods.
@@ -442,7 +442,7 @@ If the number of columns does not exceed the threshold,
execute `show auto analy
### Q3: Why are statistics not available for some columns?
-Currently, the system only supports collecting statistics for columns of basic
data types. For complex types such as JSONB, VARIANT, MAP, STRUCT, ARRAY, HLL,
BITMAP, TIME, and TIMEV2, the system skips them.
+Currently, the system only supports collecting statistics for columns of basic
data types. For complex types such as JSONB, VARIANT, MAP, STRUCT, ARRAY, HLL,
BITMAP, TIME, TIMEV2, VARBINARY the system skips them.
### Q4: Error: "Stats table not available, please make sure your cluster
status is normal"
diff --git
a/docs/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
b/docs/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
index 65910f1f6d2..9916816a7c8 100644
--- a/docs/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
+++ b/docs/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
@@ -9,7 +9,9 @@
### Description
A variable-length binary byte sequence, where M denotes the maximum length (in
bytes).
-Unlike VARCHAR, it stores and compares data byte-wise with no character set or
collation, suitable for arbitrary binary data (e.g., file fragments, hashes,
encrypted/compressed data).
+Unlike VARCHAR, it stores and compares data byte-wise with no character set or
collation, suitable for arbitrary binary data (e.g., file fragments, hashes,
encrypted/compressed data), with a maximum length of 2,147,483,647.
+
+Currently, VARBINARY columns are not supported in created materialized views,
or for use in Group By keys, Join Keys, and comparison predicates.
Version and limitations: Supported since 4.0; currently not supported as a
column type for table creation and storage in Doris. You can map
BINARY/VARBINARY fields from external systems to Doris VARBINARY via Catalogs
for querying.
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/async-materialized-view/overview.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/async-materialized-view/overview.md
index 5640fa7b226..5d770123009 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/async-materialized-view/overview.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/async-materialized-view/overview.md
@@ -21,6 +21,7 @@
- 物化视图连接表多于查询表：如果物化视图所连接的表数量多于查询所涉及的表（例如，查询仅涉及 t1 和 t2，而物化视图则包含了 t1、t2 以及额外的
t3），
则系统目前不支持将该查询透明地改写为利用该物化视图的形式。
- 如果物化视图包含 UNION ALL 等集合操作，LIMIT，ORDER BY，CROSS JOIN，物化视图可以正常构建，但是不能用于透明改写。
+- 创建物化视图中，暂不支持 VARBINARY 类型。
## 原理介绍
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/sync-materialized-view.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/sync-materialized-view.md
index 927a787c529..65912b0cca9 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/sync-materialized-view.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/sync-materialized-view.md
@@ -27,6 +27,8 @@
- SELECT 列表中，不能包含自增列，不能包含常量，不能有重复表达式，也不支持窗口函数。
+- SELECT 列表中，不能包含 VARBINARY 类型的列。
+
- SELECT 列表中的列名不能和基表中已有列相同，也不能和基表的所有其他同步物化视图中的列名重复，可以通过指定别名的方式(col as xxx)避免重名。
- 如果 SELECT 列表包含聚合函数，则聚合函数必须是根表达式（不支持 `sum(a) + 1`，支持 `sum(a +
1)`），且聚合函数之后不能有其他非聚合函数表达式（例如，`SELECT x, sum(a)` 可以，而 `SELECT sum(a)`, x 不行）。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/optimization-technology-principle/statistics.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/optimization-technology-principle/statistics.md
index 3a2a3452c9c..96cea0359d4 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/optimization-technology-principle/statistics.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/optimization-technology-principle/statistics.md
@@ -23,7 +23,7 @@ Doris 默认会开启内表的自动抽样收集，因此绝大多数情况下
目前，系统仅支持收集基本类型列的统计信息，包括
BOOLEAN、TINYINT、SMALLINT、INT、BIGINT、LARGEINT、FLOAT、DOUBLE、DATE、DATETIME、STRING、VARCHAR、TEXT
等。
-复杂类型的列会被跳过，包括 JSONB、VARIANT、MAP、STRUCT、ARRAY、HLL、BITMAP、TIME、TIMEV2 等。
+复杂类型的列会被跳过，包括 JSONB、VARIANT、MAP、STRUCT、ARRAY、HLL、BITMAP、TIME、TIMEV2、VARBINARY
等。
统计信息的收集方式有手动和自动两种，收集的结果会保存在 `internal.__internal_schema.column_statistics`
表中。下面将详细介绍这两种收集方式。
@@ -442,7 +442,7 @@ Set global auto_analyze_table_width_threshold=350
### Q3：为什么部分列没有统计信息？
-目前，系统仅支持收集基本类型列的统计信息。对于复杂类型的列，如 JSONB、VARIANT、MAP、STRUCT、ARRAY、HLL、BITMAP、TIME
以及 TIMEV2 等系统会选择跳过。
+目前，系统仅支持收集基本类型列的统计信息。对于复杂类型的列，如
JSONB、VARIANT、MAP、STRUCT、ARRAY、HLL、BITMAP、TIME、 TIMEV2、VARBINARY 等系统会选择跳过。
### Q4：报错 "Stats table not available, please make sure your cluster status is
normal"
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
index 345c548345d..ddf0d2a42f8 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
@@ -10,7 +10,9 @@
VARBINARY(M)
变长二进制字节序列，M 表示最大长度（单位：字节）。
-与 VARCHAR 不同，按字节序存储与比较，不涉及字符集或排序规则，适合存放任意二进制数据（如文件片段、哈希值、加密/压缩数据等）。
+与 VARCHAR
不同，按字节序存储与比较，不涉及字符集或排序规则，适合存放任意二进制数据（如文件片段、哈希值、加密/压缩数据等），最大长度为2,147,483,647。
+
+当前暂不支持 VARBINARY 列出现在创建的物化视图中，以及在 Group By key、Join Key、和比较谓词。
- 版本与限制：自 4.0 起支持；当前不支持在 Doris 表中作为列类型进行建表和存储，可通过 Catalog 将外部库的
BINARY/VARBINARY 字段映射为 Doris 中的 VARBINARY 以供查询。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/materialized-view/async-materialized-view/overview.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/materialized-view/async-materialized-view/overview.md
index 5640fa7b226..5d770123009 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/materialized-view/async-materialized-view/overview.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/materialized-view/async-materialized-view/overview.md
@@ -21,6 +21,7 @@
- 物化视图连接表多于查询表：如果物化视图所连接的表数量多于查询所涉及的表（例如，查询仅涉及 t1 和 t2，而物化视图则包含了 t1、t2 以及额外的
t3），
则系统目前不支持将该查询透明地改写为利用该物化视图的形式。
- 如果物化视图包含 UNION ALL 等集合操作，LIMIT，ORDER BY，CROSS JOIN，物化视图可以正常构建，但是不能用于透明改写。
+- 创建物化视图中，暂不支持 VARBINARY 类型。
## 原理介绍
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/materialized-view/sync-materialized-view.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/materialized-view/sync-materialized-view.md
index d579bed5d93..44cf8ac706a 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/materialized-view/sync-materialized-view.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/materialized-view/sync-materialized-view.md
@@ -27,6 +27,8 @@
- SELECT 列表中，不能包含自增列，不能包含常量，不能有重复表达式，也不支持窗口函数。
+- SELECT 列表中，不能包含 VARBINARY 类型的列。
+
- SELECT 列表中的列名不能和基表中已有列相同，也不能和基表的所有其他同步物化视图中的列名重复，可以通过指定别名的方式(col as xxx)避免重名。
- 如果 SELECT 列表包含聚合函数，则聚合函数必须是根表达式（不支持 `sum(a) + 1`，支持 `sum(a +
1)`），且聚合函数之后不能有其他非聚合函数表达式（例如，`SELECT x, sum(a)` 可以，而 `SELECT sum(a)`, x 不行）。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/optimization-technology-principle/statistics.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/optimization-technology-principle/statistics.md
index 3a2a3452c9c..96cea0359d4 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/optimization-technology-principle/statistics.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/optimization-technology-principle/statistics.md
@@ -23,7 +23,7 @@ Doris 默认会开启内表的自动抽样收集，因此绝大多数情况下
目前，系统仅支持收集基本类型列的统计信息，包括
BOOLEAN、TINYINT、SMALLINT、INT、BIGINT、LARGEINT、FLOAT、DOUBLE、DATE、DATETIME、STRING、VARCHAR、TEXT
等。
-复杂类型的列会被跳过，包括 JSONB、VARIANT、MAP、STRUCT、ARRAY、HLL、BITMAP、TIME、TIMEV2 等。
+复杂类型的列会被跳过，包括 JSONB、VARIANT、MAP、STRUCT、ARRAY、HLL、BITMAP、TIME、TIMEV2、VARBINARY
等。
统计信息的收集方式有手动和自动两种，收集的结果会保存在 `internal.__internal_schema.column_statistics`
表中。下面将详细介绍这两种收集方式。
@@ -442,7 +442,7 @@ Set global auto_analyze_table_width_threshold=350
### Q3：为什么部分列没有统计信息？
-目前，系统仅支持收集基本类型列的统计信息。对于复杂类型的列，如 JSONB、VARIANT、MAP、STRUCT、ARRAY、HLL、BITMAP、TIME
以及 TIMEV2 等系统会选择跳过。
+目前，系统仅支持收集基本类型列的统计信息。对于复杂类型的列，如
JSONB、VARIANT、MAP、STRUCT、ARRAY、HLL、BITMAP、TIME、 TIMEV2、VARBINARY 等系统会选择跳过。
### Q4：报错 "Stats table not available, please make sure your cluster status is
normal"
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
index 345c548345d..ddf0d2a42f8 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
@@ -10,7 +10,9 @@
VARBINARY(M)
变长二进制字节序列，M 表示最大长度（单位：字节）。
-与 VARCHAR 不同，按字节序存储与比较，不涉及字符集或排序规则，适合存放任意二进制数据（如文件片段、哈希值、加密/压缩数据等）。
+与 VARCHAR
不同，按字节序存储与比较，不涉及字符集或排序规则，适合存放任意二进制数据（如文件片段、哈希值、加密/压缩数据等），最大长度为2,147,483,647。
+
+当前暂不支持 VARBINARY 列出现在创建的物化视图中，以及在 Group By key、Join Key、和比较谓词。
- 版本与限制：自 4.0 起支持；当前不支持在 Doris 表中作为列类型进行建表和存储，可通过 Catalog 将外部库的
BINARY/VARBINARY 字段映射为 Doris 中的 VARBINARY 以供查询。
diff --git
a/versioned_docs/version-4.x/query-acceleration/materialized-view/async-materialized-view/overview.md
b/versioned_docs/version-4.x/query-acceleration/materialized-view/async-materialized-view/overview.md
index c5d93b4907e..d0696095466 100644
---
a/versioned_docs/version-4.x/query-acceleration/materialized-view/async-materialized-view/overview.md
+++
b/versioned_docs/version-4.x/query-acceleration/materialized-view/async-materialized-view/overview.md
@@ -23,6 +23,8 @@ when query requests arrive, thus avoiding the overhead of
re-executing complex q
- **Support for Window Function Queries**: Currently, if a query contains
window functions, it is not supported to transparently rewrite that query to
utilize materialized views.
- **Materialized Views Joining More Tables than Query Tables**: If the number
of tables joined in the materialized view exceeds the number of tables involved
in the query (for example, if the query only involves t1 and t2, while the
materialized view includes t1, t2, and an additional t3), the system currently
does not support transparently rewriting that query to utilize the materialized
view.
- If the materialized view contains set operations such as UNION ALL, LIMIT,
ORDER BY, or CROSS JOIN, the materialized view can be built normally, but it
cannot be used for transparent rewriting.
+- When creating a materialized view, the VARBINARY type is not currently
supported.
+
## Principle Introduction
diff --git
a/versioned_docs/version-4.x/query-acceleration/materialized-view/sync-materialized-view.md
b/versioned_docs/version-4.x/query-acceleration/materialized-view/sync-materialized-view.md
index 713ce3bb904..d2c06c0b4b6 100644
---
a/versioned_docs/version-4.x/query-acceleration/materialized-view/sync-materialized-view.md
+++
b/versioned_docs/version-4.x/query-acceleration/materialized-view/sync-materialized-view.md
@@ -27,6 +27,8 @@ A synchronous materialized view is a special type of table in
Doris that stores
- The SELECT list cannot include auto-increment columns, constants, duplicate
expressions, or window functions.
+- The SELECT list cannot include VARBINARY type column.
+
- The column names in the select list of a sync materialized view must not be
the same as any existing columns in the base table, nor duplicate the column
names of other sync materialized views on the same base table. You can avoid
name conflicts by specifying aliases (e.g., col as xxx).
- If the SELECT list contains aggregation functions, these must be root
expressions (e.g., `sum(a + 1)` is supported, but `sum(a) + 1` is not), and no
non-aggregation function expressions can follow the aggregation function (e.g.,
`SELECT x, sum(a)` is allowed, but `SELECT sum(a), x` is not).
diff --git
a/versioned_docs/version-4.x/query-acceleration/optimization-technology-principle/statistics.md
b/versioned_docs/version-4.x/query-acceleration/optimization-technology-principle/statistics.md
index 16d3ff8734b..751952436c3 100644
---
a/versioned_docs/version-4.x/query-acceleration/optimization-technology-principle/statistics.md
+++
b/versioned_docs/version-4.x/query-acceleration/optimization-technology-principle/statistics.md
@@ -23,7 +23,7 @@ Doris enables the automatic sampling collection of internal
tables by default. T
Currently, the system only supports collecting statistics for columns of basic
data types, including BOOLEAN, TINYINT, SMALLINT, INT, BIGINT, LARGEINT, FLOAT,
DOUBLE, DATE, DATETIME, STRING, VARCHAR, TEXT, among others.
-Columns of complex types, such as JSONB, VARIANT, MAP, STRUCT, ARRAY, HLL,
BITMAP, TIME, TIMEV2, are skipped.
+Columns of complex types, such as JSONB, VARIANT, MAP, STRUCT, ARRAY, HLL,
BITMAP, TIME, TIMEV2, VARBINARY are skipped.
Statistics can be collected manually or automatically, and the results are
stored in the `internal.__internal_schema.column_statistics` table. The
following sections detail these two collection methods.
@@ -442,7 +442,7 @@ If the number of columns does not exceed the threshold,
execute `show auto analy
### Q3: Why are statistics not available for some columns?
-Currently, the system only supports collecting statistics for columns of basic
data types. For complex types such as JSONB, VARIANT, MAP, STRUCT, ARRAY, HLL,
BITMAP, TIME, and TIMEV2, the system skips them.
+Currently, the system only supports collecting statistics for columns of basic
data types. For complex types such as JSONB, VARIANT, MAP, STRUCT, ARRAY, HLL,
BITMAP, TIME, TIMEV2, VARBINARY the system skips them.
### Q4: Error: "Stats table not available, please make sure your cluster
status is normal"
diff --git
a/versioned_docs/version-4.x/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
b/versioned_docs/version-4.x/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
index 65910f1f6d2..9916816a7c8 100644
---
a/versioned_docs/version-4.x/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
+++
b/versioned_docs/version-4.x/sql-manual/basic-element/sql-data-types/binary-type/VARBINARY.md
@@ -9,7 +9,9 @@
### Description
A variable-length binary byte sequence, where M denotes the maximum length (in
bytes).
-Unlike VARCHAR, it stores and compares data byte-wise with no character set or
collation, suitable for arbitrary binary data (e.g., file fragments, hashes,
encrypted/compressed data).
+Unlike VARCHAR, it stores and compares data byte-wise with no character set or
collation, suitable for arbitrary binary data (e.g., file fragments, hashes,
encrypted/compressed data), with a maximum length of 2,147,483,647.
+
+Currently, VARBINARY columns are not supported in created materialized views,
or for use in Group By keys, Join Keys, and comparison predicates.
Version and limitations: Supported since 4.0; currently not supported as a
column type for table creation and storage in Doris. You can map
BINARY/VARBINARY fields from external systems to Doris VARBINARY via Catalogs
for querying.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
