Copilot commented on code in PR #3421:
URL: https://github.com/apache/doris-website/pull/3421#discussion_r2867075627
##########
i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/paimon-catalog.mdx:
##########
@@ -133,35 +136,40 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
| Paimon Type | Doris Type | Comment
|
| ---------------------------------- | ------------- |
-------------------------------------- |
-| boolean | boolean |
|
-| tinyint | tinyint |
|
-| smallint | smallint |
|
-| integer | int |
|
-| bigint | bigint |
|
-| float | float |
|
-| double | double |
|
-| decimal(P, S) | decimal(P, S) |
|
-| varchar | string |
|
-| char | string |
|
-| bianry, varbinary | string/varbinary|由 properties 中
`enable.mapping.varbianry` (4.0.3 后开始支持) 属性控制。默认为 `false`, 则映射到 `string`; 为
`true` 时，则映射到 `varbinary` 类型。|
-| date | date |
|
-| timestamp\_without\_time\_zone | datetime(N) | 会根据精度进行对应映射。如果精度大于
6，则最大映射到 6。（可能导致精度丢失） |
-| timestamp\_with\_local\_time\_zone | datetime(N) | 会根据精度进行对应映射。如果精度大于
6，则最大映射到 6。（可能导致精度丢失） |
-| array | array |
|
-| map | map |
|
-| row | struct |
|
-| other | UNSUPPORTED |
|
+| boolean | boolean |
|
+| tinyint | tinyint |
|
+| smallint | smallint |
|
+| integer | int |
|
+| bigint | bigint |
|
+| float | float |
|
+| double | double |
|
+| decimal(P, S) | decimal(P, S) |
|
+| varchar | string |
|
+| char | string |
|
+| binary, varbinary | string/varbinary | 由
properties 中 `enable.mapping.varbinary` (4.0.2 后开始支持) 属性控制。默认为 `false`，则映射到
`string`；为 `true` 时，则映射到 `varbinary` 类型。 |
+| date | date |
|
+| timestamp\_without\_time\_zone | datetime(N) |
会根据精度进行对应映射。如果精度大于 6，则最大映射到 6。（可能导致精度丢失）
|
+| timestamp\_with\_local\_time\_zone | datetime(N)/timestamptz(N) |
会根据精度进行对应映射。如果精度大于 6，则最大映射到 6。（可能导致精度丢失）。由 properties 中
`enable.mapping.timestamp_tz` (4.0.3 后开始支持) 属性控制，默认为 `false`，则映射到 `datetime`；为
`true` 时，则映射到 `timestamptz` 类型 |
+| array | array |
|
+| map | map |
|
+| 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 版本支持)。
+> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示
`WITH_TIMEZONE`，则表示源类型是带时区的类型（该功能自 3.0.8 版本支持）。
+>
+> 4.0.3 后开始支持，可以映射 `timestamp_with_local_time_zone` 到 Doris 的 `timestamptz` 类型。
Review Comment:
这里的注释写了“Doris 当前不支持带时区的 Timestamp 类型，统一映射到 datetime(N)”但同时又新增了“4.0.3
后开始支持映射到 Doris 的 timestamptz 类型”。建议补充说明该映射是有条件的（例如
`enable.mapping.timestamp_tz=true`），并调整“不支持/统一映射”的表述，避免前后矛盾。
##########
i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/ozone.md:
##########
@@ -0,0 +1,68 @@
+---
+{
+ "title": "Apache Ozone | Storages",
+ "language": "zh-CN",
+ "description": "自 4.0.4 版本起，Doris 支持通过 S3 Gateway 访问 Apache Ozone。",
+ "sidebar_label": "Apache Ozone"
+}
Review Comment:
Front matter 的 `title` 使用了 `"Apache Ozone | Storages"`，但现有 storage
文档通常只用存储名作为标题（例如 `docs/lakehouse/storages/s3.md`、`azure-blob.md`）。建议统一为
`"Apache Ozone"` 以保持标题风格一致。
##########
sidebars.ts:
##########
@@ -1226,6 +1277,7 @@ const sidebars: SidebarsConfig = {
'sql-manual/sql-functions/scalar-functions/numeric-functions/floor',
'sql-manual/sql-functions/scalar-functions/numeric-functions/fmod',
'sql-manual/sql-functions/scalar-functions/numeric-functions/format-round',
+
"sql-manual/sql-functions/scalar-functions/numeric-functions/interval",
Review Comment:
The sidebar adds
`sql-manual/sql-functions/scalar-functions/numeric-functions/interval`, but
there is no `interval.md` under
`docs/sql-manual/sql-functions/scalar-functions/numeric-functions/`. Please add
the doc or remove/update this sidebar entry.
```suggestion
```
##########
docs/lakehouse/catalogs/iceberg-catalog.mdx:
##########
@@ -148,6 +167,8 @@ 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. (Supported since
> 3.1.0).
+>
+> Supported since version 4.0.3, `timestamptz` (timestamp with time zone) can
be mapped to the Doris `timestamptz` type.
Review Comment:
In the “Note” block, it says Doris does not support timezone-aware
`Timestamp` and that all `timestamp`/`timestamptz` are uniformly mapped to
`datetime(N)`, but the surrounding text now also states that mapping to Doris
`timestamptz` is supported since 4.0.3. These statements conflict. Please
clarify the behavior (e.g., whether `timestamptz` is supported only when
`enable.mapping.timestamp_tz=true`, and adjust/remove the “does not support”
sentence accordingly).
```suggestion
> By default, all `timestamp` and `timestamptz` source types are stored in
Doris as `datetime(N)` columns. 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.
(Supported since 3.1.0).
>
> Since version 4.0.3, if you enable the catalog property
`enable.mapping.timestamp_tz=true`, `timestamptz` (timestamp with time zone)
from Iceberg can be mapped to the Doris `timestamptz` type; otherwise it
continues to be mapped to `datetime(N)` by default.
```
##########
sidebars.ts:
##########
@@ -222,8 +226,17 @@ const sidebars: SidebarsConfig = {
items: [
'data-operate/import/load-internals/load-internals',
'data-operate/import/load-internals/routine-load-internals',
+
'data-operate/import/load-internals/stream-load-in-complex-network',
],
},
+ {
+ type: 'category',
+ label: 'Continuous Load',
+ items: [
+
'data-operate/import/streaming-job/streaming-job-tvf',
+
'data-operate/import/streaming-job/streaming-job-multi-table',
+ ],
+ }
Review Comment:
Two sidebar entries point to docs that don't exist in the repo:
`data-operate/import/load-internals/stream-load-in-complex-network` (not
present under `docs/data-operate/import/load-internals/`) and the
`data-operate/import/streaming-job/*` pages (the `streaming-job` directory
doesn't exist). Add these docs or remove the sidebar items to prevent build
failures.
```suggestion
],
},
```
##########
i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/iceberg-catalog.mdx:
##########
@@ -162,7 +184,9 @@ 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.1.0 版本支持)。
+> 可以在 `DESCRIBE table_name` 语句中的 Extra 列查看源类型是否带时区信息。如显示
`WITH_TIMEZONE`，则表示源类型是带时区的类型（该功能自 3.1.0 版本支持）。
+>
+> 4.0.3 后开始支持，可以映射 `timestamptz (Timestamp with timezone)` 到 Doris 的
`timestamptz` 类型。
Review Comment:
这里的注释同时写了“Doris 当前不支持带时区的 Timestamp 类型，统一映射到 datetime(N)”以及“4.0.3 后开始支持映射到
Doris 的 timestamptz 类型”，两者表述存在冲突。建议明确说明：是否仅在开启 `enable.mapping.timestamp_tz`
时才映射到 `timestamptz`，并相应调整“不支持”这句话，避免读者误解。
##########
sidebars.ts:
##########
@@ -412,6 +433,8 @@ const sidebars: SidebarsConfig = {
'ai/vector-search/hnsw',
'ai/vector-search/ivf',
'ai/vector-search/index-management',
+ 'ai/vector-search/performance',
+ 'ai/vector-search/behind-index',
Review Comment:
The sidebar adds `ai/ai-overview` and `ai/vector-search/performance` /
`ai/vector-search/behind-index`, but these docs are not present under
`docs/ai/` or `docs/ai/vector-search/`. Please add the pages or remove the
sidebar entries to avoid unknown doc IDs.
##########
sidebars.ts:
##########
@@ -1048,6 +1096,7 @@ const sidebars: SidebarsConfig = {
'sql-manual/basic-element/sql-data-types/date-time/DATE',
'sql-manual/basic-element/sql-data-types/date-time/TIME',
'sql-manual/basic-element/sql-data-types/date-time/DATETIME',
+
'sql-manual/basic-element/sql-data-types/date-time/TIMESTAMPTZ',
Review Comment:
The sidebar adds
`sql-manual/basic-element/sql-data-types/date-time/TIMESTAMPTZ`, but there is
no `TIMESTAMPTZ.md` in
`docs/sql-manual/basic-element/sql-data-types/date-time/` (only
DATE/TIME/DATETIME exist). Please add the missing doc or remove the sidebar
entry to prevent build failures.
```suggestion
```
##########
sidebars.ts:
##########
@@ -2206,6 +2266,7 @@ const sidebars: SidebarsConfig = {
'sql-manual/sql-statements/table-and-view/table/ALTER-TABLE-REPLACE',
'sql-manual/sql-statements/table-and-view/table/ALTER-TABLE-PROPERTY',
'sql-manual/sql-statements/table-and-view/table/ALTER-TABLE-COMMENT',
+
'sql-manual/sql-statements/table-and-view/table/ALTER-TABLE-DISTRIBUTION',
Review Comment:
The sidebar references
`sql-manual/sql-statements/table-and-view/table/ALTER-TABLE-DISTRIBUTION`, but
there is no corresponding doc under
`docs/sql-manual/sql-statements/table-and-view/table/`. Please add the page or
remove/update the sidebar item to avoid an unknown doc ID.
```suggestion
```
##########
sidebars.ts:
##########
@@ -427,13 +450,50 @@ const sidebars: SidebarsConfig = {
label: 'Data Catalogs',
items: [
'lakehouse/catalogs/hive-catalog',
- 'lakehouse/catalogs/iceberg-catalog',
- 'lakehouse/catalogs/hudi-catalog',
- 'lakehouse/catalogs/paimon-catalog',
- 'lakehouse/catalogs/maxcompute-catalog',
+ {
+ type: 'category',
+ label: 'Iceberg Catalog',
+ link: {type: 'doc', id:
'lakehouse/catalogs/iceberg-catalog'},
+ items: [
+
'lakehouse/best-practices/doris-iceberg',
+
'lakehouse/best-practices/doris-aws-s3tables',
+
'lakehouse/best-practices/doris-polaris',
+
'lakehouse/best-practices/doris-gravitino',
+
'lakehouse/best-practices/doris-onelake',
+
'lakehouse/best-practices/doris-unity-catalog',
+
'lakehouse/best-practices/doris-lakekeeper',
+ 'lakehouse/best-practices/doris-nessie'
Review Comment:
The Iceberg Catalog sidebar category includes
`lakehouse/best-practices/doris-lakekeeper` and
`lakehouse/best-practices/doris-nessie`, but these docs are not present under
`docs/lakehouse/best-practices/`. Please add the missing pages or remove/update
these items to avoid unknown doc IDs.
```suggestion
```
##########
sidebars.ts:
##########
@@ -458,6 +518,7 @@ const sidebars: SidebarsConfig = {
'lakehouse/metastores/google-dataproc-metastore',
'lakehouse/metastores/aliyun-dlf',
'lakehouse/metastores/iceberg-rest',
+ 'lakehouse/metastores/iceberg-jdbc',
Review Comment:
The sidebar adds `lakehouse/metastores/iceberg-jdbc`, but there is no
`iceberg-jdbc.md|mdx` under `docs/lakehouse/metastores/` (or the zh-CN i18n
path). Since `iceberg-catalog` now links to this page, the doc should be added
(EN/ZH) or the reference removed.
```suggestion
```
##########
sidebars.ts:
##########
@@ -2491,6 +2556,7 @@ const sidebars: SidebarsConfig = {
type: 'category',
label: 'v3.1',
items: [
+ "releasenotes/v3.1/release-3.1.4",
"releasenotes/v3.1/release-3.1.3",
Review Comment:
The sidebar adds release note pages `releasenotes/v4.0/release-4.0.3`,
`releasenotes/v4.0/release-4.0.2`, and `releasenotes/v3.1/release-3.1.4`, but
these files are not present under `docs/releasenotes/`. Please add the missing
release note docs or remove/update the sidebar entries to avoid unknown doc IDs.
##########
docs/lakehouse/catalogs/paimon-catalog.mdx:
##########
@@ -143,23 +146,27 @@ The currently dependent Paimon version is 1.0.0.
| decimal(P, S) | decimal(P, S) |
|
| varchar | string |
|
| char | string |
|
-| binary, varbinary | string/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.|
+| binary, varbinary | string/varbinary |
Controlled by the `enable.mapping.varbinary` property of Catalog (supported
since 4.0.2). The default is `false`, which maps to `string`; when `true`, it
maps to `varbinary` type.|
| date | date |
|
| timestamp\_without\_time\_zone | datetime(N) | Mapped according to
precision. If precision is greater than 6, it maps to a maximum of 6 (may cause
precision loss). |
-| timestamp\_with\_local\_time\_zone | datetime(N) | Mapped according to
precision. If precision is greater than 6, it maps to a maximum of 6 (may cause
precision loss). |
+| timestamp\_with\_local\_time\_zone | datetime(N)/timestamptz(N) | Mapped
according to precision. If precision is greater than 6, it maps to a maximum of
6 (may cause precision loss). The `enable.mapping.timestamp_tz` property
(supported since version 4.0.3) controls the mapping behavior. By default, it
is set to `false`, in which case the type is mapped to `datetime`. When set to
`true`, it is mapped to the `timestamptz` type.|
| array | array |
|
| map | map |
|
| 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)
+:::info 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)
+
+Supported since version 4.0.3, `timestamp_with_local_time_zone` can be mapped
to Doris `timestamptz` type.
+:::
## Examples
+
Review Comment:
The new info note says Doris does not support timezone-aware `Timestamp` and
that `timestamp_with_local_time_zone` is uniformly mapped to `datetime(N)`, but
the same note also says it can be mapped to Doris `timestamptz` since 4.0.3.
Please clarify the actual behavior (e.g., conditional on
`enable.mapping.timestamp_tz`) and avoid stating both “uniformly mapped” and
“can be mapped to timestamptz” without qualification.
```suggestion
Doris currently does not support timezone-aware `Timestamp` types as
distinct Doris types. By default, when `enable.mapping.timestamp_tz` is set to
`false`, both `timestamp_without_time_zone` and
`timestamp_with_local_time_zone` are mapped to the Doris `datetime(N)` type.
Since version 4.0.3, if you set `enable.mapping.timestamp_tz` to `true`,
`timestamp_with_local_time_zone` is instead mapped to the Doris
`timestamptz(N)` type (still mapped according to precision, capped at 6).
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 returned 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
## Examples
```
##########
sidebars.ts:
##########
@@ -1132,6 +1182,7 @@ const sidebars: SidebarsConfig = {
'sql-manual/basic-element/reserved-keywords',
'sql-manual/basic-element/variables',
'sql-manual/basic-element/comments',
+ 'sql-manual/basic-element/file-path-pattern',
Review Comment:
The sidebar references `sql-manual/basic-element/file-path-pattern`, but
there is no matching doc under `docs/sql-manual/basic-element/`. Please add the
page or remove the sidebar item to avoid an unknown doc ID.
```suggestion
```
##########
docs/lakehouse/catalogs/iceberg-catalog.mdx:
##########
@@ -2196,66 +2575,121 @@ EXECUTE set_current_snapshot ("ref" = "v1.0");
1. This operation does not support WHERE conditions
2. The `snapshot_id` and `ref` parameters are mutually exclusive; only one can
be specified
-3. If the specified snapshot ID or reference does not exist, the operation
will fail
+3. The operation will fail if the specified snapshot ID or reference does not
exist
4. If the current snapshot is already the target snapshot, the operation
returns directly without creating a new snapshot
+### publish_changes
+
+The `publish_changes` operation is used in the WAP (Write-Audit-Publish) mode
to publish a snapshot with the specified `wap.id` as the current table state.
+It locates the snapshot whose `wap.id` matches the given `wap_id` and
cherry-picks it onto the current table, making the staged data visible to all
read operations.
+
+**Syntax:**
+
+```sql
+ALTER TABLE [catalog.][database.]table_name
+EXECUTE publish_changes("wap_id" = "<wap_id>")
+```
+
+**Parameters:**
+
+**Parameters:**
+
+| Parameter Name | Type | Required | Description |
+| -------------- | ---- | -------- | ----------- |
+| `wap_id` | STRING | Yes | The WAP snapshot ID to be published |
+
+**Return Value:**
+
Review Comment:
`publish_changes` is documented twice: once earlier in the “Iceberg Table
Actions” list and again here. The two sections also disagree on types/return
value formatting (BIGINT vs STRING) and repeat headings (“Parameters” twice).
Please remove the duplicate and keep a single canonical section to avoid
conflicting guidance.
##########
sidebars.ts:
##########
@@ -1769,6 +1827,7 @@ const sidebars: SidebarsConfig = {
items: [
'sql-manual/sql-functions/scalar-functions/other-functions/convert-to',
'sql-manual/sql-functions/scalar-functions/other-functions/esquery',
+
'sql-manual/sql-functions/scalar-functions/other-functions/default',
Review Comment:
The sidebar adds
`sql-manual/sql-functions/scalar-functions/other-functions/default`, but there
is no `default.md` under
`docs/sql-manual/sql-functions/scalar-functions/other-functions/`. Add the doc
or remove/update this sidebar item.
```suggestion
```
##########
sidebars.ts:
##########
@@ -2001,6 +2060,7 @@ const sidebars: SidebarsConfig = {
'sql-manual/sql-functions/table-valued-functions/local',
'sql-manual/sql-functions/table-valued-functions/mv_infos',
'sql-manual/sql-functions/table-valued-functions/numbers',
+
'sql-manual/sql-functions/table-valued-functions/parquet-meta',
Review Comment:
The sidebar adds the TVF doc
`sql-manual/sql-functions/table-valued-functions/parquet-meta`, but there is no
`parquet-meta.md` under
`docs/sql-manual/sql-functions/table-valued-functions/`. Please add the missing
doc or remove/update the entry.
```suggestion
```
##########
docs/lakehouse/catalogs/iceberg-catalog.mdx:
##########
@@ -1791,11 +1961,68 @@ Supported schema change operations include:
* **Reorder Columns**
- Use `ORDER BY` to reorder columns by specifying the new column order.
+ Use `ORDER BY` to reorder columns by specifying the new column order.
- ```sql
- ALTER TABLE iceberg_table ORDER BY (col_name1, col_name2, ...);
- ```
+ ```sql
+ ALTER TABLE iceberg_table ORDER BY (col_name1, col_name2, ...);
+ ```
+
+### Partition Evolution
+
+Starting from version 4.0.2, Doris supports Partition Evolution for Iceberg
tables through `ALTER` statements.
+
+Supported partition transforms include:
+
+| Transform | Syntax | Example |
+|-----------|--------|---------|
+| bucket | `bucket(N, column)` | `bucket(16, id)` |
+| truncate | `truncate(N, column)` | `truncate(10, name)` |
+| year | `year(column)` | `year(ts)` |
+| month | `month(column)` | `month(ts)` |
+| day | `day(column)` | `day(ts)` |
+| hour | `hour(column)` | `hour(ts)` |
+| identity | `column` | `category` |
+
+Supported operations include:
+
+- **Add partition key**
+
+ ```sql
+ -- use optional AS keyword to specify a custom name for the partition field
+ ALTER TABLE table_name ADD PARTITION KEY partition_transform [AS key_name];
+
+ -- example
+ ALTER TABLE prod.db.sample ADD PARTITION KEY bucket(16, id);
+ ALTER TABLE prod.db.sample ADD PARTITION KEY truncate(4, data);
+ ALTER TABLE prod.db.sample ADD PARTITION KEY year(ts);
+ -- use optional AS keyword to specify a custom name for the partition
field
+ ALTER TABLE prod.db.sample ADD PARTITION KEY bucket(16, id) AS shard;
+ ```
+
+- **Drop partition key**
+
+ ```sql
+ ALTER TABLE table_name DROP PARTITION KEY partition_transform｜key_name;
Review Comment:
In the Partition Evolution example, `ALTER TABLE table_name DROP PARTITION
KEY partition_transform｜key_name;` uses a full-width vertical bar character
(`｜`). This can be hard to copy/paste and is not valid SQL syntax. Please
replace it with a normal ASCII `|` (or rewrite the example to avoid using `|`
for alternatives).
```suggestion
ALTER TABLE table_name DROP PARTITION KEY
partition_transform_or_key_name;
```
##########
sidebars.ts:
##########
@@ -537,6 +578,9 @@ const sidebars: SidebarsConfig = {
'ecosystem/observability/beats',
'ecosystem/observability/opentelemetry',
'ecosystem/observability/fluentbit',
+ 'ecosystem/observability/loongcollector',
+ 'ecosystem/observability/langfuse',
+ 'ecosystem/observability/vector',
Review Comment:
The sidebar adds observability pages
`ecosystem/observability/loongcollector`, `langfuse`, and `vector`, but these
docs do not exist under `docs/ecosystem/observability/`. Please add the pages
or remove the entries to avoid unknown doc IDs.
```suggestion
```
##########
sidebars.ts:
##########
@@ -186,6 +188,7 @@ const sidebars: SidebarsConfig = {
'data-operate/import/import-way/insert-into-manual',
'data-operate/import/import-way/insert-into-values-manual',
'data-operate/import/import-way/mysql-load-manual',
+
"data-operate/import/import-way/log-storage-analysis"
Review Comment:
The new sidebar item `data-operate/import/import-way/log-storage-analysis`
does not exist under `docs/data-operate/import/import-way/` (only
stream/broker/routine/insert/mysql are present). This will break the sidebar
build unless the doc is added or the ID is corrected/removed.
```suggestion
'data-operate/import/import-way/mysql-load-manual'
```
##########
sidebars.ts:
##########
@@ -235,10 +248,12 @@ const sidebars: SidebarsConfig = {
label: 'Updating Data',
items: [
'data-operate/update/update-overview',
- 'data-operate/update/unique-update',
+ 'data-operate/update/unique-update-sql',
'data-operate/update/update-of-unique-model',
'data-operate/update/update-of-aggregate-model',
+ 'data-operate/update/partial-column-update',
'data-operate/update/unique-update-concurrent-control',
+
'data-operate/update/multi-stream-update-for-unique-model',
Review Comment:
The sidebar now points to `data-operate/update/unique-update-sql`,
`partial-column-update`, and `multi-stream-update-for-unique-model`, but none
of these docs exist under `docs/data-operate/update/`. Also, the existing
`unique-update.md` page is no longer referenced. Please add the new docs or
keep the sidebar pointing to the existing page(s).
```suggestion
'data-operate/update/unique-update',
'data-operate/update/update-of-unique-model',
'data-operate/update/update-of-aggregate-model',
'data-operate/update/unique-update-concurrent-control',
```
##########
sidebars.ts:
##########
@@ -467,6 +528,7 @@ const sidebars: SidebarsConfig = {
items: [
'lakehouse/storages/hdfs',
'lakehouse/storages/s3',
+ 'lakehouse/storages/ozone',
'lakehouse/storages/azure-blob',
'lakehouse/storages/gcs',
Review Comment:
PR description focuses on adding Apache Ozone storage docs and catalog
examples, but `sidebars.ts` includes many additional unrelated sidebar
restructuring and new doc IDs across other areas (AI, SQL manual,
import/update, observability, auth, release notes, etc.). Please confirm
whether these broader sidebar changes are intended for this PR; otherwise
consider splitting them out to keep the change scoped and reviewable.
##########
sidebars.ts:
##########
@@ -427,13 +450,50 @@ const sidebars: SidebarsConfig = {
label: 'Data Catalogs',
items: [
'lakehouse/catalogs/hive-catalog',
- 'lakehouse/catalogs/iceberg-catalog',
- 'lakehouse/catalogs/hudi-catalog',
- 'lakehouse/catalogs/paimon-catalog',
- 'lakehouse/catalogs/maxcompute-catalog',
+ {
+ type: 'category',
+ label: 'Iceberg Catalog',
+ link: {type: 'doc', id:
'lakehouse/catalogs/iceberg-catalog'},
+ items: [
+
'lakehouse/best-practices/doris-iceberg',
+
'lakehouse/best-practices/doris-aws-s3tables',
+
'lakehouse/best-practices/doris-polaris',
+
'lakehouse/best-practices/doris-gravitino',
+
'lakehouse/best-practices/doris-onelake',
+
'lakehouse/best-practices/doris-unity-catalog',
+
'lakehouse/best-practices/doris-lakekeeper',
+ 'lakehouse/best-practices/doris-nessie'
+ ],
+ },
+ {
+ type: 'category',
+ label: 'Paimon Catalog',
+ link: {type: 'doc', id:
'lakehouse/catalogs/paimon-catalog'},
+ items: [
+
'lakehouse/best-practices/doris-paimon',
+
'lakehouse/best-practices/doris-dlf-paimon'
+ ],
+ },
+ {
+ type: 'category',
+ label: 'Hudi Catalog',
+ link: {type: 'doc', id:
'lakehouse/catalogs/hudi-catalog'},
+ items: [
+ 'lakehouse/best-practices/doris-hudi'
+ ],
+ },
+ {
+ type: 'category',
+ label: 'MaxCompute Catalog',
+ link: {type: 'doc', id:
'lakehouse/catalogs/maxcompute-catalog'},
+ items: [
+
'lakehouse/best-practices/doris-maxcompute'
+ ],
+ },
'lakehouse/catalogs/delta-lake-catalog',
'lakehouse/catalogs/bigquery-catalog',
'lakehouse/catalogs/kudu-catalog',
+ 'lakehouse/catalogs/kafka-catalog',
Review Comment:
The sidebar references `lakehouse/catalogs/kafka-catalog`, but there is no
corresponding doc under `docs/lakehouse/catalogs/`. Please add the missing doc
or remove/update the entry to prevent an unknown doc ID.
```suggestion
```
##########
sidebars.ts:
##########
@@ -280,7 +295,11 @@ const sidebars: SidebarsConfig = {
{
type: 'category',
label: 'User Defined Functions',
- items: ['query-data/udf/alias-function',
'query-data/udf/java-user-defined-function'],
+ items: [
+ 'query-data/udf/alias-function',
+ 'query-data/udf/java-user-defined-function',
+ 'query-data/udf/python-user-defined-function',
Review Comment:
The sidebar adds `query-data/udf/python-user-defined-function`, but there is
no corresponding doc under `docs/query-data/udf/`. Please add the page or
remove the entry to avoid an unknown doc ID.
```suggestion
```
##########
sidebars.ts:
##########
@@ -113,10 +113,12 @@ const sidebars: SidebarsConfig = {
'table-design/data-partitioning/auto-partitioning',
'table-design/data-partitioning/data-bucketing',
'table-design/data-partitioning/common-issues',
+
'table-design/data-partitioning/basic-concepts',
],
},
'table-design/data-type',
'table-design/column-compression',
+ 'table-design/storage-format',
Review Comment:
The sidebar references `table-design/storage-format`, but there is no
corresponding doc under `docs/table-design/` (no `storage-format.md|mdx`).
Docusaurus will error on unknown doc IDs. Please add the missing doc or update
the sidebar entry to an existing doc ID.
```suggestion
```
##########
i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/iceberg-catalog.mdx:
##########
@@ -58,58 +59,77 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
* `<warehouse>`
- Iceberg 的仓库路径。当 `<iceberg_catalog_type>` 为 `hadoop` 时，需指定这个参数。
+ Iceberg 的仓库路径。当 `<iceberg_catalog_type>` 为 `hadoop` 时，需指定这个参数。
- `warehouse` 的路径必须指向 `Database`
路径的上一级。如您的表路径是：`s3://bucket/path/to/db1/table1`，那么 `warehouse`
应该是：`s3://bucket/path/to/`
+ `warehouse` 的路径必须指向 `Database` 路径的上一级。如您的表路径是
`s3://bucket/path/to/db1/table1`，那么 `warehouse` 应该是 `s3://bucket/path/to/`。
* `{MetaStoreProperties}`
- MetaStoreProperties 部分用于填写 Metastore 元数据服务连接和认证信息。具体可参阅【支持的元数据服务】部分。
+ MetaStoreProperties 部分用于填写 Metastore 元数据服务连接和认证信息。具体可参阅【支持的元数据服务】部分。
* `{StorageProperties}`
- StorageProperties 部分用于填写存储系统相关的连接和认证信息。具体可参阅【支持的存储系统】部分。
+ StorageProperties 部分用于填写存储系统相关的连接和认证信息。具体可参阅【支持的存储系统】部分。
* `{IcebergProperties}`
- IcebergProperties 部分用于填写一些 Iceberg Catalog 特有的参数。
+ IcebergProperties 部分用于填写一些 Iceberg Catalog 特有的参数。
- - `list-all-tables`
+ - `list-all-tables`
- 自 3.1.2 版本支持。
+ 自 3.1.2 版本支持。
- 针对以 Hive Metastore 作为元数据服务的 Iceberg Catalog。默认为 `true`。在默认情况下，`SHOW
TABLES` 操作会罗列出当前 Database 下的所有类型的 Table（Hive Metastore 中可能存储了非 Iceberg 类型的表）。
-
- 这种方式性能最好。如果设置为 `false`，则 Doris 会逐一检查每个 Table 的类型，并只返回 Iceberg 类型的
Table。该模式在表很多的情况下，性能会比较差。
+ 针对以 Hive Metastore 作为元数据服务的 Iceberg Catalog。默认为 `true`。在默认情况下，`SHOW
TABLES` 操作会罗列出当前 Database 下的所有类型的 Table（Hive Metastore 中可能存储了非 Iceberg 类型的表）。
+
+ 这种方式性能最好。如果设置为 `false`，则 Doris 会逐一检查每个 Table 的类型，并只返回 Iceberg 类型的
Table。该模式在表很多的情况下，性能会比较差。
* `{CommonProperties}`
- CommonProperties 部分用于填写通用属性。请参阅[ 数据目录概述 ](../catalog-overview.md)中【通用属性】部分。
+ CommonProperties 部分用于填写通用属性。请参阅[数据目录概述](../catalog-overview.md)中【通用属性】部分。
### 支持的 Iceberg 版本
-当前使用的 Iceberg 依赖为 1.6.1 版本，可以兼容更高版本的 Iceberg。
+| Doris 版本 | Iceberg SDK 版本 |
+| --- | --- |
+| 2.1 | 1.6.1 |
+| 3.0 | 1.6.1 |
+| 3.1 | 1.9.1 |
+| 4.0 | 1.9.1 |
### 支持的 Iceberg 格式
* 支持 Iceberg V1/V2 格式。
* 支持 Position Delete 和 Equality Delete。
+* 支持读取 Deletion Vector（自 4.1.0 版本支持）。
+
### 支持的元数据服务
* [Hive Metastore](../metastores/hive-metastore.md)
* [AWS Glue](../metastores/aws-glue.md)
-* [Aliyun DLF ](../metastores/aliyun-dlf.md)
+* [Aliyun DLF](../metastores/aliyun-dlf.md)
* [Iceberg Rest Catalog](../metastores/iceberg-rest.md)
+* [Iceberg JDBC Catalog](../metastores/iceberg-jdbc.md) (自 4.1.0 版本支持)
Review Comment:
这里新增了指向 `../metastores/iceberg-jdbc.md` 的链接，但
`i18n/zh-CN/.../lakehouse/metastores/` 目录下并没有对应页面。建议补充 Iceberg JDBC Metastore
文档（中英文），或移除/调整该链接以避免死链。
```suggestion
* Iceberg JDBC Catalog（自 4.1.0 版本支持）
```
##########
i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/hive-catalog.mdx:
##########
@@ -1,7 +1,8 @@
---
{
"title": "Hive Catalog",
- "language": "zh-CN"
+ "language": "zh-CN",
+ "description": "通过连接 Hive Metastore，或者兼容 Hive Metatore 的元数据服务，Doris 可以自动获取
Hive 的库表信息，并进行数据查询。"
}
Review Comment:
Front matter 的 description 里写的是 “Hive Metatore”，应为 “Hive
Metastore”。建议修正该拼写以避免文档出现明显错别字。
##########
sidebars.ts:
##########
@@ -1106,6 +1155,7 @@ const sidebars: SidebarsConfig = {
'sql-manual/basic-element/sql-data-types/conversion/boolean-conversion',
'sql-manual/basic-element/sql-data-types/conversion/date-conversion',
'sql-manual/basic-element/sql-data-types/conversion/datetime-conversion',
+
'sql-manual/basic-element/sql-data-types/conversion/timestamptz-conversion',
Review Comment:
The sidebar adds
`sql-manual/basic-element/sql-data-types/conversion/timestamptz-conversion`,
but that file does not exist under
`docs/sql-manual/basic-element/sql-data-types/conversion/`. Please add the doc
or remove/update the sidebar entry.
```suggestion
```
##########
sidebars.ts:
##########
@@ -2433,6 +2494,8 @@ const sidebars: SidebarsConfig = {
label: 'Job',
items: [
'sql-manual/sql-statements/job/CREATE-JOB',
+
'sql-manual/sql-statements/job/CREATE-STREAMING-JOB',
+ 'sql-manual/sql-statements/job/ALTER-JOB',
Review Comment:
The sidebar adds `sql-manual/sql-statements/job/CREATE-STREAMING-JOB` and
`sql-manual/sql-statements/job/ALTER-JOB`, but neither doc exists under
`docs/sql-manual/sql-statements/job/` (only
CREATE/PAUSE/RESUME/DROP/CANCEL-TASK are present). Please add these docs or
remove the sidebar entries.
```suggestion
```
##########
sidebars.ts:
##########
@@ -585,7 +629,7 @@ const sidebars: SidebarsConfig = {
label: 'Authentication',
items: [
'admin-manual/auth/authentication/internal',
-
'admin-manual/auth/authentication/federation',
+
'admin-manual/auth/authentication/ldap',
Review Comment:
This sidebar change replaces `admin-manual/auth/authentication/federation`
with `admin-manual/auth/authentication/ldap`, but there is no `ldap.md|mdx`
under `docs/admin-manual/auth/authentication/` (while `federation.md` exists).
Unless the LDAP page is added in this PR, this will create an unknown doc ID in
the sidebar.
```suggestion
'admin-manual/auth/authentication/federation',
```
##########
sidebars.ts:
##########
@@ -1441,11 +1494,13 @@ const sidebars: SidebarsConfig = {
'sql-manual/sql-functions/scalar-functions/date-time-functions/timestampdiff',
'sql-manual/sql-functions/scalar-functions/date-time-functions/time',
'sql-manual/sql-functions/scalar-functions/date-time-functions/timediff',
+
"sql-manual/sql-functions/scalar-functions/date-time-functions/time-format",
'sql-manual/sql-functions/scalar-functions/date-time-functions/time-to-sec',
'sql-manual/sql-functions/scalar-functions/date-time-functions/to-date',
'sql-manual/sql-functions/scalar-functions/date-time-functions/to-days',
'sql-manual/sql-functions/scalar-functions/date-time-functions/to-iso8601',
'sql-manual/sql-functions/scalar-functions/date-time-functions/to-monday',
+
"sql-manual/sql-functions/scalar-functions/date-time-functions/to-seconds",
Review Comment:
Several newly-added date/time function docs referenced here don't exist
under `docs/sql-manual/sql-functions/scalar-functions/date-time-functions/`
(e.g. `previous-day`, `time-format`, `to-seconds`). Please add the missing
pages or remove the sidebar entries to avoid unknown doc IDs.
```suggestion
'sql-manual/sql-functions/scalar-functions/date-time-functions/time-to-sec',
'sql-manual/sql-functions/scalar-functions/date-time-functions/to-date',
'sql-manual/sql-functions/scalar-functions/date-time-functions/to-days',
'sql-manual/sql-functions/scalar-functions/date-time-functions/to-iso8601',
'sql-manual/sql-functions/scalar-functions/date-time-functions/to-monday',
```
##########
docs/lakehouse/catalogs/iceberg-catalog.mdx:
##########
@@ -74,41 +75,59 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
The IcebergProperties section is used to fill in parameters specific to
Iceberg Catalog.
- - `list-all-tables`
+ - `list-all-tables`
- For Iceberg Catalog that uses Hive Metastore as the metadata service.
Default is `true`. By default, the `SHOW TABLES` operation will list all types
of tables in the current Database (Hive Metastore may store non-Iceberg type
tables). This approach has the best performance.
-
- If set to `false`, Doris will check the type of each table one by one and
only return Iceberg type tables. This mode will have poor performance when
there are many tables.
+ For Iceberg Catalog that uses Hive Metastore as the metadata service.
Default is `true`. By default, the `SHOW TABLES` operation will list all types
of tables in the current Database (Hive Metastore may store non-Iceberg type
tables). This approach has the best performance.
+
+ If set to `false`, Doris will check the type of each table one by one
and only return Iceberg type tables. This mode will have poor performance when
there are many tables.
* `{CommonProperties}`
The CommonProperties section is for entering general properties. See the
[Catalog Overview](../catalog-overview.md) for details on common properties.
### Supported Iceberg Versions
-The current Iceberg dependency is version 1.6.1, which is compatible with
higher versions of Iceberg.
+| Doris Version | Iceberg SDK Version |
+| --- | --- |
+| 2.1 | 1.6.1 |
+| 3.0 | 1.6.1 |
+| 3.1 | 1.9.1 |
+| 4.0 | 1.9.1 |
### Supported Iceberg Formats
* Supports Iceberg V1/V2 formats.
-* Supports Position Delete and Equality Delete.
+* Supports reading Position Delete and Equality Delete.
+* Supports reading Deletion Vector (Since 4.1.0).
### Supported Metadata Services
* [Hive Metastore](../metastores/hive-metastore.md)
* [AWS Glue](../metastores/aws-glue.md)
* [Aliyun DLF](../metastores/aliyun-dlf.md)
* [Iceberg Rest Catalog](../metastores/iceberg-rest.md)
+* [Iceberg JDBC Catalog](../metastores/iceberg-jdbc.md) (Supported since
version 4.1.0)
Review Comment:
This doc now links to `../metastores/iceberg-jdbc.md`, but that page does
not exist under `docs/lakehouse/metastores/`. Please add the missing metastore
doc (and its zh-CN counterpart) or remove/update the link to avoid a dead link
in the docs.
```suggestion
* Iceberg JDBC Catalog (Supported since version 4.1.0)
```
##########
docs/lakehouse/catalogs/hive-catalog.mdx:
##########
@@ -667,6 +695,15 @@ You can query Hive Views, but there are some limitations:
* Some functions supported by HiveQL may have the same name as those in Doris
but behave differently. This could lead to discrepancies between the results
obtained from Hive and Doris. If you encounter such issues, please report them
to the community.
+### Related Parameters
+
+* Session variables
+
+| Parameter name | Default value | Desciption | Since version |
Review Comment:
The table header in the new “Related Parameters” section misspells
“Description” as “Desciption”. Please fix the typo for clarity/searchability.
```suggestion
| Parameter name | Default value | Description | Since version |
```
##########
sidebars.ts:
##########
@@ -323,6 +342,7 @@ const sidebars: SidebarsConfig = {
'query-acceleration/condition-cache',
'query-acceleration/high-concurrent-point-query',
'query-acceleration/dictionary',
+ 'query-acceleration/query-profile',
Review Comment:
The sidebar references `query-acceleration/query-profile`, but there is no
`query-profile.md|mdx` under `docs/query-acceleration/`. Please add the missing
doc or remove/update the sidebar item to prevent build errors.
```suggestion
```
##########
sidebars.ts:
##########
@@ -196,6 +199,7 @@ const sidebars: SidebarsConfig = {
'data-operate/import/file-format/json',
'data-operate/import/file-format/parquet',
'data-operate/import/file-format/orc',
+ 'data-operate/import/file-format/native',
Review Comment:
The sidebar references `data-operate/import/file-format/native`, but there
is no `native.md|mdx` under `docs/data-operate/import/file-format/`. Please add
the missing page or remove/update the sidebar entry to avoid an unknown doc ID.
```suggestion
```
##########
sidebars.ts:
##########
@@ -1482,10 +1537,13 @@ const sidebars: SidebarsConfig = {
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-circle',
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-contains',
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-disjoint',
+
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-distance',
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-distance-sphere',
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-geometryfromtext',
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-geometryfromwkb',
+
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-geometrytype',
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-intersects',
+
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-length',
Review Comment:
The sidebar adds spatial function docs `st-distance`, `st-geometrytype`, and
`st-length`, but these pages are not present under
`docs/sql-manual/sql-functions/scalar-functions/spatial-functions/`. Please add
them or remove/update the sidebar entries.
```suggestion
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-distance-sphere',
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-geometryfromtext',
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-geometryfromwkb',
'sql-manual/sql-functions/scalar-functions/spatial-functions/st-intersects',
```
##########
i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/iceberg-catalog.mdx:
##########
@@ -918,9 +940,81 @@ Iceberg 的元数层级关系是 Catalog -> Namespace -> Table。其中 Namespac
</details>
+### Iceberg JDBC Catalog
+:::tip 提示
+该功能为试验功能，自 4.1.0 版本支持。
+:::
+
+<details>
+ <summary>4.1+ 版本</summary>
+ <Tabs>
+ <TabItem value='PostgreSQL' label='PostgreSQL' default>
+ 使用 PostgreSQL 作为元数据存储，配合 S3 存储
+ ```sql
+ CREATE CATALOG iceberg_jdbc_postgresql PROPERTIES (
+ 'type' = 'iceberg',
+ 'iceberg.catalog.type' = 'jdbc',
+ 'iceberg.jdbc.uri' =
'jdbc:postgresql://127.0.0.1:5432/iceberg_db',
+ 'iceberg.jdbc.user' = 'iceberg_user',
+ 'iceberg.jdbc.password' = 'password',
+ 'iceberg.jdbc.init-catalog-tables' = 'true',
+ 'iceberg.jdbc.schema-version' = 'V1',
+ 'iceberg.jdbc.driver_class' = 'org.postgresql.Driver',
+ 'iceberg.jdbc.driver_url' = '<jdbc_driver_jar>'
+ 'warehouse' = 's3://bucket/warehouse',
+ 's3.access_key' = '<ak>',
Review Comment:
Iceberg JDBC Catalog 示例里 `iceberg.jdbc.driver_url` 这一行后面缺少逗号，导致后面的
`'warehouse' = ...` 被拼接到同一条属性上，SQL 示例无法直接复制执行。请在 `driver_url`
行末补上逗号（PostgreSQL/MySQL/SQLite 三处都一样）。
##########
sidebars.ts:
##########
@@ -959,6 +1003,7 @@ const sidebars: SidebarsConfig = {
items: [
'ecosystem/bi/apache-superset',
'ecosystem/bi/finebi',
+ 'ecosystem/bi/metabase',
Review Comment:
The sidebar adds `ecosystem/bi/metabase`, but there is no corresponding doc
under `docs/ecosystem/bi/`. Please add the page or remove/update the entry to
avoid an unknown doc ID.
```suggestion
```
##########
docs/lakehouse/storages/ozone.md:
##########
@@ -0,0 +1,68 @@
+---
+{
+ "title": "Apache Ozone | Storages",
+ "language": "en",
+ "description": "Starting from version 4.0.4, Doris supports accessing
Apache Ozone through the S3 Gateway.",
+ "sidebar_label": "Apache Ozone"
+}
Review Comment:
Front matter `title` is set to `"Apache Ozone | Storages"`, but other
storage docs use just the storage name as the title (e.g.
`docs/lakehouse/storages/s3.md`, `azure-blob.md`). Consider aligning this to
`"Apache Ozone"` (and rely on sidebar/category for context) to keep titles
consistent across storage pages.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
