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 91096f7f748 [opt](iceberg) add some timezone doc for iceberg and
paimon (#2749)
91096f7f748 is described below
commit 91096f7f7489abd47fcbe9618f05904a1f82406a
Author: Mingyu Chen (Rayner) <[email protected]>
AuthorDate: Wed Aug 13 17:38:22 2025 -0700
[opt](iceberg) add some timezone doc for iceberg and paimon (#2749)
## 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/best-practices/doris-dlf-paimon.md | 2 +-
docs/lakehouse/catalogs/iceberg-catalog.md | 8 +++++++-
docs/lakehouse/catalogs/paimon-catalog.md | 6 ++++++
.../current/lakehouse/best-practices/doris-dlf-paimon.md | 2 +-
.../current/lakehouse/catalogs/iceberg-catalog.md | 8 +++++++-
.../current/lakehouse/catalogs/paimon-catalog.md | 6 ++++++
.../version-2.1/lakehouse/best-practices/doris-dlf-paimon.md | 2 +-
.../version-2.1/lakehouse/catalogs/iceberg-catalog.md | 8 +++++++-
.../version-2.1/lakehouse/catalogs/paimon-catalog.md | 6 ++++++
.../version-3.0/lakehouse/best-practices/doris-dlf-paimon.md | 2 +-
.../version-3.0/lakehouse/catalogs/iceberg-catalog.md | 8 +++++++-
.../version-3.0/lakehouse/catalogs/paimon-catalog.md | 6 ++++++
.../version-2.1/lakehouse/best-practices/doris-dlf-paimon.md | 2 +-
versioned_docs/version-2.1/lakehouse/catalogs/iceberg-catalog.md | 8 +++++++-
versioned_docs/version-2.1/lakehouse/catalogs/paimon-catalog.md | 6 ++++++
.../version-3.0/lakehouse/best-practices/doris-dlf-paimon.md | 2 +-
versioned_docs/version-3.0/lakehouse/catalogs/iceberg-catalog.md | 8 +++++++-
versioned_docs/version-3.0/lakehouse/catalogs/paimon-catalog.md | 6 ++++++
18 files changed, 84 insertions(+), 12 deletions(-)
diff --git a/docs/lakehouse/best-practices/doris-dlf-paimon.md
b/docs/lakehouse/best-practices/doris-dlf-paimon.md
index 60af09b4c49..c8ff3b95bf5 100644
--- a/docs/lakehouse/best-practices/doris-dlf-paimon.md
+++ b/docs/lakehouse/best-practices/doris-dlf-paimon.md
@@ -1,6 +1,6 @@
---
{
- "title": "Integration with Aliyun DLF",
+ "title": "Integration with Aliyun DLF Rest Catalog",
"language": "en"
}
diff --git a/docs/lakehouse/catalogs/iceberg-catalog.md
b/docs/lakehouse/catalogs/iceberg-catalog.md
index c4d6bd3c7b4..4dac91d3878 100644
--- a/docs/lakehouse/catalogs/iceberg-catalog.md
+++ b/docs/lakehouse/catalogs/iceberg-catalog.md
@@ -124,6 +124,12 @@ The current Iceberg dependency is version 1.6.1, which is
compatible with higher
| list | array |
|
| other | UNSUPPORTED |
|
+> Note:
+>
+> 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
+
## Examples
### Iceberg on Hive Metastore
@@ -763,7 +769,7 @@ For an Iceberg Database, you must first drop all tables
under the database befor
Note that for the Iceberg table created by Doris, the Datetime corresponds
to the `timestamp_ntz` type.
- In versions after 2.1.11 and 3.0.7, when the Datetime type is written to
the Parquet file, the physical type used is INT64 instead of INT96.
+ In versions after 3.1.0, when the Datetime type is written to the Parquet
file, the physical type used is INT64 instead of INT96.
And if the Iceberg table is created by other systems, although the
`timestamp` and `timestamp_ntz` types are both mapped to the Doris Datetime
type. However, when writing, it will determine whether the time zone needs to
be processed based on the actual type.
diff --git a/docs/lakehouse/catalogs/paimon-catalog.md
b/docs/lakehouse/catalogs/paimon-catalog.md
index f2df00afdb1..fc694098c2a 100644
--- a/docs/lakehouse/catalogs/paimon-catalog.md
+++ b/docs/lakehouse/catalogs/paimon-catalog.md
@@ -124,6 +124,12 @@ The currently dependent Paimon version is 1.0.0.
| row | struct |
|
| other | UNSUPPORTED |
|
+> Note:
+>
+> Doris currently does not support `Timestamp` types with timezone. All
`timestamp_without_time_zone` and `timestamp_with_local_time_zone` will be
uniformly mapped to `datetime(N)` type. However, during reading, 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 return
results of `timestamp_with_local_time_zone` columns.
+>
+> You can check whether the source type contains timezone information in the
Extra column of the `DESCRIBE table_name` statement. If it displays
`WITH_TIMEZONE`, it indicates that the source type is a timezone-aware type.
(This feature is supported since 3.0.8)
+
## Examples
### Paimon on HDFS
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/best-practices/doris-dlf-paimon.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/best-practices/doris-dlf-paimon.md
index ee2e9753643..0db08ae4f3d 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/best-practices/doris-dlf-paimon.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/best-practices/doris-dlf-paimon.md
@@ -1,6 +1,6 @@
---
{
- "title": "Doris 集成阿里云 DLF",
+ "title": "Doris 集成阿里云 DLF Rest Catalog",
"language": "zh-CN"
}
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 cf08612ada9..fe9cc8ca014 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
@@ -136,6 +136,12 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
| list | array |
|
| other | UNSUPPORTED |
|
+> 注：
+>
+> Doris 当前不支持带时区的 `Timestamp` 类型。所有 `timestamp` 和 `timestamptz` 会统一映射到
`datetime(N)` 类型上。但在读取和写入时，Doris 会根据实际源类型正确处理时区。如通过 `SET time_zone=<tz>`
指定时区后，会影响 `timestamptz` 列的读取和写入结果。
+>
+> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示
`WITH_TIMEZONE`，则表示源类型是带时区的类型。(该功能自 3.0.8 版本支持)。
+
## 基础示例
### Iceberg on Hive Metastore
@@ -772,7 +778,7 @@ DROP DATABASE [IF EXISTS] iceberg.iceberg_db;
注意，由 Doris 创建的 Iceberg 表，Datetime 对应的是 `timestamp_ntz` 类型。
- 2.1.11 和 3.0.7 之后的版本中，Datetime 类型写入到 Parquet 文件时，物理类型使用的是 INT64 而非 INT96。
+ 3.1.0 之后的版本中，Datetime 类型写入到 Parquet 文件时，物理类型使用的是 INT64 而非 INT96。
此外，如果是其他系统创建的 Iceberg 表，虽然 `timestamp` 和 `timestamp_ntz` 类型都映射为 Doris 的
Datetime 类型。但在写入时，会根据实际类型判断是否需要处理时区。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/paimon-catalog.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/paimon-catalog.md
index 07da5d94d99..8527d15fb5c 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/paimon-catalog.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/paimon-catalog.md
@@ -124,6 +124,12 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
| row | struct |
|
| other | UNSUPPORTED |
|
+> 注：
+>
+> Doris 当前不支持带时区的 `Timestamp` 类型。所有 `timestamp_without_time_zone` 和
`timestamp_with_local_time_zone` 会统一映射到 `datetime(N)` 类型上。但在读取时，Doris
会根据实际源类型正确处理时区。如通过 `SET time_zone=<tz>` 指定时区后，会影响
`timestamp_with_local_time_zone` 列的返回结果。
+>
+> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示
`WITH_TIMEZONE`，则表示源类型是带时区的类型。(该功能自 3.0.8 版本支持)。
+
## 基础示例
### Paimon on HDFS
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/best-practices/doris-dlf-paimon.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/best-practices/doris-dlf-paimon.md
index ee2e9753643..0db08ae4f3d 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/best-practices/doris-dlf-paimon.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/best-practices/doris-dlf-paimon.md
@@ -1,6 +1,6 @@
---
{
- "title": "Doris 集成阿里云 DLF",
+ "title": "Doris 集成阿里云 DLF Rest Catalog",
"language": "zh-CN"
}
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 cf08612ada9..fe9cc8ca014 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
@@ -136,6 +136,12 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
| list | array |
|
| other | UNSUPPORTED |
|
+> 注：
+>
+> Doris 当前不支持带时区的 `Timestamp` 类型。所有 `timestamp` 和 `timestamptz` 会统一映射到
`datetime(N)` 类型上。但在读取和写入时，Doris 会根据实际源类型正确处理时区。如通过 `SET time_zone=<tz>`
指定时区后，会影响 `timestamptz` 列的读取和写入结果。
+>
+> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示
`WITH_TIMEZONE`，则表示源类型是带时区的类型。(该功能自 3.0.8 版本支持)。
+
## 基础示例
### Iceberg on Hive Metastore
@@ -772,7 +778,7 @@ DROP DATABASE [IF EXISTS] iceberg.iceberg_db;
注意，由 Doris 创建的 Iceberg 表，Datetime 对应的是 `timestamp_ntz` 类型。
- 2.1.11 和 3.0.7 之后的版本中，Datetime 类型写入到 Parquet 文件时，物理类型使用的是 INT64 而非 INT96。
+ 3.1.0 之后的版本中，Datetime 类型写入到 Parquet 文件时，物理类型使用的是 INT64 而非 INT96。
此外，如果是其他系统创建的 Iceberg 表，虽然 `timestamp` 和 `timestamp_ntz` 类型都映射为 Doris 的
Datetime 类型。但在写入时，会根据实际类型判断是否需要处理时区。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/paimon-catalog.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/paimon-catalog.md
index 07da5d94d99..8527d15fb5c 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/paimon-catalog.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/paimon-catalog.md
@@ -124,6 +124,12 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
| row | struct |
|
| other | UNSUPPORTED |
|
+> 注：
+>
+> Doris 当前不支持带时区的 `Timestamp` 类型。所有 `timestamp_without_time_zone` 和
`timestamp_with_local_time_zone` 会统一映射到 `datetime(N)` 类型上。但在读取时，Doris
会根据实际源类型正确处理时区。如通过 `SET time_zone=<tz>` 指定时区后，会影响
`timestamp_with_local_time_zone` 列的返回结果。
+>
+> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示
`WITH_TIMEZONE`，则表示源类型是带时区的类型。(该功能自 3.0.8 版本支持)。
+
## 基础示例
### Paimon on HDFS
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/best-practices/doris-dlf-paimon.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/best-practices/doris-dlf-paimon.md
index ee2e9753643..0db08ae4f3d 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/best-practices/doris-dlf-paimon.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/best-practices/doris-dlf-paimon.md
@@ -1,6 +1,6 @@
---
{
- "title": "Doris 集成阿里云 DLF",
+ "title": "Doris 集成阿里云 DLF Rest Catalog",
"language": "zh-CN"
}
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 cf08612ada9..fe9cc8ca014 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
@@ -136,6 +136,12 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
| list | array |
|
| other | UNSUPPORTED |
|
+> 注：
+>
+> Doris 当前不支持带时区的 `Timestamp` 类型。所有 `timestamp` 和 `timestamptz` 会统一映射到
`datetime(N)` 类型上。但在读取和写入时，Doris 会根据实际源类型正确处理时区。如通过 `SET time_zone=<tz>`
指定时区后，会影响 `timestamptz` 列的读取和写入结果。
+>
+> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示
`WITH_TIMEZONE`，则表示源类型是带时区的类型。(该功能自 3.0.8 版本支持)。
+
## 基础示例
### Iceberg on Hive Metastore
@@ -772,7 +778,7 @@ DROP DATABASE [IF EXISTS] iceberg.iceberg_db;
注意，由 Doris 创建的 Iceberg 表，Datetime 对应的是 `timestamp_ntz` 类型。
- 2.1.11 和 3.0.7 之后的版本中，Datetime 类型写入到 Parquet 文件时，物理类型使用的是 INT64 而非 INT96。
+ 3.1.0 之后的版本中，Datetime 类型写入到 Parquet 文件时，物理类型使用的是 INT64 而非 INT96。
此外，如果是其他系统创建的 Iceberg 表，虽然 `timestamp` 和 `timestamp_ntz` 类型都映射为 Doris 的
Datetime 类型。但在写入时，会根据实际类型判断是否需要处理时区。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/catalogs/paimon-catalog.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/catalogs/paimon-catalog.md
index 07da5d94d99..8527d15fb5c 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/catalogs/paimon-catalog.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/catalogs/paimon-catalog.md
@@ -124,6 +124,12 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
| row | struct |
|
| other | UNSUPPORTED |
|
+> 注：
+>
+> Doris 当前不支持带时区的 `Timestamp` 类型。所有 `timestamp_without_time_zone` 和
`timestamp_with_local_time_zone` 会统一映射到 `datetime(N)` 类型上。但在读取时，Doris
会根据实际源类型正确处理时区。如通过 `SET time_zone=<tz>` 指定时区后，会影响
`timestamp_with_local_time_zone` 列的返回结果。
+>
+> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示
`WITH_TIMEZONE`，则表示源类型是带时区的类型。(该功能自 3.0.8 版本支持)。
+
## 基础示例
### Paimon on HDFS
diff --git
a/versioned_docs/version-2.1/lakehouse/best-practices/doris-dlf-paimon.md
b/versioned_docs/version-2.1/lakehouse/best-practices/doris-dlf-paimon.md
index 60af09b4c49..c8ff3b95bf5 100644
--- a/versioned_docs/version-2.1/lakehouse/best-practices/doris-dlf-paimon.md
+++ b/versioned_docs/version-2.1/lakehouse/best-practices/doris-dlf-paimon.md
@@ -1,6 +1,6 @@
---
{
- "title": "Integration with Aliyun DLF",
+ "title": "Integration with Aliyun DLF Rest Catalog",
"language": "en"
}
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 c4d6bd3c7b4..4dac91d3878 100644
--- a/versioned_docs/version-2.1/lakehouse/catalogs/iceberg-catalog.md
+++ b/versioned_docs/version-2.1/lakehouse/catalogs/iceberg-catalog.md
@@ -124,6 +124,12 @@ The current Iceberg dependency is version 1.6.1, which is
compatible with higher
| list | array |
|
| other | UNSUPPORTED |
|
+> Note:
+>
+> 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
+
## Examples
### Iceberg on Hive Metastore
@@ -763,7 +769,7 @@ For an Iceberg Database, you must first drop all tables
under the database befor
Note that for the Iceberg table created by Doris, the Datetime corresponds
to the `timestamp_ntz` type.
- In versions after 2.1.11 and 3.0.7, when the Datetime type is written to
the Parquet file, the physical type used is INT64 instead of INT96.
+ In versions after 3.1.0, when the Datetime type is written to the Parquet
file, the physical type used is INT64 instead of INT96.
And if the Iceberg table is created by other systems, although the
`timestamp` and `timestamp_ntz` types are both mapped to the Doris Datetime
type. However, when writing, it will determine whether the time zone needs to
be processed based on the actual type.
diff --git a/versioned_docs/version-2.1/lakehouse/catalogs/paimon-catalog.md
b/versioned_docs/version-2.1/lakehouse/catalogs/paimon-catalog.md
index f2df00afdb1..fc694098c2a 100644
--- a/versioned_docs/version-2.1/lakehouse/catalogs/paimon-catalog.md
+++ b/versioned_docs/version-2.1/lakehouse/catalogs/paimon-catalog.md
@@ -124,6 +124,12 @@ The currently dependent Paimon version is 1.0.0.
| row | struct |
|
| other | UNSUPPORTED |
|
+> Note:
+>
+> Doris currently does not support `Timestamp` types with timezone. All
`timestamp_without_time_zone` and `timestamp_with_local_time_zone` will be
uniformly mapped to `datetime(N)` type. However, during reading, 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 return
results of `timestamp_with_local_time_zone` columns.
+>
+> You can check whether the source type contains timezone information in the
Extra column of the `DESCRIBE table_name` statement. If it displays
`WITH_TIMEZONE`, it indicates that the source type is a timezone-aware type.
(This feature is supported since 3.0.8)
+
## Examples
### Paimon on HDFS
diff --git
a/versioned_docs/version-3.0/lakehouse/best-practices/doris-dlf-paimon.md
b/versioned_docs/version-3.0/lakehouse/best-practices/doris-dlf-paimon.md
index 60af09b4c49..c8ff3b95bf5 100644
--- a/versioned_docs/version-3.0/lakehouse/best-practices/doris-dlf-paimon.md
+++ b/versioned_docs/version-3.0/lakehouse/best-practices/doris-dlf-paimon.md
@@ -1,6 +1,6 @@
---
{
- "title": "Integration with Aliyun DLF",
+ "title": "Integration with Aliyun DLF Rest Catalog",
"language": "en"
}
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 c4d6bd3c7b4..4dac91d3878 100644
--- a/versioned_docs/version-3.0/lakehouse/catalogs/iceberg-catalog.md
+++ b/versioned_docs/version-3.0/lakehouse/catalogs/iceberg-catalog.md
@@ -124,6 +124,12 @@ The current Iceberg dependency is version 1.6.1, which is
compatible with higher
| list | array |
|
| other | UNSUPPORTED |
|
+> Note:
+>
+> 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
+
## Examples
### Iceberg on Hive Metastore
@@ -763,7 +769,7 @@ For an Iceberg Database, you must first drop all tables
under the database befor
Note that for the Iceberg table created by Doris, the Datetime corresponds
to the `timestamp_ntz` type.
- In versions after 2.1.11 and 3.0.7, when the Datetime type is written to
the Parquet file, the physical type used is INT64 instead of INT96.
+ In versions after 3.1.0, when the Datetime type is written to the Parquet
file, the physical type used is INT64 instead of INT96.
And if the Iceberg table is created by other systems, although the
`timestamp` and `timestamp_ntz` types are both mapped to the Doris Datetime
type. However, when writing, it will determine whether the time zone needs to
be processed based on the actual type.
diff --git a/versioned_docs/version-3.0/lakehouse/catalogs/paimon-catalog.md
b/versioned_docs/version-3.0/lakehouse/catalogs/paimon-catalog.md
index f2df00afdb1..fc694098c2a 100644
--- a/versioned_docs/version-3.0/lakehouse/catalogs/paimon-catalog.md
+++ b/versioned_docs/version-3.0/lakehouse/catalogs/paimon-catalog.md
@@ -124,6 +124,12 @@ The currently dependent Paimon version is 1.0.0.
| row | struct |
|
| other | UNSUPPORTED |
|
+> Note:
+>
+> Doris currently does not support `Timestamp` types with timezone. All
`timestamp_without_time_zone` and `timestamp_with_local_time_zone` will be
uniformly mapped to `datetime(N)` type. However, during reading, 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 return
results of `timestamp_with_local_time_zone` columns.
+>
+> You can check whether the source type contains timezone information in the
Extra column of the `DESCRIBE table_name` statement. If it displays
`WITH_TIMEZONE`, it indicates that the source type is a timezone-aware type.
(This feature is supported since 3.0.8)
+
## Examples
### Paimon on HDFS
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
