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 f0fc929d7be [opt](catalog) add db2 charset options and opt iceberg doc 
(#2861)
f0fc929d7be is described below

commit f0fc929d7bee612b93df70f4a034fb3fa784aabe
Author: Mingyu Chen (Rayner) <[email protected]>
AuthorDate: Wed Sep 10 10:08:36 2025 -0700

    [opt](catalog) add db2 charset options and opt iceberg doc (#2861)
    
    ## Versions
    
    - [x] dev
    - [x] 3.0
    - [x] 2.1
    - [ ] 2.0
    
    ## Languages
    
    - [x] Chinese
    - [x] English
    
    ## Docs Checklist
    
    - [ ] Checked by AI
    - [ ] Test Cases Built
---
 docs/lakehouse/catalogs/iceberg-catalog.md                              | 2 +-
 .../current/lakehouse/catalogs/iceberg-catalog.md                       | 2 +-
 .../version-2.1/lakehouse/catalogs/iceberg-catalog.md                   | 2 +-
 .../version-3.0/lakehouse/catalogs/iceberg-catalog.md                   | 2 +-
 versioned_docs/version-2.1/lakehouse/catalogs/iceberg-catalog.md        | 2 +-
 versioned_docs/version-3.0/lakehouse/catalogs/iceberg-catalog.md        | 2 +-
 6 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/lakehouse/catalogs/iceberg-catalog.md 
b/docs/lakehouse/catalogs/iceberg-catalog.md
index ca24d14083e..4eebc3c74ce 100644
--- a/docs/lakehouse/catalogs/iceberg-catalog.md
+++ b/docs/lakehouse/catalogs/iceberg-catalog.md
@@ -128,7 +128,7 @@ The current Iceberg dependency is version 1.6.1, which is 
compatible with higher
 >
 > Doris currently does not support `Timestamp` types with timezone. All 
 > `timestamp` and `timestamptz` will be uniformly mapped to `datetime(N)` 
 > type. However, during reading and writing, Doris will correctly handle 
 > timezones based on the actual source type. For example, after specifying a 
 > timezone with `SET time_zone=<tz>`, it will affect the reading and writing 
 > results of `timestamptz` columns.
 >
-> You can check whether the source type has timezone information in the Extra 
column of the `DESCRIBE table_name` statement. If it shows `WITH_TIMEZONE`, it 
indicates that the source type is a timezone-aware type. (This feature is
+> You can check whether the source type has timezone information in the Extra 
column of the `DESCRIBE table_name` statement. If it shows `WITH_TIMEZONE`, it 
indicates that the source type is a timezone-aware type. (Supported since 
3.1.0).
 
 ## Examples
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/iceberg-catalog.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/iceberg-catalog.md
index 00db7d0e6e8..3e1cdeb646b 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/iceberg-catalog.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/iceberg-catalog.md
@@ -140,7 +140,7 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
 >
 > Doris 当前不支持带时区的 `Timestamp` 类型。所有 `timestamp` 和 `timestamptz` 会统一映射到 
 > `datetime(N)` 类型上。但在读取和写入时,Doris 会根据实际源类型正确处理时区。如通过 `SET time_zone=<tz>` 
 > 指定时区后,会影响 `timestamptz` 列的读取和写入结果。
 >
-> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示 
`WITH_TIMEZONE`,则表示源类型是带时区的类型。(该功能自 3.0.8 版本支持)。
+> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示 
`WITH_TIMEZONE`,则表示源类型是带时区的类型。(该功能自 3.1.0 版本支持)。
 
 ## 基础示例
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/iceberg-catalog.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/iceberg-catalog.md
index 00db7d0e6e8..3e1cdeb646b 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/iceberg-catalog.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/iceberg-catalog.md
@@ -140,7 +140,7 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
 >
 > Doris 当前不支持带时区的 `Timestamp` 类型。所有 `timestamp` 和 `timestamptz` 会统一映射到 
 > `datetime(N)` 类型上。但在读取和写入时,Doris 会根据实际源类型正确处理时区。如通过 `SET time_zone=<tz>` 
 > 指定时区后,会影响 `timestamptz` 列的读取和写入结果。
 >
-> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示 
`WITH_TIMEZONE`,则表示源类型是带时区的类型。(该功能自 3.0.8 版本支持)。
+> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示 
`WITH_TIMEZONE`,则表示源类型是带时区的类型。(该功能自 3.1.0 版本支持)。
 
 ## 基础示例
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/catalogs/iceberg-catalog.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/catalogs/iceberg-catalog.md
index 00db7d0e6e8..3e1cdeb646b 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/catalogs/iceberg-catalog.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/catalogs/iceberg-catalog.md
@@ -140,7 +140,7 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
 >
 > Doris 当前不支持带时区的 `Timestamp` 类型。所有 `timestamp` 和 `timestamptz` 会统一映射到 
 > `datetime(N)` 类型上。但在读取和写入时,Doris 会根据实际源类型正确处理时区。如通过 `SET time_zone=<tz>` 
 > 指定时区后,会影响 `timestamptz` 列的读取和写入结果。
 >
-> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示 
`WITH_TIMEZONE`,则表示源类型是带时区的类型。(该功能自 3.0.8 版本支持)。
+> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示 
`WITH_TIMEZONE`,则表示源类型是带时区的类型。(该功能自 3.1.0 版本支持)。
 
 ## 基础示例
 
diff --git a/versioned_docs/version-2.1/lakehouse/catalogs/iceberg-catalog.md 
b/versioned_docs/version-2.1/lakehouse/catalogs/iceberg-catalog.md
index ca24d14083e..4eebc3c74ce 100644
--- a/versioned_docs/version-2.1/lakehouse/catalogs/iceberg-catalog.md
+++ b/versioned_docs/version-2.1/lakehouse/catalogs/iceberg-catalog.md
@@ -128,7 +128,7 @@ The current Iceberg dependency is version 1.6.1, which is 
compatible with higher
 >
 > Doris currently does not support `Timestamp` types with timezone. All 
 > `timestamp` and `timestamptz` will be uniformly mapped to `datetime(N)` 
 > type. However, during reading and writing, Doris will correctly handle 
 > timezones based on the actual source type. For example, after specifying a 
 > timezone with `SET time_zone=<tz>`, it will affect the reading and writing 
 > results of `timestamptz` columns.
 >
-> You can check whether the source type has timezone information in the Extra 
column of the `DESCRIBE table_name` statement. If it shows `WITH_TIMEZONE`, it 
indicates that the source type is a timezone-aware type. (This feature is
+> You can check whether the source type has timezone information in the Extra 
column of the `DESCRIBE table_name` statement. If it shows `WITH_TIMEZONE`, it 
indicates that the source type is a timezone-aware type. (Supported since 
3.1.0).
 
 ## Examples
 
diff --git a/versioned_docs/version-3.0/lakehouse/catalogs/iceberg-catalog.md 
b/versioned_docs/version-3.0/lakehouse/catalogs/iceberg-catalog.md
index ca24d14083e..4eebc3c74ce 100644
--- a/versioned_docs/version-3.0/lakehouse/catalogs/iceberg-catalog.md
+++ b/versioned_docs/version-3.0/lakehouse/catalogs/iceberg-catalog.md
@@ -128,7 +128,7 @@ The current Iceberg dependency is version 1.6.1, which is 
compatible with higher
 >
 > Doris currently does not support `Timestamp` types with timezone. All 
 > `timestamp` and `timestamptz` will be uniformly mapped to `datetime(N)` 
 > type. However, during reading and writing, Doris will correctly handle 
 > timezones based on the actual source type. For example, after specifying a 
 > timezone with `SET time_zone=<tz>`, it will affect the reading and writing 
 > results of `timestamptz` columns.
 >
-> You can check whether the source type has timezone information in the Extra 
column of the `DESCRIBE table_name` statement. If it shows `WITH_TIMEZONE`, it 
indicates that the source type is a timezone-aware type. (This feature is
+> You can check whether the source type has timezone information in the Extra 
column of the `DESCRIBE table_name` statement. If it shows `WITH_TIMEZONE`, it 
indicates that the source type is a timezone-aware type. (Supported since 
3.1.0).
 
 ## Examples
 


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

Reply via email to