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 9bc6a4a0140 [opt](pg) add array mapping doc (#3141)
9bc6a4a0140 is described below
commit 9bc6a4a01403d58879e0dec684a4eaaac5ccbf84
Author: Mingyu Chen (Rayner) <[email protected]>
AuthorDate: Tue Dec 2 16:03:08 2025 +0800
[opt](pg) add array mapping doc (#3141)
## Versions
- [x] dev
- [x] 4.x
- [x] 3.x
- [x] 2.1
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [ ] Checked by AI
- [ ] Test Cases Built
---
docs/lakehouse/catalogs/jdbc-pg-catalog.md | 14 ++++++++++++++
.../current/lakehouse/catalogs/jdbc-pg-catalog.md | 14 ++++++++++++++
.../version-2.1/lakehouse/catalogs/jdbc-pg-catalog.md | 15 +++++++++++++++
.../version-3.x/lakehouse/catalogs/jdbc-pg-catalog.md | 14 ++++++++++++++
.../version-4.x/lakehouse/catalogs/jdbc-pg-catalog.md | 14 ++++++++++++++
.../version-2.1/lakehouse/catalogs/jdbc-pg-catalog.md | 17 ++++++++++++++++-
.../version-3.x/lakehouse/catalogs/jdbc-pg-catalog.md | 14 ++++++++++++++
.../version-4.x/lakehouse/catalogs/jdbc-pg-catalog.md | 14 ++++++++++++++
8 files changed, 115 insertions(+), 1 deletion(-)
diff --git a/docs/lakehouse/catalogs/jdbc-pg-catalog.md
b/docs/lakehouse/catalogs/jdbc-pg-catalog.md
index be521433ccc..48e740f29ce 100644
--- a/docs/lakehouse/catalogs/jdbc-pg-catalog.md
+++ b/docs/lakehouse/catalogs/jdbc-pg-catalog.md
@@ -82,8 +82,22 @@ When mapping PostgreSQL, a Database in Doris corresponds to
a Schema under a spe
| uuid | string |
|
| bit | boolean / string | Doris
does not support bit type, bit type will be mapped to boolean when bit(1),
otherwise mapped to string. |
| bytea | varbinary |Controlled by the
`enable.mapping.varbinary` property of Catalog (supported since 4.0.3). The
default is `false`, which maps to `string`; when `true`, it maps to `varbinary`
type.|
+| array | array | Please
refer to the following explanation regarding the mapping methods for array
types. |
| other | UNSUPPORTED |
|
+- Array Types
+
+ In PostgreSQL, array types can be defined as follows:
+
+ ```
+ col1 text[]
+ col2 in4[][]
+ ```
+
+ However, the array dimensions cannot be directly obtained from the
PostgreSQL metadata. For example, `text[]` could be a one-dimensional array or
a two-dimensional array. The array dimensions can only be determined after data
is written.
+
+ Doris requires the array dimensions to be explicitly declared. Therefore,
Doris can only map correctly if the corresponding array column in PostgreSQL
contains data; otherwise, the array column will be mapped as `UNSUPPORTED`.
+
## Appendix
### Time Zone Issues
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/jdbc-pg-catalog.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/jdbc-pg-catalog.md
index 1e25d174627..b2f14cd3044 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/jdbc-pg-catalog.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/jdbc-pg-catalog.md
@@ -82,8 +82,22 @@ CREATE CATALOG postgresql_catalog PROPERTIES (
| uuid | string |
|
| bit | boolean / string | Doris 不支持
bit 类型，bit 类型会在 bit(1) 时被映射为 boolean，其他情况下映射为 string。 |
| bytea | varbinary | 由 properties 中 `enable.mapping.varbianry` (4.0.3 后开始支持)
属性控制。默认为 `false`, 则映射到 `string`; 为 `true` 时，则映射到 `varbinary` 类型。|
+| array | array |
关于数组类型的映射方式，请参与下面的说明。 |
| other | UNSUPPORTED |
|
+- 数组类型
+
+ PostgreSQL 中可以通过如下方式定义数组类型：
+
+ ```
+ col1 text[]
+ col2 in4[][]
+ ```
+
+ 但无法从 PostgreSQL 元数据中直接获取数组的维度，比如 `text[]`
有可能是一维数组，也有可能是二维数组。数组的维度，只有在写入数据后，才能确定。
+
+ 而 Doris 必须显式声明数组的维度。因此，只有 PostgreSQL 对应的数组列中有数据，Doris 才能正确映射，否则，数组列会被映射为
`UNSUPPORTED`。
+
## 附录
### 时区问题
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/jdbc-pg-catalog.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/jdbc-pg-catalog.md
index a126c36fa60..b2f14cd3044 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/jdbc-pg-catalog.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/jdbc-pg-catalog.md
@@ -81,8 +81,23 @@ CREATE CATALOG postgresql_catalog PROPERTIES (
| cidr/inet/macaddr | string |
|
| uuid | string |
|
| bit | boolean / string | Doris 不支持
bit 类型，bit 类型会在 bit(1) 时被映射为 boolean，其他情况下映射为 string。 |
+| bytea | varbinary | 由 properties 中 `enable.mapping.varbianry` (4.0.3 后开始支持)
属性控制。默认为 `false`, 则映射到 `string`; 为 `true` 时，则映射到 `varbinary` 类型。|
+| array | array |
关于数组类型的映射方式，请参与下面的说明。 |
| other | UNSUPPORTED |
|
+- 数组类型
+
+ PostgreSQL 中可以通过如下方式定义数组类型：
+
+ ```
+ col1 text[]
+ col2 in4[][]
+ ```
+
+ 但无法从 PostgreSQL 元数据中直接获取数组的维度，比如 `text[]`
有可能是一维数组，也有可能是二维数组。数组的维度，只有在写入数据后，才能确定。
+
+ 而 Doris 必须显式声明数组的维度。因此，只有 PostgreSQL 对应的数组列中有数据，Doris 才能正确映射，否则，数组列会被映射为
`UNSUPPORTED`。
+
## 附录
### 时区问题
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/catalogs/jdbc-pg-catalog.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/catalogs/jdbc-pg-catalog.md
index 1e25d174627..b2f14cd3044 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/catalogs/jdbc-pg-catalog.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/catalogs/jdbc-pg-catalog.md
@@ -82,8 +82,22 @@ CREATE CATALOG postgresql_catalog PROPERTIES (
| uuid | string |
|
| bit | boolean / string | Doris 不支持
bit 类型，bit 类型会在 bit(1) 时被映射为 boolean，其他情况下映射为 string。 |
| bytea | varbinary | 由 properties 中 `enable.mapping.varbianry` (4.0.3 后开始支持)
属性控制。默认为 `false`, 则映射到 `string`; 为 `true` 时，则映射到 `varbinary` 类型。|
+| array | array |
关于数组类型的映射方式，请参与下面的说明。 |
| other | UNSUPPORTED |
|
+- 数组类型
+
+ PostgreSQL 中可以通过如下方式定义数组类型：
+
+ ```
+ col1 text[]
+ col2 in4[][]
+ ```
+
+ 但无法从 PostgreSQL 元数据中直接获取数组的维度，比如 `text[]`
有可能是一维数组，也有可能是二维数组。数组的维度，只有在写入数据后，才能确定。
+
+ 而 Doris 必须显式声明数组的维度。因此，只有 PostgreSQL 对应的数组列中有数据，Doris 才能正确映射，否则，数组列会被映射为
`UNSUPPORTED`。
+
## 附录
### 时区问题
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/catalogs/jdbc-pg-catalog.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/catalogs/jdbc-pg-catalog.md
index 1e25d174627..b2f14cd3044 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/catalogs/jdbc-pg-catalog.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/catalogs/jdbc-pg-catalog.md
@@ -82,8 +82,22 @@ CREATE CATALOG postgresql_catalog PROPERTIES (
| uuid | string |
|
| bit | boolean / string | Doris 不支持
bit 类型，bit 类型会在 bit(1) 时被映射为 boolean，其他情况下映射为 string。 |
| bytea | varbinary | 由 properties 中 `enable.mapping.varbianry` (4.0.3 后开始支持)
属性控制。默认为 `false`, 则映射到 `string`; 为 `true` 时，则映射到 `varbinary` 类型。|
+| array | array |
关于数组类型的映射方式，请参与下面的说明。 |
| other | UNSUPPORTED |
|
+- 数组类型
+
+ PostgreSQL 中可以通过如下方式定义数组类型：
+
+ ```
+ col1 text[]
+ col2 in4[][]
+ ```
+
+ 但无法从 PostgreSQL 元数据中直接获取数组的维度，比如 `text[]`
有可能是一维数组，也有可能是二维数组。数组的维度，只有在写入数据后，才能确定。
+
+ 而 Doris 必须显式声明数组的维度。因此，只有 PostgreSQL 对应的数组列中有数据，Doris 才能正确映射，否则，数组列会被映射为
`UNSUPPORTED`。
+
## 附录
### 时区问题
diff --git a/versioned_docs/version-2.1/lakehouse/catalogs/jdbc-pg-catalog.md
b/versioned_docs/version-2.1/lakehouse/catalogs/jdbc-pg-catalog.md
index bd0e259a54d..48e740f29ce 100644
--- a/versioned_docs/version-2.1/lakehouse/catalogs/jdbc-pg-catalog.md
+++ b/versioned_docs/version-2.1/lakehouse/catalogs/jdbc-pg-catalog.md
@@ -81,8 +81,23 @@ When mapping PostgreSQL, a Database in Doris corresponds to
a Schema under a spe
| cidr/inet/macaddr | string |
|
| uuid | string |
|
| bit | boolean / string | Doris
does not support bit type, bit type will be mapped to boolean when bit(1),
otherwise mapped to string. |
+| bytea | varbinary |Controlled by the
`enable.mapping.varbinary` property of Catalog (supported since 4.0.3). The
default is `false`, which maps to `string`; when `true`, it maps to `varbinary`
type.|
+| array | array | Please
refer to the following explanation regarding the mapping methods for array
types. |
| other | UNSUPPORTED |
|
+- Array Types
+
+ In PostgreSQL, array types can be defined as follows:
+
+ ```
+ col1 text[]
+ col2 in4[][]
+ ```
+
+ However, the array dimensions cannot be directly obtained from the
PostgreSQL metadata. For example, `text[]` could be a one-dimensional array or
a two-dimensional array. The array dimensions can only be determined after data
is written.
+
+ Doris requires the array dimensions to be explicitly declared. Therefore,
Doris can only map correctly if the corresponding array column in PostgreSQL
contains data; otherwise, the array column will be mapped as `UNSUPPORTED`.
+
## Appendix
### Time Zone Issues
@@ -91,4 +106,4 @@ Since Doris does not support timestamp types with time
zones, when reading the t
And because when reading data from JDBC type Catalog, the Java part of BE uses
the JVM time zone. The JVM time zone defaults to the time zone of the BE
deployment machine, which affects the time zone conversion when JDBC reads data.
-To ensure time zone consistency, it is recommended to set the JVM time zone in
`JAVA_OPTS` of `be.conf` to be consistent with the `time_zone` of Doris session.
\ No newline at end of file
+To ensure time zone consistency, it is recommended to set the JVM time zone in
`JAVA_OPTS` of `be.conf` to be consistent with the `time_zone` of Doris session.
diff --git a/versioned_docs/version-3.x/lakehouse/catalogs/jdbc-pg-catalog.md
b/versioned_docs/version-3.x/lakehouse/catalogs/jdbc-pg-catalog.md
index be521433ccc..48e740f29ce 100644
--- a/versioned_docs/version-3.x/lakehouse/catalogs/jdbc-pg-catalog.md
+++ b/versioned_docs/version-3.x/lakehouse/catalogs/jdbc-pg-catalog.md
@@ -82,8 +82,22 @@ When mapping PostgreSQL, a Database in Doris corresponds to
a Schema under a spe
| uuid | string |
|
| bit | boolean / string | Doris
does not support bit type, bit type will be mapped to boolean when bit(1),
otherwise mapped to string. |
| bytea | varbinary |Controlled by the
`enable.mapping.varbinary` property of Catalog (supported since 4.0.3). The
default is `false`, which maps to `string`; when `true`, it maps to `varbinary`
type.|
+| array | array | Please
refer to the following explanation regarding the mapping methods for array
types. |
| other | UNSUPPORTED |
|
+- Array Types
+
+ In PostgreSQL, array types can be defined as follows:
+
+ ```
+ col1 text[]
+ col2 in4[][]
+ ```
+
+ However, the array dimensions cannot be directly obtained from the
PostgreSQL metadata. For example, `text[]` could be a one-dimensional array or
a two-dimensional array. The array dimensions can only be determined after data
is written.
+
+ Doris requires the array dimensions to be explicitly declared. Therefore,
Doris can only map correctly if the corresponding array column in PostgreSQL
contains data; otherwise, the array column will be mapped as `UNSUPPORTED`.
+
## Appendix
### Time Zone Issues
diff --git a/versioned_docs/version-4.x/lakehouse/catalogs/jdbc-pg-catalog.md
b/versioned_docs/version-4.x/lakehouse/catalogs/jdbc-pg-catalog.md
index be521433ccc..48e740f29ce 100644
--- a/versioned_docs/version-4.x/lakehouse/catalogs/jdbc-pg-catalog.md
+++ b/versioned_docs/version-4.x/lakehouse/catalogs/jdbc-pg-catalog.md
@@ -82,8 +82,22 @@ When mapping PostgreSQL, a Database in Doris corresponds to
a Schema under a spe
| uuid | string |
|
| bit | boolean / string | Doris
does not support bit type, bit type will be mapped to boolean when bit(1),
otherwise mapped to string. |
| bytea | varbinary |Controlled by the
`enable.mapping.varbinary` property of Catalog (supported since 4.0.3). The
default is `false`, which maps to `string`; when `true`, it maps to `varbinary`
type.|
+| array | array | Please
refer to the following explanation regarding the mapping methods for array
types. |
| other | UNSUPPORTED |
|
+- Array Types
+
+ In PostgreSQL, array types can be defined as follows:
+
+ ```
+ col1 text[]
+ col2 in4[][]
+ ```
+
+ However, the array dimensions cannot be directly obtained from the
PostgreSQL metadata. For example, `text[]` could be a one-dimensional array or
a two-dimensional array. The array dimensions can only be determined after data
is written.
+
+ Doris requires the array dimensions to be explicitly declared. Therefore,
Doris can only map correctly if the corresponding array column in PostgreSQL
contains data; otherwise, the array column will be mapped as `UNSUPPORTED`.
+
## Appendix
### Time Zone Issues
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
