You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@doris.apache.org by mo...@apache.org on 2025/12/29 11:29:25 UTC
(doris-website) branch master updated: [fix](seo): duplicate titles (#3229)
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 d86233a4f20 [fix](seo): duplicate titles (#3229)
d86233a4f20 is described below
commit d86233a4f2029f43a3deef9e3f6956504b01a2bd
Author: yangon <26...@qq.com>
AuthorDate: Mon Dec 29 19:29:19 2025 +0800
[fix](seo): duplicate titles (#3229)
---
docs/admin-manual/config/fe-config-template.md | 6 +-
docs/admin-manual/config/fe-config.md | 6 +-
docs/admin-manual/data-admin/ccr/overview.md | 8 +-
docs/admin-manual/data-admin/ccr/quickstart.md | 6 +-
docs/admin-manual/maint-monitor/disk-capacity.md | 6 +-
.../open-api/be-http/compaction-run.md | 6 +-
.../open-api/fe-http/meta-info-action-V2.md | 6 +-
.../open-api/fe-http/meta-info-action.md | 6 +-
.../fe-http/query-profile-action-controller.md | 7 +-
.../open-api/fe-http/query-profile-action.md | 9 +-
docs/admin-manual/open-api/overview.md | 8 +-
.../information_schema/column_privileges.md | 2 +-
.../information_schema/column_statistics.md | 9 +-
.../internal_schema/column_statistics.md | 9 +-
docs/admin-manual/system-tables/overview.md | 8 +-
.../trouble-shooting/memory-management/overview.md | 8 +-
.../workload-management/job-scheduler.md | 8 +-
.../workload-management-summary.md | 8 +-
docs/ai/vector-search/overview.md | 8 +-
docs/compute-storage-decoupled/overview.md | 8 +-
docs/data-operate/export/export-best-practice.md | 8 +-
docs/data-operate/export/export-manual.md | 8 +-
docs/data-operate/import/complex-types/array.md | 8 +-
docs/data-operate/import/complex-types/json.md | 8 +-
docs/data-operate/import/complex-types/map.md | 8 +-
docs/data-operate/import/complex-types/struct.md | 8 +-
.../import/data-source/google-cloud-storage.md | 8 +-
docs/data-operate/import/data-source/hdfs.md | 8 +-
docs/data-operate/import/data-source/minio.md | 8 +-
docs/data-operate/import/file-format/json.md | 6 +-
docs/data-operate/import/file-format/orc.md | 8 +-
docs/data-operate/import/file-format/parquet.md | 9 +-
docs/data-operate/scheduler/job-scheduler.md | 8 +-
docs/ecosystem/bi/tableau-back.md | 8 +-
docs/ecosystem/bi/tableau.md | 8 +-
docs/gettingStarted/quick-start.mdx | 8 +-
.../install-doris-cluster.md | 8 +-
.../install-doris-cluster.md | 8 +-
docs/lakehouse/file-formats/orc.md | 8 +-
docs/lakehouse/file-formats/parquet.md | 8 +-
docs/lakehouse/statistics.md | 8 +-
docs/lakehouse/storages/gcs.md | 8 +-
docs/lakehouse/storages/hdfs.md | 9 +-
docs/lakehouse/storages/minio.md | 8 +-
docs/lakehouse/storages/s3.md | 9 +-
docs/observability/overview.mdx | 8 +-
.../async-materialized-view/use-guide.md | 9 +-
.../statistics.md | 8 +-
.../sql-data-types/data-type-overview.md | 8 +-
.../basic-element/sql-data-types/date-time/DATE.md | 8 +-
.../basic-element/sql-data-types/date-time/TIME.md | 8 +-
.../sql-data-types/semi-structured/ARRAY.md | 6 +-
.../sql-data-types/semi-structured/JSON.md | 8 +-
.../sql-data-types/semi-structured/MAP.md | 8 +-
.../sql-data-types/semi-structured/STRUCT.md | 9 +-
.../semi-structured/semi-structured-overview.md | 7 +-
.../sql-data-types/string-type/CHAR.md | 8 +-
.../sql-functions/ai-functions/overview.md | 8 +-
.../scalar-functions/array-functions/array.md | 8 +-
.../scalar-functions/bitwise-functions/xor.md | 8 +-
.../scalar-functions/date-time-functions/date.md | 9 +-
.../scalar-functions/date-time-functions/time.md | 8 +-
.../date-time-functions/timestamp.md | 8 +-
.../date-time-functions/to-iso8601.md | 8 +-
.../scalar-functions/ip-functions/inet-ntoa.md | 8 +-
.../scalar-functions/ip-functions/inet6-aton.md | 8 +-
.../scalar-functions/ip-functions/inet6-ntoa.md | 8 +-
.../ip-functions/ipv4-num-to-string.md | 8 +-
.../ip-functions/ipv6-num-to-string.md | 9 +-
.../ip-functions/ipv6-string-to-num-or-null.md | 8 +-
.../scalar-functions/map-functions/map.md | 9 +-
.../scalar-functions/numeric-functions/xor.md | 8 +-
.../scalar-functions/string-functions/char.md | 8 +-
.../scalar-functions/string-functions/date.md | 9 +-
.../scalar-functions/string-functions/timestamp.md | 7 +-
.../string-functions/to-iso8601.md | 7 +-
.../scalar-functions/struct-functions/struct.md | 8 +-
.../sql-functions/table-valued-functions/hdfs.md | 9 +-
.../sql-functions/table-valued-functions/local.md | 9 +-
.../sql-functions/table-valued-functions/s3.md | 10 +-
.../compute-management/CREATE-WORKLOAD-GROUP.md | 9 +-
.../compute-management/CREATE-WORKLOAD-POLICY.md | 8 +-
.../data-modification/load-and-export/EXPORT.md | 9 +-
docs/table-design/best-practice.md | 6 +-
docs/table-design/index/inverted-index.md | 8 +-
docs/table-design/index/inverted-index/overview.md | 5 +-
docs/table-design/overview.md | 8 +-
.../admin-manual/config/fe-config-template.md | 6 +-
.../current/admin-manual/config/fe-config.md | 6 +-
.../open-api/fe-http/meta-info-action-V2.md | 8 +-
.../open-api/fe-http/meta-info-action.md | 8 +-
.../fe-http/query-profile-action-controller.md | 9 +-
.../open-api/fe-http/query-profile-action.md | 8 +-
.../information_schema/column_statistics.md | 9 +-
.../internal_schema/column_statistics.md | 9 +-
.../current/admin-manual/system-tables/overview.md | 8 +-
.../trouble-shooting/memory-management/overview.md | 8 +-
.../data-operate/export/export-best-practice.md | 8 +-
.../data-operate/import/complex-types/array.md | 8 +-
.../data-operate/import/complex-types/json.md | 8 +-
.../data-operate/import/complex-types/map.md | 8 +-
.../data-operate/import/complex-types/struct.md | 8 +-
.../import/data-source/google-cloud-storage.md | 8 +-
.../data-operate/import/data-source/hdfs.md | 8 +-
.../data-operate/import/data-source/minio.md | 8 +-
.../data-operate/import/file-format/json.md | 6 +-
.../current/data-operate/import/file-format/orc.md | 8 +-
.../data-operate/import/file-format/parquet.md | 9 +-
.../current/ecosystem/bi/tableau-back.md | 8 +-
.../current/ecosystem/bi/tableau.md | 8 +-
.../current/lakehouse/file-formats/orc.md | 8 +-
.../current/lakehouse/file-formats/parquet.md | 8 +-
.../current/lakehouse/statistics.md | 8 +-
.../current/lakehouse/storages/gcs.md | 8 +-
.../current/lakehouse/storages/hdfs.md | 8 +-
.../current/lakehouse/storages/minio.md | 8 +-
.../current/lakehouse/storages/s3.md | 8 +-
.../current/log-storage-analysis.md | 8 +-
.../current/observability/log-storage-analysis.md | 8 +-
.../current/observability/overview.mdx | 8 +-
.../async-materialized-view/use-guide.md | 9 +-
.../statistics.md | 8 +-
.../tuning/parallelism-tuning.md | 6 +-
.../tuning/tuning-execution/parallelism-tuning.md | 8 +-
.../basic-element/sql-data-types/date-time/DATE.md | 8 +-
.../basic-element/sql-data-types/date-time/TIME.md | 8 +-
.../sql-data-types/semi-structured/ARRAY.md | 9 +-
.../sql-data-types/semi-structured/JSON.md | 8 +-
.../sql-data-types/semi-structured/MAP.md | 9 +-
.../sql-data-types/semi-structured/STRUCT.md | 9 +-
.../sql-data-types/string-type/CHAR.md | 8 +-
.../scalar-functions/array-functions/array.md | 8 +-
.../scalar-functions/date-time-functions/date.md | 9 +-
.../scalar-functions/date-time-functions/time.md | 8 +-
.../scalar-functions/ip-functions/cut-ipv6.md | 8 +-
.../scalar-functions/ip-functions/cut_ipv6.md | 8 +-
.../scalar-functions/ip-functions/inet-ntoa.md | 9 +-
.../scalar-functions/ip-functions/inet6-aton.md | 9 +-
.../scalar-functions/ip-functions/inet6-ntoa.md | 9 +-
.../ip-functions/ipv4-cidr-to-range.md | 8 +-
.../ip-functions/ipv4-num-to-string.md | 8 +-
.../ip-functions/ipv4_cidr_to_range.md | 8 +-
.../ip-functions/ipv6-cidr-to-range.md | 8 +-
.../ip-functions/ipv6-num-to-string.md | 8 +-
.../ip-functions/ipv6-string-to-num-or-null.md | 8 +-
.../ip-functions/ipv6_cidr_to_range.md | 8 +-
.../scalar-functions/map-functions/map.md | 9 +-
.../scalar-functions/string-functions/char.md | 9 +-
.../scalar-functions/struct-functions/struct.md | 8 +-
.../explode-json-array-int-outer.md | 9 +-
.../explode-json-array-json-outer.md | 9 +-
.../sql-functions/table-valued-functions/hdfs.md | 8 +-
.../sql-functions/table-valued-functions/s3.md | 8 +-
.../admin-manual/auth/security-overview.md | 8 +-
.../admin-manual/config/fe-config-template.md | 6 +-
.../version-2.1/admin-manual/config/fe-config.md | 6 +-
.../open-api/fe-http/meta-info-action-V2.md | 8 +-
.../open-api/fe-http/meta-info-action.md | 8 +-
.../fe-http/query-profile-action-controller.md | 9 +-
.../open-api/fe-http/query-profile-action.md | 8 +-
.../version-2.1/admin-manual/security-overview.md | 8 +-
.../information_schema/column_statistics.md | 9 +-
.../internal_schema/column_statistics.md | 9 +-
.../admin-manual/system-tables/overview.md | 8 +-
.../trouble-shooting/memory-management/overview.md | 8 +-
.../data-operate/export/export-best-practice.md | 8 +-
.../data-operate/import/complex-types/array.md | 8 +-
.../data-operate/import/complex-types/json.md | 8 +-
.../data-operate/import/complex-types/map.md | 8 +-
.../data-operate/import/complex-types/struct.md | 8 +-
.../import/data-source/google-cloud-storage.md | 8 +-
.../data-operate/import/data-source/hdfs.md | 8 +-
.../data-operate/import/data-source/minio.md | 8 +-
.../data-operate/import/file-format/json.md | 6 +-
.../data-operate/import/file-format/orc.md | 8 +-
.../data-operate/import/file-format/parquet.md | 9 +-
.../version-2.1/lakehouse/file-formats/orc.md | 8 +-
.../version-2.1/lakehouse/file-formats/parquet.md | 8 +-
.../version-2.1/lakehouse/statistics.md | 8 +-
.../version-2.1/lakehouse/storages/gcs.md | 8 +-
.../version-2.1/lakehouse/storages/hdfs.md | 8 +-
.../version-2.1/lakehouse/storages/minio.md | 8 +-
.../version-2.1/lakehouse/storages/s3.md | 8 +-
.../version-2.1/log-storage-analysis.md | 8 +-
.../observability/log-storage-analysis.md | 8 +-
.../version-2.1/observability/overview.mdx | 8 +-
.../async-materialized-view/use-guide.md | 9 +-
.../statistics.md | 8 +-
.../basic-element/sql-data-types/date-time/DATE.md | 8 +-
.../sql-data-types/semi-structured/ARRAY.md | 8 +-
.../sql-data-types/semi-structured/JSON.md | 8 +-
.../sql-data-types/semi-structured/MAP.md | 6 +-
.../sql-data-types/semi-structured/STRUCT.md | 8 +-
.../sql-data-types/string-type/CHAR.md | 8 +-
.../scalar-functions/array-functions/array.md | 8 +-
.../scalar-functions/date-time-functions/date.md | 9 +-
.../scalar-functions/map-functions/map.md | 8 +-
.../scalar-functions/string-functions/char.md | 9 +-
.../scalar-functions/struct-functions/struct.md | 8 +-
.../sql-functions/table-valued-functions/hdfs.md | 8 +-
.../sql-functions/table-valued-functions/s3.md | 8 +-
.../admin-manual/config/fe-config-template.md | 6 +-
.../version-3.x/admin-manual/config/fe-config.md | 6 +-
.../open-api/fe-http/meta-info-action-V2.md | 8 +-
.../open-api/fe-http/meta-info-action.md | 8 +-
.../fe-http/query-profile-action-controller.md | 9 +-
.../open-api/fe-http/query-profile-action.md | 8 +-
.../information_schema/column_statistics.md | 9 +-
.../internal_schema/column_statistics.md | 9 +-
.../admin-manual/system-tables/overview.md | 8 +-
.../trouble-shooting/memory-management/overview.md | 8 +-
.../compute-storage-decoupled/overview.md | 9 +-
.../data-operate/export/export-best-practice.md | 8 +-
.../data-operate/import/complex-types/array.md | 8 +-
.../data-operate/import/complex-types/json.md | 8 +-
.../data-operate/import/complex-types/map.md | 8 +-
.../data-operate/import/complex-types/struct.md | 8 +-
.../import/data-source/google-cloud-storage.md | 8 +-
.../data-operate/import/data-source/hdfs.md | 8 +-
.../data-operate/import/data-source/minio.md | 8 +-
.../data-operate/import/file-format/json.md | 6 +-
.../data-operate/import/file-format/orc.md | 8 +-
.../data-operate/import/file-format/parquet.md | 9 +-
.../version-3.x/lakehouse/file-formats/orc.md | 8 +-
.../version-3.x/lakehouse/file-formats/parquet.md | 8 +-
.../version-3.x/lakehouse/statistics.md | 8 +-
.../version-3.x/lakehouse/storages/gcs.md | 8 +-
.../version-3.x/lakehouse/storages/hdfs.md | 8 +-
.../version-3.x/lakehouse/storages/minio.md | 8 +-
.../version-3.x/lakehouse/storages/s3.md | 8 +-
.../version-3.x/log-storage-analysis.md | 8 +-
.../observability/log-storage-analysis.md | 8 +-
.../version-3.x/observability/overview.mdx | 8 +-
.../async-materialized-view/use-guide.md | 9 +-
.../statistics.md | 8 +-
.../basic-element/sql-data-types/date-time/DATE.md | 8 +-
.../sql-data-types/semi-structured/ARRAY.md | 8 +-
.../sql-data-types/semi-structured/JSON.md | 8 +-
.../sql-data-types/semi-structured/MAP.md | 6 +-
.../sql-data-types/semi-structured/STRUCT.md | 8 +-
.../sql-data-types/string-type/CHAR.md | 8 +-
.../scalar-functions/array-functions/array.md | 8 +-
.../scalar-functions/date-time-functions/date.md | 9 +-
.../scalar-functions/map-functions/map.md | 8 +-
.../scalar-functions/string-functions/char.md | 9 +-
.../scalar-functions/struct-functions/struct.md | 8 +-
.../sql-functions/table-valued-functions/hdfs.md | 8 +-
.../sql-functions/table-valued-functions/s3.md | 8 +-
.../version-3.x/table-design/overview.md | 9 +-
.../admin-manual/config/fe-config-template.md | 6 +-
.../version-4.x/admin-manual/config/fe-config.md | 6 +-
.../open-api/fe-http/meta-info-action-V2.md | 8 +-
.../open-api/fe-http/meta-info-action.md | 8 +-
.../fe-http/query-profile-action-controller.md | 9 +-
.../open-api/fe-http/query-profile-action.md | 8 +-
.../information_schema/column_statistics.md | 9 +-
.../internal_schema/column_statistics.md | 9 +-
.../admin-manual/system-tables/overview.md | 8 +-
.../trouble-shooting/memory-management/overview.md | 8 +-
.../data-operate/export/export-best-practice.md | 8 +-
.../data-operate/import/complex-types/array.md | 8 +-
.../data-operate/import/complex-types/json.md | 8 +-
.../data-operate/import/complex-types/map.md | 8 +-
.../data-operate/import/complex-types/struct.md | 8 +-
.../import/data-source/google-cloud-storage.md | 8 +-
.../data-operate/import/data-source/hdfs.md | 8 +-
.../data-operate/import/data-source/minio.md | 8 +-
.../data-operate/import/file-format/json.md | 6 +-
.../data-operate/import/file-format/orc.md | 8 +-
.../data-operate/import/file-format/parquet.md | 9 +-
.../version-4.x/lakehouse/file-formats/orc.md | 8 +-
.../version-4.x/lakehouse/file-formats/parquet.md | 8 +-
.../version-4.x/lakehouse/statistics.md | 8 +-
.../version-4.x/lakehouse/storages/gcs.md | 8 +-
.../version-4.x/lakehouse/storages/hdfs.md | 8 +-
.../version-4.x/lakehouse/storages/minio.md | 8 +-
.../version-4.x/lakehouse/storages/s3.md | 8 +-
.../version-4.x/log-storage-analysis.md | 8 +-
.../observability/log-storage-analysis.md | 8 +-
.../version-4.x/observability/overview.mdx | 8 +-
.../async-materialized-view/use-guide.md | 9 +-
.../statistics.md | 8 +-
.../basic-element/sql-data-types/date-time/DATE.md | 8 +-
.../basic-element/sql-data-types/date-time/TIME.md | 8 +-
.../sql-data-types/semi-structured/ARRAY.md | 9 +-
.../sql-data-types/semi-structured/JSON.md | 8 +-
.../sql-data-types/semi-structured/MAP.md | 9 +-
.../sql-data-types/semi-structured/STRUCT.md | 9 +-
.../sql-data-types/string-type/CHAR.md | 8 +-
.../scalar-functions/array-functions/array.md | 8 +-
.../scalar-functions/date-time-functions/date.md | 9 +-
.../scalar-functions/date-time-functions/time.md | 8 +-
.../scalar-functions/ip-functions/cut-ipv6.md | 8 +-
.../scalar-functions/ip-functions/cut_ipv6.md | 8 +-
.../scalar-functions/ip-functions/inet-ntoa.md | 9 +-
.../scalar-functions/ip-functions/inet6-aton.md | 9 +-
.../scalar-functions/ip-functions/inet6-ntoa.md | 9 +-
.../ip-functions/ipv4-cidr-to-range.md | 8 +-
.../ip-functions/ipv4-num-to-string.md | 8 +-
.../ip-functions/ipv4_cidr_to_range.md | 8 +-
.../ip-functions/ipv6-cidr-to-range.md | 8 +-
.../ip-functions/ipv6-num-to-string.md | 8 +-
.../ip-functions/ipv6-string-to-num-or-null.md | 8 +-
.../ip-functions/ipv6_cidr_to_range.md | 8 +-
.../scalar-functions/map-functions/map.md | 9 +-
.../scalar-functions/string-functions/char.md | 9 +-
.../scalar-functions/struct-functions/struct.md | 8 +-
.../explode-json-array-int-outer.md | 9 +-
.../explode-json-array-json-outer.md | 9 +-
.../sql-functions/table-valued-functions/hdfs.md | 8 +-
.../sql-functions/table-valued-functions/s3.md | 8 +-
package.json | 1 +
scripts/add_sidebar_label.py | 139 ++++++++++++++++
scripts/fix-duplicate-titles.js | 107 ++++++++++++
scripts/fix_title_in_content.py | 180 +++++++++++++++++++++
.../admin-manual/config/fe-config-template.md | 6 +-
.../version-2.1/admin-manual/config/fe-config.md | 6 +-
.../admin-manual/data-admin/ccr/overview.md | 8 +-
.../admin-manual/data-admin/ccr/quickstart.md | 6 +-
.../open-api/fe-http/meta-info-action-V2.md | 6 +-
.../open-api/fe-http/meta-info-action.md | 6 +-
.../fe-http/query-profile-action-controller.md | 7 +-
.../open-api/fe-http/query-profile-action.md | 8 +-
.../version-2.1/admin-manual/open-api/overview.md | 8 +-
.../information_schema/column_statistics.md | 9 +-
.../internal_schema/column_statistics.md | 9 +-
.../admin-manual/system-tables/overview.md | 8 +-
.../trouble-shooting/memory-management/overview.md | 8 +-
.../workload-management/job-scheduler.md | 8 +-
.../workload-management-summary.md | 8 +-
.../data-operate/export/export-best-practice.md | 8 +-
.../data-operate/export/export-manual.md | 8 +-
.../data-operate/import/complex-types/array.md | 8 +-
.../data-operate/import/complex-types/json.md | 8 +-
.../data-operate/import/complex-types/map.md | 8 +-
.../data-operate/import/complex-types/struct.md | 8 +-
.../import/data-source/google-cloud-storage.md | 8 +-
.../data-operate/import/data-source/hdfs.md | 8 +-
.../data-operate/import/data-source/minio.md | 8 +-
.../data-operate/import/file-format/json.md | 6 +-
.../data-operate/import/file-format/orc.md | 8 +-
.../data-operate/import/file-format/parquet.md | 9 +-
.../data-operate/scheduler/job-scheduler.md | 8 +-
.../version-2.1/gettingStarted/quick-start.mdx | 8 +-
.../version-2.1/lakehouse/file-formats/orc.md | 8 +-
.../version-2.1/lakehouse/file-formats/parquet.md | 8 +-
versioned_docs/version-2.1/lakehouse/statistics.md | 8 +-
.../version-2.1/lakehouse/storages/gcs.md | 8 +-
.../version-2.1/lakehouse/storages/hdfs.md | 9 +-
.../version-2.1/lakehouse/storages/minio.md | 8 +-
.../version-2.1/lakehouse/storages/s3.md | 9 +-
versioned_docs/version-2.1/log-storage-analysis.md | 6 +-
.../version-2.1/observability/overview.mdx | 8 +-
.../practical-guide/log-storage-analysis.md | 6 +-
.../async-materialized-view/use-guide.md | 9 +-
.../statistics.md | 8 +-
.../sql-data-types/data-type-overview.md | 8 +-
.../basic-element/sql-data-types/date-time/DATE.md | 8 +-
.../sql-data-types/semi-structured/ARRAY.md | 8 +-
.../sql-data-types/semi-structured/JSON.md | 8 +-
.../sql-data-types/semi-structured/MAP.md | 6 +-
.../sql-data-types/semi-structured/STRUCT.md | 8 +-
.../semi-structured/semi-structured-overview.md | 7 +-
.../sql-data-types/string-type/CHAR.md | 8 +-
.../scalar-functions/array-functions/array.md | 8 +-
.../scalar-functions/date-time-functions/date.md | 9 +-
.../date-time-functions/from-iso8601-date.md | 9 +-
.../date-time-functions/to-iso8601.md | 8 +-
.../date-time-functions/week-ceil.md | 8 +-
.../date-time-functions/week-floor.md | 8 +-
.../scalar-functions/map-functions/map.md | 8 +-
.../scalar-functions/string-functions/char.md | 9 +-
.../scalar-functions/string-functions/date.md | 9 +-
.../string-functions/from-iso8601-date.md | 9 +-
.../string-functions/to-iso8601.md | 7 +-
.../scalar-functions/string-functions/week-ceil.md | 8 +-
.../string-functions/week-floor.md | 8 +-
.../scalar-functions/struct-functions/struct.md | 8 +-
.../sql-functions/table-valued-functions/hdfs.md | 8 +-
.../sql-functions/table-valued-functions/s3.md | 10 +-
.../data-modification/load-and-export/EXPORT.md | 9 +-
.../version-2.1/table-design/best-practice.md | 7 +-
.../version-2.1/table-design/overview.md | 8 +-
.../admin-manual/config/fe-config-template.md | 6 +-
.../version-3.x/admin-manual/config/fe-config.md | 6 +-
.../admin-manual/data-admin/ccr/overview.md | 8 +-
.../admin-manual/data-admin/ccr/quickstart.md | 6 +-
.../open-api/fe-http/meta-info-action-V2.md | 6 +-
.../open-api/fe-http/meta-info-action.md | 6 +-
.../fe-http/query-profile-action-controller.md | 7 +-
.../open-api/fe-http/query-profile-action.md | 8 +-
.../version-3.x/admin-manual/open-api/overview.md | 8 +-
.../information_schema/column_statistics.md | 9 +-
.../internal_schema/column_statistics.md | 9 +-
.../admin-manual/system-tables/overview.md | 8 +-
.../trouble-shooting/memory-management/overview.md | 8 +-
.../workload-management/job-scheduler.md | 8 +-
.../workload-management-summary.md | 8 +-
.../compute-storage-decoupled/overview.md | 8 +-
.../data-operate/export/export-best-practice.md | 8 +-
.../data-operate/export/export-manual.md | 8 +-
.../data-operate/import/complex-types/array.md | 8 +-
.../data-operate/import/complex-types/json.md | 8 +-
.../data-operate/import/complex-types/map.md | 8 +-
.../data-operate/import/complex-types/struct.md | 8 +-
.../import/data-source/google-cloud-storage.md | 8 +-
.../data-operate/import/data-source/hdfs.md | 8 +-
.../data-operate/import/data-source/minio.md | 8 +-
.../data-operate/import/file-format/json.md | 6 +-
.../data-operate/import/file-format/orc.md | 8 +-
.../data-operate/import/file-format/parquet.md | 9 +-
.../data-operate/scheduler/job-scheduler.md | 8 +-
.../version-3.x/gettingStarted/quick-start.mdx | 8 +-
.../install-doris-cluster.md | 8 +-
.../install-doris-cluster.md | 8 +-
.../version-3.x/lakehouse/file-formats/orc.md | 8 +-
.../version-3.x/lakehouse/file-formats/parquet.md | 8 +-
versioned_docs/version-3.x/lakehouse/statistics.md | 8 +-
.../version-3.x/lakehouse/storages/gcs.md | 8 +-
.../version-3.x/lakehouse/storages/hdfs.md | 9 +-
.../version-3.x/lakehouse/storages/minio.md | 8 +-
.../version-3.x/lakehouse/storages/s3.md | 9 +-
versioned_docs/version-3.x/log-storage-analysis.md | 6 +-
.../version-3.x/observability/overview.mdx | 8 +-
.../practical-guide/log-storage-analysis.md | 6 +-
.../async-materialized-view/use-guide.md | 9 +-
.../statistics.md | 8 +-
.../tuning/tuning-execution/data-skew-handling.md | 7 +-
.../tuning/tuning-execution/parallelism-tuning.md | 6 +-
.../sql-data-types/data-type-overview.md | 8 +-
.../basic-element/sql-data-types/date-time/DATE.md | 8 +-
.../sql-data-types/semi-structured/ARRAY.md | 8 +-
.../sql-data-types/semi-structured/JSON.md | 8 +-
.../sql-data-types/semi-structured/MAP.md | 6 +-
.../sql-data-types/semi-structured/STRUCT.md | 8 +-
.../semi-structured/semi-structured-overview.md | 7 +-
.../sql-data-types/string-type/CHAR.md | 8 +-
.../scalar-functions/array-functions/array.md | 8 +-
.../scalar-functions/bitwise-functions/xor.md | 8 +-
.../scalar-functions/date-time-functions/date.md | 9 +-
.../date-time-functions/from-iso8601-date.md | 9 +-
.../date-time-functions/to-iso8601.md | 8 +-
.../date-time-functions/week-ceil.md | 8 +-
.../date-time-functions/week-floor.md | 8 +-
.../scalar-functions/map-functions/map.md | 8 +-
.../scalar-functions/numeric-functions/xor.md | 8 +-
.../scalar-functions/string-functions/char.md | 9 +-
.../scalar-functions/string-functions/date.md | 9 +-
.../string-functions/from-iso8601-date.md | 9 +-
.../string-functions/to-iso8601.md | 7 +-
.../scalar-functions/string-functions/week-ceil.md | 8 +-
.../string-functions/week-floor.md | 8 +-
.../scalar-functions/struct-functions/struct.md | 8 +-
.../sql-functions/table-valued-functions/hdfs.md | 9 +-
.../sql-functions/table-valued-functions/local.md | 9 +-
.../sql-functions/table-valued-functions/s3.md | 10 +-
.../compute-management/CREATE-WORKLOAD-GROUP.md | 9 +-
.../compute-management/CREATE-WORKLOAD-POLICY.md | 8 +-
.../data-modification/load-and-export/EXPORT.md | 9 +-
.../version-3.x/table-design/best-practice.md | 6 +-
.../version-3.x/table-design/overview.md | 8 +-
.../admin-manual/config/fe-config-template.md | 6 +-
.../version-4.x/admin-manual/config/fe-config.md | 6 +-
.../admin-manual/data-admin/ccr/overview.md | 8 +-
.../admin-manual/data-admin/ccr/quickstart.md | 6 +-
.../admin-manual/maint-monitor/disk-capacity.md | 6 +-
.../open-api/be-http/compaction-run.md | 6 +-
.../open-api/fe-http/meta-info-action-V2.md | 6 +-
.../open-api/fe-http/meta-info-action.md | 6 +-
.../fe-http/query-profile-action-controller.md | 7 +-
.../open-api/fe-http/query-profile-action.md | 9 +-
.../version-4.x/admin-manual/open-api/overview.md | 8 +-
.../information_schema/column_statistics.md | 9 +-
.../internal_schema/column_statistics.md | 9 +-
.../admin-manual/system-tables/overview.md | 8 +-
.../trouble-shooting/memory-management/overview.md | 8 +-
.../workload-management/job-scheduler.md | 8 +-
.../workload-management-summary.md | 8 +-
.../version-4.x/ai/vector-search/overview.md | 8 +-
.../compute-storage-decoupled/overview.md | 8 +-
.../data-operate/export/export-best-practice.md | 8 +-
.../data-operate/export/export-manual.md | 8 +-
.../data-operate/import/complex-types/array.md | 8 +-
.../data-operate/import/complex-types/json.md | 8 +-
.../data-operate/import/complex-types/map.md | 8 +-
.../data-operate/import/complex-types/struct.md | 8 +-
.../import/data-source/google-cloud-storage.md | 8 +-
.../data-operate/import/data-source/hdfs.md | 8 +-
.../data-operate/import/data-source/minio.md | 8 +-
.../data-operate/import/file-format/json.md | 6 +-
.../data-operate/import/file-format/orc.md | 8 +-
.../data-operate/import/file-format/parquet.md | 9 +-
.../data-operate/scheduler/job-scheduler.md | 8 +-
.../version-4.x/gettingStarted/quick-start.mdx | 8 +-
.../install-doris-cluster.md | 8 +-
.../install-doris-cluster.md | 8 +-
.../version-4.x/lakehouse/file-formats/orc.md | 8 +-
.../version-4.x/lakehouse/file-formats/parquet.md | 8 +-
versioned_docs/version-4.x/lakehouse/statistics.md | 8 +-
.../version-4.x/lakehouse/storages/gcs.md | 8 +-
.../version-4.x/lakehouse/storages/hdfs.md | 9 +-
.../version-4.x/lakehouse/storages/minio.md | 8 +-
.../version-4.x/lakehouse/storages/s3.md | 9 +-
.../version-4.x/observability/overview.mdx | 8 +-
.../async-materialized-view/use-guide.md | 9 +-
.../statistics.md | 8 +-
.../sql-data-types/data-type-overview.md | 8 +-
.../basic-element/sql-data-types/date-time/DATE.md | 8 +-
.../basic-element/sql-data-types/date-time/TIME.md | 8 +-
.../sql-data-types/semi-structured/ARRAY.md | 6 +-
.../sql-data-types/semi-structured/JSON.md | 8 +-
.../sql-data-types/semi-structured/MAP.md | 8 +-
.../sql-data-types/semi-structured/STRUCT.md | 9 +-
.../semi-structured/semi-structured-overview.md | 7 +-
.../sql-data-types/string-type/CHAR.md | 8 +-
.../sql-functions/ai-functions/overview.md | 8 +-
.../scalar-functions/array-functions/array.md | 7 +-
.../scalar-functions/bitwise-functions/xor.md | 8 +-
.../scalar-functions/date-time-functions/date.md | 9 +-
.../date-time-functions/from-iso8601-date.md | 9 +-
.../scalar-functions/date-time-functions/time.md | 8 +-
.../date-time-functions/timestamp.md | 8 +-
.../date-time-functions/to-iso8601.md | 8 +-
.../date-time-functions/week-ceil.md | 8 +-
.../date-time-functions/week-floor.md | 8 +-
.../scalar-functions/ip-functions/inet-ntoa.md | 8 +-
.../scalar-functions/ip-functions/inet6-aton.md | 8 +-
.../scalar-functions/ip-functions/inet6-ntoa.md | 8 +-
.../ip-functions/ipv4-num-to-string.md | 8 +-
.../ip-functions/ipv6-num-to-string.md | 9 +-
.../ip-functions/ipv6-string-to-num-or-null.md | 8 +-
.../scalar-functions/map-functions/map.md | 9 +-
.../scalar-functions/numeric-functions/xor.md | 8 +-
.../scalar-functions/string-functions/char.md | 8 +-
.../scalar-functions/string-functions/date.md | 9 +-
.../string-functions/from-iso8601-date.md | 9 +-
.../scalar-functions/string-functions/timestamp.md | 7 +-
.../string-functions/to-iso8601.md | 7 +-
.../scalar-functions/string-functions/week-ceil.md | 8 +-
.../string-functions/week-floor.md | 8 +-
.../scalar-functions/struct-functions/struct.md | 8 +-
.../sql-functions/table-valued-functions/hdfs.md | 9 +-
.../sql-functions/table-valued-functions/local.md | 9 +-
.../sql-functions/table-valued-functions/s3.md | 10 +-
.../compute-management/CREATE-WORKLOAD-GROUP.md | 9 +-
.../compute-management/CREATE-WORKLOAD-POLICY.md | 8 +-
.../data-modification/load-and-export/EXPORT.md | 9 +-
.../version-4.x/table-design/best-practice.md | 6 +-
.../table-design/index/inverted-index.md | 8 +-
.../table-design/index/inverted-index/overview.md | 5 +-
.../version-4.x/table-design/overview.md | 8 +-
551 files changed, 3571 insertions(+), 1210 deletions(-)
diff --git a/docs/admin-manual/config/fe-config-template.md b/docs/admin-manual/config/fe-config-template.md
index 310689f134b..53de21be3d1 100644
--- a/docs/admin-manual/config/fe-config-template.md
+++ b/docs/admin-manual/config/fe-config-template.md
@@ -1,10 +1,11 @@
---
{
- "title": "FE Configuration",
+ "title": "FE Configuration Template | Config",
"language": "en",
"toc_min_heading_level": 2,
"toc_max_heading_level": 4,
- "description": "This document mainly introduces the relevant configuration items of FE."
+ "description": "This document mainly introduces the relevant configuration items of FE.",
+ "sidebar_label": "FE Configuration"
}
---
@@ -2748,3 +2749,4 @@ If false, when select from tables in information_schema database,
the result will not contain the information of the table in external catalog.
This is to avoid query time when external catalog is not reachable.
+
diff --git a/docs/admin-manual/config/fe-config.md b/docs/admin-manual/config/fe-config.md
index 76c47a25317..c0c0d3f06b7 100644
--- a/docs/admin-manual/config/fe-config.md
+++ b/docs/admin-manual/config/fe-config.md
@@ -1,10 +1,11 @@
---
{
- "title": "FE Configuration",
+ "title": "FE Configuration | Config",
"language": "en",
"toc_min_heading_level": 2,
"toc_max_heading_level": 4,
- "description": "Complete reference guide for Frontend (FE) configuration parameters in Doris, including metadata management, query engine, load/export, and storage settings."
+ "description": "Complete reference guide for Frontend (FE) configuration parameters in Doris, including metadata management, query engine, load/export, and storage settings.",
+ "sidebar_label": "FE Configuration"
}
---
@@ -2766,3 +2767,4 @@ Description: The mode in which FE runs. `cloud` indicates the decoupled storage
Default: ""
Endpoints of the meta service should be specified in the format 'host1:port,host2:port'. This configuration is necessary for the storage and compute disaggregated mode.
+
diff --git a/docs/admin-manual/data-admin/ccr/overview.md b/docs/admin-manual/data-admin/ccr/overview.md
index 90b30d596cf..454dead9d53 100644
--- a/docs/admin-manual/data-admin/ccr/overview.md
+++ b/docs/admin-manual/data-admin/ccr/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | CCR",
"language": "en",
- "description": "CCR (Cross Cluster Replication) is a cross-cluster data synchronization mechanism that synchronizes data changes from the source cluster to the "
+ "description": "CCR (Cross Cluster Replication) is a cross-cluster data synchronization mechanism that synchronizes data changes from the source cluster to the ",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
## Overview
CCR (Cross Cluster Replication) is a cross-cluster data synchronization mechanism that synchronizes data changes from the source cluster to the target cluster at the database or table level. It is mainly used to enhance the data availability of online services, isolate read and write loads, and build a dual-site, three-center architecture. CCR currently does not support the separation of computing and storage modes.
@@ -90,3 +93,4 @@ requirement: glibc >= 2.28
| 4.0 | X64 | [ccr-syncer-4.0.1-rc01-x64.tar.xz](https://apache-doris-releases.oss-accelerate.aliyuncs.com/ccr-release/ccr-syncer-4.0.1-rc01-x64.tar.xz) | 9f2a049bb2cf107be1a4f79081c1e9da204ebebc410104793996dce3beb87865 |
+
diff --git a/docs/admin-manual/data-admin/ccr/quickstart.md b/docs/admin-manual/data-admin/ccr/quickstart.md
index 13917db3a83..2d77b5698b3 100644
--- a/docs/admin-manual/data-admin/ccr/quickstart.md
+++ b/docs/admin-manual/data-admin/ccr/quickstart.md
@@ -1,8 +1,9 @@
---
{
- "title": "Quick Start",
+ "title": "Quick Start | CCR",
"language": "en",
- "description": "Configure the following information in the fe.conf and be.conf of both the source and target clusters:"
+ "description": "Configure the following information in the fe.conf and be.conf of both the source and target clusters:",
+ "sidebar_label": "Quick Start"
}
---
@@ -78,3 +79,4 @@ If synchronizing at the database level, fill in your_db_name, and leave your_tab
If synchronizing at the table level, fill in both your_db_name and your_table_name
The name used to initiate the synchronization job can only be used once
```
+
diff --git a/docs/admin-manual/maint-monitor/disk-capacity.md b/docs/admin-manual/maint-monitor/disk-capacity.md
index b5093df9dd1..1eb34e16a72 100644
--- a/docs/admin-manual/maint-monitor/disk-capacity.md
+++ b/docs/admin-manual/maint-monitor/disk-capacity.md
@@ -1,8 +1,9 @@
---
{
- "title": "Disk Capacity Management",
+ "title": "Disk Capacity Management | Maint Monitor",
"language": "en",
- "description": "This document mainly introduces system parameters and processing strategies related to disk storage capacity."
+ "description": "This document mainly introduces system parameters and processing strategies related to disk storage capacity.",
+ "sidebar_label": "Disk Capacity Management"
}
---
@@ -147,3 +148,4 @@ When the disk capacity is higher than High Watermark or even Flood Stage, many o
* Delete tablet metadata refer to [Tablet metadata management tool](../trouble-shooting/tablet-meta-tool.md)
```./lib/meta_tool --operation=delete_header --root_path=/path/to/root_path --tablet_id=12345 --schema_hash= 352781111```
+
diff --git a/docs/admin-manual/open-api/be-http/compaction-run.md b/docs/admin-manual/open-api/be-http/compaction-run.md
index 6e416bc3a6e..86bc2c607f3 100644
--- a/docs/admin-manual/open-api/be-http/compaction-run.md
+++ b/docs/admin-manual/open-api/be-http/compaction-run.md
@@ -1,8 +1,9 @@
---
{
- "title": "Disk Capacity Management",
+ "title": "Disk Capacity Management | Be Http",
"language": "en",
- "description": "This document mainly introduces system parameters and processing strategies related to disk storage capacity."
+ "description": "This document mainly introduces system parameters and processing strategies related to disk storage capacity.",
+ "sidebar_label": "Disk Capacity Management"
}
---
@@ -147,3 +148,4 @@ When the disk capacity is higher than High Watermark or even Flood Stage, many o
* Delete tablet metadata (refer to [Tablet metadata management tool](../../trouble-shooting/tablet-meta-tool)）
```./lib/meta_tool --operation=delete_header --root_path=/path/to/root_path --tablet_id=12345 --schema_hash= 352781111```
+
diff --git a/docs/admin-manual/open-api/fe-http/meta-info-action-V2.md b/docs/admin-manual/open-api/fe-http/meta-info-action-V2.md
index 111c687d612..d317af6e4ad 100644
--- a/docs/admin-manual/open-api/fe-http/meta-info-action-V2.md
+++ b/docs/admin-manual/open-api/fe-http/meta-info-action-V2.md
@@ -1,8 +1,9 @@
---
{
- "title": "Meta Info Action",
+ "title": "Meta Info Action V2 | Fe Http",
"language": "en",
- "description": "Used to obtain metadata information about the cluster, including the database list, table list, and table schema."
+ "description": "Used to obtain metadata information about the cluster, including the database list, table list, and table schema.",
+ "sidebar_label": "Meta Info Action V2"
}
---
@@ -52,3 +53,4 @@ None
"count":0
}
```
+
diff --git a/docs/admin-manual/open-api/fe-http/meta-info-action.md b/docs/admin-manual/open-api/fe-http/meta-info-action.md
index b23625bfa71..67f2d6a1eac 100644
--- a/docs/admin-manual/open-api/fe-http/meta-info-action.md
+++ b/docs/admin-manual/open-api/fe-http/meta-info-action.md
@@ -1,8 +1,9 @@
---
{
- "title": "Meta Info Action",
+ "title": "Meta Info Action | Fe Http",
"language": "en",
- "description": "Meta Info Action is used to obtain metadata information in the cluster. Such as database list, table structure, etc."
+ "description": "Meta Info Action is used to obtain metadata information in the cluster. Such as database list, table structure, etc.",
+ "sidebar_label": "Meta Info Action"
}
---
@@ -212,3 +213,4 @@ GET /api/meta/namespaces/default/databases/db1/tables/tbl1/schema?with_mv?=1
```
* The data field returns the table structure information of the base table or rollup table.
+
diff --git a/docs/admin-manual/open-api/fe-http/query-profile-action-controller.md b/docs/admin-manual/open-api/fe-http/query-profile-action-controller.md
index b36b57d1b86..37f7ee7cab4 100644
--- a/docs/admin-manual/open-api/fe-http/query-profile-action-controller.md
+++ b/docs/admin-manual/open-api/fe-http/query-profile-action-controller.md
@@ -1,8 +1,9 @@
---
{
- "title": "Query Profile Action",
+ "title": "Query Profile Action Controller | Fe Http",
"language": "en",
- "description": "The Query Profile Action is used to obtain the Query profile."
+ "description": "The Query Profile Action is used to obtain the Query profile.",
+ "sidebar_label": "Query Profile Action Controller"
}
---
@@ -87,4 +88,4 @@ None
}
```
- `data` is the text content of the profile.
\ No newline at end of file
+ `data` is the text content of the profile.
diff --git a/docs/admin-manual/open-api/fe-http/query-profile-action.md b/docs/admin-manual/open-api/fe-http/query-profile-action.md
index 0538d765b86..27b992db796 100644
--- a/docs/admin-manual/open-api/fe-http/query-profile-action.md
+++ b/docs/admin-manual/open-api/fe-http/query-profile-action.md
@@ -1,11 +1,14 @@
---
{
- "title": "Query Profile Action",
+ "title": "Query Profile Action | Fe Http",
"language": "en",
- "description": "GET /rest/v2/manager/query/statistics/{traceid} (4.0.0+)"
+ "description": "Doris FE Query Profile REST API 文档，支持通过 HTTP 接口获取查询信息、执行 Profile、实时统计数据，并对正在运行的查询进行监控与控制。",
+ "sidebar_label": "Query Profile Action"
}
---
+# Query Profile Action
+
## Request
`GET /rest/v2/manager/query/query_info`
@@ -518,4 +521,4 @@ Retrieve the statistics of a currently running query by Trace ID. You can call t
},
"count": 0
}
-```
\ No newline at end of file
+```
diff --git a/docs/admin-manual/open-api/overview.md b/docs/admin-manual/open-api/overview.md
index 158a4611dc9..a33ce2654e9 100644
--- a/docs/admin-manual/open-api/overview.md
+++ b/docs/admin-manual/open-api/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Open Api",
"language": "en",
- "description": "As a supplement to Apache Doris operation and maintenance management,"
+ "description": "As a supplement to Apache Doris operation and maintenance management,",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
As a supplement to Apache Doris operation and maintenance management, OPEN API is mainly used by database administrators to perform some management operations.
:::note
@@ -27,3 +30,4 @@ The security authentication of FE BE API can be enabled through the following co
The permission requirements for the HTTP API of FE and BE vary from version to version. Please refer to the corresponding API documentation for details.
:::
+
diff --git a/docs/admin-manual/system-tables/information_schema/column_privileges.md b/docs/admin-manual/system-tables/information_schema/column_privileges.md
index b8729ea5c1a..10111dc8953 100644
--- a/docs/admin-manual/system-tables/information_schema/column_privileges.md
+++ b/docs/admin-manual/system-tables/information_schema/column_privileges.md
@@ -1,6 +1,6 @@
---
{
- "title": "column_privileges",
+ "title": "Column Privileges",
"language": "en",
"description": "This table is solely used for compatibility with MySQL behavior and is always empty."
}
diff --git a/docs/admin-manual/system-tables/information_schema/column_statistics.md b/docs/admin-manual/system-tables/information_schema/column_statistics.md
index e7b4d3f78fd..18cd3417f29 100644
--- a/docs/admin-manual/system-tables/information_schema/column_statistics.md
+++ b/docs/admin-manual/system-tables/information_schema/column_statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "column_statistics",
+ "title": "Column Statistics | Information Schema",
"language": "en",
- "description": "This table is solely used for compatibility with MySQL behavior and is always empty."
+ "description": "This table is solely used for compatibility with MySQL behavior and is always empty.",
+ "sidebar_label": "Column Statistics"
}
---
+# Column Statistics
+
## Overview
This table is solely used for compatibility with MySQL behavior and is always empty. It does not truly reflect the statistical information of the data within Doris. To view the statistical information collected by Doris, please refer to the [Statistics](../../../query-acceleration/optimization-technology-principle/statistics#viewing-statistics) section.
@@ -23,4 +26,4 @@ This table is solely used for compatibility with MySQL behavior and is always em
| SCHEMA_NAME | varchar(64) | |
| TABLE_NAME | varchar(64) | |
| COLUMN_NAME | varchar(64) | |
-| HISTOGRAM | json | |
\ No newline at end of file
+| HISTOGRAM | json | |
diff --git a/docs/admin-manual/system-tables/internal_schema/column_statistics.md b/docs/admin-manual/system-tables/internal_schema/column_statistics.md
index 3cd984e6f65..28394e21919 100644
--- a/docs/admin-manual/system-tables/internal_schema/column_statistics.md
+++ b/docs/admin-manual/system-tables/internal_schema/column_statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "column_statistics",
+ "title": "Column Statistics | Internal Schema",
"language": "en",
- "description": "Column statistics"
+ "description": "Column statistics",
+ "sidebar_label": "Column Statistics"
}
---
+# Column Statistics
+
## Overview
Column statistics
@@ -33,4 +36,4 @@ Column statistics
| min | varchar(65533) | Minimum value |
| max | varchar(65533) | Maximum value |
| data_size_in_bytes | bigint | Data size in bytes |
-| update_time | datetime | Update time of current statistics |
\ No newline at end of file
+| update_time | datetime | Update time of current statistics |
diff --git a/docs/admin-manual/system-tables/overview.md b/docs/admin-manual/system-tables/overview.md
index 86ede0f477b..a0de6d186b5 100644
--- a/docs/admin-manual/system-tables/overview.md
+++ b/docs/admin-manual/system-tables/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | System Tables",
"language": "zh-CN",
- "description": "Apache Doris cluster has multiple built-in system databases to store metadata information about the Doris system itself."
+ "description": "Apache Doris cluster has multiple built-in system databases to store metadata information about the Doris system itself.",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
Apache Doris cluster has multiple built-in system databases to store metadata information about the Doris system itself.
### information_schema
@@ -31,3 +34,4 @@ All tables in the `mysql` database are read-only, and users cannot modify, delet
All tables under the `__internal_schema` database are actual tables in Doris, stored similarly to user-created data tables. When a Doris cluster is created, all system tables under this database are automatically created.
By default, common users have read-only permissions for tables in this database. However, once granted, they can modify, delete, or create tables under this database.
+
diff --git a/docs/admin-manual/trouble-shooting/memory-management/overview.md b/docs/admin-manual/trouble-shooting/memory-management/overview.md
index f71814636e9..a6d669b4fa3 100644
--- a/docs/admin-manual/trouble-shooting/memory-management/overview.md
+++ b/docs/admin-manual/trouble-shooting/memory-management/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Memory Management",
"language": "en",
- "description": "Memory management is one of the most important components of Doris. During the operation of Doris,"
+ "description": "Memory management is one of the most important components of Doris. During the operation of Doris,",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
Memory management is one of the most important components of Doris. During the operation of Doris, both load and query rely on a large number of memory operations. The quality of memory management directly affects the stability and performance of Doris.
As an OLAP database based on the MPP architecture, Apache Doris will stream and calculate between operators after loading data from disk to memory, and store the intermediate results of calculation in memory. This method reduces frequent disk I/O operations and makes full use of the parallel computing capabilities of multiple machines and multiple cores, which can show huge advantages in performance.
@@ -143,3 +146,4 @@ Refer to [Memory problem FAQ](./memory-issue-faq.md) to analyze common memory pr
## Memory control strategy
Refer to [Memory Control Strategy](./memory-feature/memory-control-strategy.md) for an introduction to memory allocation, monitoring, and recycling, which ensure the efficient and controllable memory of the Doris BE process.
+
diff --git a/docs/admin-manual/workload-management/job-scheduler.md b/docs/admin-manual/workload-management/job-scheduler.md
index 49f55551635..73515bd56c8 100644
--- a/docs/admin-manual/workload-management/job-scheduler.md
+++ b/docs/admin-manual/workload-management/job-scheduler.md
@@ -1,11 +1,14 @@
---
{
- "title": "Job Scheduler",
+ "title": "Job Scheduler | Workload Management",
"language": "en",
- "description": "Introduction to Doris Job Scheduler, a built-in task scheduling system that enables automated periodic data imports, ETL operations, and data synchronization with second-level precision."
+ "description": "Introduction to Doris Job Scheduler, a built-in task scheduling system that enables automated periodic data imports, ETL operations, and data synchronization with second-level precision.",
+ "sidebar_label": "Job Scheduler"
}
---
+# Job Scheduler
+
## Background
In the context of increasing demands for refined data management, scheduled scheduling plays an important role. It is typically applied in the following scenarios:
@@ -216,3 +219,4 @@ In the future, Doris Job Scheduler will also support the following features:
- Support for JOB workflow orchestration, i.e., DAG JOB. This means we can implement internal data warehouse task orchestration, and with the Catalog functionality, it will more efficiently complete data processing and analysis tasks.
- Support for scheduling import tasks, UPDATE, and DELETE operations.
+
diff --git a/docs/admin-manual/workload-management/workload-management-summary.md b/docs/admin-manual/workload-management/workload-management-summary.md
index 97b332ac77b..c42b3d1687d 100644
--- a/docs/admin-manual/workload-management/workload-management-summary.md
+++ b/docs/admin-manual/workload-management/workload-management-summary.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Workload Management",
"language": "en",
- "description": "Workload management is a very important feature of Doris, playing a critical role in the overall system management."
+ "description": "Workload management is a very important feature of Doris, playing a critical role in the overall system management.",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
Workload management is a very important feature of Doris, playing a critical role in the overall system management. Through reasonable workload management strategies, resource utilization can be optimized, system stability enhanced, and response time reduced. It has the following abilities:
- Resource Isolation: By dividing into multiple groups and setting resource (CPU, Memory, IO) limits for each group, it ensures that there is no interference between multiple users or different tasks (such as read and write operations) of the same user.
@@ -41,3 +44,4 @@ The following table records the characteristics and advantageous scenarios of di
- Soft Limit: The soft limit is a resource limit that can be exceeded, usually representing the recommended upper limit of resource usage. When the system is not busy, if a tenant requests more resources than the soft limit, it can borrow resources from other groups. When the system is busy and there is resource contention, if a tenant requests resources exceeding the soft limit, it will not be able to obtain additional resources.
When using the Resource Group / Compute Group method to partition resources, only the hard limit mode is supported. When using the Workload Group method to partition resources, both the soft limit and hard limit of Workload Group are supported. The soft limit of Workload Group is usually used for sudden resource control, such as temporary query peaks or short-term increases in data writing.
+
diff --git a/docs/ai/vector-search/overview.md b/docs/ai/vector-search/overview.md
index 93018ce9c2f..92aaec324cd 100644
--- a/docs/ai/vector-search/overview.md
+++ b/docs/ai/vector-search/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Vector Search",
"language": "en",
- "description": "In generative AI applications, relying solely on a large model's internal parameter “memory” has clear limitations: (1) the model’s knowledge becomes "
+ "description": "In generative AI applications, relying solely on a large model's internal parameter “memory” has clear limitations: (1) the model’s knowledge becomes ",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
@@ -393,3 +396,4 @@ In the era of AI, Python has become the mainstream language for data processing
4. If the distance function in SQL does not match the metric type defined in the index DDL, Doris cannot use the ANN index for TopN—even if you call `l2_distance_approximate` / `inner_product_approximate`.
5. For metric type `inner_product`, only `ORDER BY inner_product_approximate(...) DESC LIMIT N` (DESC required) can be accelerated by the ANN index.
6. The first parameter of `xxx_approximate()` must be a ColumnArray, and the second must be a CAST or ArrayLiteral. Reversing them triggers brute-force search.
+
diff --git a/docs/compute-storage-decoupled/overview.md b/docs/compute-storage-decoupled/overview.md
index 1a91bb98df2..44c5aa04c9d 100644
--- a/docs/compute-storage-decoupled/overview.md
+++ b/docs/compute-storage-decoupled/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Compute Storage Decoupled",
"language": "en",
- "description": "This article introduces the differences, advantages,"
+ "description": "This article introduces the differences, advantages,",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
This article introduces the differences, advantages, and applicable scenarios of the compute-storage coupled mode and compute-storage decoupled mode of Doris, providing a reference for users' selection.
The following sections will describe in detail how to deploy and use Apache Doris in the compute-storage decoupled mode. For information on deployment in compute-storage coupled mode, please refer to the [Cluster Deployment](../install/deploy-manually/integrated-storage-compute-deploy-manually.md) section.
@@ -77,3 +80,4 @@ The shared storage layer stores the data files, including segment files and the
- When you require high elastic scalability, Kubernetes containerization, or to run on a private cloud;
- High throughput shared storage capability, allowing multiple computing groups to share data
- When you have a dedicated team responsible for maintaining the company's entire data warehouse platform.
+
diff --git a/docs/data-operate/export/export-best-practice.md b/docs/data-operate/export/export-best-practice.md
index e52c95d2a42..4feaba0c383 100644
--- a/docs/data-operate/export/export-best-practice.md
+++ b/docs/data-operate/export/export-best-practice.md
@@ -1,11 +1,14 @@
---
{
- "title": "Best Practices",
+ "title": "Best Practices | Export",
"language": "en",
- "description": "This document mainly introduces how to determine whether resource utilization is reasonable during data export operations,"
+ "description": "This document mainly introduces how to determine whether resource utilization is reasonable during data export operations,",
+ "sidebar_label": "Best Practices"
}
---
+# Best Practices
+
This document mainly introduces how to determine whether resource utilization is reasonable during data export operations, and how to adjust resource utilization to achieve better data export efficiency.
## SELECT INTO OUTFILE
@@ -94,3 +97,4 @@ This document mainly introduces how to determine whether resource utilization is
- `async_task_consumer_thread_num`
This is an FE configuration parameter that indicates the number of Export Tasks that the current cluster can run concurrently. The default value is 64. An Export Job is split into multiple Export Tasks based on concurrency. All Export Tasks share this threshold. To increase the overall number of concurrent export tasks that the cluster can execute, increase this parameter and restart the FE node.
+
diff --git a/docs/data-operate/export/export-manual.md b/docs/data-operate/export/export-manual.md
index ccbfdef9a9f..cef90078c84 100644
--- a/docs/data-operate/export/export-manual.md
+++ b/docs/data-operate/export/export-manual.md
@@ -1,11 +1,14 @@
---
{
- "title": "EXPORT",
+ "title": "EXPORT | Export",
"language": "en",
- "description": "This document will introduce how to use the EXPORT command to export the data stored in Doris."
+ "description": "This document will introduce how to use the EXPORT command to export the data stored in Doris.",
+ "sidebar_label": "EXPORT"
}
---
+# EXPORT
+
This document will introduce how to use the `EXPORT` command to export the data stored in Doris.
`Export` is a function provided by Doris for asynchronously exporting data. This function can export the data of the tables or partitions specified by users in the specified file format to the target storage systems, including object storage, HDFS or local file system.
@@ -386,3 +389,4 @@ The specific BE node IP can be viewed in the `OutfileInfo` column in the `SHOW E
:::caution
This function is not applicable to the production environment, and please ensure the permissions of the export directory and data security on your own.
:::
+
diff --git a/docs/data-operate/import/complex-types/array.md b/docs/data-operate/import/complex-types/array.md
index b9c6bfd21e7..5e05172aa85 100644
--- a/docs/data-operate/import/complex-types/array.md
+++ b/docs/data-operate/import/complex-types/array.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Complex Types",
"language": "en",
- "description": "ARRAY<T> An array of T-type items. Click ARRAY to learn more."
+ "description": "ARRAY<T> An array of T-type items. Click ARRAY to learn more.",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
`ARRAY<T>` An array of T-type items. Click [ARRAY](../../../sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md) to learn more.
## CSV format import
@@ -117,3 +120,4 @@ mysql> SELECT * FROM array_test;
+------+-----------------+
4 rows in set (0.01 sec)
```
+
diff --git a/docs/data-operate/import/complex-types/json.md b/docs/data-operate/import/complex-types/json.md
index 9a129e4fa9e..10e6712853d 100644
--- a/docs/data-operate/import/complex-types/json.md
+++ b/docs/data-operate/import/complex-types/json.md
@@ -1,11 +1,14 @@
---
{
- "title": "JSON",
+ "title": "JSON | Complex Types",
"language": "en",
- "description": "The JSON data type stores JSON data efficiently in a binary format and allows access to its internal fields through JSON functions."
+ "description": "The JSON data type stores JSON data efficiently in a binary format and allows access to its internal fields through JSON functions.",
+ "sidebar_label": "JSON"
}
---
+# JSON
+
The JSON data type stores JSON data efficiently in a binary format and allows access to its internal fields through JSON functions.
By default, it supports up to 1048576 bytes (1MB), and can be increased up to 2147483643 bytes (2GB). This can be adjusted via the string_type_length_soft_limit_bytes configuration.
@@ -129,3 +132,4 @@ mysql> SELECT * FROM json_test;
+------+-------------------------------+
5 rows in set (0.01 sec)
```
+
diff --git a/docs/data-operate/import/complex-types/map.md b/docs/data-operate/import/complex-types/map.md
index 81400d3dc32..e486b66dc2b 100644
--- a/docs/data-operate/import/complex-types/map.md
+++ b/docs/data-operate/import/complex-types/map.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Complex Types",
"language": "en",
- "description": "MAP<K, V> A Map of K, V items。 Click MAP to learn more."
+ "description": "MAP<K, V> A Map of K, V items。 Click MAP to learn more.",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
`MAP<K, V>` A Map of K, V items。 Click [MAP](../../../sql-manual/basic-element/sql-data-types/semi-structured/MAP.md) to learn more.
## CSV format import
@@ -117,3 +120,4 @@ mysql> SELECT * FROM map_test;
+------+-------------------------+
4 rows in set (0.01 sec)
```
+
diff --git a/docs/data-operate/import/complex-types/struct.md b/docs/data-operate/import/complex-types/struct.md
index cbbe1055ced..b5aaf86d15f 100644
--- a/docs/data-operate/import/complex-types/struct.md
+++ b/docs/data-operate/import/complex-types/struct.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Complex Types",
"language": "en",
- "description": "STRUCT<fieldname:fieldtype [COMMENT 'commentstring'], ... > Represents value with structure described by multiple fields,"
+ "description": "STRUCT<fieldname:fieldtype [COMMENT 'commentstring'], ... > Represents value with structure described by multiple fields,",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
`STRUCT<field_name:field_type [COMMENT 'comment_string'], ... >` Represents value with structure described by multiple fields, which can be viewed as a collection of multiple columns.Click [STRUCT](../../../sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md) to learn more.
## CSV format import
@@ -127,3 +130,4 @@ mysql> SELECT * FROM struct_test;
+------+--------------------------------------+
5 rows in set (0.00 sec)
```
+
diff --git a/docs/data-operate/import/data-source/google-cloud-storage.md b/docs/data-operate/import/data-source/google-cloud-storage.md
index 1af77e03847..26166feaa94 100644
--- a/docs/data-operate/import/data-source/google-cloud-storage.md
+++ b/docs/data-operate/import/data-source/google-cloud-storage.md
@@ -1,11 +1,14 @@
---
{
- "title": "Google Cloud Storage",
+ "title": "Google Cloud Storage | Data Source",
"language": "en",
- "description": "Doris provides two ways to load files from Google Cloud Storage:"
+ "description": "Doris provides two ways to load files from Google Cloud Storage:",
+ "sidebar_label": "Google Cloud Storage"
}
---
+# Google Cloud Storage
+
Doris provides two ways to load files from Google Cloud Storage:
- Use S3 Load to load Google Cloud Storage files into Doris, which is an asynchronous load method.
- Use TVF to load Google Cloud Storage files into Doris, which is a synchronous load method.
@@ -170,3 +173,4 @@ mysql> select * from test_s3load;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/docs/data-operate/import/data-source/hdfs.md b/docs/data-operate/import/data-source/hdfs.md
index 00e68dc7011..54cf9ab69e1 100644
--- a/docs/data-operate/import/data-source/hdfs.md
+++ b/docs/data-operate/import/data-source/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Data Source",
"language": "en",
- "description": "Doris provides two ways to load files from HDFS:"
+ "description": "Doris provides two ways to load files from HDFS:",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
Doris provides two ways to load files from HDFS:
- Use HDFS Load to load HDFS files into Doris, which is an asynchronous load method.
- Use TVF to load HDFS files into Doris, which is a synchronous load method.
@@ -162,3 +165,4 @@ mysql> select * from test_hdfsload;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/docs/data-operate/import/data-source/minio.md b/docs/data-operate/import/data-source/minio.md
index 02491676a1d..f931df4c21c 100644
--- a/docs/data-operate/import/data-source/minio.md
+++ b/docs/data-operate/import/data-source/minio.md
@@ -1,11 +1,14 @@
---
{
- "title": "MinIO",
+ "title": "MinIO | Data Source",
"language": "en",
- "description": "Doris provides two ways to load files from MinIO:"
+ "description": "Doris provides two ways to load files from MinIO:",
+ "sidebar_label": "MinIO"
}
---
+# MinIO
+
Doris provides two ways to load files from MinIO:
- Use S3 Load to load MinIO files into Doris, which is an asynchronous load method.
- Use TVF to load MinIO files into Doris, which is a synchronous load method.
@@ -193,3 +196,4 @@ mysql> select * from test_s3load;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/docs/data-operate/import/file-format/json.md b/docs/data-operate/import/file-format/json.md
index 4fea76c2b40..241a57b63bd 100644
--- a/docs/data-operate/import/file-format/json.md
+++ b/docs/data-operate/import/file-format/json.md
@@ -1,8 +1,9 @@
---
{
- "title": "JSON",
+ "title": "JSON | File Format",
"language": "en",
- "description": "This document explains how to load JSON format data files into Doris."
+ "description": "This document explains how to load JSON format data files into Doris.",
+ "sidebar_label": "JSON"
}
---
@@ -437,3 +438,4 @@ FROM S3
"json_root" = "$.events",
...
);
+
diff --git a/docs/data-operate/import/file-format/orc.md b/docs/data-operate/import/file-format/orc.md
index d863f73c90f..09f027cf67b 100644
--- a/docs/data-operate/import/file-format/orc.md
+++ b/docs/data-operate/import/file-format/orc.md
@@ -1,11 +1,14 @@
---
{
- "title": "ORC",
+ "title": "ORC | File Format",
"language": "en",
- "description": "This document explains how to load ORC format data files in Doris."
+ "description": "This document explains how to load ORC format data files in Doris.",
+ "sidebar_label": "ORC"
}
---
+# ORC
+
This document explains how to load ORC format data files in Doris.
## Supported Loading Methods
@@ -56,3 +59,4 @@ FROM S3
"format" = "orc",
...
);
+
diff --git a/docs/data-operate/import/file-format/parquet.md b/docs/data-operate/import/file-format/parquet.md
index 1ef73fa955b..3a47ffcead0 100644
--- a/docs/data-operate/import/file-format/parquet.md
+++ b/docs/data-operate/import/file-format/parquet.md
@@ -1,11 +1,14 @@
---
{
- "title": "Parquet",
+ "title": "Parquet | File Format",
"language": "en",
- "description": "This document explains how to load Parquet format data files in Doris."
+ "description": "This document explains how to load Parquet format data files in Doris.",
+ "sidebar_label": "Parquet"
}
---
+# Parquet
+
This document explains how to load Parquet format data files in Doris.
## Supported Loading Methods
@@ -55,4 +58,4 @@ FROM S3
"path" = "s3://bucket/example.parquet",
"format" = "parquet",
...
-);
\ No newline at end of file
+);
diff --git a/docs/data-operate/scheduler/job-scheduler.md b/docs/data-operate/scheduler/job-scheduler.md
index f398871c216..01a4683b258 100644
--- a/docs/data-operate/scheduler/job-scheduler.md
+++ b/docs/data-operate/scheduler/job-scheduler.md
@@ -1,11 +1,14 @@
---
{
- "title": "Job Scheduler",
+ "title": "Job Scheduler | Scheduler",
"language": "en",
- "description": "In the context of increasingly refined data management needs, scheduled tasks play a crucial role."
+ "description": "In the context of increasingly refined data management needs, scheduled tasks play a crucial role.",
+ "sidebar_label": "Job Scheduler"
}
---
+# Job Scheduler
+
## Background
In the context of increasingly refined data management needs, scheduled tasks play a crucial role. They are typically applied in the following scenarios:
@@ -184,3 +187,4 @@ Conclusion
## Future Plans
Doris Job Scheduler is a powerful and flexible task scheduling tool essential for data processing. Beyond common scenarios like data lake analysis and internal ETL, it plays a crucial role in implementing asynchronous materialized views. Asynchronous materialized views store precomputed result sets, and their update frequency is closely tied to source table changes. Frequent updates to source table data necess
+
diff --git a/docs/ecosystem/bi/tableau-back.md b/docs/ecosystem/bi/tableau-back.md
index 21197d6a21b..24541f6ed99 100644
--- a/docs/ecosystem/bi/tableau-back.md
+++ b/docs/ecosystem/bi/tableau-back.md
@@ -1,11 +1,14 @@
---
{
- "title": "Tableau",
+ "title": "Tableau Back | Bi",
"language": "en",
- "description": "VeloDB provides an official Tableau Doris connector. This connector accesses data based on the MySQL JDBC Driver."
+ "description": "VeloDB provides an official Tableau Doris connector. This connector accesses data based on the MySQL JDBC Driver.",
+ "sidebar_label": "Tableau Back"
}
---
+# Tableau Back
+
VeloDB provides an official Tableau Doris connector. This connector accesses data based on the MySQL JDBC Driver.
The connector has been tested by the [TDVT framework](https://tableau.github.io/connector-plugin-sdk/docs/tdvt) with a 100% pass rate.
@@ -136,3 +139,4 @@ So far, Tableau has been successfully connected to Apache Doris, and data analys
This connector simplifies the connection setup process of generic ODBC/JDBC driver-based connectors and provides a better compatible connector for Apache Doris. If you encounter any problems when using the connector, please feel free to contact us on [GitHub](https://github.com/apache/doris/issues).
+
diff --git a/docs/ecosystem/bi/tableau.md b/docs/ecosystem/bi/tableau.md
index f12d50c055a..eb332fa7517 100644
--- a/docs/ecosystem/bi/tableau.md
+++ b/docs/ecosystem/bi/tableau.md
@@ -1,11 +1,14 @@
---
{
- "title": "Tableau",
+ "title": "Tableau | Bi",
"language": "en",
- "description": "For enabling Apache Doris access on Tableau, Tableau's official MySQL connector can meet your needs."
+ "description": "For enabling Apache Doris access on Tableau, Tableau's official MySQL connector can meet your needs.",
+ "sidebar_label": "Tableau"
}
---
+# Tableau
+
For enabling Apache Doris access on Tableau, Tableau's official MySQL connector can meet your needs. This connector uses the MySQL JDBC driver to access data.
Through the MySQL connector, Tableau can integrate Apache Doris databases and tables as data sources. To enable this feature, follow the setup guide below:
@@ -107,3 +110,4 @@ At this point, Tableau has been successfully connected to Apache Doris, enabling
- Configure security groups to restrict access.
- Enable SSL/TLS connections and other access methods.
- Fine-tune Doris user account roles and access permissions to avoid excessive delegation of permissions.
+
diff --git a/docs/gettingStarted/quick-start.mdx b/docs/gettingStarted/quick-start.mdx
index c0802d5e450..40656e10723 100644
--- a/docs/gettingStarted/quick-start.mdx
+++ b/docs/gettingStarted/quick-start.mdx
@@ -1,11 +1,14 @@
---
{
- "title": "Quick Start",
+ "title": "Quick Start | GettingStarted",
"language": "en",
- "description": "Starting from Doris version 2.1.8, Docker can be used for rapid deployment."
+ "description": "Starting from Doris version 2.1.8, Docker can be used for rapid deployment.",
+ "sidebar_label": "Quick Start"
}
---
+# Quick Start
+
:::caution Warning:
The following rapid deployment methods are intended solely for local development and testing, and should not be used in production environments. The reasons are as follows:
@@ -246,3 +249,4 @@ Download the corresponding binary installation package from the Apache Doris web
+
diff --git a/docs/install/deploy-on-kubernetes/integrated-storage-compute/install-doris-cluster.md b/docs/install/deploy-on-kubernetes/integrated-storage-compute/install-doris-cluster.md
index 347b67f9497..787f618b9de 100644
--- a/docs/install/deploy-on-kubernetes/integrated-storage-compute/install-doris-cluster.md
+++ b/docs/install/deploy-on-kubernetes/integrated-storage-compute/install-doris-cluster.md
@@ -1,11 +1,14 @@
---
{
- "title": "Deploy Doris Cluster",
+ "title": "Deploy Doris Cluster | Integrated Storage Compute",
"language": "en",
- "description": "To deploy a Doris cluster on Kubernetes, ensure that the Doris Operator is deployed."
+ "description": "To deploy a Doris cluster on Kubernetes, ensure that the Doris Operator is deployed.",
+ "sidebar_label": "Deploy Doris Cluster"
}
---
+# Deploy Doris Cluster
+
To deploy a Doris cluster on Kubernetes, ensure that [the Doris Operator is deployed](install-doris-operator.md).
The deployment process for a Doris cluster consists of three steps: download the deployment template, custom the template and deploy cluster, and verify the cluster status.
## Step 1: Download the Doris deployment template
@@ -37,3 +40,4 @@ Expected output:
NAME FESTATUS BESTATUS CNSTATUS BROKERSTATUS
doriscluster-sample available available
```
+
diff --git a/docs/install/deploy-on-kubernetes/separating-storage-compute/install-doris-cluster.md b/docs/install/deploy-on-kubernetes/separating-storage-compute/install-doris-cluster.md
index 6d1e7c34e63..69889aaac23 100644
--- a/docs/install/deploy-on-kubernetes/separating-storage-compute/install-doris-cluster.md
+++ b/docs/install/deploy-on-kubernetes/separating-storage-compute/install-doris-cluster.md
@@ -1,11 +1,14 @@
---
{
- "title": "Deploy Doris Cluster",
+ "title": "Deploy Doris Cluster | Separating Storage Compute",
"language": "en",
- "description": "Deploying a functional decoupled storage and compute Doris cluster on Kubernetes involves four main steps:"
+ "description": "Deploying a functional decoupled storage and compute Doris cluster on Kubernetes involves four main steps:",
+ "sidebar_label": "Deploy Doris Cluster"
}
---
+# Deploy Doris Cluster
+
Deploying a functional decoupled storage and compute Doris cluster on Kubernetes involves four main steps:
1. Preparation – Primarily, install a FoundationDB cluster.
2. Deploying the Doris Operator.
@@ -139,3 +142,4 @@ After the cluster has successfully started, configure an available object storag
Here, {vaultName} is the name of the Vault you wish to use, for example, s3_vault as created in the example above.
+
diff --git a/docs/lakehouse/file-formats/orc.md b/docs/lakehouse/file-formats/orc.md
index 3a3b014bbda..63a8b3e8e0b 100644
--- a/docs/lakehouse/file-formats/orc.md
+++ b/docs/lakehouse/file-formats/orc.md
@@ -1,11 +1,14 @@
---
{
- "title": "ORC",
+ "title": "ORC | File Formats",
"language": "en",
- "description": "This document introduces the support for reading and writing ORC file formats in Doris. It applies to the following functionalities:"
+ "description": "This document introduces the support for reading and writing ORC file formats in Doris. It applies to the following functionalities:",
+ "sidebar_label": "ORC"
}
---
+# ORC
+
This document introduces the support for reading and writing ORC file formats in Doris. It applies to the following functionalities:
* Reading and writing data in the Catalog.
@@ -60,3 +63,4 @@ This document introduces the support for reading and writing ORC file formats in
* `orc_natural_read_size_mb` (2.1+, 3.0+)
The maximum number of bytes that the ORC Reader reads at one time. Default is 8 MB.
+
diff --git a/docs/lakehouse/file-formats/parquet.md b/docs/lakehouse/file-formats/parquet.md
index 729af5b5e77..4db89664bb7 100644
--- a/docs/lakehouse/file-formats/parquet.md
+++ b/docs/lakehouse/file-formats/parquet.md
@@ -1,11 +1,14 @@
---
{
- "title": "Parquet",
+ "title": "Parquet | File Formats",
"language": "zh-CN",
- "description": "This document introduces the support for reading and writing Parquet file formats in Doris. It applies to the following features:"
+ "description": "This document introduces the support for reading and writing Parquet file formats in Doris. It applies to the following features:",
+ "sidebar_label": "Parquet"
}
---
+# Parquet
+
This document introduces the support for reading and writing Parquet file formats in Doris. It applies to the following features:
* Reading and writing data in the Catalog.
@@ -54,3 +57,4 @@ This document introduces the support for reading and writing Parquet file format
The maximum buffer size allocated when reading a Column within a Parquet Row Group. Default is 8M.
+
diff --git a/docs/lakehouse/statistics.md b/docs/lakehouse/statistics.md
index d8579e5efb4..d7219d555a3 100644
--- a/docs/lakehouse/statistics.md
+++ b/docs/lakehouse/statistics.md
@@ -1,11 +1,15 @@
---
{
- "title": "Statistics",
+ "title": "Statistics | Lakehouse",
"language": "en",
- "description": "Doris supports automatic or manual statistics collection for tables from external data sources like Hive, Iceberg and Paimon."
+ "description": "Doris supports automatic or manual statistics collection for tables from external data sources like Hive, Iceberg and Paimon.",
+ "sidebar_label": "Statistics"
}
---
+# Statistics
+
Doris supports automatic or manual statistics collection for tables from external data sources like Hive, Iceberg and Paimon. The accuracy of statistics directly determines the accuracy of cost estimation, which is crucial for selecting the optimal query plan. This can significantly improve query execution efficiency, especially in complex query scenarios.
For details, please refer to the [Statistics](../query-acceleration/optimization-technology-principle/statistics#外表收集) document in the "External Table Collection" section.
+
diff --git a/docs/lakehouse/storages/gcs.md b/docs/lakehouse/storages/gcs.md
index 1503817c0dd..2e52959ec73 100644
--- a/docs/lakehouse/storages/gcs.md
+++ b/docs/lakehouse/storages/gcs.md
@@ -1,10 +1,14 @@
---
{
- "title": "Google Cloud Storage",
+ "title": "Google Cloud Storage | Storages",
"language": "zh-CN",
- "description": "The document is under development."
+ "description": "The document is under development.",
+ "sidebar_label": "Google Cloud Storage"
}
---
+# Google Cloud Storage
+
The document is under development.
+
diff --git a/docs/lakehouse/storages/hdfs.md b/docs/lakehouse/storages/hdfs.md
index 1414bee3ca8..5c6444afa44 100644
--- a/docs/lakehouse/storages/hdfs.md
+++ b/docs/lakehouse/storages/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Storages",
"language": "en",
- "description": "This document describes the parameters required for accessing HDFS. These parameters apply to:"
+ "description": "This document describes the parameters required for accessing HDFS. These parameters apply to:",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
This document describes the parameters required for accessing HDFS. These parameters apply to:
* Catalog properties
@@ -214,4 +217,4 @@ The Java version uses Java to access HDFS and can simulate the logic of Doris FE
The CPP version accesses HDFS through C++ calling libhdfs and can simulate the logic of Doris BE side accessing HDFS.
-For specific usage, please refer to the README in each code repository.
\ No newline at end of file
+For specific usage, please refer to the README in each code repository.
diff --git a/docs/lakehouse/storages/minio.md b/docs/lakehouse/storages/minio.md
index 0dec6403993..ae8e0160735 100644
--- a/docs/lakehouse/storages/minio.md
+++ b/docs/lakehouse/storages/minio.md
@@ -1,11 +1,14 @@
---
{
- "title": "MinIO",
+ "title": "MinIO | Storages",
"language": "en",
- "description": "This document describes the parameters required to access MinIO, which apply to the following scenarios:"
+ "description": "This document describes the parameters required to access MinIO, which apply to the following scenarios:",
+ "sidebar_label": "MinIO"
}
---
+# MinIO
+
This document describes the parameters required to access MinIO, which apply to the following scenarios:
- Catalog properties
@@ -56,3 +59,4 @@ For versions before 3.1:
* It is recommended to use the `minio.` prefix for configuration parameters to ensure consistency and clarity with MinIO.
* For versions before 3.1, please use the legacy name `s3.` as the prefix.
* Connection pool parameters can be adjusted according to concurrency requirements to avoid connection
+
diff --git a/docs/lakehouse/storages/s3.md b/docs/lakehouse/storages/s3.md
index a85b20c2a88..1f2ba5d54e5 100644
--- a/docs/lakehouse/storages/s3.md
+++ b/docs/lakehouse/storages/s3.md
@@ -1,11 +1,14 @@
---
{
- "title": "S3",
+ "title": "S3 | Storages",
"language": "en",
- "description": "This document describes the parameters required for accessing AWS S3. These parameters apply to:"
+ "description": "This document describes the parameters required for accessing AWS S3. These parameters apply to:",
+ "sidebar_label": "S3"
}
---
+# S3
+
This document describes the parameters required for accessing AWS S3. These parameters apply to:
- Catalog properties.
@@ -152,4 +155,4 @@ Based on read-only permissions, additionally allows deleting, creating, and modi
2. Principle of Least Privilege
- If only querying, do not grant write permissions.
-
\ No newline at end of file
+
diff --git a/docs/observability/overview.mdx b/docs/observability/overview.mdx
index 1d77bbe6c08..1d3e7783769 100644
--- a/docs/observability/overview.mdx
+++ b/docs/observability/overview.mdx
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Observability",
"language": "en",
- "description": "Observability refers to the ability to infer a system's internal state through its external output data. An observability platform collects, stores,"
+ "description": "Observability refers to the ability to infer a system's internal state through its external output data. An observability platform collects, stores,",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
## What Is Observability?
Observability refers to the ability to infer a system's internal state through its external output data. An observability platform collects, stores, and visualizes three core data: Logs, Traces, and Metrics. This helps teams gain a comprehensive understanding of the operational status of distributed systems, supports resource optimization, fault prediction, root cause analysis, improves system reliability, and enhances user experience.
@@ -153,3 +156,4 @@ Grafana connects to Doris via MySQL datasource, offering unified visualization a
While Grafana's log visualization and analysis capabilities are relatively basic compared to Kibana, third-party vendors have implemented Kibana-like Discover features. These will soon be integrated into Grafana's Doris datasource, enhancing unified observability visualization. Future enhancements will include Elasticsearch protocol compatibility, enabling native Kibana connections to Doris. For ELK users, replacing Elasticsearch with Doris maintains existing logging and visualization ha [...]
+
diff --git a/docs/query-acceleration/materialized-view/async-materialized-view/use-guide.md b/docs/query-acceleration/materialized-view/async-materialized-view/use-guide.md
index 0bfcadda691..9d4ab70939e 100644
--- a/docs/query-acceleration/materialized-view/async-materialized-view/use-guide.md
+++ b/docs/query-acceleration/materialized-view/async-materialized-view/use-guide.md
@@ -1,11 +1,14 @@
---
{
- "title": "Best Practices",
+ "title": "Best Practices | Async Materialized View",
"language": "en",
- "description": "When the following conditions are met, it is recommended to create partitioned materialized views:"
+ "description": "When the following conditions are met, it is recommended to create partitioned materialized views:",
+ "sidebar_label": "Best Practices"
}
---
+# Best Practices
+
## Principles for Using Asynchronous Materialized Views
- **Timeliness Consideration:** Asynchronous materialized views are typically used in scenarios where data timeliness is not critical, usually T+1 data. If high timeliness is required, consider using synchronous materialized views.
@@ -778,4 +781,4 @@ Note that: If the DML operation involves external tables whose data changes cann
For DML, when the materialized view contains external tables whose data cannot be detected in real-time, whether to enable materialized view transparent rewriting based on structure information, default disabled
-`SET enable_dml_materialized_view_rewrite_when_base_table_unawareness = true;`
\ No newline at end of file
+`SET enable_dml_materialized_view_rewrite_when_base_table_unawareness = true;`
diff --git a/docs/query-acceleration/optimization-technology-principle/statistics.md b/docs/query-acceleration/optimization-technology-principle/statistics.md
index 9b6877c0227..60ee895af4e 100644
--- a/docs/query-acceleration/optimization-technology-principle/statistics.md
+++ b/docs/query-acceleration/optimization-technology-principle/statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "Statistics",
+ "title": "Statistics | Optimization Technology Principle",
"language": "en",
- "description": "Starting from version 2.0, Doris integrated Cost-Based Optimization (CBO) capabilities into its optimizer. Statistics are the cornerstone of CBO,"
+ "description": "Starting from version 2.0, Doris integrated Cost-Based Optimization (CBO) capabilities into its optimizer. Statistics are the cornerstone of CBO,",
+ "sidebar_label": "Statistics"
}
---
+# Statistics
+
Starting from version 2.0, Doris integrated Cost-Based Optimization (CBO) capabilities into its optimizer. Statistics are the cornerstone of CBO, and their accuracy directly determines the accuracy of cost estimation, which is crucial for selecting the optimal execution plan. This document serves as a guide to statistical usage for unreleased development version, focusing on the collection and management methods, relevant configuration options, and frequently asked questions.
## Collection of Statistics
@@ -478,3 +481,4 @@ Automatic collection uses sampling and does not require full table scans, and th
For some special tables, such as those with many partitions or large individual tablets, memory usage may be higher.
It is recommended to plan the number of tablets reasonably when creating tables to avoid creating oversized tablets. If the tablet structure is not easily adjustable, consider enabling automatic collection or manually collecting statistics for large tables during off-peak hours to avoid impacting business operations. In the Doris 3.x series, we will optimize for such scenarios.
+
diff --git a/docs/sql-manual/basic-element/sql-data-types/data-type-overview.md b/docs/sql-manual/basic-element/sql-data-types/data-type-overview.md
index 8937e8516bf..d2cbb092323 100644
--- a/docs/sql-manual/basic-element/sql-data-types/data-type-overview.md
+++ b/docs/sql-manual/basic-element/sql-data-types/data-type-overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Sql Data Types",
"language": "en",
- "description": "Doris supports the following numeric data types:"
+ "description": "Doris supports the following numeric data types:",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
## Numeric Types
Doris supports the following numeric data types:
@@ -98,3 +101,4 @@ IP data types store IP addresses in a binary format, which is faster and more sp
- **[IPv4](../sql-data-types/ip/IPV4.md)**: It stores IPv4 addresses as a 4-byte binary value. It is used in conjunction with the `ipv4_*` family of functions.
- **[IPv6](../sql-data-types/ip/IPV6.md)**: It stores IPv6 addresses as a 16-byte binary value. It is used in conjunction with the `ipv6_*` family of functions.
+
diff --git a/docs/sql-manual/basic-element/sql-data-types/date-time/DATE.md b/docs/sql-manual/basic-element/sql-data-types/date-time/DATE.md
index 0096dddb1ae..8e65a0eafc9 100644
--- a/docs/sql-manual/basic-element/sql-data-types/date-time/DATE.md
+++ b/docs/sql-manual/basic-element/sql-data-types/date-time/DATE.md
@@ -1,11 +1,14 @@
---
{
- "title": "DATE",
+ "title": "DATE | Date Time",
"language": "en",
- "description": "DATE type stores dates, with a value range of [0000-01-01, 9999-12-31], and the default output format is 'yyyy-MM-dd'."
+ "description": "DATE type stores dates, with a value range of [0000-01-01, 9999-12-31], and the default output format is 'yyyy-MM-dd'.",
+ "sidebar_label": "DATE"
}
---
+# DATE
+
## Description
DATE type stores dates, with a value range of `[0000-01-01, 9999-12-31]`, and the default output format is 'yyyy-MM-dd'.
@@ -45,3 +48,4 @@ select cast('0120-02-29' as date);
| 0120-02-29 |
+----------------------------+
```
+
diff --git a/docs/sql-manual/basic-element/sql-data-types/date-time/TIME.md b/docs/sql-manual/basic-element/sql-data-types/date-time/TIME.md
index 01d15c210f6..a4908fa355d 100644
--- a/docs/sql-manual/basic-element/sql-data-types/date-time/TIME.md
+++ b/docs/sql-manual/basic-element/sql-data-types/date-time/TIME.md
@@ -1,11 +1,14 @@
---
{
- "title": "TIME",
+ "title": "TIME | Date Time",
"language": "en",
- "description": "The TIME(p) type stores time, where p is the precision, with the range of values for p being [0, 6], and the default value is 0. That is,"
+ "description": "The TIME(p) type stores time, where p is the precision, with the range of values for p being [0, 6], and the default value is 0. That is,",
+ "sidebar_label": "TIME"
}
---
+# TIME
+
## Description
The TIME(p) type stores time, where p is the precision, with the range of values for p being `[0, 6]`, and the default value is 0. That is, TIME is equivalent to TIME(0).
@@ -43,3 +46,4 @@ select cast('838:59:59.999999' as time(6));
| 838:59:59.999999 |
+-------------------------------------+
```
+
diff --git a/docs/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md b/docs/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
index 8ccd38b7806..4e9d4dd6cc1 100644
--- a/docs/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
+++ b/docs/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
@@ -1,8 +1,9 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Semi Structured",
"language": "en",
- "description": "The ARRAY<T> type is used to represent an ordered collection of elements, where each element has the same data type. For example,"
+ "description": "The ARRAY<T> type is used to represent an ordered collection of elements, where each element has the same data type. For example,",
+ "sidebar_label": "ARRAY"
}
---
@@ -326,3 +327,4 @@ select array(null) < array(-1), array(null) > array(-1);
| 3 | [7, 8, 9] |
+------+--------------+
```
+
diff --git a/docs/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md b/docs/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
index 1c4a66d4f48..cc4f4b933eb 100644
--- a/docs/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
+++ b/docs/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
@@ -1,11 +1,14 @@
---
{
- "title": "JSON",
+ "title": "JSON | Semi Structured",
"language": "en",
- "description": "JSON (JavaScript Object Notation) is an open standard file format and data interchange format that uses human-readable text to store and transmit "
+ "description": "JSON (JavaScript Object Notation) is an open standard file format and data interchange format that uses human-readable text to store and transmit ",
+ "sidebar_label": "JSON"
}
---
+# JSON
+
## JSON Introduction
JSON (JavaScript Object Notation) is an open standard file format and data interchange format that uses human-readable text to store and transmit data. According to the official specification [RFC7159](https://datatracker.ietf.org/doc/html/rfc7159), JSON supports the following basic types:
@@ -1227,3 +1230,4 @@ The `GET_JSON_XXX` functions are designed for use on string types — they extra
### keywords
JSONB, JSON, json_parse, json_parse_error_to_null, json_parse_error_to_value, json_extract, json_extract_isnull, json_extract_bool, json_extract_int, json_extract_bigint, json_extract_double, json_extract_string, json_exists_path, json_type
+
diff --git a/docs/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md b/docs/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
index a79ad6e1bab..f110dcd1307 100644
--- a/docs/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
+++ b/docs/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Semi Structured",
"language": "en",
- "description": "```SQL SELECT MAP('Alice', 21, 'Bob', 23);"
+ "description": "```SQL SELECT MAP('Alice', 21, 'Bob', 23);",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
## Type Description
- The `MAP<key_type, value_type>` type is used to represent a composite type of key-value pairs, where each key uniquely corresponds to a value.
@@ -218,3 +221,4 @@
+---------------------+------------------------------+------+-------+---------+-------+
```
+
diff --git a/docs/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md b/docs/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
index f9e4de0b279..14c11118f47 100644
--- a/docs/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
+++ b/docs/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Semi Structured",
"language": "en",
- "description": "The STRUCT type is used to combine multiple fields into a single structure, where each field can have its own name and type,"
+ "description": "The STRUCT type is used to combine multiple fields into a single structure, where each field can have its own name and type,",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
## Type Description
The STRUCT type is used to combine multiple fields into a single structure, where each field can have its own name and type, suitable for representing nested or complex business data structures.
@@ -222,4 +225,4 @@ CREATE TABLE struct_table (
| k | int | No | true | NULL | |
| struct_varchar | struct<name:varchar(10),age:int,id:int> | Yes | false | NULL | NONE |
+----------------+-----------------------------------------+------+-------+---------+-------+
-```
\ No newline at end of file
+```
diff --git a/docs/sql-manual/basic-element/sql-data-types/semi-structured/semi-structured-overview.md b/docs/sql-manual/basic-element/sql-data-types/semi-structured/semi-structured-overview.md
index ecce17ecd3b..e8f758a6bd0 100644
--- a/docs/sql-manual/basic-element/sql-data-types/semi-structured/semi-structured-overview.md
+++ b/docs/sql-manual/basic-element/sql-data-types/semi-structured/semi-structured-overview.md
@@ -1,8 +1,11 @@
---
{
- "title": "Overview",
+ "title": "Overview | Semi Structured",
"language": "en",
- "draft": true
+ "draft": true,
+ "sidebar_label": "Overview"
}
---
+# Overview
+
diff --git a/docs/sql-manual/basic-element/sql-data-types/string-type/CHAR.md b/docs/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
index 8675a8096f4..5874346d705 100644
--- a/docs/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
+++ b/docs/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
@@ -1,11 +1,14 @@
---
{
- "title": "CHAR",
+ "title": "CHAR | String Type",
"language": "en",
- "description": "CHAR(M) A fixed-length string, M represents the byte length of a fixed-length string. The range of M is 1-255."
+ "description": "CHAR(M) A fixed-length string, M represents the byte length of a fixed-length string. The range of M is 1-255.",
+ "sidebar_label": "CHAR"
}
---
+# CHAR
+
## CHAR
### Description
CHAR(M)
@@ -13,3 +16,4 @@ A fixed-length string, M represents the byte length of a fixed-length string. Th
### keywords
CHAR
+
diff --git a/docs/sql-manual/sql-functions/ai-functions/overview.md b/docs/sql-manual/sql-functions/ai-functions/overview.md
index ad6cae65c62..40828b156f8 100644
--- a/docs/sql-manual/sql-functions/ai-functions/overview.md
+++ b/docs/sql-manual/sql-functions/ai-functions/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Ai Functions",
"language": "en",
- "description": "AI Function is a built-in function provided by Doris based on Artificial Intelligence (AI) capabilities."
+ "description": "AI Function is a built-in function provided by Doris based on Artificial Intelligence (AI) capabilities.",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
@@ -158,3 +161,4 @@ SELECT AI_SENTIMENT('Apache Doris is a great DBMS.');
```
For detailed function and usage, please refer to the documentation of each specific function.
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/array-functions/array.md b/docs/sql-manual/sql-functions/scalar-functions/array-functions/array.md
index efccad475f6..353b6f00b7d 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/array-functions/array.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/array-functions/array.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Array Functions",
"language": "en-US",
- "description": "Creates an array. The function accepts zero or more parameters and returns an array containing all input elements."
+ "description": "Creates an array. The function accepts zero or more parameters and returns an array containing all input elements.",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
## array
<version since="2.0.0">
@@ -136,3 +139,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = Can not find the compatibility
### Keywords
ARRAY
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/bitwise-functions/xor.md b/docs/sql-manual/sql-functions/scalar-functions/bitwise-functions/xor.md
index 8267bb939a9..cdaf5def6da 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/bitwise-functions/xor.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/bitwise-functions/xor.md
@@ -1,11 +1,14 @@
---
{
- "title": "XOR",
+ "title": "XOR | Bitwise Functions",
"language": "zh-CN",
- "description": "Performs a bitwise XOR operation on two BOOLEAN values."
+ "description": "Performs a bitwise XOR operation on two BOOLEAN values.",
+ "sidebar_label": "XOR"
}
---
+# XOR
+
## Description
Performs a bitwise XOR operation on two BOOLEAN values.
@@ -44,3 +47,4 @@ Returns the XOR value of the two BOOLEAN values.
| NULL | NULL | NULL | NULL | NULL |
+---------------+---------------+----------------+----------------+---------------+
```
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md b/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
index 17a5a339f6e..c6f034e8561 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
@@ -1,11 +1,14 @@
---
{
- "title": "DATE",
+ "title": "DATE | Date Time Functions",
"language": "en",
- "description": "The DATE function is used to extract the pure date part from a datetime value (which includes both date and time), ignoring the time information."
+ "description": "The DATE function is used to extract the pure date part from a datetime value (which includes both date and time), ignoring the time information.",
+ "sidebar_label": "DATE"
}
---
+# DATE
+
## Description
The DATE function is used to extract the pure date part from a datetime value (which includes both date and time), ignoring the time information. This function can convert a DATETIME type into a DATE type, retaining only the year, month, and day information.
@@ -57,4 +60,4 @@ mysql> select date(NULL);
| NULL |
+------------+
-```
\ No newline at end of file
+```
diff --git a/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/time.md b/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/time.md
index 6d706dc7273..b40f20b8b03 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/time.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/time.md
@@ -1,11 +1,14 @@
---
{
- "title": "TIME",
+ "title": "TIME | Date Time Functions",
"language": "en",
- "description": "The TIME function get the Datetime value's time part."
+ "description": "The TIME function get the Datetime value's time part.",
+ "sidebar_label": "TIME"
}
---
+# TIME
+
## Description
The `TIME` function get the Datetime value's `time` part.
@@ -38,3 +41,4 @@ mysql>
| 12:12:12 |
+---------------------------+
```
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/timestamp.md b/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/timestamp.md
index eb6b5843fbd..64402b73348 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/timestamp.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/timestamp.md
@@ -1,11 +1,14 @@
---
{
- "title": "TIMESTAMP",
+ "title": "TIMESTAMP | Date Time Functions",
"language": "en",
- "description": "The TIMESTAMP function converts a datetime format string to DATETIME type."
+ "description": "The TIMESTAMP function converts a datetime format string to DATETIME type.",
+ "sidebar_label": "TIMESTAMP"
}
---
+# TIMESTAMP
+
## Description
The TIMESTAMP function converts a datetime format string to DATETIME type.
@@ -61,3 +64,4 @@ SELECT TIMESTAMP(NULL);
| NULL |
+-----------------+
```
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/to-iso8601.md b/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/to-iso8601.md
index 700685701f0..3b24b2bda1e 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/to-iso8601.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/date-time-functions/to-iso8601.md
@@ -1,11 +1,14 @@
---
{
- "title": "TO_ISO8601",
+ "title": "TO_ISO8601 | Date Time Functions",
"language": "en",
- "description": "Converts datetime values to ISO8601 formatted strings, supporting input types DATETIME and DATE."
+ "description": "Converts datetime values to ISO8601 formatted strings, supporting input types DATETIME and DATE.",
+ "sidebar_label": "TO_ISO8601"
}
---
+# TO_ISO8601
+
## Description
Converts datetime values to ISO8601 formatted strings, supporting input types DATETIME and DATE.
@@ -73,3 +76,4 @@ SELECT TO_ISO8601(NULL) AS null_input;
| NULL |
+------------+
```
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/ip-functions/inet-ntoa.md b/docs/sql-manual/sql-functions/scalar-functions/ip-functions/inet-ntoa.md
index dadf1c6543b..b350e67e651 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/ip-functions/inet-ntoa.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/ip-functions/inet-ntoa.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV4_NUM_TO_STRING",
+ "title": "IPV4_NUM_TO_STRING | Ip Functions",
"language": "en",
- "description": "Alias for ipv4numtostring."
+ "description": "Alias for ipv4numtostring.",
+ "sidebar_label": "IPV4_NUM_TO_STRING"
}
---
+# IPV4_NUM_TO_STRING
+
## inet_ntoa
Alias for `ipv4_num_to_string`.
@@ -87,3 +90,4 @@ select ipv4_num_to_string(4294967296);
INET_NTOA, IPV4_NUM_TO_STRING
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-aton.md b/docs/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-aton.md
index 041b6c5a3e7..305fb8ae420 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-aton.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-aton.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_STRING_TO_NUM_OR_NULL",
+ "title": "IPV6_STRING_TO_NUM_OR_NULL | Ip Functions",
"language": "en",
- "description": "Alias for ipv6stringtonumornull."
+ "description": "Alias for ipv6stringtonumornull.",
+ "sidebar_label": "IPV6_STRING_TO_NUM_OR_NULL"
}
---
+# IPV6_STRING_TO_NUM_OR_NULL
+
## inet6_aton
Alias for `ipv6_string_to_num_or_null`.
@@ -80,3 +83,4 @@ select hex(ipv6_string_to_num_or_null('notaaddress')) as invalid;
INET6_ATON, IPV6_STRING_TO_NUM_OR_NULL
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-ntoa.md b/docs/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-ntoa.md
index 10f1288fe20..a8470ed4c54 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-ntoa.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-ntoa.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_NUM_TO_STRING",
+ "title": "IPV6_NUM_TO_STRING | Ip Functions",
"language": "en",
- "description": "Alias for ipv6numtostring."
+ "description": "Alias for ipv6numtostring.",
+ "sidebar_label": "IPV6_NUM_TO_STRING"
}
---
+# IPV6_NUM_TO_STRING
+
## inet6_ntoa
Alias for `ipv6_num_to_string`.
@@ -69,3 +72,4 @@ select ipv6_num_to_string('-23vno12i34nlfwlsj') as invalid;
INET6_NTOA, IPV6_NUM_TO_STRING
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-num-to-string.md b/docs/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-num-to-string.md
index f3efbdf05e6..a98326ae061 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-num-to-string.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-num-to-string.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV4_NUM_TO_STRING",
+ "title": "IPV4_NUM_TO_STRING | Ip Functions",
"language": "en",
- "description": "Takes a Int16, Int32, Int64 number. Interprets it as an IPv4 address in big endian."
+ "description": "Takes a Int16, Int32, Int64 number. Interprets it as an IPv4 address in big endian.",
+ "sidebar_label": "IPV4_NUM_TO_STRING"
}
---
+# IPV4_NUM_TO_STRING
+
## Description
Takes a Int16, Int32, Int64 number. Interprets it as an IPv4 address in big endian. Returns a string containing the corresponding IPv4 address in the format A.B.C.D (dot-separated numbers in decimal form)
@@ -54,3 +57,4 @@ select num,ipv4_num_to_string(num) from ipv4_bi;
| 4294967296 | NULL |
+------------+---------------------------+
```
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-num-to-string.md b/docs/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-num-to-string.md
index 0a693d1dfe6..f8685edb74d 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-num-to-string.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-num-to-string.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_NUM_TO_STRING",
+ "title": "IPV6_NUM_TO_STRING | Ip Functions",
"language": "en",
- "description": "Takes an IPv6 address in binary format of type String. Returns the string of this address in text format."
+ "description": "Takes an IPv6 address in binary format of type String. Returns the string of this address in text format.",
+ "sidebar_label": "IPV6_NUM_TO_STRING"
}
---
+# IPV6_NUM_TO_STRING
+
## Description
Takes an IPv6 address in binary format of type String. Returns the string of this address in text format.
- The IPv4 address mapped by IPv6 starts with ::ffff:111.222.33.
@@ -38,4 +41,4 @@ select ipv6_num_to_string(unhex('2A0206B8000000000000000000000011')) as addr, ip
+--------------+------------------------------------------+
| 2a02:6b8::11 | NULL |
+--------------+------------------------------------------+
-```
\ No newline at end of file
+```
diff --git a/docs/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-string-to-num-or-null.md b/docs/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-string-to-num-or-null.md
index a0f6b419474..d12f4be9c55 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-string-to-num-or-null.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-string-to-num-or-null.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_STRING_TO_NUM_OR_NULL",
+ "title": "IPV6_STRING_TO_NUM_OR_NULL | Ip Functions",
"language": "en",
- "description": "The reverse function of IPv6NumToString, it takes an IP address String and returns an IPv6 address in binary format."
+ "description": "The reverse function of IPv6NumToString, it takes an IP address String and returns an IPv6 address in binary format.",
+ "sidebar_label": "IPV6_STRING_TO_NUM_OR_NULL"
}
---
+# IPV6_STRING_TO_NUM_OR_NULL
+
## Description
The reverse function of IPv6NumToString, it takes an IP address String and returns an IPv6 address in binary format.
@@ -39,3 +42,4 @@ select hex(ipv6_string_to_num_or_null('1111::ffff')) as r1, hex(ipv6_string_to_n
| 1111000000000000000000000000FFFF | 00000000000000000000FFFFC0A80001 | NULL |
+----------------------------------+----------------------------------+------+
```
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/map-functions/map.md b/docs/sql-manual/sql-functions/scalar-functions/map-functions/map.md
index 692b00490bd..2d409102e92 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/map-functions/map.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/map-functions/map.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Map Functions",
"language": "en",
- "description": "Constructs a MAP<K, V> of a specific type using several groups of key-value pairs"
+ "description": "Constructs a MAP<K, V> of a specific type using several groups of key-value pairs",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
## Description
Constructs a [`MAP<K, V>`](../../../basic-element/sql-data-types/semi-structured/MAP.md) of a specific type using several groups of key-value pairs
@@ -77,4 +80,4 @@ Returns a specific type `MAP<K, V>` constructed from several groups of key-value
+--------------------------------------------------------+
| {2:"11", 1:"3", null:"null 2"} |
+--------------------------------------------------------+
- ```
\ No newline at end of file
+ ```
diff --git a/docs/sql-manual/sql-functions/scalar-functions/numeric-functions/xor.md b/docs/sql-manual/sql-functions/scalar-functions/numeric-functions/xor.md
index 8b121b0541c..c06787546ae 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/numeric-functions/xor.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/numeric-functions/xor.md
@@ -1,11 +1,14 @@
---
{
- "title": "XOR",
+ "title": "XOR | Numeric Functions",
"language": "en",
- "description": "Return the XOR value of two numbers."
+ "description": "Return the XOR value of two numbers.",
+ "sidebar_label": "XOR"
}
---
+# XOR
+
## Description
Return the XOR value of two numbers.
@@ -27,3 +30,4 @@ mysql >select true xor false,true xor true;
## Keywords
XOR
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/string-functions/char.md b/docs/sql-manual/sql-functions/scalar-functions/string-functions/char.md
index 580092ae1b5..9bb914a3596 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/string-functions/char.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/string-functions/char.md
@@ -1,11 +1,14 @@
---
{
- "title": "CHAR",
+ "title": "CHAR | String Functions",
"language": "en",
- "description": "The CHAR function interprets each argument as an integer and returns a string consisting of the characters represented by those integer code values."
+ "description": "The CHAR function interprets each argument as an integer and returns a string consisting of the characters represented by those integer code values.",
+ "sidebar_label": "CHAR"
}
---
+# CHAR
+
## Description
The CHAR function interprets each argument as an integer and returns a string consisting of the characters represented by those integer code values.
@@ -80,3 +83,4 @@ SELECT CHAR(NULL);
| |
+------------+
```
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/string-functions/date.md b/docs/sql-manual/sql-functions/scalar-functions/string-functions/date.md
index d1a778b40a5..b02c71d7807 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/string-functions/date.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/string-functions/date.md
@@ -1,11 +1,14 @@
---
{
- "title": "DATE",
+ "title": "DATE | String Functions",
"language": "en",
- "description": "Extracts the date from the datetime."
+ "description": "Extracts the date from the datetime.",
+ "sidebar_label": "DATE"
}
---
+# DATE
+
## Description
Extracts the date from the datetime.
@@ -38,4 +41,4 @@ select date('2010-12-02 19:28:30');
+----------------------------------------------------+
| 2010-12-02 |
+----------------------------------------------------+
-```
\ No newline at end of file
+```
diff --git a/docs/sql-manual/sql-functions/scalar-functions/string-functions/timestamp.md b/docs/sql-manual/sql-functions/scalar-functions/string-functions/timestamp.md
index e01f95a6425..97ba218a117 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/string-functions/timestamp.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/string-functions/timestamp.md
@@ -1,8 +1,11 @@
---
{
- "title": "TIMESTAMP",
+ "title": "TIMESTAMP | String Functions",
"language": "zh-CN",
- "draft": true
+ "draft": true,
+ "sidebar_label": "TIMESTAMP"
}
---
+# TIMESTAMP
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/string-functions/to-iso8601.md b/docs/sql-manual/sql-functions/scalar-functions/string-functions/to-iso8601.md
index e2dc79aa362..c9139e1a8be 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/string-functions/to-iso8601.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/string-functions/to-iso8601.md
@@ -1,8 +1,11 @@
---
{
- "title": "TO_ISO8601",
+ "title": "TO_ISO8601 | String Functions",
"language": "zh-CN",
- "draft": true
+ "draft": true,
+ "sidebar_label": "TO_ISO8601"
}
---
+# TO_ISO8601
+
diff --git a/docs/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md b/docs/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
index 687fc724049..e6a6d4cd172 100644
--- a/docs/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
+++ b/docs/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Struct Functions",
"language": "en-US",
- "description": "Constructs and returns a struct based on given values. The function accepts one or more parameters and returns a struct containing all input elements."
+ "description": "Constructs and returns a struct based on given values. The function accepts one or more parameters and returns a struct containing all input elements.",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
## Description
Constructs and returns a struct based on given values. The function accepts one or more parameters and returns a struct containing all input elements.
@@ -93,3 +96,4 @@ Creating empty struct will report error, at least one parameter is required, con
select struct();
ERROR 1105 (HY000): errCode = 2, detailMessage = struct requires at least one argument, like: struct(1)
```
+
diff --git a/docs/sql-manual/sql-functions/table-valued-functions/hdfs.md b/docs/sql-manual/sql-functions/table-valued-functions/hdfs.md
index 58f044c40e6..4d69c673bf4 100644
--- a/docs/sql-manual/sql-functions/table-valued-functions/hdfs.md
+++ b/docs/sql-manual/sql-functions/table-valued-functions/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "LOCAL",
+ "title": "LOCAL | Table Valued Functions",
"language": "en",
- "description": "Local table-valued-function(tvf), allows users to read and access local file contents on be node, just like accessing relational table."
+ "description": "Local table-valued-function(tvf), allows users to read and access local file contents on be node, just like accessing relational table.",
+ "sidebar_label": "LOCAL"
}
---
+# LOCAL
+
## Description
Local table-valued-function(tvf), allows users to read and access local file contents on be node, just like accessing relational table. Currently supports `csv/csv_with_names/csv_with_names_and_types/json/parquet/orc` file format.
@@ -139,4 +142,4 @@ desc function local(
| c2 | TEXT | Yes | false | NULL | NONE |
| c3 | TEXT | Yes | false | NULL | NONE |
+-------+------+------+-------+---------+-------+
-```
\ No newline at end of file
+```
diff --git a/docs/sql-manual/sql-functions/table-valued-functions/local.md b/docs/sql-manual/sql-functions/table-valued-functions/local.md
index 58f044c40e6..4d69c673bf4 100644
--- a/docs/sql-manual/sql-functions/table-valued-functions/local.md
+++ b/docs/sql-manual/sql-functions/table-valued-functions/local.md
@@ -1,11 +1,14 @@
---
{
- "title": "LOCAL",
+ "title": "LOCAL | Table Valued Functions",
"language": "en",
- "description": "Local table-valued-function(tvf), allows users to read and access local file contents on be node, just like accessing relational table."
+ "description": "Local table-valued-function(tvf), allows users to read and access local file contents on be node, just like accessing relational table.",
+ "sidebar_label": "LOCAL"
}
---
+# LOCAL
+
## Description
Local table-valued-function(tvf), allows users to read and access local file contents on be node, just like accessing relational table. Currently supports `csv/csv_with_names/csv_with_names_and_types/json/parquet/orc` file format.
@@ -139,4 +142,4 @@ desc function local(
| c2 | TEXT | Yes | false | NULL | NONE |
| c3 | TEXT | Yes | false | NULL | NONE |
+-------+------+------+-------+---------+-------+
-```
\ No newline at end of file
+```
diff --git a/docs/sql-manual/sql-functions/table-valued-functions/s3.md b/docs/sql-manual/sql-functions/table-valued-functions/s3.md
index 3a3d034d495..07a2ceac3be 100644
--- a/docs/sql-manual/sql-functions/table-valued-functions/s3.md
+++ b/docs/sql-manual/sql-functions/table-valued-functions/s3.md
@@ -1,11 +1,14 @@
---
{
- "title": "S3",
- "language": "en",
- "description": "The S3 table-valued function (TVF) allows users to read and access files stored on S3-compatible object storage as if accessing relational table-formatted data. Currently supports `csv/csv_with_names/csv_with_names_and_types/json/parquet/orc` file formats."
+ "title": "S3 | Table Valued Functions",
+ "language": "en",
+ "description": "The S3 table-valued function (TVF) allows users to read and access files stored on S3-compatible object storage as if accessing relational table-formatted data. Currently supports `csv/csv_with_names/csv_with_names_and_types/json/parquet/orc` file formats.",
+ "sidebar_label": "S3"
}
---
+# S3
+
## Description
The S3 table-valued function (TVF) allows users to read and access files stored on S3-compatible object storage as if accessing relational table-formatted data. Currently supports `csv/csv_with_names/csv_with_names_and_types/json/parquet/orc` file formats.
@@ -592,3 +595,4 @@ S3(
"read_json_by_line" = "true",
"use_path_style" = "true");
```
+
diff --git a/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-GROUP.md b/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-GROUP.md
index 6caf4bae89a..464f7dd67ee 100644
--- a/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-GROUP.md
+++ b/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-GROUP.md
@@ -1,11 +1,14 @@
---
{
- "title": "CREATE WORKLOAD GROUP",
+ "title": "CREATE WORKLOAD GROUP | Compute Management",
"language": "en",
- "description": "This statement is used to create a workload group. Workload groups enable the isolation of cpu resources and memory resources on a single be."
+ "description": "This statement is used to create a workload group. Workload groups enable the isolation of cpu resources and memory resources on a single be.",
+ "sidebar_label": "CREATE WORKLOAD GROUP"
}
---
+# CREATE WORKLOAD GROUP
+
## Description
This statement is used to create a workload group. Workload groups enable the isolation of cpu resources and memory resources on a single be.
@@ -37,4 +40,4 @@ PROPERTIES (
"max_cpu_percent"="10%",
"max_memory_percent"="30%"
);
- ```
\ No newline at end of file
+ ```
diff --git a/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-POLICY.md b/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-POLICY.md
index a82450fd8b6..72674d56f15 100644
--- a/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-POLICY.md
+++ b/docs/sql-manual/sql-statements/cluster-management/compute-management/CREATE-WORKLOAD-POLICY.md
@@ -1,11 +1,14 @@
---
{
- "title": "CREATE WORKLOAD GROUP",
+ "title": "CREATE WORKLOAD GROUP | Compute Management",
"language": "en",
- "description": "This statement is used to create a workload group. Workload groups enable the isolation of cpu resources and memory resources on a single be."
+ "description": "This statement is used to create a workload group. Workload groups enable the isolation of cpu resources and memory resources on a single be.",
+ "sidebar_label": "CREATE WORKLOAD GROUP"
}
---
+# CREATE WORKLOAD GROUP
+
## Description
This statement is used to create a workload group. Workload groups enable the isolation of cpu resources and memory resources on a single be.
@@ -48,3 +51,4 @@ CREATE, WORKLOAD, GROUP
+
diff --git a/docs/sql-manual/sql-statements/data-modification/load-and-export/EXPORT.md b/docs/sql-manual/sql-statements/data-modification/load-and-export/EXPORT.md
index e5ebc209abc..b461286e855 100644
--- a/docs/sql-manual/sql-statements/data-modification/load-and-export/EXPORT.md
+++ b/docs/sql-manual/sql-statements/data-modification/load-and-export/EXPORT.md
@@ -1,11 +1,14 @@
---
{
- "title": "EXPORT",
+ "title": "EXPORT | Load And Export",
"language": "en",
- "description": "The EXPORT command is used to export data from a specified table to files at a specified location."
+ "description": "The EXPORT command is used to export data from a specified table to files at a specified location.",
+ "sidebar_label": "EXPORT"
}
---
+# EXPORT
+
## Description
The `EXPORT` command is used to export data from a specified table to files at a specified location. Currently supports exporting to remote storage such as HDFS, S3, BOS, COS (Tencent Cloud) through Broker processes, S3 protocol, or HDFS protocol.
@@ -381,4 +384,4 @@ WITH BROKER "broker_name"
"username"="xxx",
"password"="yyy"
)
-```
\ No newline at end of file
+```
diff --git a/docs/table-design/best-practice.md b/docs/table-design/best-practice.md
index 1a7161a679c..3a70c2b72ab 100644
--- a/docs/table-design/best-practice.md
+++ b/docs/table-design/best-practice.md
@@ -1,8 +1,9 @@
---
{
- "title": "Best Practices",
+ "title": "Best Practices | Table Design",
"language": "en",
- "description": "When only the sorting columns are specified, rows with the same key will not be merged."
+ "description": "When only the sorting columns are specified, rows with the same key will not be merged.",
+ "sidebar_label": "Best Practices"
}
---
@@ -448,3 +449,4 @@ show partitions from tbl_unique_merge_on_write_p;
```
:::
+
diff --git a/docs/table-design/index/inverted-index.md b/docs/table-design/index/inverted-index.md
index 9688c305760..859214bf37c 100644
--- a/docs/table-design/index/inverted-index.md
+++ b/docs/table-design/index/inverted-index.md
@@ -1,11 +1,14 @@
---
{
- "title": "Inverted Index",
+ "title": "Inverted Index | Index",
"language": "en",
- "description": "Inverted Index is a commonly used indexing technique in the field of information retrieval."
+ "description": "Inverted Index is a commonly used indexing technique in the field of information retrieval.",
+ "sidebar_label": "Inverted Index"
}
---
+# Inverted Index
+
## Indexing Principle
[Inverted Index](https://en.wikipedia.org/wiki/Inverted_index) is a commonly used indexing technique in the field of information retrieval. It divides text into individual words and constructs a word -> document IDs index, allowing for quick searches to determine which documents contain a specific word.
@@ -667,3 +670,4 @@ SELECT count() FROM hackernews_1m WHERE author = 'faster';
+---------+
```
+
diff --git a/docs/table-design/index/inverted-index/overview.md b/docs/table-design/index/inverted-index/overview.md
index 6212e9e253f..31017f129f0 100644
--- a/docs/table-design/index/inverted-index/overview.md
+++ b/docs/table-design/index/inverted-index/overview.md
@@ -1,12 +1,14 @@
---
{
- "title": "Inverted Index",
+ "title": "Inverted Index | Inverted Index",
"sidebar_label": "Overview",
"language": "en",
"description": "Inverted Index is a commonly used indexing technique in the field of information retrieval."
}
---
+# Inverted Index
+
## Indexing Principle
[Inverted Index](https://en.wikipedia.org/wiki/Inverted_index) is a commonly used indexing technique in the field of information retrieval. It divides text into individual words and constructs a word -> document IDs index, allowing for quick searches to determine which documents contain a specific word.
@@ -751,3 +753,4 @@ SELECT count() FROM hackernews_1m WHERE author = 'faster';
| 20 |
+---------+
```
+
diff --git a/docs/table-design/overview.md b/docs/table-design/overview.md
index da4f29ea3b3..fd3fa79f241 100644
--- a/docs/table-design/overview.md
+++ b/docs/table-design/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Table Design",
"language": "en",
- "description": "Users can use the CREATE TABLE statement to create a table in Doris."
+ "description": "Users can use the CREATE TABLE statement to create a table in Doris.",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
## Creating tables
Users can use the [CREATE TABLE](../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE) statement to create a table in Doris. You can also use the [CREATE TABLE LIKE](../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE#create-table--like) or [CREATE TABLE AS](../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE#create-table--as-select-also-referred-to-as-ctas) clause to derive the table definition from another table.
@@ -37,3 +40,4 @@ These properties apply to partitions, meaning that once a partition is created,
3. **Column addition operations**: Adding or removing VALUE columns is a lightweight operation that can be completed in seconds. Adding or removing KEY columns or modifying data types is a heavyweight operation, and the completion time depends on the amount of data. For large datasets, it is recommended to avoid adding or removing KEY columns or modifying data types.
4. **Optimize storage strategy**: You can use tiered storage to store cold data on HDD or S3/HDFS.
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/fe-config-template.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/fe-config-template.md
index 42689c0ba21..5c8c5ed5826 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/fe-config-template.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/fe-config-template.md
@@ -1,10 +1,11 @@
---
{
- "title": "FE 配置项",
+ "title": "FE 配置项 | Config",
"language": "zh-CN",
"toc_min_heading_level": 2,
"toc_max_heading_level": 4,
- "description": "该文档主要介绍 FE 的相关配置项。"
+ "description": "该文档主要介绍 FE 的相关配置项。",
+ "sidebar_label": "FE 配置项"
}
---
@@ -118,3 +119,4 @@ FE 的配置项有两种方式进行配置：
> 如需修改，请修改 `fe/fe-common/src/main/java/org/apache/doris/common/Config.java` 中的描述信息。
<--DOC_PLACEHOLDER-->
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/fe-config.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/fe-config.md
index 1ce7e8f9bfc..1046d34cc14 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/fe-config.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/fe-config.md
@@ -1,10 +1,11 @@
---
{
- "title": "FE 配置项",
+ "title": "FE 配置项 | Config",
"language": "zh-CN",
"toc_min_heading_level": 2,
"toc_max_heading_level": 4,
- "description": "该文档主要介绍 FE 的相关配置项。"
+ "description": "该文档主要介绍 FE 的相关配置项。",
+ "sidebar_label": "FE 配置项"
}
---
@@ -2774,3 +2775,4 @@ Doris 为了兼用 mysql 周边工具生态，会内置一个名为 mysql 的数
默认值： ""
Meta Service 的端点应以 'host1:port,host2:port' 的格式指定。此配置对于存储和计算分离模式是必要的。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/meta-info-action-V2.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/meta-info-action-V2.md
index 09963040bf6..2bd99841252 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/meta-info-action-V2.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/meta-info-action-V2.md
@@ -1,11 +1,14 @@
---
{
- "title": "Meta Info Action",
+ "title": "Meta Info Action | Fe Http",
"language": "zh-CN",
- "description": "获取集群内的元数据信息，包括数据库列表、表列表以及表结构等。"
+ "description": "获取集群内的元数据信息，包括数据库列表、表列表以及表结构等。",
+ "sidebar_label": "Meta Info Action"
}
---
+# Meta Info Action
+
## Request
`GET /api/meta/namespaces/<ns>/databases`
@@ -50,3 +53,4 @@
"count":0
}
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/meta-info-action.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/meta-info-action.md
index d9c622d3cec..4e477f2f180 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/meta-info-action.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/meta-info-action.md
@@ -1,11 +1,14 @@
---
{
- "title": "Meta Info Action",
+ "title": "Meta Info Action | Fe Http",
"language": "zh-CN",
- "description": "Meta Info Action 用于获取集群内的元数据信息。如数据库列表，表结构等。"
+ "description": "Meta Info Action 用于获取集群内的元数据信息。如数据库列表，表结构等。",
+ "sidebar_label": "Meta Info Action"
}
---
+# Meta Info Action
+
Meta Info Action 用于获取集群内的元数据信息。如数据库列表，表结构等。
## 数据库列表
@@ -210,3 +213,4 @@ GET /api/meta/namespaces/default/databases/db1/tables/tbl1/schema?with_mv?=1
```
* data 字段返回 base 表或 rollup 表的表结构信息。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/query-profile-action-controller.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/query-profile-action-controller.md
index 368412b2cd3..ee60a32ebd1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/query-profile-action-controller.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/query-profile-action-controller.md
@@ -1,11 +1,14 @@
---
{
- "title": "Query Profile Action",
+ "title": "Query Profile Action | Fe Http",
"language": "zh-CN",
- "description": "Query Profile Action 用于获取 Query 的 profile"
+ "description": "Query Profile Action 用于获取 Query 的 profile",
+ "sidebar_label": "Query Profile Action"
}
---
+# Query Profile Action
+
## Request
```
@@ -85,4 +88,4 @@ Query Profile Action 用于获取 Query 的 profile
}
```
- `data` is the text content of the profile.
\ No newline at end of file
+ `data` is the text content of the profile.
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/query-profile-action.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/query-profile-action.md
index 2a90b30884c..f1f8ecd46e4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/query-profile-action.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/open-api/fe-http/query-profile-action.md
@@ -1,11 +1,14 @@
---
{
- "title": "Query Profile Action",
+ "title": "Query Profile Action | Fe Http",
"language": "zh-CN",
- "description": "GET /rest/v2/manager/query/statistics/{traceid} (4.0.0+)"
+ "description": "Doris FE Query Profile REST API 文档，支持通过 HTTP 接口获取查询信息、执行 Profile、实时统计数据，并对正在运行的查询进行监控与控制。",
+ "sidebar_label": "Query Profile Action"
}
---
+# Query Profile Action
+
## Request
`GET /rest/v2/manager/query/query_info`
@@ -498,3 +501,4 @@ Admin 和 Root 用户可以查看所有 Query。普通用户仅能查看自己
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/system-tables/information_schema/column_statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/system-tables/information_schema/column_statistics.md
index e4c88305642..bfc4a3b1fd0 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/system-tables/information_schema/column_statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/system-tables/information_schema/column_statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "column_statistics",
+ "title": "column_statistics | Information Schema",
"language": "zh-CN",
- "description": "此表仅用于兼容 MySQL 行为，永远为空。并不能真实反映 Doris 内数据的统计信息。如需查看 Doris 收集的统计信息，请查看统计信息章节。"
+ "description": "此表仅用于兼容 MySQL 行为，永远为空。并不能真实反映 Doris 内数据的统计信息。如需查看 Doris 收集的统计信息，请查看统计信息章节。",
+ "sidebar_label": "column_statistics"
}
---
+# column_statistics
+
## 概述
此表仅用于兼容 MySQL 行为，永远为空。并不能真实反映 Doris 内数据的统计信息。如需查看 Doris 收集的统计信息，请[查看统计信息章节](../../../query-acceleration/optimization-technology-principle/statistics#查看统计信息)。
@@ -23,4 +26,4 @@
| SCHEMA_NAME | varchar(64) | |
| TABLE_NAME | varchar(64) | |
| COLUMN_NAME | varchar(64) | |
-| HISTOGRAM | json | |
\ No newline at end of file
+| HISTOGRAM | json | |
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/system-tables/internal_schema/column_statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/system-tables/internal_schema/column_statistics.md
index 439989fa288..6c2c8f2d9bc 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/system-tables/internal_schema/column_statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/system-tables/internal_schema/column_statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "column_statistics",
+ "title": "column_statistics | Internal Schema",
"language": "zh-CN",
- "description": "列统计信息"
+ "description": "列统计信息",
+ "sidebar_label": "column_statistics"
}
---
+# column_statistics
+
## 概述
列统计信息
@@ -33,4 +36,4 @@
| min | varchar(65533) | 最小值 |
| max | varchar(65533) | 最大值 |
| data_size_in_bytes | bigint | 以字节计算的数据量 |
-| update_time | datetime | 当前统计信息的更新时间 |
\ No newline at end of file
+| update_time | datetime | 当前统计信息的更新时间 |
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/system-tables/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/system-tables/overview.md
index 4941656a8ba..0c00235ee62 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/system-tables/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/system-tables/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "概述",
+ "title": "概述 | System Tables",
"language": "zh-CN",
- "description": "Doris 集群内置多个系统数据库，用于存储 Doris 系统本身的一些元数据信息。"
+ "description": "Doris 集群内置多个系统数据库，用于存储 Doris 系统本身的一些元数据信息。",
+ "sidebar_label": "概述"
}
---
+# 概述
+
Doris 集群内置多个系统数据库，用于存储 Doris 系统本身的一些元数据信息。
## information_schema
@@ -35,3 +38,4 @@ Doris 会在集群创建时，自动创建这个库下的所有系统表。
默认情况下，普通用户对这个库下的表拥有只读权限。但被授权后，可以对这个库下的表进行修改、删除或创建。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/overview.md
index b85e9af9c9a..e42117b0237 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "概述",
+ "title": "概述 | Memory Management",
"language": "zh-CN",
- "description": "内存管理是 Doris 中最重要的组成部分之一，在 Doris 运行过程中，不论导入还是查询都依赖大量的内存操作。内存管理的好坏直接影响到 Doris 的稳定性和性能。"
+ "description": "内存管理是 Doris 中最重要的组成部分之一，在 Doris 运行过程中，不论导入还是查询都依赖大量的内存操作。内存管理的好坏直接影响到 Doris 的稳定性和性能。",
+ "sidebar_label": "概述"
}
---
+# 概述
+
内存管理是 Doris 中最重要的组成部分之一，在 Doris 运行过程中，不论导入还是查询都依赖大量的内存操作。内存管理的好坏直接影响到 Doris 的稳定性和性能。
Apache Doris 作为基于 MPP 架构的 OLAP 数据库，数据从磁盘加载到内存后，会在算子间流式传递并计算，在内存中存储计算的中间结果，这种方式减少了频繁的磁盘 I/O 操作，充分利用多机多核的并行计算能力，可在性能上呈现巨大优势。
@@ -143,3 +146,4 @@ Doris BE Process Memory
## 内存控制策略
参考 [内存控制策略](./memory-feature/memory-control-strategy.md) 中对内存分配、监控、回收的介绍，它们保证了 Doris BE 进程内存的高效可控。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/export/export-best-practice.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/export/export-best-practice.md
index e7a5982042a..cca825026e4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/export/export-best-practice.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/export/export-best-practice.md
@@ -1,11 +1,14 @@
---
{
- "title": "最佳实践",
+ "title": "最佳实践 | Export",
"language": "zh-CN",
- "description": "本文档主要用于介绍在进行数据导出操作中，如何判断资源利用是否合理，以及如何调整资源利用率已达到更好的数据导出效率。"
+ "description": "本文档主要用于介绍在进行数据导出操作中，如何判断资源利用是否合理，以及如何调整资源利用率已达到更好的数据导出效率。",
+ "sidebar_label": "最佳实践"
}
---
+# 最佳实践
+
本文档主要用于介绍在进行数据导出操作中，如何判断资源利用是否合理，以及如何调整资源利用率已达到更好的数据导出效率。
## SELECT INTO OUTFILE
@@ -95,3 +98,4 @@
FE 配置参数，表示当前集群能够同时运行的 Export Task 的数量，默认是是 64。一个 Export Job 会根据并发度拆分成多个 Export Task。所有 Export Task 共享这个阈值。如果希望提升集群整体的可并发执行导出任务的数量，可以调大这个参数，并重启 FE 节点。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/array.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/array.md
index 0aedadbb036..642b65fa333 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/array.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/array.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Complex Types",
"language": "zh-CN",
- "description": "ARRAY<T> 表示由 T 类型元素组成的数组。点击 ARRAY 数据类型 了解具体信息。"
+ "description": "ARRAY<T> 表示由 T 类型元素组成的数组。点击 ARRAY 数据类型 了解具体信息。",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
`ARRAY<T>` 表示由 T 类型元素组成的数组。点击 [ARRAY 数据类型](../../../sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md) 了解具体信息。
## CSV 格式导入
@@ -117,3 +120,4 @@ mysql> SELECT * FROM array_test;
+------+-----------------+
4 rows in set (0.01 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/json.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/json.md
index f3954a3cdfb..b280abc0329 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/json.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/json.md
@@ -1,11 +1,14 @@
---
{
- "title": "JSON",
+ "title": "JSON | Complex Types",
"language": "zh-CN",
- "description": "JSON 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。"
+ "description": "JSON 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。",
+ "sidebar_label": "JSON"
}
---
+# JSON
+
`JSON` 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。
默认支持 1048576 字节（1 MB），可调大到 2147483643 字节（2 GB），可通过 BE 配置`string_type_length_soft_limit_bytes` 调整。
@@ -132,3 +135,4 @@ mysql> SELECT * FROM json_test;
+------+-------------------------------+
5 rows in set (0.01 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/map.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/map.md
index 5749cf65fc0..d46a1c6f210 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/map.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/map.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Complex Types",
"language": "zh-CN",
- "description": "MAP<K, V> 表示由K,V类型元素组成的MAP。 点击MAP 数据类型 了解具体信息。"
+ "description": "MAP<K, V> 表示由K,V类型元素组成的MAP。 点击MAP 数据类型 了解具体信息。",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
`MAP<K, V>` 表示由`K,V`类型元素组成的`MAP`。 点击[MAP 数据类型](../../../sql-manual/basic-element/sql-data-types/semi-structured/MAP.md) 了解具体信息。
## CSV 格式导入
@@ -117,3 +120,4 @@ mysql> SELECT * FROM map_test;
+------+-------------------------+
4 rows in set (0.01 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/struct.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/struct.md
index 3492cb6bee5..fc117872758 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/struct.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/struct.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Complex Types",
"language": "zh-CN",
- "description": "STRUCT<fieldname:fieldtype [COMMENT 'commentstring'], ... > 表示由多个 Field 组成的结构体，也可被理解为多个列的集合。点击STRUCT 数据类型 了解具体信息。"
+ "description": "STRUCT<fieldname:fieldtype [COMMENT 'commentstring'], ... > 表示由多个 Field 组成的结构体，也可被理解为多个列的集合。点击STRUCT 数据类型 了解具体信息。",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
`STRUCT<field_name:field_type [COMMENT 'comment_string'], ... >` 表示由多个 Field 组成的结构体，也可被理解为多个列的集合。点击[STRUCT 数据类型](../../../sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md) 了解具体信息。
## CSV 格式导入
@@ -127,3 +130,4 @@ mysql> SELECT * FROM struct_test;
+------+--------------------------------------+
5 rows in set (0.00 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/data-source/google-cloud-storage.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/data-source/google-cloud-storage.md
index 98d3272a75b..96261c66b68 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/data-source/google-cloud-storage.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/data-source/google-cloud-storage.md
@@ -1,11 +1,14 @@
---
{
- "title": "Google Cloud Storage",
+ "title": "Google Cloud Storage | Data Source",
"language": "zh-CN",
- "description": "Doris 提供两种方式从 Google Cloud Storage 导入文件："
+ "description": "Doris 提供两种方式从 Google Cloud Storage 导入文件：",
+ "sidebar_label": "Google Cloud Storage"
}
---
+# Google Cloud Storage
+
Doris 提供两种方式从 Google Cloud Storage 导入文件：
- 使用 S3 Load 将 Google Cloud Storage 文件导入到 Doris 中，这是一个异步的导入方式。
- 使用 TVF 将 Google Cloud Storage 文件导入到 Doris 中，这是一个同步的导入方式。
@@ -170,3 +173,4 @@ mysql> select * from test_s3load;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/data-source/hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/data-source/hdfs.md
index 558c26e4299..5f17a8e7250 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/data-source/hdfs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/data-source/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Data Source",
"language": "zh-CN",
- "description": "Doris 提供两种方式从 HDFS 导入文件："
+ "description": "Doris 提供两种方式从 HDFS 导入文件：",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
Doris 提供两种方式从 HDFS 导入文件：
- 使用 HDFS Load 将 HDFS 文件导入到 Doris 中，这是一个异步的导入方式。
- 使用 TVF 将 HDFS 文件导入到 Doris 中，这是一个同步的导入方式。
@@ -162,3 +165,4 @@ mysql> select * from test_hdfsload;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/data-source/minio.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/data-source/minio.md
index 595520c75d7..93303ace2d7 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/data-source/minio.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/data-source/minio.md
@@ -1,11 +1,14 @@
---
{
- "title": "MinIO",
+ "title": "MinIO | Data Source",
"language": "zh-CN",
- "description": "Doris 提供两种方式从 MinIO 导入文件："
+ "description": "Doris 提供两种方式从 MinIO 导入文件：",
+ "sidebar_label": "MinIO"
}
---
+# MinIO
+
Doris 提供两种方式从 MinIO 导入文件：
- 使用 S3 Load 将 MinIO 文件导入到 Doris 中，这是一个异步的导入方式。
- 使用 TVF 将 MinIO 文件导入到 Doris 中，这是一个同步的导入方式。
@@ -192,3 +195,4 @@ mysql> select * from test_s3load;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/json.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/json.md
index 1d86ed4d1b4..db50697027f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/json.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/json.md
@@ -1,8 +1,9 @@
---
{
- "title": "JSON",
+ "title": "JSON | File Format",
"language": "zh-CN",
- "description": "本文介绍如何在 Doris 中导入 JSON 格式的数据文件。Doris 支持导入标准 JSON 格式数据，通过配置相关参数，可以灵活地处理不同的 JSON 数据结构，并支持从 JSON 数据中抽取字段、处理嵌套结构等场景。"
+ "description": "本文介绍如何在 Doris 中导入 JSON 格式的数据文件。Doris 支持导入标准 JSON 格式数据，通过配置相关参数，可以灵活地处理不同的 JSON 数据结构，并支持从 JSON 数据中抽取字段、处理嵌套结构等场景。",
+ "sidebar_label": "JSON"
}
---
@@ -440,3 +441,4 @@ FROM S3
"json_root" = "$.events",
...
);
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/orc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/orc.md
index 4b6488a2cb2..500f74abf2c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/orc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/orc.md
@@ -1,11 +1,14 @@
---
{
- "title": "ORC",
+ "title": "ORC | File Format",
"language": "zh-CN",
- "description": "本文介绍如何在 Doris 中导入 ORC 格式的数据文件。"
+ "description": "本文介绍如何在 Doris 中导入 ORC 格式的数据文件。",
+ "sidebar_label": "ORC"
}
---
+# ORC
+
本文介绍如何在 Doris 中导入 ORC 格式的数据文件。
## 支持的导入方式
@@ -60,3 +63,4 @@ FROM S3
);
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/parquet.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/parquet.md
index ad990fe3875..7bb97a966d5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/parquet.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/parquet.md
@@ -1,11 +1,14 @@
---
{
- "title": "Parquet",
+ "title": "Parquet | File Format",
"language": "zh-CN",
- "description": "本文介绍如何在 Doris 中导入 Parquet 格式的数据文件。"
+ "description": "本文介绍如何在 Doris 中导入 Parquet 格式的数据文件。",
+ "sidebar_label": "Parquet"
}
---
+# Parquet
+
本文介绍如何在 Doris 中导入 Parquet 格式的数据文件。
## 支持的导入方式
@@ -56,4 +59,4 @@ FROM S3
"format" = "parquet",
...
);
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/ecosystem/bi/tableau-back.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/ecosystem/bi/tableau-back.md
index b14ebfbcd65..cc774af57b5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/ecosystem/bi/tableau-back.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/ecosystem/bi/tableau-back.md
@@ -1,11 +1,14 @@
---
{
- "title": "Tableau",
+ "title": "Tableau | Bi",
"language": "zh-CN",
- "description": "VeloDB 提供了一个官方的 Tableau Doris 连接器。 该连接器基于 MySQL JDBC Driver 实现访问数据。"
+ "description": "VeloDB 提供了一个官方的 Tableau Doris 连接器。 该连接器基于 MySQL JDBC Driver 实现访问数据。",
+ "sidebar_label": "Tableau"
}
---
+# Tableau
+
VeloDB 提供了一个官方的 Tableau Doris 连接器。 该连接器基于 MySQL JDBC Driver 实现访问数据。
该连接器通过 [TDVT framework](https://tableau.github.io/connector-plugin-sdk/docs/tdvt) 测试，通过率为 100%。
@@ -135,3 +138,4 @@ VeloDB 提供了一个官方的 Tableau Doris 连接器。 该连接器基于 My
这个连接器简化了通用 ODBC/JDBC 驱动程序的连接器 连接设置流程，为 Apache Doris 提供了更好兼容的连接器。如果您在使用连接器时遇到任何问题，请随时在 [GitHub](https://github.com/apache/doris/issues) 联系我们。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/ecosystem/bi/tableau.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/ecosystem/bi/tableau.md
index 1ebccf60168..fbdea851ddf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/ecosystem/bi/tableau.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/ecosystem/bi/tableau.md
@@ -1,11 +1,14 @@
---
{
- "title": "Tableau",
+ "title": "Tableau | Bi",
"language": "zh-CN",
- "description": "对于在 Tableau 上实现 Apache Doris 访问，Tableau 官方的 MySQL 连接器可以满足需求。 该连接器基于 MySQL JDBC Driver 实现访问数据。"
+ "description": "对于在 Tableau 上实现 Apache Doris 访问，Tableau 官方的 MySQL 连接器可以满足需求。 该连接器基于 MySQL JDBC Driver 实现访问数据。",
+ "sidebar_label": "Tableau"
}
---
+# Tableau
+
对于在 Tableau 上实现 Apache Doris 访问，Tableau 官方的 MySQL 连接器可以满足需求。 该连接器基于 MySQL JDBC Driver 实现访问数据。
通过 MySQL 连接器，Tableau 可以将 Apache Doris 数据库和表作为数据源进行集成。要启用此功能，请遵循下面的设置指南：
@@ -107,3 +110,4 @@
- 配置 安全组 限制访问。
- 启用 SSL/TLS 连接等访问方式。
- 细化 Doris 用户账号角色和访问权限，避免过度下放权限。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/file-formats/orc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/file-formats/orc.md
index cafd01e62de..7e2bfa5b36c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/file-formats/orc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/file-formats/orc.md
@@ -1,11 +1,14 @@
---
{
- "title": "ORC",
+ "title": "ORC | File Formats",
"language": "zh-CN",
- "description": "本文档用于介绍 Doris 的 ORC 文件格式的读写支持情况。该文档适用于以下功能。"
+ "description": "本文档用于介绍 Doris 的 ORC 文件格式的读写支持情况。该文档适用于以下功能。",
+ "sidebar_label": "ORC"
}
---
+# ORC
+
本文档用于介绍 Doris 的 ORC 文件格式的读写支持情况。该文档适用于以下功能。
* Catalog 中对数据的读取、写入操作。
@@ -69,3 +72,4 @@
* `orc_natural_read_size_mb` (2.1+, 3.0+)
ORC Reader 一次性读取的最大字节大小。默认 8 MB。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/file-formats/parquet.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/file-formats/parquet.md
index dee4524d0bc..2c029d1c5cf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/file-formats/parquet.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/file-formats/parquet.md
@@ -1,11 +1,14 @@
---
{
- "title": "Parquet",
+ "title": "Parquet | File Formats",
"language": "zh-CN",
- "description": "本文档用于介绍 Doris 的 Parquet 文件格式的读写支持情况。该文档适用于以下功能。"
+ "description": "本文档用于介绍 Doris 的 Parquet 文件格式的读写支持情况。该文档适用于以下功能。",
+ "sidebar_label": "Parquet"
}
---
+# Parquet
+
本文档用于介绍 Doris 的 Parquet 文件格式的读写支持情况。该文档适用于以下功能。
* Catalog 中对数据的读取、写入操作。
@@ -63,3 +66,4 @@
* `parquet_column_max_buffer_mb` (2.1+, 3.0+)
读取 Parquet Row Group 中的 Column 时所分配的最大 Buffer 大小，默认为 8M。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/statistics.md
index 2e928aa3798..04f9422952f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/statistics.md
@@ -1,12 +1,16 @@
---
{
- "title": "统计信息",
+ "title": "统计信息 | Lakehouse",
"language": "zh-CN",
- "description": "Doris 支持对外部数据源的表，如 Hive、Iceberg、Paimon 等进行自动或手动的统计信息收集。统计信息准确性直接决定了代价估算的准确性，对于选择最优查询计划至关重要，尤其在复杂查询场景下能显著提升查询执行效率。"
+ "description": "Doris 支持对外部数据源的表，如 Hive、Iceberg、Paimon 等进行自动或手动的统计信息收集。统计信息准确性直接决定了代价估算的准确性，对于选择最优查询计划至关重要，尤其在复杂查询场景下能显著提升查询执行效率。",
+ "sidebar_label": "统计信息"
}
---
+# 统计信息
+
Doris 支持对外部数据源的表，如 Hive、Iceberg、Paimon 等进行自动或手动的统计信息收集。统计信息准确性直接决定了代价估算的准确性，对于选择最优查询计划至关重要，尤其在复杂查询场景下能显著提升查询执行效率。
具体可参阅 [统计信息](../query-acceleration/optimization-technology-principle/statistics#外表收集) 文档中的【外表收集】部分。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/gcs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/gcs.md
index f06004bd9f6..35d0e2dc6f4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/gcs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/gcs.md
@@ -1,10 +1,14 @@
---
{
- "title": "Google Cloud Storage",
+ "title": "Google Cloud Storage | Storages",
"language": "zh-CN",
- "description": "文档更新中。"
+ "description": "文档更新中。",
+ "sidebar_label": "Google Cloud Storage"
}
---
+# Google Cloud Storage
+
文档更新中。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/hdfs.md
index 1c6b9843990..eb561af6609 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/hdfs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Storages",
"language": "zh-CN",
- "description": "本文档用于介绍访问 HDFS 时所需的参数。这些参数适用于："
+ "description": "本文档用于介绍访问 HDFS 时所需的参数。这些参数适用于：",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
本文档用于介绍访问 HDFS 时所需的参数。这些参数适用于：
* Catalog 属性。
@@ -217,3 +220,4 @@ Java 版本使用通过 Java 访问 HDFS，可以模拟 Doris FE 侧访问 HDFS
CPP 版本通过 C++ 调用 libhdfs 访问 HDFS，可以模拟 Doris BE 侧访问 HDFS 的逻辑。
具体使用方式可以各自代码库的 README。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/minio.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/minio.md
index 876139f0cc4..2c743026482 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/minio.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/minio.md
@@ -1,11 +1,14 @@
---
{
- "title": "MinIO",
+ "title": "MinIO | Storages",
"language": "zh-CN",
- "description": "本文档介绍访问 MinIO 所需的参数，这些参数适用于以下场景："
+ "description": "本文档介绍访问 MinIO 所需的参数，这些参数适用于以下场景：",
+ "sidebar_label": "MinIO"
}
---
+# MinIO
+
本文档介绍访问 MinIO 所需的参数，这些参数适用于以下场景：
- Catalog 属性
@@ -56,3 +59,4 @@ Minio 默认使用 Host-style 访问方式，但也支持 Path-style 访问。
* 推荐使用 `minio.` 前缀配置参数，保证与 MinIO 的一致性和清晰度。
* 3.1 之前的版本，请使用曾用名 `s3.` 作为前缀。
* 连接池参数可根据并发需求调整，避免连接阻塞。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/s3.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/s3.md
index 85544fd553f..a0d275f715d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/s3.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/storages/s3.md
@@ -1,11 +1,14 @@
---
{
- "title": "S3",
+ "title": "S3 | Storages",
"language": "zh-CN",
- "description": "本文档用于介绍访问 AWS S3 时所需的参数。这些参数适用于："
+ "description": "本文档用于介绍访问 AWS S3 时所需的参数。这些参数适用于：",
+ "sidebar_label": "S3"
}
---
+# S3
+
本文档用于介绍访问 AWS S3 时所需的参数。这些参数适用于：
- Catalog 属性。
@@ -153,3 +156,4 @@ Amazon S3 Express One Zone（又名 Directory Bucket）提供更高性能，但
- 如果只做查询，不要授予写权限。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/log-storage-analysis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/log-storage-analysis.md
index ac4999e5e5b..134b86d7aea 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/log-storage-analysis.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/log-storage-analysis.md
@@ -1,11 +1,14 @@
---
{
- "title": "日志存储与分析",
+ "title": "日志存储与分析 | Doris Docs",
"language": "zh-CN",
- "description": "日志是系统运行的详细记录，包含各种事件发生的主体、时间、位置、内容等关键信息。出于运维可观测、网络安全监控及业务分析等多重需求，企业通常需要将分散的日志采集起来，进行集中存储、查询和分析，以进一步从日志数据里挖掘出有价值的内容。"
+ "description": "日志是系统运行的详细记录，包含各种事件发生的主体、时间、位置、内容等关键信息。出于运维可观测、网络安全监控及业务分析等多重需求，企业通常需要将分散的日志采集起来，进行集中存储、查询和分析，以进一步从日志数据里挖掘出有价值的内容。",
+ "sidebar_label": "日志存储与分析"
}
---
+# 日志存储与分析
+
日志是系统运行的详细记录，包含各种事件发生的主体、时间、位置、内容等关键信息。出于运维可观测、网络安全监控及业务分析等多重需求，企业通常需要将分散的日志采集起来，进行集中存储、查询和分析，以进一步从日志数据里挖掘出有价值的内容。
针对此场景，Apache Doris 提供了相应解决方案，针对日志场景的特点，增加了倒排索引和极速全文检索能力，极致优化写入性能和存储空间，使得用户可以基于 Apache Doris 构建开放、高性能、低成本、统一的日志存储与分析平台。
@@ -542,3 +545,4 @@ ORDER BY ts DESC LIMIT 10;
您可以联系 dev@doris.apache.org 获得更多帮助。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/observability/log-storage-analysis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/observability/log-storage-analysis.md
index af2f5d4d43f..c541708912c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/observability/log-storage-analysis.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/observability/log-storage-analysis.md
@@ -1,11 +1,14 @@
---
{
- "title": "日志存储与分析",
+ "title": "日志存储与分析 | Observability",
"language": "zh-CN",
- "description": "在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤："
+ "description": "在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤：",
+ "sidebar_label": "日志存储与分析"
}
---
+# 日志存储与分析
+
### 第 1 步：评估资源
在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤：
@@ -461,3 +464,4 @@ ORDER BY ts DESC LIMIT 10;
您可以联系 dev@doris.apache.org 获得更多帮助。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/observability/overview.mdx b/i18n/zh-CN/docusaurus-plugin-content-docs/current/observability/overview.mdx
index 1a4878d4c04..cb85a683e47 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/observability/overview.mdx
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/observability/overview.mdx
@@ -1,11 +1,14 @@
---
{
- "title": "概述",
+ "title": "概述 | Observability",
"language": "zh_CN",
- "description": "可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台通过采集、存储、可视化分析三大可关键数据：日志（Logging）、链路追踪（Tracing）和指标（Metrics），帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等，"
+ "description": "可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台通过采集、存储、可视化分析三大可关键数据：日志（Logging）、链路追踪（Tracing）和指标（Metrics），帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等，",
+ "sidebar_label": "概述"
}
---
+# 概述
+
## 什么是可观测性
可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台通过采集、存储、可视化分析三大可关键数据：日志（Logging）、链路追踪（Tracing）和指标（Metrics），帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等，提升系统可靠性和用户体验。
@@ -133,3 +136,4 @@ Grafana 的 Log 可视化和分析能力相对于 Kibana 来说是比较简单
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/async-materialized-view/use-guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/async-materialized-view/use-guide.md
index 2a7a209f274..ecbbad1cbce 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/async-materialized-view/use-guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/async-materialized-view/use-guide.md
@@ -1,11 +1,14 @@
---
{
- "title": "最佳实践",
+ "title": "最佳实践 | Async Materialized View",
"language": "zh-CN",
- "description": "当满足以下条件时，建议创建分区物化视图："
+ "description": "当满足以下条件时，建议创建分区物化视图：",
+ "sidebar_label": "最佳实践"
}
---
+# 最佳实践
+
## 异步物化视图使用原则
- **时效性考虑：** 异步物化视图通常用于对数据时效性要求不高的场景，一般是 T+1 的数据。如果时效性要求高，应考虑使用同步物化视图。
@@ -783,4 +786,4 @@ FROM common_schedule_join_mv;
DML 时，当物化视图存在无法实时感知数据的外表时，是否开启基于结构信息的物化视图透明改写，默认关闭
-`SET enable_dml_materialized_view_rewrite_when_base_table_unawareness = true;`
\ No newline at end of file
+`SET enable_dml_materialized_view_rewrite_when_base_table_unawareness = true;`
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 24d00db6c9e..0711741d252 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
@@ -1,11 +1,14 @@
---
{
- "title": "统计信息",
+ "title": "统计信息 | Optimization Technology Principle",
"language": "zh-CN",
- "description": "从 2.0 版本开始，Doris 在优化器中加入了 CBO 的能力。统计信息是 CBO 的基石，其准确性直接决定了代价估算的准确性，对于选择最优 Plan 至关重要。本文主要介绍统计信息的收集和管理方法、相关配置项以及常见问题。"
+ "description": "从 2.0 版本开始，Doris 在优化器中加入了 CBO 的能力。统计信息是 CBO 的基石，其准确性直接决定了代价估算的准确性，对于选择最优 Plan 至关重要。本文主要介绍统计信息的收集和管理方法、相关配置项以及常见问题。",
+ "sidebar_label": "统计信息"
}
---
+# 统计信息
+
从 2.0 版本开始，Doris 在优化器中加入了 CBO 的能力。统计信息是 CBO 的基石，其准确性直接决定了代价估算的准确性，对于选择最优 Plan 至关重要。本文主要介绍统计信息的收集和管理方法、相关配置项以及常见问题。
## 统计信息的收集
@@ -478,3 +481,4 @@ ADMIN DIAGNOSE TABLET tablet_id
对于某些特殊表，如分区众多的表或单个 Tablet 体积庞大的表，可能会出现内存占用较多的情况。
建议用户在建表时合理规划 Tablet 数量，避免产生超大 Tablet。若 Tablet 结构不易调整，建议在系统低峰期开启自动收集，或于低峰期手动收集这些大表，以免在高峰期影响业务运行。在 Doris 3.x 系列中，我们将针对此类场景进行优化。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/tuning/parallelism-tuning.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/tuning/parallelism-tuning.md
index 3edd80faa3a..73a5527ed0e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/tuning/parallelism-tuning.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/tuning/parallelism-tuning.md
@@ -1,8 +1,9 @@
---
{
- "title": "并行度调优",
+ "title": "并行度调优 | Tuning",
"language": "zh-CN",
- "description": "Doris 的查询是一个 MPP 的执行框架，每一条查询都会在多个 BE 上并行执行；同时，在单个 BE 内部也会采用多线程并行的方式来加速查询的执行效率，目前所有的语句（包括 Query，DML，DDL）均支持并行执行。"
+ "description": "Doris 的查询是一个 MPP 的执行框架，每一条查询都会在多个 BE 上并行执行；同时，在单个 BE 内部也会采用多线程并行的方式来加速查询的执行效率，目前所有的语句（包括 Query，DML，DDL）均支持并行执行。",
+ "sidebar_label": "并行度调优"
}
---
@@ -64,3 +65,4 @@ set parallel_pipeline_task_num = 8;
```SQL
set global parallel_pipeline_task_num = 8;
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/tuning/tuning-execution/parallelism-tuning.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/tuning/tuning-execution/parallelism-tuning.md
index eb1d8bd837f..1deb0d6c256 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/tuning/tuning-execution/parallelism-tuning.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/tuning/tuning-execution/parallelism-tuning.md
@@ -1,11 +1,14 @@
---
{
- "title": "并行度调优",
+ "title": "并行度调优 | Tuning Execution",
"language": "zh-CN",
- "description": "Doris 的查询是一个 MPP 的执行框架，每一条查询都会在多个 BE 上并行执行；同时，在单个 BE 内部也会采用多线程并行的方式来加速查询的执行效率，目前所有的语句（包括 Query，DML，DDL）均支持并行执行。"
+ "description": "Doris 的查询是一个 MPP 的执行框架，每一条查询都会在多个 BE 上并行执行；同时，在单个 BE 内部也会采用多线程并行的方式来加速查询的执行效率，目前所有的语句（包括 Query，DML，DDL）均支持并行执行。",
+ "sidebar_label": "并行度调优"
}
---
+# 并行度调优
+
## 概述
Doris 的查询是一个 MPP 的执行框架，每一条查询都会在多个 BE 上并行执行；同时，在单个 BE 内部也会采用多线程并行的方式来加速查询的执行效率，目前所有的语句（包括 Query，DML，DDL）均支持并行执行。
@@ -139,3 +142,4 @@ set parallel_pipeline_task_num = 16;
1. 建议从 CPU 利用率出发。通过 PROFILE 工具输出观察是否是 CPU 瓶颈，尝试进行并行度的合理修改
2. 单 SQL 调整比较安全，尽量不要全局做过于激进的修改
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/date-time/DATE.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/date-time/DATE.md
index 49520815002..edad3af3f95 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/date-time/DATE.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/date-time/DATE.md
@@ -1,11 +1,14 @@
---
{
- "title": "DATE",
+ "title": "DATE | Date Time",
"language": "zh-CN",
- "description": "DATE 类型存储日期，取值范围是 [0000-01-01, 9999-12-31], 默认的输出格式为 'yyyy-MM-dd'。"
+ "description": "DATE 类型存储日期，取值范围是 [0000-01-01, 9999-12-31], 默认的输出格式为 'yyyy-MM-dd'。",
+ "sidebar_label": "DATE"
}
---
+# DATE
+
## 描述
DATE 类型存储日期，取值范围是 `[0000-01-01, 9999-12-31]`, 默认的输出格式为 'yyyy-MM-dd'。
@@ -45,3 +48,4 @@ select cast('0120-02-29' as date);
| 0120-02-29 |
+----------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/date-time/TIME.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/date-time/TIME.md
index 6d071a54e31..14f876aa4b2 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/date-time/TIME.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/date-time/TIME.md
@@ -1,11 +1,14 @@
---
{
- "title": "TIME",
+ "title": "TIME | Date Time",
"language": "zh-CN",
- "description": "TIME(p) 类型存储时间，其中 p 为精度，p 的取值范围为 [0, 6]，缺省值为 0。即 TIME 等同于 TIME(0)。"
+ "description": "TIME(p) 类型存储时间，其中 p 为精度，p 的取值范围为 [0, 6]，缺省值为 0。即 TIME 等同于 TIME(0)。",
+ "sidebar_label": "TIME"
}
---
+# TIME
+
## 描述
TIME(p) 类型存储时间，其中 p 为精度，p 的取值范围为 `[0, 6]`，缺省值为 0。即 TIME 等同于 TIME(0)。
@@ -43,3 +46,4 @@ select cast('838:59:59.999999' as time(6));
| 838:59:59.999999 |
+-------------------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
index 6b41688d39e..3d109b1f3e6 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Semi Structured",
"language": "zh-CN",
- "description": "ARRAY<T> 类型用于表示有序元素集合，集合中的每个元素具有相同的数据类型。例如，一个整数数组可表示为[1, 2, 3]，一个字符串数组可表示为[\"a\", \"b\", \"c\"]。"
+ "description": "ARRAY<T> 类型用于表示有序元素集合，集合中的每个元素具有相同的数据类型。例如，一个整数数组可表示为[1, 2, 3]，一个字符串数组可表示为[\"a\", \"b\", \"c\"]。",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
## 类型描述
`ARRAY<T>` 类型用于表示有序元素集合，集合中的每个元素具有相同的数据类型。例如，一个整数数组可表示为`[1, 2, 3]`，一个字符串数组可表示为`["a", "b", "c"]`。
@@ -324,4 +327,4 @@ select array(null) < array(-1), array(null) > array(-1);
| 2 | [4, 5, 6] |
| 3 | [7, 8, 9] |
+------+--------------+
- ```
\ No newline at end of file
+ ```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
index ad21c509e02..7a23ac58a62 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
@@ -1,11 +1,14 @@
---
{
- "title": "JSON",
+ "title": "JSON | Semi Structured",
"language": "zh-CN",
- "description": "JSON（JavaScript Object Notation）是一种开放标准的文件格式和数据交换格式，使用可读性强的纯文本来存储和传输数据。根据官方规范 RFC7159，JSON 支持以下基本类型："
+ "description": "JSON（JavaScript Object Notation）是一种开放标准的文件格式和数据交换格式，使用可读性强的纯文本来存储和传输数据。根据官方规范 RFC7159，JSON 支持以下基本类型：",
+ "sidebar_label": "JSON"
}
---
+# JSON
+
## JSON 介绍
JSON（JavaScript Object Notation）是一种开放标准的文件格式和数据交换格式，使用可读性强的纯文本来存储和传输数据。根据官方规范 [RFC7159](https://datatracker.ietf.org/doc/html/rfc7159)，JSON 支持以下基本类型：
@@ -1222,3 +1225,4 @@ mysql> SELECT JSON_EXTRACT_STRING('{"key1" : null}', "$.key_not_exist") IS NULL;
### keywords
JSON, json_parse, json_parse_error_to_null, json_parse_error_to_value, json_extract, json_extract_isnull, json_extract_bool, json_extract_int, json_extract_bigint, json_extract_double, json_extract_String, json_exists_path, json_type
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
index b152666e25a..fbac009dac1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Semi Structured",
"language": "zh-CN",
- "description": "````SQL SELECT MAP('Alice', 21, 'Bob', 23);"
+ "description": "````SQL SELECT MAP('Alice', 21, 'Bob', 23);",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
## 类型描述
- `MAP<key_type, value_type>`类型用于表示键值对集合的复合类型,每个键（key）唯一地对应一个值（value）。
@@ -211,4 +214,4 @@
| map_int_varchar | map<int,varchar(20)> | Yes | false | NULL | NONE |
| map_varchar_varchar | map<varchar(20),varchar(20)> | Yes | false | NULL | NONE |
+---------------------+------------------------------+------+-------+---------+-------+
- ```
\ No newline at end of file
+ ```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
index 0734e9e9ef9..e235d7956bf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Semi Structured",
"language": "zh-CN",
- "description": "STRUCT 类型用于将多个字段组合成一个结构体，每个字段可以有自己的名字和类型，适合表示嵌套或复杂的业务数据结构。"
+ "description": "STRUCT 类型用于将多个字段组合成一个结构体，每个字段可以有自己的名字和类型，适合表示嵌套或复杂的业务数据结构。",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
## 类型描述
STRUCT 类型用于将多个字段组合成一个结构体，每个字段可以有自己的名字和类型，适合表示嵌套或复杂的业务数据结构。
@@ -201,4 +204,4 @@ CREATE TABLE struct_table (
| k | int | No | true | NULL | |
| struct_varchar | struct<name:varchar(10),age:int,id:int> | Yes | false | NULL | NONE |
+----------------+-----------------------------------------+------+-------+---------+-------+
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/string-type/CHAR.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
index cd06dcfb960..2b86fcaca5e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
@@ -1,11 +1,14 @@
---
{
- "title": "CHAR",
+ "title": "CHAR | String Type",
"language": "zh-CN",
- "description": "CHAR(M)"
+ "description": "CHAR(M)",
+ "sidebar_label": "CHAR"
}
---
+# CHAR
+
## description
CHAR(M)
@@ -15,3 +18,4 @@ CHAR(M)
## keywords
CHAR
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/array-functions/array.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/array-functions/array.md
index f10386e68e5..fb6d9109937 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/array-functions/array.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/array-functions/array.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Array Functions",
"language": "zh-CN",
- "description": "创建一个数组。函数接受零个或多个参数，返回一个包含所有输入元素的数组。"
+ "description": "创建一个数组。函数接受零个或多个参数，返回一个包含所有输入元素的数组。",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
## array
<version since="2.0.0">
@@ -136,3 +139,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = Can not find the compatibility
### Keywords
ARRAY
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
index e5f9b86f2e4..09fc033198d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
@@ -1,11 +1,14 @@
---
{
- "title": "DATE",
+ "title": "DATE | Date Time Functions",
"language": "zh-CN",
- "description": "DATE 函数用于从日期时间值(包含日期和时间)中提取出纯日期部分，忽略时间信息。该函数可将 DATETIME 类型转换为 DATE 类型，仅保留年、月、日信息。"
+ "description": "DATE 函数用于从日期时间值(包含日期和时间)中提取出纯日期部分，忽略时间信息。该函数可将 DATETIME 类型转换为 DATE 类型，仅保留年、月、日信息。",
+ "sidebar_label": "DATE"
}
---
+# DATE
+
## 描述
DATE 函数用于从日期时间值(包含日期和时间)中提取出纯日期部分，忽略时间信息。该函数可将 DATETIME 类型转换为 DATE 类型，仅保留年、月、日信息。
@@ -58,4 +61,4 @@ mysql> select date(NULL);
| NULL |
+------------+
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/date-time-functions/time.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/date-time-functions/time.md
index 50574d0e6b7..b520510a39b 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/date-time-functions/time.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/date-time-functions/time.md
@@ -1,11 +1,14 @@
---
{
- "title": "TIME",
+ "title": "TIME | Date Time Functions",
"language": "zh-CN",
- "description": "TIME 函数可以获取一个DateTime值的 time 部分."
+ "description": "TIME 函数可以获取一个DateTime值的 time 部分.",
+ "sidebar_label": "TIME"
}
---
+# TIME
+
## 描述
`TIME` 函数可以获取一个`DateTime`值的 `time` 部分.
@@ -38,3 +41,4 @@ mysql>
| 12:12:12 |
+---------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/cut-ipv6.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/cut-ipv6.md
index b8091da0746..40fa4c8fdaf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/cut-ipv6.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/cut-ipv6.md
@@ -1,11 +1,14 @@
---
{
- "title": "CUT_IPV6",
+ "title": "CUT_IPV6 | Ip Functions",
"language": "zh-CN",
- "description": "根据 IPv6 地址的类型（IPv4 映射或纯 IPv6），从 IPv6 地址的末尾截取指定数量的字节，并返回截取后的 IPv6 地址字符串。"
+ "description": "根据 IPv6 地址的类型（IPv4 映射或纯 IPv6），从 IPv6 地址的末尾截取指定数量的字节，并返回截取后的 IPv6 地址字符串。",
+ "sidebar_label": "CUT_IPV6"
}
---
+# CUT_IPV6
+
## cut_ipv6
## 描述
@@ -79,3 +82,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = (...)[INVALID_ARGUMENT]Illegal
CUT_IPV6
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/cut_ipv6.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/cut_ipv6.md
index 66bc1602d2d..44fbb050ba9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/cut_ipv6.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/cut_ipv6.md
@@ -1,11 +1,14 @@
---
{
- "title": "CUT_IPV6",
+ "title": "CUT_IPV6 | Ip Functions",
"language": "zh-CN",
- "description": "根据 IPv6 地址的类型（IPv4 映射或纯 IPv6），从 IPv6 地址的末尾截取指定数量的字节，并返回截取后的 IPv6 地址字符串。"
+ "description": "根据 IPv6 地址的类型（IPv4 映射或纯 IPv6），从 IPv6 地址的末尾截取指定数量的字节，并返回截取后的 IPv6 地址字符串。",
+ "sidebar_label": "CUT_IPV6"
}
---
+# CUT_IPV6
+
## cut_ipv6
## 描述
@@ -107,3 +110,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = (...)[INVALID_ARGUMENT]Illegal
CUT_IPV6
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/inet-ntoa.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/inet-ntoa.md
index 0068f2bd089..fe6b1010177 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/inet-ntoa.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/inet-ntoa.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV4_NUM_TO_STRING",
+ "title": "IPV4_NUM_TO_STRING | Ip Functions",
"language": "zh-CN",
- "description": "别名 ipv4numtostring。"
+ "description": "别名 ipv4numtostring。",
+ "sidebar_label": "IPV4_NUM_TO_STRING"
}
---
+# IPV4_NUM_TO_STRING
+
## inet_ntoa
别名 `ipv4_num_to_string`。
@@ -85,4 +88,4 @@ select ipv4_num_to_string(4294967296);
### Keywords
-INET_NTOA, IPV4_NUM_TO_STRING
\ No newline at end of file
+INET_NTOA, IPV4_NUM_TO_STRING
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-aton.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-aton.md
index 550a00c8c55..49b4f8b406b 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-aton.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-aton.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_STRING_TO_NUM_OR_NULL",
+ "title": "IPV6_STRING_TO_NUM_OR_NULL | Ip Functions",
"language": "zh-CN",
- "description": "别名 ipv6stringtonumornull。"
+ "description": "别名 ipv6stringtonumornull。",
+ "sidebar_label": "IPV6_STRING_TO_NUM_OR_NULL"
}
---
+# IPV6_STRING_TO_NUM_OR_NULL
+
## inet6_aton
别名 `ipv6_string_to_num_or_null`。
@@ -78,4 +81,4 @@ select hex(ipv6_string_to_num_or_null('notaaddress')) as invalid;
### Keywords
-INET6_ATON, IPV6_STRING_TO_NUM_OR_NULL
\ No newline at end of file
+INET6_ATON, IPV6_STRING_TO_NUM_OR_NULL
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-ntoa.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-ntoa.md
index d08bb0a6091..20886a97923 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-ntoa.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-ntoa.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_NUM_TO_STRING",
+ "title": "IPV6_NUM_TO_STRING | Ip Functions",
"language": "zh-CN",
- "description": "别名 ipv6numtostring。"
+ "description": "别名 ipv6numtostring。",
+ "sidebar_label": "IPV6_NUM_TO_STRING"
}
---
+# IPV6_NUM_TO_STRING
+
## inet6_ntoa
别名 `ipv6_num_to_string`。
@@ -67,4 +70,4 @@ select ipv6_num_to_string('-23vno12i34nlfwlsj') as invalid;
### Keywords
-INET6_NTOA, IPV6_NUM_TO_STRING
\ No newline at end of file
+INET6_NTOA, IPV6_NUM_TO_STRING
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-cidr-to-range.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-cidr-to-range.md
index 911d3b5df04..9f3b11b22c4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-cidr-to-range.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-cidr-to-range.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV4_CIDR_TO_RANGE",
+ "title": "IPV4_CIDR_TO_RANGE | Ip Functions",
"language": "zh-CN",
- "description": "根据 IPv4 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv4 地址，返回一个包含两个 IPv4 地址的结构体。"
+ "description": "根据 IPv4 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv4 地址，返回一个包含两个 IPv4 地址的结构体。",
+ "sidebar_label": "IPV4_CIDR_TO_RANGE"
}
---
+# IPV4_CIDR_TO_RANGE
+
## ipv4_cidr_to_range
## 描述
@@ -77,3 +80,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = (...)[INVALID_ARGUMENT]Illegal
IPV4_CIDR_TO_RANGE
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-num-to-string.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-num-to-string.md
index 503d6584ef9..fd38cb1dab6 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-num-to-string.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-num-to-string.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV4_NUM_TO_STRING",
+ "title": "IPV4_NUM_TO_STRING | Ip Functions",
"language": "zh-CN",
- "description": "接受一个类型为 Int16、Int32、Int64 且大端表示的 IPv4 的地址，返回相应 IPv4 的字符串表现形式，格式为 A.B.C.D（以点分割的十进制数字）。"
+ "description": "接受一个类型为 Int16、Int32、Int64 且大端表示的 IPv4 的地址，返回相应 IPv4 的字符串表现形式，格式为 A.B.C.D（以点分割的十进制数字）。",
+ "sidebar_label": "IPV4_NUM_TO_STRING"
}
---
+# IPV4_NUM_TO_STRING
+
## 描述
接受一个类型为 Int16、Int32、Int64 且大端表示的 IPv4 的地址，返回相应 IPv4 的字符串表现形式，格式为 A.B.C.D（以点分割的十进制数字）。
@@ -51,3 +54,4 @@ select num,ipv4_num_to_string(num) from ipv4_bi;
| 4294967296 | NULL |
+------------+---------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4_cidr_to_range.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4_cidr_to_range.md
index 8feb817adce..8035cf8bfd3 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4_cidr_to_range.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4_cidr_to_range.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV4_CIDR_TO_RANGE",
+ "title": "IPV4_CIDR_TO_RANGE | Ip Functions",
"language": "zh-CN",
- "description": "根据 IPv4 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv4 地址，返回一个包含两个 IPv4 地址的结构体。"
+ "description": "根据 IPv4 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv4 地址，返回一个包含两个 IPv4 地址的结构体。",
+ "sidebar_label": "IPV4_CIDR_TO_RANGE"
}
---
+# IPV4_CIDR_TO_RANGE
+
## ipv4_cidr_to_range
## 描述
@@ -101,3 +104,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = (...)[INVALID_ARGUMENT]Illegal
IPV4_CIDR_TO_RANGE
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-cidr-to-range.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-cidr-to-range.md
index 93ac43b40e5..91c5d48f3a9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-cidr-to-range.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-cidr-to-range.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_CIDR_TO_RANGE",
+ "title": "IPV6_CIDR_TO_RANGE | Ip Functions",
"language": "zh-CN",
- "description": "根据 IPv6 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv6 地址，返回一个包含两个 IPv6 地址的结构体。"
+ "description": "根据 IPv6 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv6 地址，返回一个包含两个 IPv6 地址的结构体。",
+ "sidebar_label": "IPV6_CIDR_TO_RANGE"
}
---
+# IPV6_CIDR_TO_RANGE
+
## ipv6_cidr_to_range
## 描述
@@ -78,3 +81,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = (...)[INVALID_ARGUMENT]Illegal
IPV6_CIDR_TO_RANGE
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-num-to-string.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-num-to-string.md
index f1b3f24439d..2fcff0b9a4e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-num-to-string.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-num-to-string.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_NUM_TO_STRING",
+ "title": "IPV6_NUM_TO_STRING | Ip Functions",
"language": "zh-CN",
- "description": "接受字符串类型的二进制格式的 IPv6 地址。以文本格式返回此地址的字符串。"
+ "description": "接受字符串类型的二进制格式的 IPv6 地址。以文本格式返回此地址的字符串。",
+ "sidebar_label": "IPV6_NUM_TO_STRING"
}
---
+# IPV6_NUM_TO_STRING
+
## 描述
接受字符串类型的二进制格式的 IPv6 地址。以文本格式返回此地址的字符串。
@@ -38,3 +41,4 @@ select ipv6_num_to_string(unhex('2A0206B8000000000000000000000011')) as addr, ip
| 2a02:6b8::11 | NULL |
+--------------+------------------------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-string-to-num-or-null.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-string-to-num-or-null.md
index b6069d33bf7..7634ab38224 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-string-to-num-or-null.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-string-to-num-or-null.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_STRING_TO_NUM_OR_NULL",
+ "title": "IPV6_STRING_TO_NUM_OR_NULL | Ip Functions",
"language": "zh-CN",
- "description": "IPv6NumToString 的反向函数，它接受一个 IP 地址字符串并返回二进制格式的 IPv6 地址。"
+ "description": "IPv6NumToString 的反向函数，它接受一个 IP 地址字符串并返回二进制格式的 IPv6 地址。",
+ "sidebar_label": "IPV6_STRING_TO_NUM_OR_NULL"
}
---
+# IPV6_STRING_TO_NUM_OR_NULL
+
## 描述
IPv6NumToString 的反向函数，它接受一个 IP 地址字符串并返回二进制格式的 IPv6 地址。
@@ -38,3 +41,4 @@ select hex(ipv6_string_to_num_or_null('1111::ffff')) as r1, hex(ipv6_string_to_n
| 1111000000000000000000000000FFFF | 00000000000000000000FFFFC0A80001 | NULL |
+----------------------------------+----------------------------------+------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6_cidr_to_range.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6_cidr_to_range.md
index f224e86ca42..4681778176f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6_cidr_to_range.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6_cidr_to_range.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_CIDR_TO_RANGE",
+ "title": "IPV6_CIDR_TO_RANGE | Ip Functions",
"language": "zh-CN",
- "description": "根据 IPv6 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv6 地址，返回一个包含两个 IPv6 地址的结构体。"
+ "description": "根据 IPv6 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv6 地址，返回一个包含两个 IPv6 地址的结构体。",
+ "sidebar_label": "IPV6_CIDR_TO_RANGE"
}
---
+# IPV6_CIDR_TO_RANGE
+
## ipv6_cidr_to_range
## 描述
@@ -94,3 +97,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = (...)[INVALID_ARGUMENT]Illegal
IPV6_CIDR_TO_RANGE
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/map-functions/map.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/map-functions/map.md
index 1fdb0a894c7..459a0d636cf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/map-functions/map.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/map-functions/map.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Map Functions",
"language": "zh-CN",
- "description": "使用若干组键值对构造一个特定类型的 MAP<K, V>"
+ "description": "使用若干组键值对构造一个特定类型的 MAP<K, V>",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
## 描述
使用若干组键值对构造一个特定类型的 [`MAP<K, V>`](../../../basic-element/sql-data-types/semi-structured/MAP.md)
@@ -78,4 +81,4 @@ MAP( <key1> , <value1> [, <key2>, <value2> ... ])
+--------------------------------------------------------+
| {2:"11", 1:"3", null:"null 2"} |
+--------------------------------------------------------+
- ```
\ No newline at end of file
+ ```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/string-functions/char.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/string-functions/char.md
index 5261aaa0fae..86269511004 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/string-functions/char.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/string-functions/char.md
@@ -1,11 +1,14 @@
---
{
- "title": "CHAR",
+ "title": "CHAR | String Functions",
"language": "zh-CN",
- "description": "CHAR 函数将每个参数解释为整数，并返回一个由这些整数代码值组成字符的字符串。"
+ "description": "CHAR 函数将每个参数解释为整数，并返回一个由这些整数代码值组成字符的字符串。",
+ "sidebar_label": "CHAR"
}
---
+# CHAR
+
## 描述
CHAR 函数将每个参数解释为整数，并返回一个由这些整数代码值组成字符的字符串。
@@ -79,4 +82,4 @@ SELECT CHAR(NULL);
+------------+
| |
+------------+
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
index b0a071b0b6d..2d087f414cf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Struct Functions",
"language": "zh-CN",
- "description": "根据给定的值构造并返回 struct。函数接受一个或多个参数，返回一个包含所有输入元素的结构体。"
+ "description": "根据给定的值构造并返回 struct。函数接受一个或多个参数，返回一个包含所有输入元素的结构体。",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
## 描述
根据给定的值构造并返回 struct。函数接受一个或多个参数，返回一个包含所有输入元素的结构体。
@@ -96,3 +99,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = struct requires at least one ar
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
index 3fe0ec00420..f82a3bdea5b 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
@@ -1,11 +1,14 @@
---
{
- "title": "EXPLODE_JSON_ARRAY_JSON_OUTER",
+ "title": "EXPLODE_JSON_ARRAY_JSON_OUTER | Table Functions",
"language": "zh-CN",
- "description": "explodejsonarrayjsonouter 表函数，接受一个 JSON 数组，其实现逻辑是将 JSON 数组转换为数组类型然后再调用 explodeouter 函数处理，行为等价于：explodeouter(cast(<jsonarray> as Array<JSON>)) 。"
+ "description": "explodejsonarrayjsonouter 表函数，接受一个 JSON 数组，其实现逻辑是将 JSON 数组转换为数组类型然后再调用 explodeouter 函数处理，行为等价于：explodeouter(cast(<jsonarray> as Array<JSON>)) 。",
+ "sidebar_label": "EXPLODE_JSON_ARRAY_JSON_OUTER"
}
---
+# EXPLODE_JSON_ARRAY_JSON_OUTER
+
## 描述
`explode_json_array_json_outer` 表函数，接受一个 JSON 数组，其实现逻辑是将 JSON 数组转换为数组类型然后再调用 `explode_outer` 函数处理，行为等价于：`explode_outer(cast(<json_array> as Array<JSON>))`
。需配合 [`LATERAL VIEW`](../../../query-data/lateral-view.md) 使用。
@@ -80,4 +83,4 @@ EXPLODE_JSON_ARRAY_JSON_OUTER(<json>)
+------+------+
| 1 | NULL |
+------+------+
- ```
\ No newline at end of file
+ ```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-json-array-json-outer.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-json-array-json-outer.md
index 3fe0ec00420..f82a3bdea5b 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-json-array-json-outer.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-functions/explode-json-array-json-outer.md
@@ -1,11 +1,14 @@
---
{
- "title": "EXPLODE_JSON_ARRAY_JSON_OUTER",
+ "title": "EXPLODE_JSON_ARRAY_JSON_OUTER | Table Functions",
"language": "zh-CN",
- "description": "explodejsonarrayjsonouter 表函数，接受一个 JSON 数组，其实现逻辑是将 JSON 数组转换为数组类型然后再调用 explodeouter 函数处理，行为等价于：explodeouter(cast(<jsonarray> as Array<JSON>)) 。"
+ "description": "explodejsonarrayjsonouter 表函数，接受一个 JSON 数组，其实现逻辑是将 JSON 数组转换为数组类型然后再调用 explodeouter 函数处理，行为等价于：explodeouter(cast(<jsonarray> as Array<JSON>)) 。",
+ "sidebar_label": "EXPLODE_JSON_ARRAY_JSON_OUTER"
}
---
+# EXPLODE_JSON_ARRAY_JSON_OUTER
+
## 描述
`explode_json_array_json_outer` 表函数，接受一个 JSON 数组，其实现逻辑是将 JSON 数组转换为数组类型然后再调用 `explode_outer` 函数处理，行为等价于：`explode_outer(cast(<json_array> as Array<JSON>))`
。需配合 [`LATERAL VIEW`](../../../query-data/lateral-view.md) 使用。
@@ -80,4 +83,4 @@ EXPLODE_JSON_ARRAY_JSON_OUTER(<json>)
+------+------+
| 1 | NULL |
+------+------+
- ```
\ No newline at end of file
+ ```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-valued-functions/hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-valued-functions/hdfs.md
index 6e630bb3316..9470a432325 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-valued-functions/hdfs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-valued-functions/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Table Valued Functions",
"language": "zh-CN",
- "description": "HDFS 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 HDFS 上的文件内容。目前支持csv/csvwithnames/csvwithnamesandtypes/json/parquet/orc文件格式。"
+ "description": "HDFS 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 HDFS 上的文件内容。目前支持csv/csvwithnames/csvwithnamesandtypes/json/parquet/orc文件格式。",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
## 描述
HDFS 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 HDFS 上的文件内容。目前支持`csv/csv_with_names/csv_with_names_and_types/json/parquet/orc`文件格式。
@@ -125,3 +128,4 @@ HDFS(
"hadoop.username" = "doris",
"format" = "csv_with_names");
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-valued-functions/s3.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-valued-functions/s3.md
index d094a6667ca..b431becba8e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-valued-functions/s3.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/table-valued-functions/s3.md
@@ -1,11 +1,14 @@
---
{
- "title": "S3",
+ "title": "S3 | Table Valued Functions",
"language": "zh-CN",
- "description": "S3 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 S3 兼容的对象存储上的文件内容。目前支持 csv/csv_with_names/csv_with_names_and_types/json/parquet/orc 文件格式。"
+ "description": "S3 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 S3 兼容的对象存储上的文件内容。目前支持 csv/csv_with_names/csv_with_names_and_types/json/parquet/orc 文件格式。",
+ "sidebar_label": "S3"
}
---
+# S3
+
## 描述
S3 表函数（table-valued-function, tvf）可以让用户像访问关系表格式数据一样，读取并访问 S3 兼容的对象存储上的文件内容。目前支持 `csv/csv_with_names/csv_with_names_and_types/json/parquet/orc` 文件格式。
@@ -592,3 +595,4 @@ S3(
"read_json_by_line" = "true",
"use_path_style" = "true");
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/auth/security-overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/auth/security-overview.md
index d25bc1d3074..c4951d764c9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/auth/security-overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/auth/security-overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "安全概览",
+ "title": "安全概览 | Auth",
"language": "zh-CN",
- "description": "Doris 提供以下机制管理数据安全："
+ "description": "Doris 提供以下机制管理数据安全：",
+ "sidebar_label": "安全概览"
}
---
+# 安全概览
+
Doris 提供以下机制管理数据安全：
身份认证：Doris 支持用户名/密码与 LDAP 认证方式。
@@ -31,3 +34,4 @@ Doris 提供以下机制管理数据安全：
JAVA-UDF安全：Doris 支持用户自定义函数功能，所以需要Root 管理员审查用户 UDF 的实现，确保实现逻辑的操作安全，防止在 UDF 中执行高危操作，例如删除数据和破坏系统等。
第三方包：在使用 Doris 的 JDBC Catalog、UDF 等功能时，如需引入第三方包，管理员需自行确保这些包来源安全可信。建议仅使用来自官方渠道或受信任社区的依赖包，以降低安全风险。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/config/fe-config-template.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/config/fe-config-template.md
index 42689c0ba21..5c8c5ed5826 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/config/fe-config-template.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/config/fe-config-template.md
@@ -1,10 +1,11 @@
---
{
- "title": "FE 配置项",
+ "title": "FE 配置项 | Config",
"language": "zh-CN",
"toc_min_heading_level": 2,
"toc_max_heading_level": 4,
- "description": "该文档主要介绍 FE 的相关配置项。"
+ "description": "该文档主要介绍 FE 的相关配置项。",
+ "sidebar_label": "FE 配置项"
}
---
@@ -118,3 +119,4 @@ FE 的配置项有两种方式进行配置：
> 如需修改，请修改 `fe/fe-common/src/main/java/org/apache/doris/common/Config.java` 中的描述信息。
<--DOC_PLACEHOLDER-->
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/config/fe-config.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/config/fe-config.md
index 0d94aebe82d..3f24c07c922 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/config/fe-config.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/config/fe-config.md
@@ -1,10 +1,11 @@
---
{
- "title": "FE 配置项",
+ "title": "FE 配置项 | Config",
"language": "zh-CN",
"toc_min_heading_level": 2,
"toc_max_heading_level": 4,
- "description": "该文档主要介绍 FE 的相关配置项。"
+ "description": "该文档主要介绍 FE 的相关配置项。",
+ "sidebar_label": "FE 配置项"
}
---
@@ -2759,3 +2760,4 @@ Doris 为了兼用 mysql 周边工具生态，会内置一个名为 mysql 的数
默认值：1
用于控制 ProfileManager 进行 Profile 垃圾回收的间隔时间，垃圾回收期间 ProfileManager 会把多余的以及过期的 profile 从内存和磁盘中清理掉，节省内存。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action-V2.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action-V2.md
index 09963040bf6..2bd99841252 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action-V2.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action-V2.md
@@ -1,11 +1,14 @@
---
{
- "title": "Meta Info Action",
+ "title": "Meta Info Action | Fe Http",
"language": "zh-CN",
- "description": "获取集群内的元数据信息，包括数据库列表、表列表以及表结构等。"
+ "description": "获取集群内的元数据信息，包括数据库列表、表列表以及表结构等。",
+ "sidebar_label": "Meta Info Action"
}
---
+# Meta Info Action
+
## Request
`GET /api/meta/namespaces/<ns>/databases`
@@ -50,3 +53,4 @@
"count":0
}
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action.md
index d9c622d3cec..4e477f2f180 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action.md
@@ -1,11 +1,14 @@
---
{
- "title": "Meta Info Action",
+ "title": "Meta Info Action | Fe Http",
"language": "zh-CN",
- "description": "Meta Info Action 用于获取集群内的元数据信息。如数据库列表，表结构等。"
+ "description": "Meta Info Action 用于获取集群内的元数据信息。如数据库列表，表结构等。",
+ "sidebar_label": "Meta Info Action"
}
---
+# Meta Info Action
+
Meta Info Action 用于获取集群内的元数据信息。如数据库列表，表结构等。
## 数据库列表
@@ -210,3 +213,4 @@ GET /api/meta/namespaces/default/databases/db1/tables/tbl1/schema?with_mv?=1
```
* data 字段返回 base 表或 rollup 表的表结构信息。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action-controller.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action-controller.md
index 368412b2cd3..ee60a32ebd1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action-controller.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action-controller.md
@@ -1,11 +1,14 @@
---
{
- "title": "Query Profile Action",
+ "title": "Query Profile Action | Fe Http",
"language": "zh-CN",
- "description": "Query Profile Action 用于获取 Query 的 profile"
+ "description": "Query Profile Action 用于获取 Query 的 profile",
+ "sidebar_label": "Query Profile Action"
}
---
+# Query Profile Action
+
## Request
```
@@ -85,4 +88,4 @@ Query Profile Action 用于获取 Query 的 profile
}
```
- `data` is the text content of the profile.
\ No newline at end of file
+ `data` is the text content of the profile.
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action.md
index 24f420b306e..81b4423c9bf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action.md
@@ -1,11 +1,14 @@
---
{
- "title": "Query Profile Action",
+ "title": "Query Profile Action | Fe Http",
"language": "zh-CN",
- "description": "可获取集群所有 fe 节点 select 查询信息。"
+ "description": "可获取集群所有 fe 节点 select 查询信息。",
+ "sidebar_label": "Query Profile Action"
}
---
+# Query Profile Action
+
## Request
`GET /rest/v2/manager/query/query_info`
@@ -457,3 +460,4 @@ Admin 和 Root 用户可以查看所有 Query。普通用户仅能查看自己
}
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/security-overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/security-overview.md
index d80541ef69d..13068aa2c14 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/security-overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/security-overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "安全概览",
+ "title": "安全概览 | Admin Manual",
"language": "zh-CN",
- "description": "Doris 提供以下机制管理数据安全："
+ "description": "Doris 提供以下机制管理数据安全：",
+ "sidebar_label": "安全概览"
}
---
+# 安全概览
+
Doris 提供以下机制管理数据安全：
身份认证：Doris 支持用户名/密码与 LDAP 认证方式。
@@ -31,3 +34,4 @@ Ranger 权限管理：Doris 可以通过集成 Ranger 实现集中化的权限
JAVA-UDF安全：Doris 支持用户自定义函数功能，所以需要Root 管理员审查用户 UDF 的实现，确保实现逻辑的操作安全，防止在 UDF 中执行高危操作，例如删除数据和破坏系统等。
第三方包：在使用 Doris 的 JDBC Catalog、UDF 等功能时，如需引入第三方包，管理员需自行确保这些包来源安全可信。建议仅使用来自官方渠道或受信任社区的依赖包，以降低安全风险。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/system-tables/information_schema/column_statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/system-tables/information_schema/column_statistics.md
index e4c88305642..bfc4a3b1fd0 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/system-tables/information_schema/column_statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/system-tables/information_schema/column_statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "column_statistics",
+ "title": "column_statistics | Information Schema",
"language": "zh-CN",
- "description": "此表仅用于兼容 MySQL 行为，永远为空。并不能真实反映 Doris 内数据的统计信息。如需查看 Doris 收集的统计信息，请查看统计信息章节。"
+ "description": "此表仅用于兼容 MySQL 行为，永远为空。并不能真实反映 Doris 内数据的统计信息。如需查看 Doris 收集的统计信息，请查看统计信息章节。",
+ "sidebar_label": "column_statistics"
}
---
+# column_statistics
+
## 概述
此表仅用于兼容 MySQL 行为，永远为空。并不能真实反映 Doris 内数据的统计信息。如需查看 Doris 收集的统计信息，请[查看统计信息章节](../../../query-acceleration/optimization-technology-principle/statistics#查看统计信息)。
@@ -23,4 +26,4 @@
| SCHEMA_NAME | varchar(64) | |
| TABLE_NAME | varchar(64) | |
| COLUMN_NAME | varchar(64) | |
-| HISTOGRAM | json | |
\ No newline at end of file
+| HISTOGRAM | json | |
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/system-tables/internal_schema/column_statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/system-tables/internal_schema/column_statistics.md
index 439989fa288..6c2c8f2d9bc 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/system-tables/internal_schema/column_statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/system-tables/internal_schema/column_statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "column_statistics",
+ "title": "column_statistics | Internal Schema",
"language": "zh-CN",
- "description": "列统计信息"
+ "description": "列统计信息",
+ "sidebar_label": "column_statistics"
}
---
+# column_statistics
+
## 概述
列统计信息
@@ -33,4 +36,4 @@
| min | varchar(65533) | 最小值 |
| max | varchar(65533) | 最大值 |
| data_size_in_bytes | bigint | 以字节计算的数据量 |
-| update_time | datetime | 当前统计信息的更新时间 |
\ No newline at end of file
+| update_time | datetime | 当前统计信息的更新时间 |
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/system-tables/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/system-tables/overview.md
index 4941656a8ba..0c00235ee62 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/system-tables/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/system-tables/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "概述",
+ "title": "概述 | System Tables",
"language": "zh-CN",
- "description": "Doris 集群内置多个系统数据库，用于存储 Doris 系统本身的一些元数据信息。"
+ "description": "Doris 集群内置多个系统数据库，用于存储 Doris 系统本身的一些元数据信息。",
+ "sidebar_label": "概述"
}
---
+# 概述
+
Doris 集群内置多个系统数据库，用于存储 Doris 系统本身的一些元数据信息。
## information_schema
@@ -35,3 +38,4 @@ Doris 会在集群创建时，自动创建这个库下的所有系统表。
默认情况下，普通用户对这个库下的表拥有只读权限。但被授权后，可以对这个库下的表进行修改、删除或创建。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/trouble-shooting/memory-management/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/trouble-shooting/memory-management/overview.md
index 460f1b7a790..348a7785563 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/trouble-shooting/memory-management/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/trouble-shooting/memory-management/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "概述",
+ "title": "概述 | Memory Management",
"language": "zh-CN",
- "description": "内存管理是 Doris 中最重要的组成部分之一，在 Doris 运行过程中，不论导入还是查询都依赖大量的内存操作。内存管理的好坏直接影响到 Doris 的稳定性和性能。"
+ "description": "内存管理是 Doris 中最重要的组成部分之一，在 Doris 运行过程中，不论导入还是查询都依赖大量的内存操作。内存管理的好坏直接影响到 Doris 的稳定性和性能。",
+ "sidebar_label": "概述"
}
---
+# 概述
+
内存管理是 Doris 中最重要的组成部分之一，在 Doris 运行过程中，不论导入还是查询都依赖大量的内存操作。内存管理的好坏直接影响到 Doris 的稳定性和性能。
Apache Doris 作为基于 MPP 架构的 OLAP 数据库，数据从磁盘加载到内存后，会在算子间流式传递并计算，在内存中存储计算的中间结果，这种方式减少了频繁的磁盘 I/O 操作，充分利用多机多核的并行计算能力，可在性能上呈现巨大优势。
@@ -143,3 +146,4 @@ Doris BE Process Memory
## 内存控制策略
参考 [内存控制策略](./memory-feature/memory-control-strategy.md) 中对内存分配、监控、回收的介绍，它们保证了 Doris BE 进程内存的高效可控。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/export/export-best-practice.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/export/export-best-practice.md
index e7a5982042a..cca825026e4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/export/export-best-practice.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/export/export-best-practice.md
@@ -1,11 +1,14 @@
---
{
- "title": "最佳实践",
+ "title": "最佳实践 | Export",
"language": "zh-CN",
- "description": "本文档主要用于介绍在进行数据导出操作中，如何判断资源利用是否合理，以及如何调整资源利用率已达到更好的数据导出效率。"
+ "description": "本文档主要用于介绍在进行数据导出操作中，如何判断资源利用是否合理，以及如何调整资源利用率已达到更好的数据导出效率。",
+ "sidebar_label": "最佳实践"
}
---
+# 最佳实践
+
本文档主要用于介绍在进行数据导出操作中，如何判断资源利用是否合理，以及如何调整资源利用率已达到更好的数据导出效率。
## SELECT INTO OUTFILE
@@ -95,3 +98,4 @@
FE 配置参数，表示当前集群能够同时运行的 Export Task 的数量，默认是是 64。一个 Export Job 会根据并发度拆分成多个 Export Task。所有 Export Task 共享这个阈值。如果希望提升集群整体的可并发执行导出任务的数量，可以调大这个参数，并重启 FE 节点。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/array.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/array.md
index 9ca52150754..3a3098fbf20 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/array.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/array.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Complex Types",
"language": "zh-CN",
- "description": "ARRAY<T> 表示由 T 类型元素组成的数组，不能作为 key 列使用。"
+ "description": "ARRAY<T> 表示由 T 类型元素组成的数组，不能作为 key 列使用。",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
`ARRAY<T>` 表示由 T 类型元素组成的数组，不能作为 key 列使用。
- 2.0 之前仅支持在 Duplicate 模型的表中使用。
@@ -127,3 +130,4 @@ mysql> SELECT * FROM array_test;
+------+-----------------+
4 rows in set (0.01 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/json.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/json.md
index f3954a3cdfb..b280abc0329 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/json.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/json.md
@@ -1,11 +1,14 @@
---
{
- "title": "JSON",
+ "title": "JSON | Complex Types",
"language": "zh-CN",
- "description": "JSON 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。"
+ "description": "JSON 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。",
+ "sidebar_label": "JSON"
}
---
+# JSON
+
`JSON` 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。
默认支持 1048576 字节（1 MB），可调大到 2147483643 字节（2 GB），可通过 BE 配置`string_type_length_soft_limit_bytes` 调整。
@@ -132,3 +135,4 @@ mysql> SELECT * FROM json_test;
+------+-------------------------------+
5 rows in set (0.01 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/map.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/map.md
index 15ddc9cfd00..9be7a4364dc 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/map.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/map.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Complex Types",
"language": "zh-CN",
- "description": "MAP<K, V> 表示由 K, V 类型元素组成的 map，不能作为 key 列使用。"
+ "description": "MAP<K, V> 表示由 K, V 类型元素组成的 map，不能作为 key 列使用。",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
`MAP<K, V>` 表示由 K, V 类型元素组成的 map，不能作为 key 列使用。
- 目前支持在 Duplicate，Unique 模型的表中使用。
@@ -126,3 +129,4 @@ mysql> SELECT * FROM map_test;
+------+-------------------------+
4 rows in set (0.01 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/struct.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/struct.md
index 34e05d4c0c8..dc7e1231cd9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/struct.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/struct.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Complex Types",
"language": "zh-CN",
- "description": "STRUCT<fieldname:fieldtype [COMMENT 'commentstring'], ... > 表示由多个 Field 组成的结构体，也可被理解为多个列的集合。"
+ "description": "STRUCT<fieldname:fieldtype [COMMENT 'commentstring'], ... > 表示由多个 Field 组成的结构体，也可被理解为多个列的集合。",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
`STRUCT<field_name:field_type [COMMENT 'comment_string'], ... >` 表示由多个 Field 组成的结构体，也可被理解为多个列的集合。
- 不能作为 Key 使用，目前 STRUCT 仅支持在 Duplicate 模型的表中使用。
@@ -134,3 +137,4 @@ mysql> SELECT * FROM struct_test;
+------+--------------------------------------+
5 rows in set (0.00 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/data-source/google-cloud-storage.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/data-source/google-cloud-storage.md
index 98d3272a75b..96261c66b68 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/data-source/google-cloud-storage.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/data-source/google-cloud-storage.md
@@ -1,11 +1,14 @@
---
{
- "title": "Google Cloud Storage",
+ "title": "Google Cloud Storage | Data Source",
"language": "zh-CN",
- "description": "Doris 提供两种方式从 Google Cloud Storage 导入文件："
+ "description": "Doris 提供两种方式从 Google Cloud Storage 导入文件：",
+ "sidebar_label": "Google Cloud Storage"
}
---
+# Google Cloud Storage
+
Doris 提供两种方式从 Google Cloud Storage 导入文件：
- 使用 S3 Load 将 Google Cloud Storage 文件导入到 Doris 中，这是一个异步的导入方式。
- 使用 TVF 将 Google Cloud Storage 文件导入到 Doris 中，这是一个同步的导入方式。
@@ -170,3 +173,4 @@ mysql> select * from test_s3load;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/data-source/hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/data-source/hdfs.md
index 558c26e4299..5f17a8e7250 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/data-source/hdfs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/data-source/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Data Source",
"language": "zh-CN",
- "description": "Doris 提供两种方式从 HDFS 导入文件："
+ "description": "Doris 提供两种方式从 HDFS 导入文件：",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
Doris 提供两种方式从 HDFS 导入文件：
- 使用 HDFS Load 将 HDFS 文件导入到 Doris 中，这是一个异步的导入方式。
- 使用 TVF 将 HDFS 文件导入到 Doris 中，这是一个同步的导入方式。
@@ -162,3 +165,4 @@ mysql> select * from test_hdfsload;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/data-source/minio.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/data-source/minio.md
index 595520c75d7..93303ace2d7 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/data-source/minio.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/data-source/minio.md
@@ -1,11 +1,14 @@
---
{
- "title": "MinIO",
+ "title": "MinIO | Data Source",
"language": "zh-CN",
- "description": "Doris 提供两种方式从 MinIO 导入文件："
+ "description": "Doris 提供两种方式从 MinIO 导入文件：",
+ "sidebar_label": "MinIO"
}
---
+# MinIO
+
Doris 提供两种方式从 MinIO 导入文件：
- 使用 S3 Load 将 MinIO 文件导入到 Doris 中，这是一个异步的导入方式。
- 使用 TVF 将 MinIO 文件导入到 Doris 中，这是一个同步的导入方式。
@@ -192,3 +195,4 @@ mysql> select * from test_s3load;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/file-format/json.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/file-format/json.md
index e529d8a9d00..4287c523dcd 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/file-format/json.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/file-format/json.md
@@ -1,8 +1,9 @@
---
{
- "title": "JSON",
+ "title": "JSON | File Format",
"language": "zh-CN",
- "description": "本文介绍如何在 Doris 中导入 JSON 格式的数据文件。Doris 支持导入标准 JSON 格式数据，通过配置相关参数，可以灵活地处理不同的 JSON 数据结构，并支持从 JSON 数据中抽取字段、处理嵌套结构等场景。"
+ "description": "本文介绍如何在 Doris 中导入 JSON 格式的数据文件。Doris 支持导入标准 JSON 格式数据，通过配置相关参数，可以灵活地处理不同的 JSON 数据结构，并支持从 JSON 数据中抽取字段、处理嵌套结构等场景。",
+ "sidebar_label": "JSON"
}
---
@@ -437,3 +438,4 @@ FROM S3
"json_root" = "$.events",
...
);
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/file-format/orc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/file-format/orc.md
index 4b6488a2cb2..500f74abf2c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/file-format/orc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/file-format/orc.md
@@ -1,11 +1,14 @@
---
{
- "title": "ORC",
+ "title": "ORC | File Format",
"language": "zh-CN",
- "description": "本文介绍如何在 Doris 中导入 ORC 格式的数据文件。"
+ "description": "本文介绍如何在 Doris 中导入 ORC 格式的数据文件。",
+ "sidebar_label": "ORC"
}
---
+# ORC
+
本文介绍如何在 Doris 中导入 ORC 格式的数据文件。
## 支持的导入方式
@@ -60,3 +63,4 @@ FROM S3
);
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/file-format/parquet.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/file-format/parquet.md
index ad990fe3875..7bb97a966d5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/file-format/parquet.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/file-format/parquet.md
@@ -1,11 +1,14 @@
---
{
- "title": "Parquet",
+ "title": "Parquet | File Format",
"language": "zh-CN",
- "description": "本文介绍如何在 Doris 中导入 Parquet 格式的数据文件。"
+ "description": "本文介绍如何在 Doris 中导入 Parquet 格式的数据文件。",
+ "sidebar_label": "Parquet"
}
---
+# Parquet
+
本文介绍如何在 Doris 中导入 Parquet 格式的数据文件。
## 支持的导入方式
@@ -56,4 +59,4 @@ FROM S3
"format" = "parquet",
...
);
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/file-formats/orc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/file-formats/orc.md
index cafd01e62de..7e2bfa5b36c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/file-formats/orc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/file-formats/orc.md
@@ -1,11 +1,14 @@
---
{
- "title": "ORC",
+ "title": "ORC | File Formats",
"language": "zh-CN",
- "description": "本文档用于介绍 Doris 的 ORC 文件格式的读写支持情况。该文档适用于以下功能。"
+ "description": "本文档用于介绍 Doris 的 ORC 文件格式的读写支持情况。该文档适用于以下功能。",
+ "sidebar_label": "ORC"
}
---
+# ORC
+
本文档用于介绍 Doris 的 ORC 文件格式的读写支持情况。该文档适用于以下功能。
* Catalog 中对数据的读取、写入操作。
@@ -69,3 +72,4 @@
* `orc_natural_read_size_mb` (2.1+, 3.0+)
ORC Reader 一次性读取的最大字节大小。默认 8 MB。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/file-formats/parquet.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/file-formats/parquet.md
index dee4524d0bc..2c029d1c5cf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/file-formats/parquet.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/file-formats/parquet.md
@@ -1,11 +1,14 @@
---
{
- "title": "Parquet",
+ "title": "Parquet | File Formats",
"language": "zh-CN",
- "description": "本文档用于介绍 Doris 的 Parquet 文件格式的读写支持情况。该文档适用于以下功能。"
+ "description": "本文档用于介绍 Doris 的 Parquet 文件格式的读写支持情况。该文档适用于以下功能。",
+ "sidebar_label": "Parquet"
}
---
+# Parquet
+
本文档用于介绍 Doris 的 Parquet 文件格式的读写支持情况。该文档适用于以下功能。
* Catalog 中对数据的读取、写入操作。
@@ -63,3 +66,4 @@
* `parquet_column_max_buffer_mb` (2.1+, 3.0+)
读取 Parquet Row Group 中的 Column 时所分配的最大 Buffer 大小，默认为 8M。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/statistics.md
index 2e928aa3798..04f9422952f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/statistics.md
@@ -1,12 +1,16 @@
---
{
- "title": "统计信息",
+ "title": "统计信息 | Lakehouse",
"language": "zh-CN",
- "description": "Doris 支持对外部数据源的表，如 Hive、Iceberg、Paimon 等进行自动或手动的统计信息收集。统计信息准确性直接决定了代价估算的准确性，对于选择最优查询计划至关重要，尤其在复杂查询场景下能显著提升查询执行效率。"
+ "description": "Doris 支持对外部数据源的表，如 Hive、Iceberg、Paimon 等进行自动或手动的统计信息收集。统计信息准确性直接决定了代价估算的准确性，对于选择最优查询计划至关重要，尤其在复杂查询场景下能显著提升查询执行效率。",
+ "sidebar_label": "统计信息"
}
---
+# 统计信息
+
Doris 支持对外部数据源的表，如 Hive、Iceberg、Paimon 等进行自动或手动的统计信息收集。统计信息准确性直接决定了代价估算的准确性，对于选择最优查询计划至关重要，尤其在复杂查询场景下能显著提升查询执行效率。
具体可参阅 [统计信息](../query-acceleration/optimization-technology-principle/statistics#外表收集) 文档中的【外表收集】部分。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/gcs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/gcs.md
index f06004bd9f6..35d0e2dc6f4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/gcs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/gcs.md
@@ -1,10 +1,14 @@
---
{
- "title": "Google Cloud Storage",
+ "title": "Google Cloud Storage | Storages",
"language": "zh-CN",
- "description": "文档更新中。"
+ "description": "文档更新中。",
+ "sidebar_label": "Google Cloud Storage"
}
---
+# Google Cloud Storage
+
文档更新中。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/hdfs.md
index 68e36b0304d..932aeeb06d6 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/hdfs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Storages",
"language": "zh-CN",
- "description": "本文档用于介绍访问 HDFS 时所需的参数。这些参数适用于："
+ "description": "本文档用于介绍访问 HDFS 时所需的参数。这些参数适用于：",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
本文档用于介绍访问 HDFS 时所需的参数。这些参数适用于：
* Catalog 属性。
@@ -216,3 +219,4 @@ Java 版本使用通过 Java 访问 HDFS，可以模拟 Doris FE 侧访问 HDFS
CPP 版本通过 C++ 调用 libhdfs 访问 HDFS，可以模拟 Doris BE 侧访问 HDFS 的逻辑。
具体使用方式可以各自代码库的 README。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/minio.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/minio.md
index 876139f0cc4..2c743026482 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/minio.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/minio.md
@@ -1,11 +1,14 @@
---
{
- "title": "MinIO",
+ "title": "MinIO | Storages",
"language": "zh-CN",
- "description": "本文档介绍访问 MinIO 所需的参数，这些参数适用于以下场景："
+ "description": "本文档介绍访问 MinIO 所需的参数，这些参数适用于以下场景：",
+ "sidebar_label": "MinIO"
}
---
+# MinIO
+
本文档介绍访问 MinIO 所需的参数，这些参数适用于以下场景：
- Catalog 属性
@@ -56,3 +59,4 @@ Minio 默认使用 Host-style 访问方式，但也支持 Path-style 访问。
* 推荐使用 `minio.` 前缀配置参数，保证与 MinIO 的一致性和清晰度。
* 3.1 之前的版本，请使用曾用名 `s3.` 作为前缀。
* 连接池参数可根据并发需求调整，避免连接阻塞。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/s3.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/s3.md
index 85544fd553f..a0d275f715d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/s3.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/storages/s3.md
@@ -1,11 +1,14 @@
---
{
- "title": "S3",
+ "title": "S3 | Storages",
"language": "zh-CN",
- "description": "本文档用于介绍访问 AWS S3 时所需的参数。这些参数适用于："
+ "description": "本文档用于介绍访问 AWS S3 时所需的参数。这些参数适用于：",
+ "sidebar_label": "S3"
}
---
+# S3
+
本文档用于介绍访问 AWS S3 时所需的参数。这些参数适用于：
- Catalog 属性。
@@ -153,3 +156,4 @@ Amazon S3 Express One Zone（又名 Directory Bucket）提供更高性能，但
- 如果只做查询，不要授予写权限。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/log-storage-analysis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/log-storage-analysis.md
index 2cb79c585c0..0ab89ed4e3f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/log-storage-analysis.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/log-storage-analysis.md
@@ -1,11 +1,14 @@
---
{
- "title": "日志存储与分析",
+ "title": "日志存储与分析 | Doris Docs",
"language": "zh-CN",
- "description": "在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤："
+ "description": "在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤：",
+ "sidebar_label": "日志存储与分析"
}
---
+# 日志存储与分析
+
### 第 1 步：评估资源
在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤：
@@ -461,3 +464,4 @@ ORDER BY ts DESC LIMIT 10;
您可以联系 dev@doris.apache.org 获得更多帮助。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/observability/log-storage-analysis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/observability/log-storage-analysis.md
index 22170faa62d..ac532a01f6a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/observability/log-storage-analysis.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/observability/log-storage-analysis.md
@@ -1,11 +1,14 @@
---
{
- "title": "日志存储与分析",
+ "title": "日志存储与分析 | Observability",
"language": "zh-CN",
- "description": "在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤："
+ "description": "在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤：",
+ "sidebar_label": "日志存储与分析"
}
---
+# 日志存储与分析
+
### 第 1 步：评估资源
在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤：
@@ -461,3 +464,4 @@ ORDER BY ts DESC LIMIT 10;
您可以联系 dev@doris.apache.org 获得更多帮助。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/observability/overview.mdx b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/observability/overview.mdx
index f7fe33ca2c9..f5752acde8d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/observability/overview.mdx
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/observability/overview.mdx
@@ -1,11 +1,14 @@
---
{
- "title": "概述",
+ "title": "概述 | Observability",
"language": "zh_CN",
- "description": "可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台通过采集、存储、可视化分析三大可关键数据：日志（Logging）、链路追踪（Tracing）和指标（Metrics），帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等，"
+ "description": "可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台通过采集、存储、可视化分析三大可关键数据：日志（Logging）、链路追踪（Tracing）和指标（Metrics），帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等，",
+ "sidebar_label": "概述"
}
---
+# 概述
+
## 什么是可观测性
可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台通过采集、存储、可视化分析三大可关键数据：日志（Logging）、链路追踪（Tracing）和指标（Metrics），帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等，提升系统可靠性和用户体验。
@@ -133,3 +136,4 @@ Grafana 的 Log 可视化和分析能力相对于 Kibana 来说是比较简单
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/query-acceleration/materialized-view/async-materialized-view/use-guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/query-acceleration/materialized-view/async-materialized-view/use-guide.md
index e04e6f06d07..cb910f92be3 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/query-acceleration/materialized-view/async-materialized-view/use-guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/query-acceleration/materialized-view/async-materialized-view/use-guide.md
@@ -1,11 +1,14 @@
---
{
- "title": "最佳实践",
+ "title": "最佳实践 | Async Materialized View",
"language": "zh-CN",
- "description": "当满足以下条件时，建议创建分区物化视图："
+ "description": "当满足以下条件时，建议创建分区物化视图：",
+ "sidebar_label": "最佳实践"
}
---
+# 最佳实践
+
## 异步物化视图使用原则
- **时效性考虑：** 异步物化视图通常用于对数据时效性要求不高的场景，一般是 T+1 的数据。如果时效性要求高，应考虑使用同步物化视图。
@@ -883,4 +886,4 @@ FROM common_schedule_join_mv;
DML 时，当物化视图存在无法实时感知数据的外表时，是否开启基于结构信息的物化视图透明改写，默认关闭
-`SET enable_dml_materialized_view_rewrite_when_base_table_unawareness = true;`
\ No newline at end of file
+`SET enable_dml_materialized_view_rewrite_when_base_table_unawareness = true;`
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/query-acceleration/optimization-technology-principle/statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/query-acceleration/optimization-technology-principle/statistics.md
index c91975ade97..bd23c1828ba 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/query-acceleration/optimization-technology-principle/statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/query-acceleration/optimization-technology-principle/statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "统计信息",
+ "title": "统计信息 | Optimization Technology Principle",
"language": "zh-CN",
- "description": "从 2.0 版本开始，Doris 在优化器中加入了 CBO 的能力。统计信息是 CBO 的基石，其准确性直接决定了代价估算的准确性，对于选择最优 Plan 至关重要。本文主要介绍统计信息的收集和管理方法、相关配置项以及常见问题。"
+ "description": "从 2.0 版本开始，Doris 在优化器中加入了 CBO 的能力。统计信息是 CBO 的基石，其准确性直接决定了代价估算的准确性，对于选择最优 Plan 至关重要。本文主要介绍统计信息的收集和管理方法、相关配置项以及常见问题。",
+ "sidebar_label": "统计信息"
}
---
+# 统计信息
+
从 2.0 版本开始，Doris 在优化器中加入了 CBO 的能力。统计信息是 CBO 的基石，其准确性直接决定了代价估算的准确性，对于选择最优 Plan 至关重要。本文主要介绍统计信息的收集和管理方法、相关配置项以及常见问题。
## 统计信息的收集
@@ -491,3 +494,4 @@ ADMIN DIAGNOSE TABLET tablet_id
对于某些特殊表，如分区众多的表或单个 Tablet 体积庞大的表，可能会出现内存占用较多的情况。
建议用户在建表时合理规划 Tablet 数量，避免产生超大 Tablet。若 Tablet 结构不易调整，建议在系统低峰期开启自动收集，或于低峰期手动收集这些大表，以免在高峰期影响业务运行。在 Doris 3.x 系列中，我们将针对此类场景进行优化。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/date-time/DATE.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/date-time/DATE.md
index f1af6391ec5..fb0d51e123c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/date-time/DATE.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/date-time/DATE.md
@@ -1,11 +1,14 @@
---
{
- "title": "DATE",
+ "title": "DATE | Date Time",
"language": "zh-CN",
- "description": "DATE"
+ "description": "DATE",
+ "sidebar_label": "DATE"
}
---
+# DATE
+
## DATE
### name
@@ -30,3 +33,4 @@ SELECT DATE('2003-12-31 01:02:03');
### keywords
DATE
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
index c4a60778f3a..3e60ebdd7e0 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Semi Structured",
"language": "zh-CN",
- "description": "由 T 类型元素组成的数组，不能作为 key 列使用。目前支持在 Duplicate 和 Unique 模型的表中使用。"
+ "description": "由 T 类型元素组成的数组，不能作为 key 列使用。目前支持在 Duplicate 和 Unique 模型的表中使用。",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
## 描述
`ARRAY<T>`
@@ -61,3 +64,4 @@ mysql> SELECT * FROM `array_test`;
+------+-----------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
index 63e311f844d..9050a348091 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
@@ -1,11 +1,14 @@
---
{
- "title": "JSON",
+ "title": "JSON | Semi Structured",
"language": "zh-CN",
- "description": "JSON 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。"
+ "description": "JSON 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。",
+ "sidebar_label": "JSON"
}
---
+# JSON
+
JSON 数据类型，用二进制格式高效存储 [JSON](https://www.rfc-editor.org/rfc/rfc8785) 数据，通过 JSON 函数访问其内部字段。
默认支持 1048576 字节（1 MB），可调大到 2147483643 字节（2 GB），可通过 BE 配置`string_type_length_soft_limit_bytes` 调整。
@@ -860,3 +863,4 @@ mysql> SELECT JSON_EXTRACT_STRING('{"key1" : null}', "$.key_not_exist") IS NULL;
### keywords
JSON, json_parse, json_parse_error_to_null, json_parse_error_to_value, json_extract, json_extract_isnull, json_extract_bool, json_extract_int, json_extract_bigint, json_extract_double, json_extract_String, json_exists_path, json_type
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
index b06a84d644d..b919680842b 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
@@ -1,8 +1,9 @@
---
{
- "title": "MAP",
+ "title": "MAP | Semi Structured",
"language": "zh-CN",
- "description": "MAP"
+ "description": "MAP",
+ "sidebar_label": "MAP"
}
---
@@ -248,3 +249,4 @@ mysql> SELECT id, map_values(m) FROM simple_map ORDER BY id;
### keywords
MAP
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
index 2a36322ecf7..1037e1f10f8 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Semi Structured",
"language": "zh-CN",
- "description": "STRUCT"
+ "description": "STRUCT",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
## STRUCT
### name
@@ -101,3 +104,4 @@ mysql> select * from struct_test;
### keywords
STRUCT
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/string-type/CHAR.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
index cd06dcfb960..2b86fcaca5e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
@@ -1,11 +1,14 @@
---
{
- "title": "CHAR",
+ "title": "CHAR | String Type",
"language": "zh-CN",
- "description": "CHAR(M)"
+ "description": "CHAR(M)",
+ "sidebar_label": "CHAR"
}
---
+# CHAR
+
## description
CHAR(M)
@@ -15,3 +18,4 @@ CHAR(M)
## keywords
CHAR
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/array-functions/array.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/array-functions/array.md
index a2fa0db987c..7cfde2ade24 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/array-functions/array.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/array-functions/array.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Array Functions",
"language": "zh-CN",
- "description": "根据参数构造并返回 array, 参数可以是多列或者常量"
+ "description": "根据参数构造并返回 array, 参数可以是多列或者常量",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
## 描述
根据参数构造并返回 array, 参数可以是多列或者常量
@@ -72,3 +75,4 @@ select array(qid, creationDate, null) from nested limit 4;
+-------------------------------------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
index acbc4fc015d..2d01c36f9d1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
@@ -1,11 +1,14 @@
---
{
- "title": "DATE",
+ "title": "DATE | Date Time Functions",
"language": "zh-CN",
- "description": "提取日期时间中的日期。"
+ "description": "提取日期时间中的日期。",
+ "sidebar_label": "DATE"
}
---
+# DATE
+
## 描述
提取日期时间中的日期。
@@ -38,4 +41,4 @@ select date('2010-12-02 19:28:30');
+----------------------------------------------------+
| 2010-12-02 |
+----------------------------------------------------+
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/map-functions/map.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/map-functions/map.md
index eb2f3aa03d1..40e74d1bcf1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/map-functions/map.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/map-functions/map.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Map Functions",
"language": "zh-CN",
- "description": "使用若干组键值对构造一个特定类型的 Map<K, V>"
+ "description": "使用若干组键值对构造一个特定类型的 Map<K, V>",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
## 描述
使用若干组键值对构造一个特定类型的 `Map<K, V>`
@@ -40,3 +43,4 @@ select map(1, "100", 0.1, 2),map(1, "100", 0.1, 2)[1];
| {1.0:"100", 0.1:"2"} | 100 |
+---------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/string-functions/char.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/string-functions/char.md
index ac7443f94ff..c222b39ca30 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/string-functions/char.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/string-functions/char.md
@@ -1,11 +1,14 @@
---
{
- "title": "CHAR",
+ "title": "CHAR | String Functions",
"language": "zh-CN",
- "description": "将每个参数解释为整数，并返回一个字符串，该字符串由这些整数的代码值给出的字符组成。特殊情况："
+ "description": "将每个参数解释为整数，并返回一个字符串，该字符串由这些整数的代码值给出的字符组成。特殊情况：",
+ "sidebar_label": "CHAR"
}
---
+# CHAR
+
## 描述
将每个参数解释为整数，并返回一个字符串，该字符串由这些整数的代码值给出的字符组成。特殊情况：
@@ -48,4 +51,4 @@ SELECT CHAR(68, 111, 114, 105, 115),CHAR(15049882, 15179199, 14989469),CHAR(255)
+--------------------------------------+--------------------------------------------+-------------------+
| Doris | 多睿丝 | NULL |
+--------------------------------------+--------------------------------------------+-------------------+
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
index a6b128ace74..4510e2493ff 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Struct Functions",
"language": "zh-CN",
- "description": "根据给定的值构造并返回 struct，参数可以是多列或常量"
+ "description": "根据给定的值构造并返回 struct，参数可以是多列或常量",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
## 描述
根据给定的值构造并返回 struct，参数可以是多列或常量
@@ -39,3 +42,4 @@ select struct(1, 'a', "abc"),struct(null, 1, null),struct(cast('2023-03-16' as d
| {"col1":1, "col2":"a", "col3":"abc"} | {"col1":null, "col2":1, "col3":null} | {"col1":"2023-03-16 00:00:00"} |
+--------------------------------------+--------------------------------------+---------------------------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/table-valued-functions/hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/table-valued-functions/hdfs.md
index 3ae6dba7dde..61961401572 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/table-valued-functions/hdfs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/table-valued-functions/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Table Valued Functions",
"language": "zh-CN",
- "description": "HDFS 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 HDFS 上的文件内容。目前支持csv/csvwithnames/csvwithnamesandtypes/json/parquet/orc文件格式。"
+ "description": "HDFS 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 HDFS 上的文件内容。目前支持csv/csvwithnames/csvwithnamesandtypes/json/parquet/orc文件格式。",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
## 描述
HDFS 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 HDFS 上的文件内容。目前支持`csv/csv_with_names/csv_with_names_and_types/json/parquet/orc`文件格式。
@@ -124,3 +127,4 @@ HDFS(
"hadoop.username" = "doris",
"format" = "csv_with_names");
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/table-valued-functions/s3.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/table-valued-functions/s3.md
index d094a6667ca..b431becba8e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/table-valued-functions/s3.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/sql-manual/sql-functions/table-valued-functions/s3.md
@@ -1,11 +1,14 @@
---
{
- "title": "S3",
+ "title": "S3 | Table Valued Functions",
"language": "zh-CN",
- "description": "S3 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 S3 兼容的对象存储上的文件内容。目前支持 csv/csv_with_names/csv_with_names_and_types/json/parquet/orc 文件格式。"
+ "description": "S3 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 S3 兼容的对象存储上的文件内容。目前支持 csv/csv_with_names/csv_with_names_and_types/json/parquet/orc 文件格式。",
+ "sidebar_label": "S3"
}
---
+# S3
+
## 描述
S3 表函数（table-valued-function, tvf）可以让用户像访问关系表格式数据一样，读取并访问 S3 兼容的对象存储上的文件内容。目前支持 `csv/csv_with_names/csv_with_names_and_types/json/parquet/orc` 文件格式。
@@ -592,3 +595,4 @@ S3(
"read_json_by_line" = "true",
"use_path_style" = "true");
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/config/fe-config-template.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/config/fe-config-template.md
index 42689c0ba21..5c8c5ed5826 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/config/fe-config-template.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/config/fe-config-template.md
@@ -1,10 +1,11 @@
---
{
- "title": "FE 配置项",
+ "title": "FE 配置项 | Config",
"language": "zh-CN",
"toc_min_heading_level": 2,
"toc_max_heading_level": 4,
- "description": "该文档主要介绍 FE 的相关配置项。"
+ "description": "该文档主要介绍 FE 的相关配置项。",
+ "sidebar_label": "FE 配置项"
}
---
@@ -118,3 +119,4 @@ FE 的配置项有两种方式进行配置：
> 如需修改，请修改 `fe/fe-common/src/main/java/org/apache/doris/common/Config.java` 中的描述信息。
<--DOC_PLACEHOLDER-->
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/config/fe-config.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/config/fe-config.md
index 99b0efa98b1..77d2b32e7f3 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/config/fe-config.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/config/fe-config.md
@@ -1,10 +1,11 @@
---
{
- "title": "FE 配置项",
+ "title": "FE 配置项 | Config",
"language": "zh-CN",
"toc_min_heading_level": 2,
"toc_max_heading_level": 4,
- "description": "该文档主要介绍 FE 的相关配置项。"
+ "description": "该文档主要介绍 FE 的相关配置项。",
+ "sidebar_label": "FE 配置项"
}
---
@@ -2772,3 +2773,4 @@ Doris 为了兼用 mysql 周边工具生态，会内置一个名为 mysql 的数
默认值： ""
Meta Service 的端点应以 'host1:port,host2:port' 的格式指定。此配置对于存算分离模式是必要的。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/meta-info-action-V2.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/meta-info-action-V2.md
index 09963040bf6..2bd99841252 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/meta-info-action-V2.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/meta-info-action-V2.md
@@ -1,11 +1,14 @@
---
{
- "title": "Meta Info Action",
+ "title": "Meta Info Action | Fe Http",
"language": "zh-CN",
- "description": "获取集群内的元数据信息，包括数据库列表、表列表以及表结构等。"
+ "description": "获取集群内的元数据信息，包括数据库列表、表列表以及表结构等。",
+ "sidebar_label": "Meta Info Action"
}
---
+# Meta Info Action
+
## Request
`GET /api/meta/namespaces/<ns>/databases`
@@ -50,3 +53,4 @@
"count":0
}
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/meta-info-action.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/meta-info-action.md
index d9c622d3cec..4e477f2f180 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/meta-info-action.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/meta-info-action.md
@@ -1,11 +1,14 @@
---
{
- "title": "Meta Info Action",
+ "title": "Meta Info Action | Fe Http",
"language": "zh-CN",
- "description": "Meta Info Action 用于获取集群内的元数据信息。如数据库列表，表结构等。"
+ "description": "Meta Info Action 用于获取集群内的元数据信息。如数据库列表，表结构等。",
+ "sidebar_label": "Meta Info Action"
}
---
+# Meta Info Action
+
Meta Info Action 用于获取集群内的元数据信息。如数据库列表，表结构等。
## 数据库列表
@@ -210,3 +213,4 @@ GET /api/meta/namespaces/default/databases/db1/tables/tbl1/schema?with_mv?=1
```
* data 字段返回 base 表或 rollup 表的表结构信息。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/query-profile-action-controller.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/query-profile-action-controller.md
index 368412b2cd3..ee60a32ebd1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/query-profile-action-controller.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/query-profile-action-controller.md
@@ -1,11 +1,14 @@
---
{
- "title": "Query Profile Action",
+ "title": "Query Profile Action | Fe Http",
"language": "zh-CN",
- "description": "Query Profile Action 用于获取 Query 的 profile"
+ "description": "Query Profile Action 用于获取 Query 的 profile",
+ "sidebar_label": "Query Profile Action"
}
---
+# Query Profile Action
+
## Request
```
@@ -85,4 +88,4 @@ Query Profile Action 用于获取 Query 的 profile
}
```
- `data` is the text content of the profile.
\ No newline at end of file
+ `data` is the text content of the profile.
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/query-profile-action.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/query-profile-action.md
index 24f420b306e..81b4423c9bf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/query-profile-action.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/open-api/fe-http/query-profile-action.md
@@ -1,11 +1,14 @@
---
{
- "title": "Query Profile Action",
+ "title": "Query Profile Action | Fe Http",
"language": "zh-CN",
- "description": "可获取集群所有 fe 节点 select 查询信息。"
+ "description": "可获取集群所有 fe 节点 select 查询信息。",
+ "sidebar_label": "Query Profile Action"
}
---
+# Query Profile Action
+
## Request
`GET /rest/v2/manager/query/query_info`
@@ -457,3 +460,4 @@ Admin 和 Root 用户可以查看所有 Query。普通用户仅能查看自己
}
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/system-tables/information_schema/column_statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/system-tables/information_schema/column_statistics.md
index e4c88305642..bfc4a3b1fd0 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/system-tables/information_schema/column_statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/system-tables/information_schema/column_statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "column_statistics",
+ "title": "column_statistics | Information Schema",
"language": "zh-CN",
- "description": "此表仅用于兼容 MySQL 行为，永远为空。并不能真实反映 Doris 内数据的统计信息。如需查看 Doris 收集的统计信息，请查看统计信息章节。"
+ "description": "此表仅用于兼容 MySQL 行为，永远为空。并不能真实反映 Doris 内数据的统计信息。如需查看 Doris 收集的统计信息，请查看统计信息章节。",
+ "sidebar_label": "column_statistics"
}
---
+# column_statistics
+
## 概述
此表仅用于兼容 MySQL 行为，永远为空。并不能真实反映 Doris 内数据的统计信息。如需查看 Doris 收集的统计信息，请[查看统计信息章节](../../../query-acceleration/optimization-technology-principle/statistics#查看统计信息)。
@@ -23,4 +26,4 @@
| SCHEMA_NAME | varchar(64) | |
| TABLE_NAME | varchar(64) | |
| COLUMN_NAME | varchar(64) | |
-| HISTOGRAM | json | |
\ No newline at end of file
+| HISTOGRAM | json | |
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/system-tables/internal_schema/column_statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/system-tables/internal_schema/column_statistics.md
index 439989fa288..6c2c8f2d9bc 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/system-tables/internal_schema/column_statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/system-tables/internal_schema/column_statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "column_statistics",
+ "title": "column_statistics | Internal Schema",
"language": "zh-CN",
- "description": "列统计信息"
+ "description": "列统计信息",
+ "sidebar_label": "column_statistics"
}
---
+# column_statistics
+
## 概述
列统计信息
@@ -33,4 +36,4 @@
| min | varchar(65533) | 最小值 |
| max | varchar(65533) | 最大值 |
| data_size_in_bytes | bigint | 以字节计算的数据量 |
-| update_time | datetime | 当前统计信息的更新时间 |
\ No newline at end of file
+| update_time | datetime | 当前统计信息的更新时间 |
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/system-tables/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/system-tables/overview.md
index 4941656a8ba..0c00235ee62 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/system-tables/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/system-tables/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "概述",
+ "title": "概述 | System Tables",
"language": "zh-CN",
- "description": "Doris 集群内置多个系统数据库，用于存储 Doris 系统本身的一些元数据信息。"
+ "description": "Doris 集群内置多个系统数据库，用于存储 Doris 系统本身的一些元数据信息。",
+ "sidebar_label": "概述"
}
---
+# 概述
+
Doris 集群内置多个系统数据库，用于存储 Doris 系统本身的一些元数据信息。
## information_schema
@@ -35,3 +38,4 @@ Doris 会在集群创建时，自动创建这个库下的所有系统表。
默认情况下，普通用户对这个库下的表拥有只读权限。但被授权后，可以对这个库下的表进行修改、删除或创建。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/trouble-shooting/memory-management/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/trouble-shooting/memory-management/overview.md
index 460f1b7a790..348a7785563 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/trouble-shooting/memory-management/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/trouble-shooting/memory-management/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "概述",
+ "title": "概述 | Memory Management",
"language": "zh-CN",
- "description": "内存管理是 Doris 中最重要的组成部分之一，在 Doris 运行过程中，不论导入还是查询都依赖大量的内存操作。内存管理的好坏直接影响到 Doris 的稳定性和性能。"
+ "description": "内存管理是 Doris 中最重要的组成部分之一，在 Doris 运行过程中，不论导入还是查询都依赖大量的内存操作。内存管理的好坏直接影响到 Doris 的稳定性和性能。",
+ "sidebar_label": "概述"
}
---
+# 概述
+
内存管理是 Doris 中最重要的组成部分之一，在 Doris 运行过程中，不论导入还是查询都依赖大量的内存操作。内存管理的好坏直接影响到 Doris 的稳定性和性能。
Apache Doris 作为基于 MPP 架构的 OLAP 数据库，数据从磁盘加载到内存后，会在算子间流式传递并计算，在内存中存储计算的中间结果，这种方式减少了频繁的磁盘 I/O 操作，充分利用多机多核的并行计算能力，可在性能上呈现巨大优势。
@@ -143,3 +146,4 @@ Doris BE Process Memory
## 内存控制策略
参考 [内存控制策略](./memory-feature/memory-control-strategy.md) 中对内存分配、监控、回收的介绍，它们保证了 Doris BE 进程内存的高效可控。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/compute-storage-decoupled/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/compute-storage-decoupled/overview.md
index 3f4887962dc..9eeb24e65d7 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/compute-storage-decoupled/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/compute-storage-decoupled/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "概览",
+ "title": "概览 | Compute Storage Decoupled",
"language": "zh-CN",
- "description": "本文介绍存算分离与存算一体两种架构的区别、优势和适用场景，为用户的选择与使用提供参考。后文将详细说明如何部署并使用 Apache Doris 存算分离模式。如需部署存算一体模式，请参考集群部署。"
+ "description": "本文介绍存算分离与存算一体两种架构的区别、优势和适用场景，为用户的选择与使用提供参考。后文将详细说明如何部署并使用 Apache Doris 存算分离模式。如需部署存算一体模式，请参考集群部署。",
+ "sidebar_label": "概览"
}
---
+# 概览
+
本文介绍存算分离与存算一体两种架构的区别、优势和适用场景，为用户的选择与使用提供参考。后文将详细说明如何部署并使用 Apache Doris 存算分离模式。如需部署存算一体模式，请参考[集群部署](../../current/install/deploy-manually/integrated-storage-compute-deploy-manually)。
## 存算一体 VS 存算分离
@@ -72,4 +75,4 @@ Meta Service 是 Doris 存算分离元数据服务，主要负责处理导入事
- 已使用公有云服务
- 具备可靠的共享存储系统，比如 HDFS、Ceph、对象存储等
- 需要极致的弹性扩缩容，需要 K8S 容器化，需要运行在私有云上
-- 有专职团队维护整个公司的数据仓库平台
\ No newline at end of file
+- 有专职团队维护整个公司的数据仓库平台
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/export/export-best-practice.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/export/export-best-practice.md
index e7a5982042a..cca825026e4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/export/export-best-practice.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/export/export-best-practice.md
@@ -1,11 +1,14 @@
---
{
- "title": "最佳实践",
+ "title": "最佳实践 | Export",
"language": "zh-CN",
- "description": "本文档主要用于介绍在进行数据导出操作中，如何判断资源利用是否合理，以及如何调整资源利用率已达到更好的数据导出效率。"
+ "description": "本文档主要用于介绍在进行数据导出操作中，如何判断资源利用是否合理，以及如何调整资源利用率已达到更好的数据导出效率。",
+ "sidebar_label": "最佳实践"
}
---
+# 最佳实践
+
本文档主要用于介绍在进行数据导出操作中，如何判断资源利用是否合理，以及如何调整资源利用率已达到更好的数据导出效率。
## SELECT INTO OUTFILE
@@ -95,3 +98,4 @@
FE 配置参数，表示当前集群能够同时运行的 Export Task 的数量，默认是是 64。一个 Export Job 会根据并发度拆分成多个 Export Task。所有 Export Task 共享这个阈值。如果希望提升集群整体的可并发执行导出任务的数量，可以调大这个参数，并重启 FE 节点。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/array.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/array.md
index 9ca52150754..3a3098fbf20 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/array.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/array.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Complex Types",
"language": "zh-CN",
- "description": "ARRAY<T> 表示由 T 类型元素组成的数组，不能作为 key 列使用。"
+ "description": "ARRAY<T> 表示由 T 类型元素组成的数组，不能作为 key 列使用。",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
`ARRAY<T>` 表示由 T 类型元素组成的数组，不能作为 key 列使用。
- 2.0 之前仅支持在 Duplicate 模型的表中使用。
@@ -127,3 +130,4 @@ mysql> SELECT * FROM array_test;
+------+-----------------+
4 rows in set (0.01 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/json.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/json.md
index f3954a3cdfb..b280abc0329 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/json.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/json.md
@@ -1,11 +1,14 @@
---
{
- "title": "JSON",
+ "title": "JSON | Complex Types",
"language": "zh-CN",
- "description": "JSON 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。"
+ "description": "JSON 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。",
+ "sidebar_label": "JSON"
}
---
+# JSON
+
`JSON` 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。
默认支持 1048576 字节（1 MB），可调大到 2147483643 字节（2 GB），可通过 BE 配置`string_type_length_soft_limit_bytes` 调整。
@@ -132,3 +135,4 @@ mysql> SELECT * FROM json_test;
+------+-------------------------------+
5 rows in set (0.01 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/map.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/map.md
index 15ddc9cfd00..9be7a4364dc 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/map.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/map.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Complex Types",
"language": "zh-CN",
- "description": "MAP<K, V> 表示由 K, V 类型元素组成的 map，不能作为 key 列使用。"
+ "description": "MAP<K, V> 表示由 K, V 类型元素组成的 map，不能作为 key 列使用。",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
`MAP<K, V>` 表示由 K, V 类型元素组成的 map，不能作为 key 列使用。
- 目前支持在 Duplicate，Unique 模型的表中使用。
@@ -126,3 +129,4 @@ mysql> SELECT * FROM map_test;
+------+-------------------------+
4 rows in set (0.01 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/struct.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/struct.md
index c3bc1e8ac34..e2d7fe2d08d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/struct.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/complex-types/struct.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Complex Types",
"language": "zh-CN",
- "description": "STRUCT<fieldname:fieldtype [COMMENT 'commentstring'], ... > 表示由多个 Field 组成的结构体，也可被理解为多个列的集合。"
+ "description": "STRUCT<fieldname:fieldtype [COMMENT 'commentstring'], ... > 表示由多个 Field 组成的结构体，也可被理解为多个列的集合。",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
`STRUCT<field_name:field_type [COMMENT 'comment_string'], ... >` 表示由多个 Field 组成的结构体，也可被理解为多个列的集合。
- 不能作为 Key 使用，目前 STRUCT 仅支持在 Duplicate 模型的表中使用。
@@ -140,3 +143,4 @@ mysql> SELECT * FROM struct_test;
+------+--------------------------------------+
5 rows in set (0.00 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/data-source/google-cloud-storage.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/data-source/google-cloud-storage.md
index 98d3272a75b..96261c66b68 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/data-source/google-cloud-storage.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/data-source/google-cloud-storage.md
@@ -1,11 +1,14 @@
---
{
- "title": "Google Cloud Storage",
+ "title": "Google Cloud Storage | Data Source",
"language": "zh-CN",
- "description": "Doris 提供两种方式从 Google Cloud Storage 导入文件："
+ "description": "Doris 提供两种方式从 Google Cloud Storage 导入文件：",
+ "sidebar_label": "Google Cloud Storage"
}
---
+# Google Cloud Storage
+
Doris 提供两种方式从 Google Cloud Storage 导入文件：
- 使用 S3 Load 将 Google Cloud Storage 文件导入到 Doris 中，这是一个异步的导入方式。
- 使用 TVF 将 Google Cloud Storage 文件导入到 Doris 中，这是一个同步的导入方式。
@@ -170,3 +173,4 @@ mysql> select * from test_s3load;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/data-source/hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/data-source/hdfs.md
index 558c26e4299..5f17a8e7250 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/data-source/hdfs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/data-source/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Data Source",
"language": "zh-CN",
- "description": "Doris 提供两种方式从 HDFS 导入文件："
+ "description": "Doris 提供两种方式从 HDFS 导入文件：",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
Doris 提供两种方式从 HDFS 导入文件：
- 使用 HDFS Load 将 HDFS 文件导入到 Doris 中，这是一个异步的导入方式。
- 使用 TVF 将 HDFS 文件导入到 Doris 中，这是一个同步的导入方式。
@@ -162,3 +165,4 @@ mysql> select * from test_hdfsload;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/data-source/minio.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/data-source/minio.md
index 595520c75d7..93303ace2d7 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/data-source/minio.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/data-source/minio.md
@@ -1,11 +1,14 @@
---
{
- "title": "MinIO",
+ "title": "MinIO | Data Source",
"language": "zh-CN",
- "description": "Doris 提供两种方式从 MinIO 导入文件："
+ "description": "Doris 提供两种方式从 MinIO 导入文件：",
+ "sidebar_label": "MinIO"
}
---
+# MinIO
+
Doris 提供两种方式从 MinIO 导入文件：
- 使用 S3 Load 将 MinIO 文件导入到 Doris 中，这是一个异步的导入方式。
- 使用 TVF 将 MinIO 文件导入到 Doris 中，这是一个同步的导入方式。
@@ -192,3 +195,4 @@ mysql> select * from test_s3load;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/file-format/json.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/file-format/json.md
index 3b025f318bf..4ce3c705ba5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/file-format/json.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/file-format/json.md
@@ -1,8 +1,9 @@
---
{
- "title": "JSON",
+ "title": "JSON | File Format",
"language": "zh-CN",
- "description": "本文介绍如何在 Doris 中导入 JSON 格式的数据文件。Doris 支持导入标准 JSON 格式数据，通过配置相关参数，可以灵活地处理不同的 JSON 数据结构，并支持从 JSON 数据中抽取字段、处理嵌套结构等场景。"
+ "description": "本文介绍如何在 Doris 中导入 JSON 格式的数据文件。Doris 支持导入标准 JSON 格式数据，通过配置相关参数，可以灵活地处理不同的 JSON 数据结构，并支持从 JSON 数据中抽取字段、处理嵌套结构等场景。",
+ "sidebar_label": "JSON"
}
---
@@ -437,3 +438,4 @@ FROM S3
"json_root" = "$.events",
...
);
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/file-format/orc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/file-format/orc.md
index 4b6488a2cb2..500f74abf2c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/file-format/orc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/file-format/orc.md
@@ -1,11 +1,14 @@
---
{
- "title": "ORC",
+ "title": "ORC | File Format",
"language": "zh-CN",
- "description": "本文介绍如何在 Doris 中导入 ORC 格式的数据文件。"
+ "description": "本文介绍如何在 Doris 中导入 ORC 格式的数据文件。",
+ "sidebar_label": "ORC"
}
---
+# ORC
+
本文介绍如何在 Doris 中导入 ORC 格式的数据文件。
## 支持的导入方式
@@ -60,3 +63,4 @@ FROM S3
);
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/file-format/parquet.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/file-format/parquet.md
index ad990fe3875..7bb97a966d5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/file-format/parquet.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/import/file-format/parquet.md
@@ -1,11 +1,14 @@
---
{
- "title": "Parquet",
+ "title": "Parquet | File Format",
"language": "zh-CN",
- "description": "本文介绍如何在 Doris 中导入 Parquet 格式的数据文件。"
+ "description": "本文介绍如何在 Doris 中导入 Parquet 格式的数据文件。",
+ "sidebar_label": "Parquet"
}
---
+# Parquet
+
本文介绍如何在 Doris 中导入 Parquet 格式的数据文件。
## 支持的导入方式
@@ -56,4 +59,4 @@ FROM S3
"format" = "parquet",
...
);
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/file-formats/orc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/file-formats/orc.md
index cafd01e62de..7e2bfa5b36c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/file-formats/orc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/file-formats/orc.md
@@ -1,11 +1,14 @@
---
{
- "title": "ORC",
+ "title": "ORC | File Formats",
"language": "zh-CN",
- "description": "本文档用于介绍 Doris 的 ORC 文件格式的读写支持情况。该文档适用于以下功能。"
+ "description": "本文档用于介绍 Doris 的 ORC 文件格式的读写支持情况。该文档适用于以下功能。",
+ "sidebar_label": "ORC"
}
---
+# ORC
+
本文档用于介绍 Doris 的 ORC 文件格式的读写支持情况。该文档适用于以下功能。
* Catalog 中对数据的读取、写入操作。
@@ -69,3 +72,4 @@
* `orc_natural_read_size_mb` (2.1+, 3.0+)
ORC Reader 一次性读取的最大字节大小。默认 8 MB。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/file-formats/parquet.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/file-formats/parquet.md
index dee4524d0bc..2c029d1c5cf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/file-formats/parquet.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/file-formats/parquet.md
@@ -1,11 +1,14 @@
---
{
- "title": "Parquet",
+ "title": "Parquet | File Formats",
"language": "zh-CN",
- "description": "本文档用于介绍 Doris 的 Parquet 文件格式的读写支持情况。该文档适用于以下功能。"
+ "description": "本文档用于介绍 Doris 的 Parquet 文件格式的读写支持情况。该文档适用于以下功能。",
+ "sidebar_label": "Parquet"
}
---
+# Parquet
+
本文档用于介绍 Doris 的 Parquet 文件格式的读写支持情况。该文档适用于以下功能。
* Catalog 中对数据的读取、写入操作。
@@ -63,3 +66,4 @@
* `parquet_column_max_buffer_mb` (2.1+, 3.0+)
读取 Parquet Row Group 中的 Column 时所分配的最大 Buffer 大小，默认为 8M。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/statistics.md
index 2e928aa3798..04f9422952f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/statistics.md
@@ -1,12 +1,16 @@
---
{
- "title": "统计信息",
+ "title": "统计信息 | Lakehouse",
"language": "zh-CN",
- "description": "Doris 支持对外部数据源的表，如 Hive、Iceberg、Paimon 等进行自动或手动的统计信息收集。统计信息准确性直接决定了代价估算的准确性，对于选择最优查询计划至关重要，尤其在复杂查询场景下能显著提升查询执行效率。"
+ "description": "Doris 支持对外部数据源的表，如 Hive、Iceberg、Paimon 等进行自动或手动的统计信息收集。统计信息准确性直接决定了代价估算的准确性，对于选择最优查询计划至关重要，尤其在复杂查询场景下能显著提升查询执行效率。",
+ "sidebar_label": "统计信息"
}
---
+# 统计信息
+
Doris 支持对外部数据源的表，如 Hive、Iceberg、Paimon 等进行自动或手动的统计信息收集。统计信息准确性直接决定了代价估算的准确性，对于选择最优查询计划至关重要，尤其在复杂查询场景下能显著提升查询执行效率。
具体可参阅 [统计信息](../query-acceleration/optimization-technology-principle/statistics#外表收集) 文档中的【外表收集】部分。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/gcs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/gcs.md
index f06004bd9f6..35d0e2dc6f4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/gcs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/gcs.md
@@ -1,10 +1,14 @@
---
{
- "title": "Google Cloud Storage",
+ "title": "Google Cloud Storage | Storages",
"language": "zh-CN",
- "description": "文档更新中。"
+ "description": "文档更新中。",
+ "sidebar_label": "Google Cloud Storage"
}
---
+# Google Cloud Storage
+
文档更新中。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/hdfs.md
index 68e36b0304d..932aeeb06d6 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/hdfs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Storages",
"language": "zh-CN",
- "description": "本文档用于介绍访问 HDFS 时所需的参数。这些参数适用于："
+ "description": "本文档用于介绍访问 HDFS 时所需的参数。这些参数适用于：",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
本文档用于介绍访问 HDFS 时所需的参数。这些参数适用于：
* Catalog 属性。
@@ -216,3 +219,4 @@ Java 版本使用通过 Java 访问 HDFS，可以模拟 Doris FE 侧访问 HDFS
CPP 版本通过 C++ 调用 libhdfs 访问 HDFS，可以模拟 Doris BE 侧访问 HDFS 的逻辑。
具体使用方式可以各自代码库的 README。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/minio.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/minio.md
index 876139f0cc4..2c743026482 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/minio.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/minio.md
@@ -1,11 +1,14 @@
---
{
- "title": "MinIO",
+ "title": "MinIO | Storages",
"language": "zh-CN",
- "description": "本文档介绍访问 MinIO 所需的参数，这些参数适用于以下场景："
+ "description": "本文档介绍访问 MinIO 所需的参数，这些参数适用于以下场景：",
+ "sidebar_label": "MinIO"
}
---
+# MinIO
+
本文档介绍访问 MinIO 所需的参数，这些参数适用于以下场景：
- Catalog 属性
@@ -56,3 +59,4 @@ Minio 默认使用 Host-style 访问方式，但也支持 Path-style 访问。
* 推荐使用 `minio.` 前缀配置参数，保证与 MinIO 的一致性和清晰度。
* 3.1 之前的版本，请使用曾用名 `s3.` 作为前缀。
* 连接池参数可根据并发需求调整，避免连接阻塞。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/s3.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/s3.md
index 85544fd553f..a0d275f715d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/s3.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/storages/s3.md
@@ -1,11 +1,14 @@
---
{
- "title": "S3",
+ "title": "S3 | Storages",
"language": "zh-CN",
- "description": "本文档用于介绍访问 AWS S3 时所需的参数。这些参数适用于："
+ "description": "本文档用于介绍访问 AWS S3 时所需的参数。这些参数适用于：",
+ "sidebar_label": "S3"
}
---
+# S3
+
本文档用于介绍访问 AWS S3 时所需的参数。这些参数适用于：
- Catalog 属性。
@@ -153,3 +156,4 @@ Amazon S3 Express One Zone（又名 Directory Bucket）提供更高性能，但
- 如果只做查询，不要授予写权限。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/log-storage-analysis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/log-storage-analysis.md
index d424b239819..8b1b05d55de 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/log-storage-analysis.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/log-storage-analysis.md
@@ -1,11 +1,14 @@
---
{
- "title": "日志存储与分析",
+ "title": "日志存储与分析 | Doris Docs",
"language": "zh-CN",
- "description": "在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤："
+ "description": "在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤：",
+ "sidebar_label": "日志存储与分析"
}
---
+# 日志存储与分析
+
### 第 1 步：评估资源
在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤：
@@ -461,3 +464,4 @@ ORDER BY ts DESC LIMIT 10;
您可以联系 dev@doris.apache.org 获得更多帮助。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/observability/log-storage-analysis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/observability/log-storage-analysis.md
index 22170faa62d..ac532a01f6a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/observability/log-storage-analysis.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/observability/log-storage-analysis.md
@@ -1,11 +1,14 @@
---
{
- "title": "日志存储与分析",
+ "title": "日志存储与分析 | Observability",
"language": "zh-CN",
- "description": "在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤："
+ "description": "在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤：",
+ "sidebar_label": "日志存储与分析"
}
---
+# 日志存储与分析
+
### 第 1 步：评估资源
在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤：
@@ -461,3 +464,4 @@ ORDER BY ts DESC LIMIT 10;
您可以联系 dev@doris.apache.org 获得更多帮助。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/observability/overview.mdx b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/observability/overview.mdx
index 8a20b721123..da5f2cfb286 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/observability/overview.mdx
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/observability/overview.mdx
@@ -1,11 +1,14 @@
---
{
- "title": "概述",
+ "title": "概述 | Observability",
"language": "zh_CN",
- "description": "可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台通过采集、存储、可视化分析三大可关键数据：日志（Logging）、链路追踪（Tracing）和指标（Metrics），帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等，"
+ "description": "可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台通过采集、存储、可视化分析三大可关键数据：日志（Logging）、链路追踪（Tracing）和指标（Metrics），帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等，",
+ "sidebar_label": "概述"
}
---
+# 概述
+
## 什么是可观测性
可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台通过采集、存储、可视化分析三大可关键数据：日志（Logging）、链路追踪（Tracing）和指标（Metrics），帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等，提升系统可靠性和用户体验。
@@ -132,3 +135,4 @@ Grafana 的 Log 可视化和分析能力相对于 Kibana 来说是比较简单
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/query-acceleration/materialized-view/async-materialized-view/use-guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/query-acceleration/materialized-view/async-materialized-view/use-guide.md
index dec82e96f4c..87efdc1af17 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/query-acceleration/materialized-view/async-materialized-view/use-guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/query-acceleration/materialized-view/async-materialized-view/use-guide.md
@@ -1,11 +1,14 @@
---
{
- "title": "最佳实践",
+ "title": "最佳实践 | Async Materialized View",
"language": "zh-CN",
- "description": "当满足以下条件时，建议创建分区物化视图："
+ "description": "当满足以下条件时，建议创建分区物化视图：",
+ "sidebar_label": "最佳实践"
}
---
+# 最佳实践
+
## 异步物化视图使用原则
- **时效性考虑：** 异步物化视图通常用于对数据时效性要求不高的场景，一般是 T+1 的数据。如果时效性要求高，应考虑使用同步物化视图。
@@ -883,4 +886,4 @@ FROM common_schedule_join_mv;
DML 时，当物化视图存在无法实时感知数据的外表时，是否开启基于结构信息的物化视图透明改写，默认关闭
-`SET enable_dml_materialized_view_rewrite_when_base_table_unawareness = true;`
\ No newline at end of file
+`SET enable_dml_materialized_view_rewrite_when_base_table_unawareness = true;`
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/query-acceleration/optimization-technology-principle/statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/query-acceleration/optimization-technology-principle/statistics.md
index 0c377378627..ad1ea2a006d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/query-acceleration/optimization-technology-principle/statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/query-acceleration/optimization-technology-principle/statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "统计信息",
+ "title": "统计信息 | Optimization Technology Principle",
"language": "zh-CN",
- "description": "从 2.0 版本开始，Doris 在优化器中加入了 CBO 的能力。统计信息是 CBO 的基石，其准确性直接决定了代价估算的准确性，对于选择最优 Plan 至关重要。本文主要介绍统计信息的收集和管理方法、相关配置项以及常见问题。"
+ "description": "从 2.0 版本开始，Doris 在优化器中加入了 CBO 的能力。统计信息是 CBO 的基石，其准确性直接决定了代价估算的准确性，对于选择最优 Plan 至关重要。本文主要介绍统计信息的收集和管理方法、相关配置项以及常见问题。",
+ "sidebar_label": "统计信息"
}
---
+# 统计信息
+
从 2.0 版本开始，Doris 在优化器中加入了 CBO 的能力。统计信息是 CBO 的基石，其准确性直接决定了代价估算的准确性，对于选择最优 Plan 至关重要。本文主要介绍统计信息的收集和管理方法、相关配置项以及常见问题。
## 统计信息的收集
@@ -478,3 +481,4 @@ ADMIN DIAGNOSE TABLET tablet_id
对于某些特殊表，如分区众多的表或单个 Tablet 体积庞大的表，可能会出现内存占用较多的情况。
建议用户在建表时合理规划 Tablet 数量，避免产生超大 Tablet。若 Tablet 结构不易调整，建议在系统低峰期开启自动收集，或于低峰期手动收集这些大表，以免在高峰期影响业务运行。在 Doris 3.x 系列中，我们将针对此类场景进行优化。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/date-time/DATE.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/date-time/DATE.md
index f1af6391ec5..fb0d51e123c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/date-time/DATE.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/date-time/DATE.md
@@ -1,11 +1,14 @@
---
{
- "title": "DATE",
+ "title": "DATE | Date Time",
"language": "zh-CN",
- "description": "DATE"
+ "description": "DATE",
+ "sidebar_label": "DATE"
}
---
+# DATE
+
## DATE
### name
@@ -30,3 +33,4 @@ SELECT DATE('2003-12-31 01:02:03');
### keywords
DATE
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
index c4a60778f3a..3e60ebdd7e0 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Semi Structured",
"language": "zh-CN",
- "description": "由 T 类型元素组成的数组，不能作为 key 列使用。目前支持在 Duplicate 和 Unique 模型的表中使用。"
+ "description": "由 T 类型元素组成的数组，不能作为 key 列使用。目前支持在 Duplicate 和 Unique 模型的表中使用。",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
## 描述
`ARRAY<T>`
@@ -61,3 +64,4 @@ mysql> SELECT * FROM `array_test`;
+------+-----------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
index 269162366d1..0148299e257 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
@@ -1,11 +1,14 @@
---
{
- "title": "JSON",
+ "title": "JSON | Semi Structured",
"language": "zh-CN",
- "description": "JSON 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。"
+ "description": "JSON 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。",
+ "sidebar_label": "JSON"
}
---
+# JSON
+
JSON 数据类型，用二进制格式高效存储 [JSON](https://www.rfc-editor.org/rfc/rfc8785) 数据，通过 JSON 函数访问其内部字段。
默认支持 1048576 字节（1 MB），可调大到 2147483643 字节（2 GB），可通过 BE 配置`string_type_length_soft_limit_bytes` 调整。
@@ -860,3 +863,4 @@ mysql> SELECT JSON_EXTRACT_STRING('{"key1" : null}', "$.key_not_exist") IS NULL;
### keywords
JSON, json_parse, json_parse_error_to_null, json_parse_error_to_value, json_extract, json_extract_isnull, json_extract_bool, json_extract_int, json_extract_bigint, json_extract_double, json_extract_String, json_exists_path, json_type
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
index 51dc37569b1..e0555a5b300 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
@@ -1,8 +1,9 @@
---
{
- "title": "MAP",
+ "title": "MAP | Semi Structured",
"language": "zh-CN",
- "description": "MAP"
+ "description": "MAP",
+ "sidebar_label": "MAP"
}
---
@@ -249,3 +250,4 @@ mysql> SELECT id, map_values(m) FROM simple_map ORDER BY id;
### keywords
MAP
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
index 2a36322ecf7..1037e1f10f8 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Semi Structured",
"language": "zh-CN",
- "description": "STRUCT"
+ "description": "STRUCT",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
## STRUCT
### name
@@ -101,3 +104,4 @@ mysql> select * from struct_test;
### keywords
STRUCT
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/string-type/CHAR.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
index cd06dcfb960..2b86fcaca5e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
@@ -1,11 +1,14 @@
---
{
- "title": "CHAR",
+ "title": "CHAR | String Type",
"language": "zh-CN",
- "description": "CHAR(M)"
+ "description": "CHAR(M)",
+ "sidebar_label": "CHAR"
}
---
+# CHAR
+
## description
CHAR(M)
@@ -15,3 +18,4 @@ CHAR(M)
## keywords
CHAR
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/array-functions/array.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/array-functions/array.md
index 6ddec1e1c9d..7201c960069 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/array-functions/array.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/array-functions/array.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Array Functions",
"language": "zh-CN",
- "description": "根据参数构造并返回 array, 参数可以是多列或者常量"
+ "description": "根据参数构造并返回 array, 参数可以是多列或者常量",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
## 描述
根据参数构造并返回 array, 参数可以是多列或者常量
@@ -71,3 +74,4 @@ select array(qid, creationDate, null) from nested limit 4;
| [null, "2009-06-16 08:15:45", null] |
+-------------------------------------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
index acbc4fc015d..2d01c36f9d1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
@@ -1,11 +1,14 @@
---
{
- "title": "DATE",
+ "title": "DATE | Date Time Functions",
"language": "zh-CN",
- "description": "提取日期时间中的日期。"
+ "description": "提取日期时间中的日期。",
+ "sidebar_label": "DATE"
}
---
+# DATE
+
## 描述
提取日期时间中的日期。
@@ -38,4 +41,4 @@ select date('2010-12-02 19:28:30');
+----------------------------------------------------+
| 2010-12-02 |
+----------------------------------------------------+
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/map-functions/map.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/map-functions/map.md
index eb2f3aa03d1..40e74d1bcf1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/map-functions/map.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/map-functions/map.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Map Functions",
"language": "zh-CN",
- "description": "使用若干组键值对构造一个特定类型的 Map<K, V>"
+ "description": "使用若干组键值对构造一个特定类型的 Map<K, V>",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
## 描述
使用若干组键值对构造一个特定类型的 `Map<K, V>`
@@ -40,3 +43,4 @@ select map(1, "100", 0.1, 2),map(1, "100", 0.1, 2)[1];
| {1.0:"100", 0.1:"2"} | 100 |
+---------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/string-functions/char.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/string-functions/char.md
index ac7443f94ff..c222b39ca30 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/string-functions/char.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/string-functions/char.md
@@ -1,11 +1,14 @@
---
{
- "title": "CHAR",
+ "title": "CHAR | String Functions",
"language": "zh-CN",
- "description": "将每个参数解释为整数，并返回一个字符串，该字符串由这些整数的代码值给出的字符组成。特殊情况："
+ "description": "将每个参数解释为整数，并返回一个字符串，该字符串由这些整数的代码值给出的字符组成。特殊情况：",
+ "sidebar_label": "CHAR"
}
---
+# CHAR
+
## 描述
将每个参数解释为整数，并返回一个字符串，该字符串由这些整数的代码值给出的字符组成。特殊情况：
@@ -48,4 +51,4 @@ SELECT CHAR(68, 111, 114, 105, 115),CHAR(15049882, 15179199, 14989469),CHAR(255)
+--------------------------------------+--------------------------------------------+-------------------+
| Doris | 多睿丝 | NULL |
+--------------------------------------+--------------------------------------------+-------------------+
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
index a6b128ace74..4510e2493ff 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Struct Functions",
"language": "zh-CN",
- "description": "根据给定的值构造并返回 struct，参数可以是多列或常量"
+ "description": "根据给定的值构造并返回 struct，参数可以是多列或常量",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
## 描述
根据给定的值构造并返回 struct，参数可以是多列或常量
@@ -39,3 +42,4 @@ select struct(1, 'a', "abc"),struct(null, 1, null),struct(cast('2023-03-16' as d
| {"col1":1, "col2":"a", "col3":"abc"} | {"col1":null, "col2":1, "col3":null} | {"col1":"2023-03-16 00:00:00"} |
+--------------------------------------+--------------------------------------+---------------------------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/table-valued-functions/hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/table-valued-functions/hdfs.md
index 6e630bb3316..9470a432325 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/table-valued-functions/hdfs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/table-valued-functions/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Table Valued Functions",
"language": "zh-CN",
- "description": "HDFS 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 HDFS 上的文件内容。目前支持csv/csvwithnames/csvwithnamesandtypes/json/parquet/orc文件格式。"
+ "description": "HDFS 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 HDFS 上的文件内容。目前支持csv/csvwithnames/csvwithnamesandtypes/json/parquet/orc文件格式。",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
## 描述
HDFS 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 HDFS 上的文件内容。目前支持`csv/csv_with_names/csv_with_names_and_types/json/parquet/orc`文件格式。
@@ -125,3 +128,4 @@ HDFS(
"hadoop.username" = "doris",
"format" = "csv_with_names");
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/table-valued-functions/s3.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/table-valued-functions/s3.md
index d094a6667ca..b431becba8e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/table-valued-functions/s3.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/sql-manual/sql-functions/table-valued-functions/s3.md
@@ -1,11 +1,14 @@
---
{
- "title": "S3",
+ "title": "S3 | Table Valued Functions",
"language": "zh-CN",
- "description": "S3 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 S3 兼容的对象存储上的文件内容。目前支持 csv/csv_with_names/csv_with_names_and_types/json/parquet/orc 文件格式。"
+ "description": "S3 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 S3 兼容的对象存储上的文件内容。目前支持 csv/csv_with_names/csv_with_names_and_types/json/parquet/orc 文件格式。",
+ "sidebar_label": "S3"
}
---
+# S3
+
## 描述
S3 表函数（table-valued-function, tvf）可以让用户像访问关系表格式数据一样，读取并访问 S3 兼容的对象存储上的文件内容。目前支持 `csv/csv_with_names/csv_with_names_and_types/json/parquet/orc` 文件格式。
@@ -592,3 +595,4 @@ S3(
"read_json_by_line" = "true",
"use_path_style" = "true");
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/overview.md
index 739a22f2078..59b9fc2d08f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/table-design/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "概览",
+ "title": "概览 | Table Design",
"language": "zh-CN",
- "description": "使用 CREATE TABLE 语句在 Doris 中创建一个表，也可以使用 CREATE TABKE LIKE 或 CREATE TABLE AS 子句从另一个表派生表定义。"
+ "description": "使用 CREATE TABLE 语句在 Doris 中创建一个表，也可以使用 CREATE TABKE LIKE 或 CREATE TABLE AS 子句从另一个表派生表定义。",
+ "sidebar_label": "概览"
}
---
+# 概览
+
## 创建表
使用 [CREATE TABLE](../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE) 语句在 Doris 中创建一个表，也可以使用 [CREATE TABKE LIKE](../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE#create-table--like) 或 [CREATE TABLE AS](../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE#create-table--as-select也称为-ctas) 子句从另一个表派生表定义。
@@ -37,4 +40,4 @@ Doris 的建表语句中可以指定[建表属性](../sql-manual/sql-statements/
3. **添加列操作**：加减 VALUE 列是轻量级实现，秒级别可以完成，加减 KEY 列或者修改数据类型是重量级操作，完成时间取决于数据量，大规模数据下尽量避免加减 KEY 列或者修改数据类型；
-4. **优化存储策略**：可以使用层级存储将冷数据保存到 HDD 或者 S3 / HDFS。
\ No newline at end of file
+4. **优化存储策略**：可以使用层级存储将冷数据保存到 HDD 或者 S3 / HDFS。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/config/fe-config-template.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/config/fe-config-template.md
index 42689c0ba21..5c8c5ed5826 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/config/fe-config-template.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/config/fe-config-template.md
@@ -1,10 +1,11 @@
---
{
- "title": "FE 配置项",
+ "title": "FE 配置项 | Config",
"language": "zh-CN",
"toc_min_heading_level": 2,
"toc_max_heading_level": 4,
- "description": "该文档主要介绍 FE 的相关配置项。"
+ "description": "该文档主要介绍 FE 的相关配置项。",
+ "sidebar_label": "FE 配置项"
}
---
@@ -118,3 +119,4 @@ FE 的配置项有两种方式进行配置：
> 如需修改，请修改 `fe/fe-common/src/main/java/org/apache/doris/common/Config.java` 中的描述信息。
<--DOC_PLACEHOLDER-->
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/config/fe-config.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/config/fe-config.md
index 1ce7e8f9bfc..1046d34cc14 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/config/fe-config.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/config/fe-config.md
@@ -1,10 +1,11 @@
---
{
- "title": "FE 配置项",
+ "title": "FE 配置项 | Config",
"language": "zh-CN",
"toc_min_heading_level": 2,
"toc_max_heading_level": 4,
- "description": "该文档主要介绍 FE 的相关配置项。"
+ "description": "该文档主要介绍 FE 的相关配置项。",
+ "sidebar_label": "FE 配置项"
}
---
@@ -2774,3 +2775,4 @@ Doris 为了兼用 mysql 周边工具生态，会内置一个名为 mysql 的数
默认值： ""
Meta Service 的端点应以 'host1:port,host2:port' 的格式指定。此配置对于存储和计算分离模式是必要的。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/meta-info-action-V2.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/meta-info-action-V2.md
index 09963040bf6..2bd99841252 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/meta-info-action-V2.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/meta-info-action-V2.md
@@ -1,11 +1,14 @@
---
{
- "title": "Meta Info Action",
+ "title": "Meta Info Action | Fe Http",
"language": "zh-CN",
- "description": "获取集群内的元数据信息，包括数据库列表、表列表以及表结构等。"
+ "description": "获取集群内的元数据信息，包括数据库列表、表列表以及表结构等。",
+ "sidebar_label": "Meta Info Action"
}
---
+# Meta Info Action
+
## Request
`GET /api/meta/namespaces/<ns>/databases`
@@ -50,3 +53,4 @@
"count":0
}
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/meta-info-action.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/meta-info-action.md
index d9c622d3cec..4e477f2f180 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/meta-info-action.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/meta-info-action.md
@@ -1,11 +1,14 @@
---
{
- "title": "Meta Info Action",
+ "title": "Meta Info Action | Fe Http",
"language": "zh-CN",
- "description": "Meta Info Action 用于获取集群内的元数据信息。如数据库列表，表结构等。"
+ "description": "Meta Info Action 用于获取集群内的元数据信息。如数据库列表，表结构等。",
+ "sidebar_label": "Meta Info Action"
}
---
+# Meta Info Action
+
Meta Info Action 用于获取集群内的元数据信息。如数据库列表，表结构等。
## 数据库列表
@@ -210,3 +213,4 @@ GET /api/meta/namespaces/default/databases/db1/tables/tbl1/schema?with_mv?=1
```
* data 字段返回 base 表或 rollup 表的表结构信息。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/query-profile-action-controller.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/query-profile-action-controller.md
index 368412b2cd3..ee60a32ebd1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/query-profile-action-controller.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/query-profile-action-controller.md
@@ -1,11 +1,14 @@
---
{
- "title": "Query Profile Action",
+ "title": "Query Profile Action | Fe Http",
"language": "zh-CN",
- "description": "Query Profile Action 用于获取 Query 的 profile"
+ "description": "Query Profile Action 用于获取 Query 的 profile",
+ "sidebar_label": "Query Profile Action"
}
---
+# Query Profile Action
+
## Request
```
@@ -85,4 +88,4 @@ Query Profile Action 用于获取 Query 的 profile
}
```
- `data` is the text content of the profile.
\ No newline at end of file
+ `data` is the text content of the profile.
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/query-profile-action.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/query-profile-action.md
index 2a90b30884c..f1f8ecd46e4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/query-profile-action.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/open-api/fe-http/query-profile-action.md
@@ -1,11 +1,14 @@
---
{
- "title": "Query Profile Action",
+ "title": "Query Profile Action | Fe Http",
"language": "zh-CN",
- "description": "GET /rest/v2/manager/query/statistics/{traceid} (4.0.0+)"
+ "description": "Doris FE Query Profile REST API 文档，支持通过 HTTP 接口获取查询信息、执行 Profile、实时统计数据，并对正在运行的查询进行监控与控制。",
+ "sidebar_label": "Query Profile Action"
}
---
+# Query Profile Action
+
## Request
`GET /rest/v2/manager/query/query_info`
@@ -498,3 +501,4 @@ Admin 和 Root 用户可以查看所有 Query。普通用户仅能查看自己
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/system-tables/information_schema/column_statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/system-tables/information_schema/column_statistics.md
index e4c88305642..bfc4a3b1fd0 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/system-tables/information_schema/column_statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/system-tables/information_schema/column_statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "column_statistics",
+ "title": "column_statistics | Information Schema",
"language": "zh-CN",
- "description": "此表仅用于兼容 MySQL 行为，永远为空。并不能真实反映 Doris 内数据的统计信息。如需查看 Doris 收集的统计信息，请查看统计信息章节。"
+ "description": "此表仅用于兼容 MySQL 行为，永远为空。并不能真实反映 Doris 内数据的统计信息。如需查看 Doris 收集的统计信息，请查看统计信息章节。",
+ "sidebar_label": "column_statistics"
}
---
+# column_statistics
+
## 概述
此表仅用于兼容 MySQL 行为，永远为空。并不能真实反映 Doris 内数据的统计信息。如需查看 Doris 收集的统计信息，请[查看统计信息章节](../../../query-acceleration/optimization-technology-principle/statistics#查看统计信息)。
@@ -23,4 +26,4 @@
| SCHEMA_NAME | varchar(64) | |
| TABLE_NAME | varchar(64) | |
| COLUMN_NAME | varchar(64) | |
-| HISTOGRAM | json | |
\ No newline at end of file
+| HISTOGRAM | json | |
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/system-tables/internal_schema/column_statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/system-tables/internal_schema/column_statistics.md
index 439989fa288..6c2c8f2d9bc 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/system-tables/internal_schema/column_statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/system-tables/internal_schema/column_statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "column_statistics",
+ "title": "column_statistics | Internal Schema",
"language": "zh-CN",
- "description": "列统计信息"
+ "description": "列统计信息",
+ "sidebar_label": "column_statistics"
}
---
+# column_statistics
+
## 概述
列统计信息
@@ -33,4 +36,4 @@
| min | varchar(65533) | 最小值 |
| max | varchar(65533) | 最大值 |
| data_size_in_bytes | bigint | 以字节计算的数据量 |
-| update_time | datetime | 当前统计信息的更新时间 |
\ No newline at end of file
+| update_time | datetime | 当前统计信息的更新时间 |
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/system-tables/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/system-tables/overview.md
index 4941656a8ba..0c00235ee62 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/system-tables/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/system-tables/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "概述",
+ "title": "概述 | System Tables",
"language": "zh-CN",
- "description": "Doris 集群内置多个系统数据库，用于存储 Doris 系统本身的一些元数据信息。"
+ "description": "Doris 集群内置多个系统数据库，用于存储 Doris 系统本身的一些元数据信息。",
+ "sidebar_label": "概述"
}
---
+# 概述
+
Doris 集群内置多个系统数据库，用于存储 Doris 系统本身的一些元数据信息。
## information_schema
@@ -35,3 +38,4 @@ Doris 会在集群创建时，自动创建这个库下的所有系统表。
默认情况下，普通用户对这个库下的表拥有只读权限。但被授权后，可以对这个库下的表进行修改、删除或创建。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/overview.md
index b85e9af9c9a..e42117b0237 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "概述",
+ "title": "概述 | Memory Management",
"language": "zh-CN",
- "description": "内存管理是 Doris 中最重要的组成部分之一，在 Doris 运行过程中，不论导入还是查询都依赖大量的内存操作。内存管理的好坏直接影响到 Doris 的稳定性和性能。"
+ "description": "内存管理是 Doris 中最重要的组成部分之一，在 Doris 运行过程中，不论导入还是查询都依赖大量的内存操作。内存管理的好坏直接影响到 Doris 的稳定性和性能。",
+ "sidebar_label": "概述"
}
---
+# 概述
+
内存管理是 Doris 中最重要的组成部分之一，在 Doris 运行过程中，不论导入还是查询都依赖大量的内存操作。内存管理的好坏直接影响到 Doris 的稳定性和性能。
Apache Doris 作为基于 MPP 架构的 OLAP 数据库，数据从磁盘加载到内存后，会在算子间流式传递并计算，在内存中存储计算的中间结果，这种方式减少了频繁的磁盘 I/O 操作，充分利用多机多核的并行计算能力，可在性能上呈现巨大优势。
@@ -143,3 +146,4 @@ Doris BE Process Memory
## 内存控制策略
参考 [内存控制策略](./memory-feature/memory-control-strategy.md) 中对内存分配、监控、回收的介绍，它们保证了 Doris BE 进程内存的高效可控。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/export/export-best-practice.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/export/export-best-practice.md
index e7a5982042a..cca825026e4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/export/export-best-practice.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/export/export-best-practice.md
@@ -1,11 +1,14 @@
---
{
- "title": "最佳实践",
+ "title": "最佳实践 | Export",
"language": "zh-CN",
- "description": "本文档主要用于介绍在进行数据导出操作中，如何判断资源利用是否合理，以及如何调整资源利用率已达到更好的数据导出效率。"
+ "description": "本文档主要用于介绍在进行数据导出操作中，如何判断资源利用是否合理，以及如何调整资源利用率已达到更好的数据导出效率。",
+ "sidebar_label": "最佳实践"
}
---
+# 最佳实践
+
本文档主要用于介绍在进行数据导出操作中，如何判断资源利用是否合理，以及如何调整资源利用率已达到更好的数据导出效率。
## SELECT INTO OUTFILE
@@ -95,3 +98,4 @@
FE 配置参数，表示当前集群能够同时运行的 Export Task 的数量，默认是是 64。一个 Export Job 会根据并发度拆分成多个 Export Task。所有 Export Task 共享这个阈值。如果希望提升集群整体的可并发执行导出任务的数量，可以调大这个参数，并重启 FE 节点。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/array.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/array.md
index 0aedadbb036..642b65fa333 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/array.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/array.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Complex Types",
"language": "zh-CN",
- "description": "ARRAY<T> 表示由 T 类型元素组成的数组。点击 ARRAY 数据类型 了解具体信息。"
+ "description": "ARRAY<T> 表示由 T 类型元素组成的数组。点击 ARRAY 数据类型 了解具体信息。",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
`ARRAY<T>` 表示由 T 类型元素组成的数组。点击 [ARRAY 数据类型](../../../sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md) 了解具体信息。
## CSV 格式导入
@@ -117,3 +120,4 @@ mysql> SELECT * FROM array_test;
+------+-----------------+
4 rows in set (0.01 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/json.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/json.md
index f3954a3cdfb..b280abc0329 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/json.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/json.md
@@ -1,11 +1,14 @@
---
{
- "title": "JSON",
+ "title": "JSON | Complex Types",
"language": "zh-CN",
- "description": "JSON 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。"
+ "description": "JSON 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。",
+ "sidebar_label": "JSON"
}
---
+# JSON
+
`JSON` 数据类型，用二进制格式高效存储 JSON 数据，通过 JSON 函数访问其内部字段。
默认支持 1048576 字节（1 MB），可调大到 2147483643 字节（2 GB），可通过 BE 配置`string_type_length_soft_limit_bytes` 调整。
@@ -132,3 +135,4 @@ mysql> SELECT * FROM json_test;
+------+-------------------------------+
5 rows in set (0.01 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/map.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/map.md
index 5749cf65fc0..d46a1c6f210 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/map.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/map.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Complex Types",
"language": "zh-CN",
- "description": "MAP<K, V> 表示由K,V类型元素组成的MAP。 点击MAP 数据类型 了解具体信息。"
+ "description": "MAP<K, V> 表示由K,V类型元素组成的MAP。 点击MAP 数据类型 了解具体信息。",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
`MAP<K, V>` 表示由`K,V`类型元素组成的`MAP`。 点击[MAP 数据类型](../../../sql-manual/basic-element/sql-data-types/semi-structured/MAP.md) 了解具体信息。
## CSV 格式导入
@@ -117,3 +120,4 @@ mysql> SELECT * FROM map_test;
+------+-------------------------+
4 rows in set (0.01 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/struct.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/struct.md
index 3492cb6bee5..fc117872758 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/struct.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/struct.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Complex Types",
"language": "zh-CN",
- "description": "STRUCT<fieldname:fieldtype [COMMENT 'commentstring'], ... > 表示由多个 Field 组成的结构体，也可被理解为多个列的集合。点击STRUCT 数据类型 了解具体信息。"
+ "description": "STRUCT<fieldname:fieldtype [COMMENT 'commentstring'], ... > 表示由多个 Field 组成的结构体，也可被理解为多个列的集合。点击STRUCT 数据类型 了解具体信息。",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
`STRUCT<field_name:field_type [COMMENT 'comment_string'], ... >` 表示由多个 Field 组成的结构体，也可被理解为多个列的集合。点击[STRUCT 数据类型](../../../sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md) 了解具体信息。
## CSV 格式导入
@@ -127,3 +130,4 @@ mysql> SELECT * FROM struct_test;
+------+--------------------------------------+
5 rows in set (0.00 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/data-source/google-cloud-storage.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/data-source/google-cloud-storage.md
index 98d3272a75b..96261c66b68 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/data-source/google-cloud-storage.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/data-source/google-cloud-storage.md
@@ -1,11 +1,14 @@
---
{
- "title": "Google Cloud Storage",
+ "title": "Google Cloud Storage | Data Source",
"language": "zh-CN",
- "description": "Doris 提供两种方式从 Google Cloud Storage 导入文件："
+ "description": "Doris 提供两种方式从 Google Cloud Storage 导入文件：",
+ "sidebar_label": "Google Cloud Storage"
}
---
+# Google Cloud Storage
+
Doris 提供两种方式从 Google Cloud Storage 导入文件：
- 使用 S3 Load 将 Google Cloud Storage 文件导入到 Doris 中，这是一个异步的导入方式。
- 使用 TVF 将 Google Cloud Storage 文件导入到 Doris 中，这是一个同步的导入方式。
@@ -170,3 +173,4 @@ mysql> select * from test_s3load;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/data-source/hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/data-source/hdfs.md
index 558c26e4299..5f17a8e7250 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/data-source/hdfs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/data-source/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Data Source",
"language": "zh-CN",
- "description": "Doris 提供两种方式从 HDFS 导入文件："
+ "description": "Doris 提供两种方式从 HDFS 导入文件：",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
Doris 提供两种方式从 HDFS 导入文件：
- 使用 HDFS Load 将 HDFS 文件导入到 Doris 中，这是一个异步的导入方式。
- 使用 TVF 将 HDFS 文件导入到 Doris 中，这是一个同步的导入方式。
@@ -162,3 +165,4 @@ mysql> select * from test_hdfsload;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/data-source/minio.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/data-source/minio.md
index 595520c75d7..93303ace2d7 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/data-source/minio.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/data-source/minio.md
@@ -1,11 +1,14 @@
---
{
- "title": "MinIO",
+ "title": "MinIO | Data Source",
"language": "zh-CN",
- "description": "Doris 提供两种方式从 MinIO 导入文件："
+ "description": "Doris 提供两种方式从 MinIO 导入文件：",
+ "sidebar_label": "MinIO"
}
---
+# MinIO
+
Doris 提供两种方式从 MinIO 导入文件：
- 使用 S3 Load 将 MinIO 文件导入到 Doris 中，这是一个异步的导入方式。
- 使用 TVF 将 MinIO 文件导入到 Doris 中，这是一个同步的导入方式。
@@ -192,3 +195,4 @@ mysql> select * from test_s3load;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/json.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/json.md
index 1d86ed4d1b4..db50697027f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/json.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/json.md
@@ -1,8 +1,9 @@
---
{
- "title": "JSON",
+ "title": "JSON | File Format",
"language": "zh-CN",
- "description": "本文介绍如何在 Doris 中导入 JSON 格式的数据文件。Doris 支持导入标准 JSON 格式数据，通过配置相关参数，可以灵活地处理不同的 JSON 数据结构，并支持从 JSON 数据中抽取字段、处理嵌套结构等场景。"
+ "description": "本文介绍如何在 Doris 中导入 JSON 格式的数据文件。Doris 支持导入标准 JSON 格式数据，通过配置相关参数，可以灵活地处理不同的 JSON 数据结构，并支持从 JSON 数据中抽取字段、处理嵌套结构等场景。",
+ "sidebar_label": "JSON"
}
---
@@ -440,3 +441,4 @@ FROM S3
"json_root" = "$.events",
...
);
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/orc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/orc.md
index 4b6488a2cb2..500f74abf2c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/orc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/orc.md
@@ -1,11 +1,14 @@
---
{
- "title": "ORC",
+ "title": "ORC | File Format",
"language": "zh-CN",
- "description": "本文介绍如何在 Doris 中导入 ORC 格式的数据文件。"
+ "description": "本文介绍如何在 Doris 中导入 ORC 格式的数据文件。",
+ "sidebar_label": "ORC"
}
---
+# ORC
+
本文介绍如何在 Doris 中导入 ORC 格式的数据文件。
## 支持的导入方式
@@ -60,3 +63,4 @@ FROM S3
);
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/parquet.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/parquet.md
index ad990fe3875..7bb97a966d5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/parquet.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/parquet.md
@@ -1,11 +1,14 @@
---
{
- "title": "Parquet",
+ "title": "Parquet | File Format",
"language": "zh-CN",
- "description": "本文介绍如何在 Doris 中导入 Parquet 格式的数据文件。"
+ "description": "本文介绍如何在 Doris 中导入 Parquet 格式的数据文件。",
+ "sidebar_label": "Parquet"
}
---
+# Parquet
+
本文介绍如何在 Doris 中导入 Parquet 格式的数据文件。
## 支持的导入方式
@@ -56,4 +59,4 @@ FROM S3
"format" = "parquet",
...
);
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/file-formats/orc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/file-formats/orc.md
index cafd01e62de..7e2bfa5b36c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/file-formats/orc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/file-formats/orc.md
@@ -1,11 +1,14 @@
---
{
- "title": "ORC",
+ "title": "ORC | File Formats",
"language": "zh-CN",
- "description": "本文档用于介绍 Doris 的 ORC 文件格式的读写支持情况。该文档适用于以下功能。"
+ "description": "本文档用于介绍 Doris 的 ORC 文件格式的读写支持情况。该文档适用于以下功能。",
+ "sidebar_label": "ORC"
}
---
+# ORC
+
本文档用于介绍 Doris 的 ORC 文件格式的读写支持情况。该文档适用于以下功能。
* Catalog 中对数据的读取、写入操作。
@@ -69,3 +72,4 @@
* `orc_natural_read_size_mb` (2.1+, 3.0+)
ORC Reader 一次性读取的最大字节大小。默认 8 MB。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/file-formats/parquet.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/file-formats/parquet.md
index dee4524d0bc..2c029d1c5cf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/file-formats/parquet.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/file-formats/parquet.md
@@ -1,11 +1,14 @@
---
{
- "title": "Parquet",
+ "title": "Parquet | File Formats",
"language": "zh-CN",
- "description": "本文档用于介绍 Doris 的 Parquet 文件格式的读写支持情况。该文档适用于以下功能。"
+ "description": "本文档用于介绍 Doris 的 Parquet 文件格式的读写支持情况。该文档适用于以下功能。",
+ "sidebar_label": "Parquet"
}
---
+# Parquet
+
本文档用于介绍 Doris 的 Parquet 文件格式的读写支持情况。该文档适用于以下功能。
* Catalog 中对数据的读取、写入操作。
@@ -63,3 +66,4 @@
* `parquet_column_max_buffer_mb` (2.1+, 3.0+)
读取 Parquet Row Group 中的 Column 时所分配的最大 Buffer 大小，默认为 8M。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/statistics.md
index 2e928aa3798..04f9422952f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/statistics.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/statistics.md
@@ -1,12 +1,16 @@
---
{
- "title": "统计信息",
+ "title": "统计信息 | Lakehouse",
"language": "zh-CN",
- "description": "Doris 支持对外部数据源的表，如 Hive、Iceberg、Paimon 等进行自动或手动的统计信息收集。统计信息准确性直接决定了代价估算的准确性，对于选择最优查询计划至关重要，尤其在复杂查询场景下能显著提升查询执行效率。"
+ "description": "Doris 支持对外部数据源的表，如 Hive、Iceberg、Paimon 等进行自动或手动的统计信息收集。统计信息准确性直接决定了代价估算的准确性，对于选择最优查询计划至关重要，尤其在复杂查询场景下能显著提升查询执行效率。",
+ "sidebar_label": "统计信息"
}
---
+# 统计信息
+
Doris 支持对外部数据源的表，如 Hive、Iceberg、Paimon 等进行自动或手动的统计信息收集。统计信息准确性直接决定了代价估算的准确性，对于选择最优查询计划至关重要，尤其在复杂查询场景下能显著提升查询执行效率。
具体可参阅 [统计信息](../query-acceleration/optimization-technology-principle/statistics#外表收集) 文档中的【外表收集】部分。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/gcs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/gcs.md
index f06004bd9f6..35d0e2dc6f4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/gcs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/gcs.md
@@ -1,10 +1,14 @@
---
{
- "title": "Google Cloud Storage",
+ "title": "Google Cloud Storage | Storages",
"language": "zh-CN",
- "description": "文档更新中。"
+ "description": "文档更新中。",
+ "sidebar_label": "Google Cloud Storage"
}
---
+# Google Cloud Storage
+
文档更新中。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/hdfs.md
index 68e36b0304d..932aeeb06d6 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/hdfs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Storages",
"language": "zh-CN",
- "description": "本文档用于介绍访问 HDFS 时所需的参数。这些参数适用于："
+ "description": "本文档用于介绍访问 HDFS 时所需的参数。这些参数适用于：",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
本文档用于介绍访问 HDFS 时所需的参数。这些参数适用于：
* Catalog 属性。
@@ -216,3 +219,4 @@ Java 版本使用通过 Java 访问 HDFS，可以模拟 Doris FE 侧访问 HDFS
CPP 版本通过 C++ 调用 libhdfs 访问 HDFS，可以模拟 Doris BE 侧访问 HDFS 的逻辑。
具体使用方式可以各自代码库的 README。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/minio.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/minio.md
index 876139f0cc4..2c743026482 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/minio.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/minio.md
@@ -1,11 +1,14 @@
---
{
- "title": "MinIO",
+ "title": "MinIO | Storages",
"language": "zh-CN",
- "description": "本文档介绍访问 MinIO 所需的参数，这些参数适用于以下场景："
+ "description": "本文档介绍访问 MinIO 所需的参数，这些参数适用于以下场景：",
+ "sidebar_label": "MinIO"
}
---
+# MinIO
+
本文档介绍访问 MinIO 所需的参数，这些参数适用于以下场景：
- Catalog 属性
@@ -56,3 +59,4 @@ Minio 默认使用 Host-style 访问方式，但也支持 Path-style 访问。
* 推荐使用 `minio.` 前缀配置参数，保证与 MinIO 的一致性和清晰度。
* 3.1 之前的版本，请使用曾用名 `s3.` 作为前缀。
* 连接池参数可根据并发需求调整，避免连接阻塞。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/s3.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/s3.md
index 85544fd553f..a0d275f715d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/s3.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/storages/s3.md
@@ -1,11 +1,14 @@
---
{
- "title": "S3",
+ "title": "S3 | Storages",
"language": "zh-CN",
- "description": "本文档用于介绍访问 AWS S3 时所需的参数。这些参数适用于："
+ "description": "本文档用于介绍访问 AWS S3 时所需的参数。这些参数适用于：",
+ "sidebar_label": "S3"
}
---
+# S3
+
本文档用于介绍访问 AWS S3 时所需的参数。这些参数适用于：
- Catalog 属性。
@@ -153,3 +156,4 @@ Amazon S3 Express One Zone（又名 Directory Bucket）提供更高性能，但
- 如果只做查询，不要授予写权限。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/log-storage-analysis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/log-storage-analysis.md
index ac4999e5e5b..134b86d7aea 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/log-storage-analysis.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/log-storage-analysis.md
@@ -1,11 +1,14 @@
---
{
- "title": "日志存储与分析",
+ "title": "日志存储与分析 | Doris Docs",
"language": "zh-CN",
- "description": "日志是系统运行的详细记录，包含各种事件发生的主体、时间、位置、内容等关键信息。出于运维可观测、网络安全监控及业务分析等多重需求，企业通常需要将分散的日志采集起来，进行集中存储、查询和分析，以进一步从日志数据里挖掘出有价值的内容。"
+ "description": "日志是系统运行的详细记录，包含各种事件发生的主体、时间、位置、内容等关键信息。出于运维可观测、网络安全监控及业务分析等多重需求，企业通常需要将分散的日志采集起来，进行集中存储、查询和分析，以进一步从日志数据里挖掘出有价值的内容。",
+ "sidebar_label": "日志存储与分析"
}
---
+# 日志存储与分析
+
日志是系统运行的详细记录，包含各种事件发生的主体、时间、位置、内容等关键信息。出于运维可观测、网络安全监控及业务分析等多重需求，企业通常需要将分散的日志采集起来，进行集中存储、查询和分析，以进一步从日志数据里挖掘出有价值的内容。
针对此场景，Apache Doris 提供了相应解决方案，针对日志场景的特点，增加了倒排索引和极速全文检索能力，极致优化写入性能和存储空间，使得用户可以基于 Apache Doris 构建开放、高性能、低成本、统一的日志存储与分析平台。
@@ -542,3 +545,4 @@ ORDER BY ts DESC LIMIT 10;
您可以联系 dev@doris.apache.org 获得更多帮助。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/observability/log-storage-analysis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/observability/log-storage-analysis.md
index af2f5d4d43f..c541708912c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/observability/log-storage-analysis.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/observability/log-storage-analysis.md
@@ -1,11 +1,14 @@
---
{
- "title": "日志存储与分析",
+ "title": "日志存储与分析 | Observability",
"language": "zh-CN",
- "description": "在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤："
+ "description": "在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤：",
+ "sidebar_label": "日志存储与分析"
}
---
+# 日志存储与分析
+
### 第 1 步：评估资源
在部署集群之前，首先应评估所需服务器硬件资源，包括以下几个关键步骤：
@@ -461,3 +464,4 @@ ORDER BY ts DESC LIMIT 10;
您可以联系 dev@doris.apache.org 获得更多帮助。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/observability/overview.mdx b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/observability/overview.mdx
index 1a4878d4c04..cb85a683e47 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/observability/overview.mdx
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/observability/overview.mdx
@@ -1,11 +1,14 @@
---
{
- "title": "概述",
+ "title": "概述 | Observability",
"language": "zh_CN",
- "description": "可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台通过采集、存储、可视化分析三大可关键数据：日志（Logging）、链路追踪（Tracing）和指标（Metrics），帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等，"
+ "description": "可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台通过采集、存储、可视化分析三大可关键数据：日志（Logging）、链路追踪（Tracing）和指标（Metrics），帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等，",
+ "sidebar_label": "概述"
}
---
+# 概述
+
## 什么是可观测性
可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台通过采集、存储、可视化分析三大可关键数据：日志（Logging）、链路追踪（Tracing）和指标（Metrics），帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等，提升系统可靠性和用户体验。
@@ -133,3 +136,4 @@ Grafana 的 Log 可视化和分析能力相对于 Kibana 来说是比较简单
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/materialized-view/async-materialized-view/use-guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/materialized-view/async-materialized-view/use-guide.md
index 2a7a209f274..ecbbad1cbce 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/materialized-view/async-materialized-view/use-guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/query-acceleration/materialized-view/async-materialized-view/use-guide.md
@@ -1,11 +1,14 @@
---
{
- "title": "最佳实践",
+ "title": "最佳实践 | Async Materialized View",
"language": "zh-CN",
- "description": "当满足以下条件时，建议创建分区物化视图："
+ "description": "当满足以下条件时，建议创建分区物化视图：",
+ "sidebar_label": "最佳实践"
}
---
+# 最佳实践
+
## 异步物化视图使用原则
- **时效性考虑：** 异步物化视图通常用于对数据时效性要求不高的场景，一般是 T+1 的数据。如果时效性要求高，应考虑使用同步物化视图。
@@ -783,4 +786,4 @@ FROM common_schedule_join_mv;
DML 时，当物化视图存在无法实时感知数据的外表时，是否开启基于结构信息的物化视图透明改写，默认关闭
-`SET enable_dml_materialized_view_rewrite_when_base_table_unawareness = true;`
\ No newline at end of file
+`SET enable_dml_materialized_view_rewrite_when_base_table_unawareness = true;`
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 24d00db6c9e..0711741d252 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
@@ -1,11 +1,14 @@
---
{
- "title": "统计信息",
+ "title": "统计信息 | Optimization Technology Principle",
"language": "zh-CN",
- "description": "从 2.0 版本开始，Doris 在优化器中加入了 CBO 的能力。统计信息是 CBO 的基石，其准确性直接决定了代价估算的准确性，对于选择最优 Plan 至关重要。本文主要介绍统计信息的收集和管理方法、相关配置项以及常见问题。"
+ "description": "从 2.0 版本开始，Doris 在优化器中加入了 CBO 的能力。统计信息是 CBO 的基石，其准确性直接决定了代价估算的准确性，对于选择最优 Plan 至关重要。本文主要介绍统计信息的收集和管理方法、相关配置项以及常见问题。",
+ "sidebar_label": "统计信息"
}
---
+# 统计信息
+
从 2.0 版本开始，Doris 在优化器中加入了 CBO 的能力。统计信息是 CBO 的基石，其准确性直接决定了代价估算的准确性，对于选择最优 Plan 至关重要。本文主要介绍统计信息的收集和管理方法、相关配置项以及常见问题。
## 统计信息的收集
@@ -478,3 +481,4 @@ ADMIN DIAGNOSE TABLET tablet_id
对于某些特殊表，如分区众多的表或单个 Tablet 体积庞大的表，可能会出现内存占用较多的情况。
建议用户在建表时合理规划 Tablet 数量，避免产生超大 Tablet。若 Tablet 结构不易调整，建议在系统低峰期开启自动收集，或于低峰期手动收集这些大表，以免在高峰期影响业务运行。在 Doris 3.x 系列中，我们将针对此类场景进行优化。
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/date-time/DATE.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/date-time/DATE.md
index 49520815002..edad3af3f95 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/date-time/DATE.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/date-time/DATE.md
@@ -1,11 +1,14 @@
---
{
- "title": "DATE",
+ "title": "DATE | Date Time",
"language": "zh-CN",
- "description": "DATE 类型存储日期，取值范围是 [0000-01-01, 9999-12-31], 默认的输出格式为 'yyyy-MM-dd'。"
+ "description": "DATE 类型存储日期，取值范围是 [0000-01-01, 9999-12-31], 默认的输出格式为 'yyyy-MM-dd'。",
+ "sidebar_label": "DATE"
}
---
+# DATE
+
## 描述
DATE 类型存储日期，取值范围是 `[0000-01-01, 9999-12-31]`, 默认的输出格式为 'yyyy-MM-dd'。
@@ -45,3 +48,4 @@ select cast('0120-02-29' as date);
| 0120-02-29 |
+----------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/date-time/TIME.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/date-time/TIME.md
index 6d071a54e31..14f876aa4b2 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/date-time/TIME.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/date-time/TIME.md
@@ -1,11 +1,14 @@
---
{
- "title": "TIME",
+ "title": "TIME | Date Time",
"language": "zh-CN",
- "description": "TIME(p) 类型存储时间，其中 p 为精度，p 的取值范围为 [0, 6]，缺省值为 0。即 TIME 等同于 TIME(0)。"
+ "description": "TIME(p) 类型存储时间，其中 p 为精度，p 的取值范围为 [0, 6]，缺省值为 0。即 TIME 等同于 TIME(0)。",
+ "sidebar_label": "TIME"
}
---
+# TIME
+
## 描述
TIME(p) 类型存储时间，其中 p 为精度，p 的取值范围为 `[0, 6]`，缺省值为 0。即 TIME 等同于 TIME(0)。
@@ -43,3 +46,4 @@ select cast('838:59:59.999999' as time(6));
| 838:59:59.999999 |
+-------------------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
index a896154c5fb..5d0b1363b7d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/ARRAY.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Semi Structured",
"language": "zh-CN",
- "description": "ARRAY<T> 类型用于表示有序元素集合，集合中的每个元素具有相同的数据类型。例如，一个整数数组可表示为[1, 2, 3]，一个字符串数组可表示为[\"a\", \"b\", \"c\"]。"
+ "description": "ARRAY<T> 类型用于表示有序元素集合，集合中的每个元素具有相同的数据类型。例如，一个整数数组可表示为[1, 2, 3]，一个字符串数组可表示为[\"a\", \"b\", \"c\"]。",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
## 类型描述
`ARRAY<T>` 类型用于表示有序元素集合，集合中的每个元素具有相同的数据类型。例如，一个整数数组可表示为`[1, 2, 3]`，一个字符串数组可表示为`["a", "b", "c"]`。
@@ -324,4 +327,4 @@ select array(null) < array(-1), array(null) > array(-1);
| 2 | [4, 5, 6] |
| 3 | [7, 8, 9] |
+------+--------------+
- ```
\ No newline at end of file
+ ```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
index 7c2e06f1dda..fc416766ba5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/JSON.md
@@ -1,11 +1,14 @@
---
{
- "title": "JSON",
+ "title": "JSON | Semi Structured",
"language": "zh-CN",
- "description": "JSON（JavaScript Object Notation）是一种开放标准的文件格式和数据交换格式，使用可读性强的纯文本来存储和传输数据。根据官方规范 RFC7159，JSON 支持以下基本类型："
+ "description": "JSON（JavaScript Object Notation）是一种开放标准的文件格式和数据交换格式，使用可读性强的纯文本来存储和传输数据。根据官方规范 RFC7159，JSON 支持以下基本类型：",
+ "sidebar_label": "JSON"
}
---
+# JSON
+
## JSON 介绍
JSON（JavaScript Object Notation）是一种开放标准的文件格式和数据交换格式，使用可读性强的纯文本来存储和传输数据。根据官方规范 [RFC7159](https://datatracker.ietf.org/doc/html/rfc7159)，JSON 支持以下基本类型：
@@ -1097,3 +1100,4 @@ mysql> SELECT JSON_EXTRACT_STRING('{"key1" : null}', "$.key_not_exist") IS NULL;
### keywords
JSON, json_parse, json_parse_error_to_null, json_parse_error_to_value, json_extract, json_extract_isnull, json_extract_bool, json_extract_int, json_extract_bigint, json_extract_double, json_extract_String, json_exists_path, json_type
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
index 2b892f41d4d..efe5ee5a1cd 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/MAP.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Semi Structured",
"language": "zh-CN",
- "description": "````SQL SELECT MAP('Alice', 21, 'Bob', 23);"
+ "description": "````SQL SELECT MAP('Alice', 21, 'Bob', 23);",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
## 类型描述
- `MAP<key_type, value_type>`类型用于表示键值对集合的复合类型,每个键（key）唯一地对应一个值（value）。
@@ -211,4 +214,4 @@
| map_int_varchar | map<int,varchar(20)> | Yes | false | NULL | NONE |
| map_varchar_varchar | map<varchar(20),varchar(20)> | Yes | false | NULL | NONE |
+---------------------+------------------------------+------+-------+---------+-------+
- ```
\ No newline at end of file
+ ```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
index 3409fee76d3..16b28554afa 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/semi-structured/STRUCT.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Semi Structured",
"language": "zh-CN",
- "description": "STRUCT 类型用于将多个字段组合成一个结构体，每个字段可以有自己的名字和类型，适合表示嵌套或复杂的业务数据结构。"
+ "description": "STRUCT 类型用于将多个字段组合成一个结构体，每个字段可以有自己的名字和类型，适合表示嵌套或复杂的业务数据结构。",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
## 类型描述
STRUCT 类型用于将多个字段组合成一个结构体，每个字段可以有自己的名字和类型，适合表示嵌套或复杂的业务数据结构。
@@ -201,4 +204,4 @@ CREATE TABLE struct_table (
| k | int | No | true | NULL | |
| struct_varchar | struct<name:varchar(10),age:int,id:int> | Yes | false | NULL | NONE |
+----------------+-----------------------------------------+------+-------+---------+-------+
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/string-type/CHAR.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
index cd06dcfb960..2b86fcaca5e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/basic-element/sql-data-types/string-type/CHAR.md
@@ -1,11 +1,14 @@
---
{
- "title": "CHAR",
+ "title": "CHAR | String Type",
"language": "zh-CN",
- "description": "CHAR(M)"
+ "description": "CHAR(M)",
+ "sidebar_label": "CHAR"
}
---
+# CHAR
+
## description
CHAR(M)
@@ -15,3 +18,4 @@ CHAR(M)
## keywords
CHAR
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/array-functions/array.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/array-functions/array.md
index f10386e68e5..fb6d9109937 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/array-functions/array.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/array-functions/array.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Array Functions",
"language": "zh-CN",
- "description": "创建一个数组。函数接受零个或多个参数，返回一个包含所有输入元素的数组。"
+ "description": "创建一个数组。函数接受零个或多个参数，返回一个包含所有输入元素的数组。",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
## array
<version since="2.0.0">
@@ -136,3 +139,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = Can not find the compatibility
### Keywords
ARRAY
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
index e5f9b86f2e4..09fc033198d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/date-time-functions/date.md
@@ -1,11 +1,14 @@
---
{
- "title": "DATE",
+ "title": "DATE | Date Time Functions",
"language": "zh-CN",
- "description": "DATE 函数用于从日期时间值(包含日期和时间)中提取出纯日期部分，忽略时间信息。该函数可将 DATETIME 类型转换为 DATE 类型，仅保留年、月、日信息。"
+ "description": "DATE 函数用于从日期时间值(包含日期和时间)中提取出纯日期部分，忽略时间信息。该函数可将 DATETIME 类型转换为 DATE 类型，仅保留年、月、日信息。",
+ "sidebar_label": "DATE"
}
---
+# DATE
+
## 描述
DATE 函数用于从日期时间值(包含日期和时间)中提取出纯日期部分，忽略时间信息。该函数可将 DATETIME 类型转换为 DATE 类型，仅保留年、月、日信息。
@@ -58,4 +61,4 @@ mysql> select date(NULL);
| NULL |
+------------+
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/date-time-functions/time.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/date-time-functions/time.md
index 50574d0e6b7..b520510a39b 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/date-time-functions/time.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/date-time-functions/time.md
@@ -1,11 +1,14 @@
---
{
- "title": "TIME",
+ "title": "TIME | Date Time Functions",
"language": "zh-CN",
- "description": "TIME 函数可以获取一个DateTime值的 time 部分."
+ "description": "TIME 函数可以获取一个DateTime值的 time 部分.",
+ "sidebar_label": "TIME"
}
---
+# TIME
+
## 描述
`TIME` 函数可以获取一个`DateTime`值的 `time` 部分.
@@ -38,3 +41,4 @@ mysql>
| 12:12:12 |
+---------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/cut-ipv6.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/cut-ipv6.md
index b8091da0746..40fa4c8fdaf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/cut-ipv6.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/cut-ipv6.md
@@ -1,11 +1,14 @@
---
{
- "title": "CUT_IPV6",
+ "title": "CUT_IPV6 | Ip Functions",
"language": "zh-CN",
- "description": "根据 IPv6 地址的类型（IPv4 映射或纯 IPv6），从 IPv6 地址的末尾截取指定数量的字节，并返回截取后的 IPv6 地址字符串。"
+ "description": "根据 IPv6 地址的类型（IPv4 映射或纯 IPv6），从 IPv6 地址的末尾截取指定数量的字节，并返回截取后的 IPv6 地址字符串。",
+ "sidebar_label": "CUT_IPV6"
}
---
+# CUT_IPV6
+
## cut_ipv6
## 描述
@@ -79,3 +82,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = (...)[INVALID_ARGUMENT]Illegal
CUT_IPV6
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/cut_ipv6.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/cut_ipv6.md
index 66bc1602d2d..44fbb050ba9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/cut_ipv6.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/cut_ipv6.md
@@ -1,11 +1,14 @@
---
{
- "title": "CUT_IPV6",
+ "title": "CUT_IPV6 | Ip Functions",
"language": "zh-CN",
- "description": "根据 IPv6 地址的类型（IPv4 映射或纯 IPv6），从 IPv6 地址的末尾截取指定数量的字节，并返回截取后的 IPv6 地址字符串。"
+ "description": "根据 IPv6 地址的类型（IPv4 映射或纯 IPv6），从 IPv6 地址的末尾截取指定数量的字节，并返回截取后的 IPv6 地址字符串。",
+ "sidebar_label": "CUT_IPV6"
}
---
+# CUT_IPV6
+
## cut_ipv6
## 描述
@@ -107,3 +110,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = (...)[INVALID_ARGUMENT]Illegal
CUT_IPV6
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/inet-ntoa.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/inet-ntoa.md
index 0068f2bd089..fe6b1010177 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/inet-ntoa.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/inet-ntoa.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV4_NUM_TO_STRING",
+ "title": "IPV4_NUM_TO_STRING | Ip Functions",
"language": "zh-CN",
- "description": "别名 ipv4numtostring。"
+ "description": "别名 ipv4numtostring。",
+ "sidebar_label": "IPV4_NUM_TO_STRING"
}
---
+# IPV4_NUM_TO_STRING
+
## inet_ntoa
别名 `ipv4_num_to_string`。
@@ -85,4 +88,4 @@ select ipv4_num_to_string(4294967296);
### Keywords
-INET_NTOA, IPV4_NUM_TO_STRING
\ No newline at end of file
+INET_NTOA, IPV4_NUM_TO_STRING
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-aton.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-aton.md
index 550a00c8c55..49b4f8b406b 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-aton.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-aton.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_STRING_TO_NUM_OR_NULL",
+ "title": "IPV6_STRING_TO_NUM_OR_NULL | Ip Functions",
"language": "zh-CN",
- "description": "别名 ipv6stringtonumornull。"
+ "description": "别名 ipv6stringtonumornull。",
+ "sidebar_label": "IPV6_STRING_TO_NUM_OR_NULL"
}
---
+# IPV6_STRING_TO_NUM_OR_NULL
+
## inet6_aton
别名 `ipv6_string_to_num_or_null`。
@@ -78,4 +81,4 @@ select hex(ipv6_string_to_num_or_null('notaaddress')) as invalid;
### Keywords
-INET6_ATON, IPV6_STRING_TO_NUM_OR_NULL
\ No newline at end of file
+INET6_ATON, IPV6_STRING_TO_NUM_OR_NULL
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-ntoa.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-ntoa.md
index d08bb0a6091..20886a97923 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-ntoa.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/inet6-ntoa.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_NUM_TO_STRING",
+ "title": "IPV6_NUM_TO_STRING | Ip Functions",
"language": "zh-CN",
- "description": "别名 ipv6numtostring。"
+ "description": "别名 ipv6numtostring。",
+ "sidebar_label": "IPV6_NUM_TO_STRING"
}
---
+# IPV6_NUM_TO_STRING
+
## inet6_ntoa
别名 `ipv6_num_to_string`。
@@ -67,4 +70,4 @@ select ipv6_num_to_string('-23vno12i34nlfwlsj') as invalid;
### Keywords
-INET6_NTOA, IPV6_NUM_TO_STRING
\ No newline at end of file
+INET6_NTOA, IPV6_NUM_TO_STRING
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-cidr-to-range.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-cidr-to-range.md
index 911d3b5df04..9f3b11b22c4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-cidr-to-range.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-cidr-to-range.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV4_CIDR_TO_RANGE",
+ "title": "IPV4_CIDR_TO_RANGE | Ip Functions",
"language": "zh-CN",
- "description": "根据 IPv4 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv4 地址，返回一个包含两个 IPv4 地址的结构体。"
+ "description": "根据 IPv4 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv4 地址，返回一个包含两个 IPv4 地址的结构体。",
+ "sidebar_label": "IPV4_CIDR_TO_RANGE"
}
---
+# IPV4_CIDR_TO_RANGE
+
## ipv4_cidr_to_range
## 描述
@@ -77,3 +80,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = (...)[INVALID_ARGUMENT]Illegal
IPV4_CIDR_TO_RANGE
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-num-to-string.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-num-to-string.md
index 503d6584ef9..fd38cb1dab6 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-num-to-string.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4-num-to-string.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV4_NUM_TO_STRING",
+ "title": "IPV4_NUM_TO_STRING | Ip Functions",
"language": "zh-CN",
- "description": "接受一个类型为 Int16、Int32、Int64 且大端表示的 IPv4 的地址，返回相应 IPv4 的字符串表现形式，格式为 A.B.C.D（以点分割的十进制数字）。"
+ "description": "接受一个类型为 Int16、Int32、Int64 且大端表示的 IPv4 的地址，返回相应 IPv4 的字符串表现形式，格式为 A.B.C.D（以点分割的十进制数字）。",
+ "sidebar_label": "IPV4_NUM_TO_STRING"
}
---
+# IPV4_NUM_TO_STRING
+
## 描述
接受一个类型为 Int16、Int32、Int64 且大端表示的 IPv4 的地址，返回相应 IPv4 的字符串表现形式，格式为 A.B.C.D（以点分割的十进制数字）。
@@ -51,3 +54,4 @@ select num,ipv4_num_to_string(num) from ipv4_bi;
| 4294967296 | NULL |
+------------+---------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4_cidr_to_range.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4_cidr_to_range.md
index 8feb817adce..8035cf8bfd3 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4_cidr_to_range.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv4_cidr_to_range.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV4_CIDR_TO_RANGE",
+ "title": "IPV4_CIDR_TO_RANGE | Ip Functions",
"language": "zh-CN",
- "description": "根据 IPv4 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv4 地址，返回一个包含两个 IPv4 地址的结构体。"
+ "description": "根据 IPv4 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv4 地址，返回一个包含两个 IPv4 地址的结构体。",
+ "sidebar_label": "IPV4_CIDR_TO_RANGE"
}
---
+# IPV4_CIDR_TO_RANGE
+
## ipv4_cidr_to_range
## 描述
@@ -101,3 +104,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = (...)[INVALID_ARGUMENT]Illegal
IPV4_CIDR_TO_RANGE
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-cidr-to-range.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-cidr-to-range.md
index 93ac43b40e5..91c5d48f3a9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-cidr-to-range.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-cidr-to-range.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_CIDR_TO_RANGE",
+ "title": "IPV6_CIDR_TO_RANGE | Ip Functions",
"language": "zh-CN",
- "description": "根据 IPv6 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv6 地址，返回一个包含两个 IPv6 地址的结构体。"
+ "description": "根据 IPv6 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv6 地址，返回一个包含两个 IPv6 地址的结构体。",
+ "sidebar_label": "IPV6_CIDR_TO_RANGE"
}
---
+# IPV6_CIDR_TO_RANGE
+
## ipv6_cidr_to_range
## 描述
@@ -78,3 +81,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = (...)[INVALID_ARGUMENT]Illegal
IPV6_CIDR_TO_RANGE
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-num-to-string.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-num-to-string.md
index f1b3f24439d..2fcff0b9a4e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-num-to-string.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-num-to-string.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_NUM_TO_STRING",
+ "title": "IPV6_NUM_TO_STRING | Ip Functions",
"language": "zh-CN",
- "description": "接受字符串类型的二进制格式的 IPv6 地址。以文本格式返回此地址的字符串。"
+ "description": "接受字符串类型的二进制格式的 IPv6 地址。以文本格式返回此地址的字符串。",
+ "sidebar_label": "IPV6_NUM_TO_STRING"
}
---
+# IPV6_NUM_TO_STRING
+
## 描述
接受字符串类型的二进制格式的 IPv6 地址。以文本格式返回此地址的字符串。
@@ -38,3 +41,4 @@ select ipv6_num_to_string(unhex('2A0206B8000000000000000000000011')) as addr, ip
| 2a02:6b8::11 | NULL |
+--------------+------------------------------------------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-string-to-num-or-null.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-string-to-num-or-null.md
index b6069d33bf7..7634ab38224 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-string-to-num-or-null.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6-string-to-num-or-null.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_STRING_TO_NUM_OR_NULL",
+ "title": "IPV6_STRING_TO_NUM_OR_NULL | Ip Functions",
"language": "zh-CN",
- "description": "IPv6NumToString 的反向函数，它接受一个 IP 地址字符串并返回二进制格式的 IPv6 地址。"
+ "description": "IPv6NumToString 的反向函数，它接受一个 IP 地址字符串并返回二进制格式的 IPv6 地址。",
+ "sidebar_label": "IPV6_STRING_TO_NUM_OR_NULL"
}
---
+# IPV6_STRING_TO_NUM_OR_NULL
+
## 描述
IPv6NumToString 的反向函数，它接受一个 IP 地址字符串并返回二进制格式的 IPv6 地址。
@@ -38,3 +41,4 @@ select hex(ipv6_string_to_num_or_null('1111::ffff')) as r1, hex(ipv6_string_to_n
| 1111000000000000000000000000FFFF | 00000000000000000000FFFFC0A80001 | NULL |
+----------------------------------+----------------------------------+------+
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6_cidr_to_range.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6_cidr_to_range.md
index f224e86ca42..4681778176f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6_cidr_to_range.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/ip-functions/ipv6_cidr_to_range.md
@@ -1,11 +1,14 @@
---
{
- "title": "IPV6_CIDR_TO_RANGE",
+ "title": "IPV6_CIDR_TO_RANGE | Ip Functions",
"language": "zh-CN",
- "description": "根据 IPv6 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv6 地址，返回一个包含两个 IPv6 地址的结构体。"
+ "description": "根据 IPv6 地址和 CIDR 前缀长度，计算该网段的最小和最大 IPv6 地址，返回一个包含两个 IPv6 地址的结构体。",
+ "sidebar_label": "IPV6_CIDR_TO_RANGE"
}
---
+# IPV6_CIDR_TO_RANGE
+
## ipv6_cidr_to_range
## 描述
@@ -94,3 +97,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = (...)[INVALID_ARGUMENT]Illegal
IPV6_CIDR_TO_RANGE
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/map-functions/map.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/map-functions/map.md
index 1fdb0a894c7..459a0d636cf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/map-functions/map.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/map-functions/map.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Map Functions",
"language": "zh-CN",
- "description": "使用若干组键值对构造一个特定类型的 MAP<K, V>"
+ "description": "使用若干组键值对构造一个特定类型的 MAP<K, V>",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
## 描述
使用若干组键值对构造一个特定类型的 [`MAP<K, V>`](../../../basic-element/sql-data-types/semi-structured/MAP.md)
@@ -78,4 +81,4 @@ MAP( <key1> , <value1> [, <key2>, <value2> ... ])
+--------------------------------------------------------+
| {2:"11", 1:"3", null:"null 2"} |
+--------------------------------------------------------+
- ```
\ No newline at end of file
+ ```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/string-functions/char.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/string-functions/char.md
index 5261aaa0fae..86269511004 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/string-functions/char.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/string-functions/char.md
@@ -1,11 +1,14 @@
---
{
- "title": "CHAR",
+ "title": "CHAR | String Functions",
"language": "zh-CN",
- "description": "CHAR 函数将每个参数解释为整数，并返回一个由这些整数代码值组成字符的字符串。"
+ "description": "CHAR 函数将每个参数解释为整数，并返回一个由这些整数代码值组成字符的字符串。",
+ "sidebar_label": "CHAR"
}
---
+# CHAR
+
## 描述
CHAR 函数将每个参数解释为整数，并返回一个由这些整数代码值组成字符的字符串。
@@ -79,4 +82,4 @@ SELECT CHAR(NULL);
+------------+
| |
+------------+
-```
\ No newline at end of file
+```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
index b0a071b0b6d..2d087f414cf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/struct-functions/struct.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Struct Functions",
"language": "zh-CN",
- "description": "根据给定的值构造并返回 struct。函数接受一个或多个参数，返回一个包含所有输入元素的结构体。"
+ "description": "根据给定的值构造并返回 struct。函数接受一个或多个参数，返回一个包含所有输入元素的结构体。",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
## 描述
根据给定的值构造并返回 struct。函数接受一个或多个参数，返回一个包含所有输入元素的结构体。
@@ -96,3 +99,4 @@ ERROR 1105 (HY000): errCode = 2, detailMessage = struct requires at least one ar
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
index 3fe0ec00420..f82a3bdea5b 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-int-outer.md
@@ -1,11 +1,14 @@
---
{
- "title": "EXPLODE_JSON_ARRAY_JSON_OUTER",
+ "title": "EXPLODE_JSON_ARRAY_JSON_OUTER | Table Functions",
"language": "zh-CN",
- "description": "explodejsonarrayjsonouter 表函数，接受一个 JSON 数组，其实现逻辑是将 JSON 数组转换为数组类型然后再调用 explodeouter 函数处理，行为等价于：explodeouter(cast(<jsonarray> as Array<JSON>)) 。"
+ "description": "explodejsonarrayjsonouter 表函数，接受一个 JSON 数组，其实现逻辑是将 JSON 数组转换为数组类型然后再调用 explodeouter 函数处理，行为等价于：explodeouter(cast(<jsonarray> as Array<JSON>)) 。",
+ "sidebar_label": "EXPLODE_JSON_ARRAY_JSON_OUTER"
}
---
+# EXPLODE_JSON_ARRAY_JSON_OUTER
+
## 描述
`explode_json_array_json_outer` 表函数，接受一个 JSON 数组，其实现逻辑是将 JSON 数组转换为数组类型然后再调用 `explode_outer` 函数处理，行为等价于：`explode_outer(cast(<json_array> as Array<JSON>))`
。需配合 [`LATERAL VIEW`](../../../query-data/lateral-view.md) 使用。
@@ -80,4 +83,4 @@ EXPLODE_JSON_ARRAY_JSON_OUTER(<json>)
+------+------+
| 1 | NULL |
+------+------+
- ```
\ No newline at end of file
+ ```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-json-outer.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-json-outer.md
index 3fe0ec00420..f82a3bdea5b 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-json-outer.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-functions/explode-json-array-json-outer.md
@@ -1,11 +1,14 @@
---
{
- "title": "EXPLODE_JSON_ARRAY_JSON_OUTER",
+ "title": "EXPLODE_JSON_ARRAY_JSON_OUTER | Table Functions",
"language": "zh-CN",
- "description": "explodejsonarrayjsonouter 表函数，接受一个 JSON 数组，其实现逻辑是将 JSON 数组转换为数组类型然后再调用 explodeouter 函数处理，行为等价于：explodeouter(cast(<jsonarray> as Array<JSON>)) 。"
+ "description": "explodejsonarrayjsonouter 表函数，接受一个 JSON 数组，其实现逻辑是将 JSON 数组转换为数组类型然后再调用 explodeouter 函数处理，行为等价于：explodeouter(cast(<jsonarray> as Array<JSON>)) 。",
+ "sidebar_label": "EXPLODE_JSON_ARRAY_JSON_OUTER"
}
---
+# EXPLODE_JSON_ARRAY_JSON_OUTER
+
## 描述
`explode_json_array_json_outer` 表函数，接受一个 JSON 数组，其实现逻辑是将 JSON 数组转换为数组类型然后再调用 `explode_outer` 函数处理，行为等价于：`explode_outer(cast(<json_array> as Array<JSON>))`
。需配合 [`LATERAL VIEW`](../../../query-data/lateral-view.md) 使用。
@@ -80,4 +83,4 @@ EXPLODE_JSON_ARRAY_JSON_OUTER(<json>)
+------+------+
| 1 | NULL |
+------+------+
- ```
\ No newline at end of file
+ ```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-valued-functions/hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-valued-functions/hdfs.md
index 6e630bb3316..9470a432325 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-valued-functions/hdfs.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-valued-functions/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Table Valued Functions",
"language": "zh-CN",
- "description": "HDFS 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 HDFS 上的文件内容。目前支持csv/csvwithnames/csvwithnamesandtypes/json/parquet/orc文件格式。"
+ "description": "HDFS 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 HDFS 上的文件内容。目前支持csv/csvwithnames/csvwithnamesandtypes/json/parquet/orc文件格式。",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
## 描述
HDFS 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 HDFS 上的文件内容。目前支持`csv/csv_with_names/csv_with_names_and_types/json/parquet/orc`文件格式。
@@ -125,3 +128,4 @@ HDFS(
"hadoop.username" = "doris",
"format" = "csv_with_names");
```
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-valued-functions/s3.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-valued-functions/s3.md
index d094a6667ca..b431becba8e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-valued-functions/s3.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/table-valued-functions/s3.md
@@ -1,11 +1,14 @@
---
{
- "title": "S3",
+ "title": "S3 | Table Valued Functions",
"language": "zh-CN",
- "description": "S3 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 S3 兼容的对象存储上的文件内容。目前支持 csv/csv_with_names/csv_with_names_and_types/json/parquet/orc 文件格式。"
+ "description": "S3 表函数（table-valued-function,tvf），可以让用户像访问关系表格式数据一样，读取并访问 S3 兼容的对象存储上的文件内容。目前支持 csv/csv_with_names/csv_with_names_and_types/json/parquet/orc 文件格式。",
+ "sidebar_label": "S3"
}
---
+# S3
+
## 描述
S3 表函数（table-valued-function, tvf）可以让用户像访问关系表格式数据一样，读取并访问 S3 兼容的对象存储上的文件内容。目前支持 `csv/csv_with_names/csv_with_names_and_types/json/parquet/orc` 文件格式。
@@ -592,3 +595,4 @@ S3(
"read_json_by_line" = "true",
"use_path_style" = "true");
```
+
diff --git a/package.json b/package.json
index 65238ab24b8..e5485c9df95 100644
--- a/package.json
+++ b/package.json
@@ -50,6 +50,7 @@
"devDependencies": {
"@docusaurus/module-type-aliases": "3.6.3",
"@tsconfig/docusaurus": "2.0.3",
+ "gray-matter": "^4.0.3",
"typescript": "^5.2.2"
},
"resolutions": {
diff --git a/scripts/add_sidebar_label.py b/scripts/add_sidebar_label.py
new file mode 100644
index 00000000000..b89865fdf9f
--- /dev/null
+++ b/scripts/add_sidebar_label.py
@@ -0,0 +1,139 @@
+#!/usr/bin/env python3
+# -*- coding: utf-8 -*-
+"""
+脚本功能：
+1. 遍历 i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x 目录下的所有 md/mdx 文件
+2. 如果 frontMatter 中的 title 中包含 |，则在 frontMatter 中添加 sidebar_label 属性
+3. sidebar_label 的值是 title 中 | 的前面部分
+4. 如果 frontMatter 中已经有 sidebar_label 了，则不修改
+"""
+
+import re
+import json
+import sys
+from pathlib import Path
+
+
+def parse_frontmatter(content):
+ """解析frontMatter，支持JSON格式"""
+ # 匹配frontMatter，格式为 ---\n{...}\n---
+ frontmatter_pattern = re.compile(r'^---\s*\n(.*?)\n---\s*\n', re.DOTALL)
+ match = frontmatter_pattern.match(content)
+
+ if not match:
+ return None, content, None
+
+ frontmatter_str = match.group(1).strip()
+ body = content[match.end():]
+
+ # 尝试解析为JSON
+ try:
+ frontmatter = json.loads(frontmatter_str)
+ return frontmatter, body, frontmatter_str
+ except json.JSONDecodeError as e:
+ print(f"⚠️ 无法解析 frontMatter 为 JSON: {e}")
+ return None, content, None
+
+
+def process_file(file_path):
+ """处理单个文件"""
+ file_path = Path(file_path)
+ if not file_path.exists():
+ print(f"⚠️ 文件不存在：{file_path}")
+ return False
+
+ try:
+ with open(file_path, 'r', encoding='utf-8') as f:
+ content = f.read()
+ except Exception as e:
+ print(f"⚠️ 无法读取文件 {file_path}：{e}")
+ return False
+
+ # 解析frontMatter
+ result = parse_frontmatter(content)
+ if result[0] is None:
+ print(f"⚠️ {file_path} 没有有效的 frontMatter，跳过")
+ return False
+
+ frontmatter, body, frontmatter_str = result
+
+ # 检查是否已有 sidebar_label
+ if 'sidebar_label' in frontmatter:
+ print(f"✓ {file_path} 已有 sidebar_label，跳过")
+ return False
+
+ # 检查是否有 title
+ title = frontmatter.get('title')
+ if not title:
+ print(f"⚠️ {file_path} 没有 title 属性，跳过")
+ return False
+
+ # 检查 title 中是否包含 |
+ if '|' not in title:
+ print(f"✓ {file_path} title 中不包含 |，跳过")
+ return False
+
+ # 提取 | 前面的部分作为 sidebar_label
+ sidebar_label = title.split('|')[0].strip()
+
+ # 添加 sidebar_label
+ frontmatter['sidebar_label'] = sidebar_label
+
+ # 重新构建内容
+ # 保持原有的 JSON 格式（缩进等）
+ try:
+ # 尝试保持原有的格式
+ new_frontmatter_str = json.dumps(frontmatter, indent=4, ensure_ascii=False)
+ new_content = f"---\n{new_frontmatter_str}\n---\n\n{body}"
+
+ # 写回文件
+ with open(file_path, 'w', encoding='utf-8') as f:
+ f.write(new_content)
+ print(f"✓ 已处理：{file_path}，添加 sidebar_label: {sidebar_label}")
+ return True
+ except Exception as e:
+ print(f"❌ 无法写入文件 {file_path}：{e}")
+ return False
+
+
+def find_md_files(root_dir):
+ """递归查找所有 md/mdx 文件"""
+ root_path = Path(root_dir)
+ md_files = []
+
+ for file_path in root_path.rglob('*.md'):
+ md_files.append(file_path)
+
+ for file_path in root_path.rglob('*.mdx'):
+ md_files.append(file_path)
+
+ return md_files
+
+
+def main():
+ root_dir = "versioned_docs/version-2.1"
+
+ if not Path(root_dir).exists():
+ print(f"错误：目录 {root_dir} 不存在")
+ sys.exit(1)
+
+ print(f"正在查找 {root_dir} 目录下的所有 md/mdx 文件...")
+ md_files = find_md_files(root_dir)
+
+ if not md_files:
+ print("没有找到 md/mdx 文件")
+ return
+
+ print(f"找到 {len(md_files)} 个 md/mdx 文件\n")
+
+ processed_count = 0
+ for file_path in md_files:
+ if process_file(file_path):
+ processed_count += 1
+
+ print(f"\n处理完成！共处理 {processed_count} 个文件")
+
+
+if __name__ == '__main__':
+ main()
+
diff --git a/scripts/fix-duplicate-titles.js b/scripts/fix-duplicate-titles.js
new file mode 100644
index 00000000000..2dc413be4cd
--- /dev/null
+++ b/scripts/fix-duplicate-titles.js
@@ -0,0 +1,107 @@
+const fs = require('fs');
+const path = require('path');
+const matter = require('gray-matter');
+
+/**
+ * 遍历目录，返回所有 md/mdx 文件的路径
+ */
+function getAllDocs(dir) {
+ const result = [];
+ const entries = fs.readdirSync(dir, { withFileTypes: true });
+ for (const entry of entries) {
+ const fullPath = path.join(dir, entry.name);
+ if (entry.isDirectory()) {
+ result.push(...getAllDocs(fullPath));
+ } else if (entry.isFile() && /\.(md|mdx)$/.test(entry.name)) {
+ result.push(fullPath);
+ }
+ }
+ return result;
+}
+
+/**
+ * 将父目录名转成人类可读格式
+ * 例如：
+ * "complex-types" → "Complex Types"
+ * "sql_data-type" → "Sql Data Type"
+ */
+function formatDirName(name) {
+ return name
+ .split(/[-_]/g)
+ .filter(Boolean)
+ .map(word => word.charAt(0).toUpperCase() + word.slice(1))
+ .join(' ');
+}
+
+/**
+ * 提取原始 front matter 类型（判断是否 JSON）
+ */
+function detectFrontMatterFormat(content) {
+ const fmMatch = content.match(/^---\s*\n([\s\S]*?)\n---/);
+ if (!fmMatch) return null;
+ const fmText = fmMatch[1].trim();
+ return fmText.startsWith('{') ? 'json' : 'yaml';
+}
+
+/**
+ * 主逻辑
+ */
+function fixDuplicateTitles(baseDir) {
+ const files = getAllDocs(baseDir);
+
+ // 1️⃣ 读取所有文档的 title
+ const titleMap = new Map(); // title -> [filePaths]
+ for (const file of files) {
+ const content = fs.readFileSync(file, 'utf8');
+ const { data } = matter(content);
+ if (data.title) {
+ const title = String(data.title).trim();
+ if (!titleMap.has(title)) titleMap.set(title, []);
+ titleMap.get(title).push(file);
+ }
+ }
+
+ // 2️⃣ 找出重复 title
+ for (const [title, paths] of titleMap.entries()) {
+ if (paths.length > 1) {
+ console.log(`\n⚠️ 发现重复标题 "${title}" (${paths.length} 个文件)：`);
+ for (const filePath of paths) {
+ console.log(` → ${filePath}`);
+
+ const content = fs.readFileSync(filePath, 'utf8');
+ const parsed = matter(content);
+ const fmFormat = detectFrontMatterFormat(content);
+ const parentDir = path.basename(path.dirname(filePath));
+ const formattedParent = formatDirName(parentDir);
+
+ // 更新标题
+ parsed.data.title = `${title} | ${formattedParent}`;
+
+ // 保留 JSON 格式 front matter
+ let newFrontMatter = '';
+ if (fmFormat === 'json') {
+ newFrontMatter = `---\n${JSON.stringify(parsed.data, null, 4)}\n---`;
+ } else {
+ // fallback (YAML)
+ newFrontMatter = matter.stringify('', parsed.data).split('\n').slice(0, -1).join('\n');
+ }
+
+ // 拼回完整文件
+ const body = parsed.content.trimStart();
+ const newContent = `${newFrontMatter}\n\n${body}\n`;
+ fs.writeFileSync(filePath, newContent);
+ }
+ }
+ }
+
+ console.log('\n✅ 重复标题已修正完成。');
+}
+
+// CLI 调用
+const baseDir = process.argv[2];
+if (!baseDir) {
+ console.error('❌ 请提供要遍历的目录，如: node fix-duplicate-titles.js ./docs');
+ process.exit(1);
+}
+
+fixDuplicateTitles(path.resolve(baseDir));
diff --git a/scripts/fix_title_in_content.py b/scripts/fix_title_in_content.py
new file mode 100644
index 00000000000..f3b1e746cc1
--- /dev/null
+++ b/scripts/fix_title_in_content.py
@@ -0,0 +1,180 @@
+#!/usr/bin/env python3
+# -*- coding: utf-8 -*-
+"""
+脚本功能：
+1. 获取指定commit修改的md/mdx文件
+2. 如果frontMatter的title属性是 "${title} | xxxx" 格式
+3. 检查文档内容中是否已有任何一级标题（# xxx 格式）
+4. 如果文档中没有一级标题，则在文档开头添加 "# ${title}"（| 之前的内容）
+"""
+
+import re
+import json
+import subprocess
+import sys
+from pathlib import Path
+
+
+def get_modified_files(commit_hash):
+ """获取指定commit修改的md/mdx文件"""
+ try:
+ # 获取该commit修改的文件列表
+ result = subprocess.run(
+ ['git', 'diff-tree', '--no-commit-id', '--name-only', '-r', commit_hash],
+ capture_output=True,
+ text=True,
+ check=True
+ )
+
+ files = result.stdout.strip().split('\n')
+ # 过滤出md和mdx文件
+ md_files = [f for f in files if f.endswith(('.md', '.mdx'))]
+ return md_files
+ except subprocess.CalledProcessError as e:
+ print(f"错误：无法获取commit {commit_hash} 的信息")
+ print(f"错误信息：{e.stderr}")
+ sys.exit(1)
+ except Exception as e:
+ print(f"错误：{e}")
+ sys.exit(1)
+
+
+def parse_frontmatter(content):
+ """解析frontMatter，支持JSON和YAML格式"""
+ # 匹配frontMatter，格式为 ---\n{...}\n--- 或 ---\n...\n---
+ frontmatter_pattern = re.compile(r'^---\s*\n(.*?)\n---\s*\n', re.DOTALL)
+ match = frontmatter_pattern.match(content)
+
+ if not match:
+ return None, content
+
+ frontmatter_str = match.group(1).strip()
+ body = content[match.end():]
+
+ # 尝试解析为JSON
+ try:
+ frontmatter = json.loads(frontmatter_str)
+ return frontmatter, body
+ except json.JSONDecodeError:
+ # 如果不是JSON，尝试解析为YAML（简单处理）
+ # 这里只处理简单的key: value格式
+ frontmatter = {}
+ for line in frontmatter_str.split('\n'):
+ if ':' in line:
+ key, value = line.split(':', 1)
+ key = key.strip()
+ value = value.strip().strip('"').strip("'")
+ frontmatter[key] = value
+ return frontmatter, body
+
+
+def check_title_format(title):
+ """检查title格式是否为 "${title} | xxxx" """
+ if not title or not isinstance(title, str):
+ return None, None
+
+ pattern = r'^(.+?)\s*\|\s*(.+)$'
+ match = re.match(pattern, title)
+ if match:
+ main_title = match.group(1).strip()
+ suffix = match.group(2).strip()
+ return main_title, suffix
+ return None, None
+
+
+def has_heading_in_content(content, heading_text):
+ """检查文档内容中是否有 "# heading_text" """
+ # 匹配markdown标题，格式为 # heading_text 或 ## heading_text 等
+ # 需要精确匹配，考虑标题可能在行首或行中
+ pattern = r'^#{1,6}\s+' + re.escape(heading_text) + r'(?:\s|$|#)'
+ return bool(re.search(pattern, content, re.MULTILINE))
+
+
+def has_any_level1_heading(content):
+ """检查文档内容中是否有任何一级标题（# xxx 格式）"""
+ # 匹配一级标题，格式为 # 后面跟非空内容
+ pattern = r'^#\s+[^\s#]'
+ return bool(re.search(pattern, content, re.MULTILINE))
+
+
+def process_file(file_path):
+ """处理单个文件"""
+ file_path = Path(file_path)
+ if not file_path.exists():
+ print(f"⚠️ 文件不存在：{file_path}")
+ return False
+
+ try:
+ with open(file_path, 'r', encoding='utf-8') as f:
+ content = f.read()
+ except Exception as e:
+ print(f"⚠️ 无法读取文件 {file_path}：{e}")
+ return False
+
+ # 解析frontMatter
+ frontmatter, body = parse_frontmatter(content)
+ if not frontmatter:
+ print(f"⚠️ {file_path} 没有frontMatter，跳过")
+ return False
+
+ # 检查title
+ title = frontmatter.get('title')
+ if not title:
+ print(f"⚠️ {file_path} 没有title属性，跳过")
+ return False
+
+ # 检查title格式
+ main_title, suffix = check_title_format(title)
+ if not main_title or not suffix:
+ print(f"⚠️ {file_path} title格式不符合要求：{title}")
+ return False
+
+ # 检查文档内容中是否已有任何一级标题（# xxx 格式）
+ if has_any_level1_heading(body):
+ print(f"✓ {file_path} 文档中已包含一级标题，跳过")
+ return False
+
+ # 在文档开头添加标题
+ # 在frontMatter之后，body之前添加
+ # 添加的是 | 之前的内容（main_title）
+ new_title_line = f"# {main_title}\n\n"
+
+ # 重新构建内容
+ frontmatter_str = json.dumps(frontmatter, indent=4, ensure_ascii=False)
+ new_content = f"---\n{frontmatter_str}\n---\n\n{new_title_line}{body}"
+
+ # 写回文件
+ try:
+ with open(file_path, 'w', encoding='utf-8') as f:
+ f.write(new_content)
+ print(f"✓ 已处理：{file_path}，添加标题 '# {main_title}'")
+ return True
+ except Exception as e:
+ print(f"❌ 无法写入文件 {file_path}：{e}")
+ return False
+
+
+def main():
+ commit_hash = "c402aa049343c669dbbb0e57c193b7957627dbef"
+
+ print(f"正在获取commit {commit_hash} 修改的md/mdx文件...")
+ modified_files = get_modified_files(commit_hash)
+
+ if not modified_files:
+ print("没有找到修改的md/mdx文件")
+ return
+
+ print(f"找到 {len(modified_files)} 个修改的md/mdx文件\n")
+
+ processed_count = 0
+ for file_path in modified_files:
+ if process_file(file_path):
+ processed_count += 1
+ print()
+
+ print(f"处理完成！共处理 {processed_count} 个文件")
+
+
+if __name__ == '__main__':
+ main()
+
diff --git a/versioned_docs/version-2.1/admin-manual/config/fe-config-template.md b/versioned_docs/version-2.1/admin-manual/config/fe-config-template.md
index d31f7025021..1ae6f1ac36e 100644
--- a/versioned_docs/version-2.1/admin-manual/config/fe-config-template.md
+++ b/versioned_docs/version-2.1/admin-manual/config/fe-config-template.md
@@ -1,10 +1,11 @@
---
{
- "title": "FE Configuration",
+ "title": "FE Configuration Template | Config",
"language": "en",
"toc_min_heading_level": 2,
"toc_max_heading_level": 4,
- "description": "This document mainly introduces the relevant configuration items of FE."
+ "description": "This document mainly introduces the relevant configuration items of FE.",
+ "sidebar_label": "FE Configuration Template"
}
---
@@ -121,3 +122,4 @@ There are two ways to configure FE configuration items:
> If you need to modify, please modify the description information in `fe/fe-common/src/main/java/org/apache/doris/common/Config.java`.
<--DOC_PLACEHOLDER-->
+
diff --git a/versioned_docs/version-2.1/admin-manual/config/fe-config.md b/versioned_docs/version-2.1/admin-manual/config/fe-config.md
index 62669ebadde..6797b9f5733 100644
--- a/versioned_docs/version-2.1/admin-manual/config/fe-config.md
+++ b/versioned_docs/version-2.1/admin-manual/config/fe-config.md
@@ -1,10 +1,11 @@
---
{
- "title": "FE Configuration",
+ "title": "FE Configuration | Config",
"language": "en",
"toc_min_heading_level": 2,
"toc_max_heading_level": 4,
- "description": "This document mainly introduces the relevant configuration items of FE."
+ "description": "This document mainly introduces the relevant configuration items of FE.",
+ "sidebar_label": "FE Configuration"
}
---
@@ -2754,3 +2755,4 @@ To ensure compatibility with the MySQL ecosystem, Doris includes a built-in data
Default value: 2000
For auto-partitioned tables to prevent users from accidentally creating a large number of partitions, the number of partitions allowed per OLAP table is `max_auto_partition_num`. Default 2000.
+
diff --git a/versioned_docs/version-2.1/admin-manual/data-admin/ccr/overview.md b/versioned_docs/version-2.1/admin-manual/data-admin/ccr/overview.md
index d4593f5e91c..5191d4d1eda 100644
--- a/versioned_docs/version-2.1/admin-manual/data-admin/ccr/overview.md
+++ b/versioned_docs/version-2.1/admin-manual/data-admin/ccr/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | CCR",
"language": "en",
- "description": "CCR (Cross Cluster Replication) is a cross-cluster data synchronization mechanism that synchronizes data changes from the source cluster to the "
+ "description": "CCR (Cross Cluster Replication) is a cross-cluster data synchronization mechanism that synchronizes data changes from the source cluster to the ",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
## Overview
CCR (Cross Cluster Replication) is a cross-cluster data synchronization mechanism that synchronizes data changes from the source cluster to the target cluster at the database or table level. It is mainly used to enhance the data availability of online services, isolate read and write loads, and build a dual-site, three-center architecture. CCR currently does not support the separation of computing and storage modes.
@@ -87,3 +90,4 @@ requirement: glibc >= 2.28
| 3.0 | ARM64 | [ccr-syncer-3.0.6-rc05-arm64.tar.xz](https://apache-doris-releases.oss-accelerate.aliyuncs.com/ccr-release/ccr-syncer-3.0.6-rc05-arm64.tar.xz) | dd5f154c68007732c3c3a9f808f16a7f287fd742bd35d0272ef596779f0eb8e6 |
| 3.0 | X64 | [ccr-syncer-3.0.6-rc05-x64.tar.xz](https://apache-doris-releases.oss-accelerate.aliyuncs.com/ccr-release/ccr-syncer-3.0.6-rc05-x64.tar.xz) | 77a4e4e2a74c376ffaef0207cfdef957729380fa3718418bccece015a41ad15a |
+
diff --git a/versioned_docs/version-2.1/admin-manual/data-admin/ccr/quickstart.md b/versioned_docs/version-2.1/admin-manual/data-admin/ccr/quickstart.md
index 13917db3a83..2d77b5698b3 100644
--- a/versioned_docs/version-2.1/admin-manual/data-admin/ccr/quickstart.md
+++ b/versioned_docs/version-2.1/admin-manual/data-admin/ccr/quickstart.md
@@ -1,8 +1,9 @@
---
{
- "title": "Quick Start",
+ "title": "Quick Start | CCR",
"language": "en",
- "description": "Configure the following information in the fe.conf and be.conf of both the source and target clusters:"
+ "description": "Configure the following information in the fe.conf and be.conf of both the source and target clusters:",
+ "sidebar_label": "Quick Start"
}
---
@@ -78,3 +79,4 @@ If synchronizing at the database level, fill in your_db_name, and leave your_tab
If synchronizing at the table level, fill in both your_db_name and your_table_name
The name used to initiate the synchronization job can only be used once
```
+
diff --git a/versioned_docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action-V2.md b/versioned_docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action-V2.md
index 111c687d612..4bf2ed2c20d 100644
--- a/versioned_docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action-V2.md
+++ b/versioned_docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action-V2.md
@@ -1,8 +1,9 @@
---
{
- "title": "Meta Info Action",
+ "title": "Meta Info Action | Fe Http",
"language": "en",
- "description": "Used to obtain metadata information about the cluster, including the database list, table list, and table schema."
+ "description": "Used to obtain metadata information about the cluster, including the database list, table list, and table schema.",
+ "sidebar_label": "Meta Info Action"
}
---
@@ -52,3 +53,4 @@ None
"count":0
}
```
+
diff --git a/versioned_docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action.md b/versioned_docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action.md
index b23625bfa71..67f2d6a1eac 100644
--- a/versioned_docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action.md
+++ b/versioned_docs/version-2.1/admin-manual/open-api/fe-http/meta-info-action.md
@@ -1,8 +1,9 @@
---
{
- "title": "Meta Info Action",
+ "title": "Meta Info Action | Fe Http",
"language": "en",
- "description": "Meta Info Action is used to obtain metadata information in the cluster. Such as database list, table structure, etc."
+ "description": "Meta Info Action is used to obtain metadata information in the cluster. Such as database list, table structure, etc.",
+ "sidebar_label": "Meta Info Action"
}
---
@@ -212,3 +213,4 @@ GET /api/meta/namespaces/default/databases/db1/tables/tbl1/schema?with_mv?=1
```
* The data field returns the table structure information of the base table or rollup table.
+
diff --git a/versioned_docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action-controller.md b/versioned_docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action-controller.md
index b36b57d1b86..37ab7dbd158 100644
--- a/versioned_docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action-controller.md
+++ b/versioned_docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action-controller.md
@@ -1,8 +1,9 @@
---
{
- "title": "Query Profile Action",
+ "title": "Query Profile Action | Fe Http",
"language": "en",
- "description": "The Query Profile Action is used to obtain the Query profile."
+ "description": "The Query Profile Action is used to obtain the Query profile.",
+ "sidebar_label": "Query Profile Action"
}
---
@@ -87,4 +88,4 @@ None
}
```
- `data` is the text content of the profile.
\ No newline at end of file
+ `data` is the text content of the profile.
diff --git a/versioned_docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action.md b/versioned_docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action.md
index aa983657684..df6067d13b9 100644
--- a/versioned_docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action.md
+++ b/versioned_docs/version-2.1/admin-manual/open-api/fe-http/query-profile-action.md
@@ -1,11 +1,14 @@
---
{
- "title": "Query Profile Action",
+ "title": "Query Profile Action | Fe Http",
"language": "en",
- "description": "Gets information about select queries for all fe nodes in the cluster."
+ "description": "Gets information about select queries for all fe nodes in the cluster.",
+ "sidebar_label": "Query Profile Action"
}
---
+# Query Profile Action
+
## Request
`GET /rest/v2/manager/query/query_info`
@@ -479,3 +482,4 @@ Cancel query of specified connection.
"count": 0
}
```
+
diff --git a/versioned_docs/version-2.1/admin-manual/open-api/overview.md b/versioned_docs/version-2.1/admin-manual/open-api/overview.md
index 158a4611dc9..a33ce2654e9 100644
--- a/versioned_docs/version-2.1/admin-manual/open-api/overview.md
+++ b/versioned_docs/version-2.1/admin-manual/open-api/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Open Api",
"language": "en",
- "description": "As a supplement to Apache Doris operation and maintenance management,"
+ "description": "As a supplement to Apache Doris operation and maintenance management,",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
As a supplement to Apache Doris operation and maintenance management, OPEN API is mainly used by database administrators to perform some management operations.
:::note
@@ -27,3 +30,4 @@ The security authentication of FE BE API can be enabled through the following co
The permission requirements for the HTTP API of FE and BE vary from version to version. Please refer to the corresponding API documentation for details.
:::
+
diff --git a/versioned_docs/version-2.1/admin-manual/system-tables/information_schema/column_statistics.md b/versioned_docs/version-2.1/admin-manual/system-tables/information_schema/column_statistics.md
index e7b4d3f78fd..18cd3417f29 100644
--- a/versioned_docs/version-2.1/admin-manual/system-tables/information_schema/column_statistics.md
+++ b/versioned_docs/version-2.1/admin-manual/system-tables/information_schema/column_statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "column_statistics",
+ "title": "Column Statistics | Information Schema",
"language": "en",
- "description": "This table is solely used for compatibility with MySQL behavior and is always empty."
+ "description": "This table is solely used for compatibility with MySQL behavior and is always empty.",
+ "sidebar_label": "Column Statistics"
}
---
+# Column Statistics
+
## Overview
This table is solely used for compatibility with MySQL behavior and is always empty. It does not truly reflect the statistical information of the data within Doris. To view the statistical information collected by Doris, please refer to the [Statistics](../../../query-acceleration/optimization-technology-principle/statistics#viewing-statistics) section.
@@ -23,4 +26,4 @@ This table is solely used for compatibility with MySQL behavior and is always em
| SCHEMA_NAME | varchar(64) | |
| TABLE_NAME | varchar(64) | |
| COLUMN_NAME | varchar(64) | |
-| HISTOGRAM | json | |
\ No newline at end of file
+| HISTOGRAM | json | |
diff --git a/versioned_docs/version-2.1/admin-manual/system-tables/internal_schema/column_statistics.md b/versioned_docs/version-2.1/admin-manual/system-tables/internal_schema/column_statistics.md
index 3cd984e6f65..28394e21919 100644
--- a/versioned_docs/version-2.1/admin-manual/system-tables/internal_schema/column_statistics.md
+++ b/versioned_docs/version-2.1/admin-manual/system-tables/internal_schema/column_statistics.md
@@ -1,11 +1,14 @@
---
{
- "title": "column_statistics",
+ "title": "Column Statistics | Internal Schema",
"language": "en",
- "description": "Column statistics"
+ "description": "Column statistics",
+ "sidebar_label": "Column Statistics"
}
---
+# Column Statistics
+
## Overview
Column statistics
@@ -33,4 +36,4 @@ Column statistics
| min | varchar(65533) | Minimum value |
| max | varchar(65533) | Maximum value |
| data_size_in_bytes | bigint | Data size in bytes |
-| update_time | datetime | Update time of current statistics |
\ No newline at end of file
+| update_time | datetime | Update time of current statistics |
diff --git a/versioned_docs/version-2.1/admin-manual/system-tables/overview.md b/versioned_docs/version-2.1/admin-manual/system-tables/overview.md
index 86ede0f477b..a0de6d186b5 100644
--- a/versioned_docs/version-2.1/admin-manual/system-tables/overview.md
+++ b/versioned_docs/version-2.1/admin-manual/system-tables/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | System Tables",
"language": "zh-CN",
- "description": "Apache Doris cluster has multiple built-in system databases to store metadata information about the Doris system itself."
+ "description": "Apache Doris cluster has multiple built-in system databases to store metadata information about the Doris system itself.",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
Apache Doris cluster has multiple built-in system databases to store metadata information about the Doris system itself.
### information_schema
@@ -31,3 +34,4 @@ All tables in the `mysql` database are read-only, and users cannot modify, delet
All tables under the `__internal_schema` database are actual tables in Doris, stored similarly to user-created data tables. When a Doris cluster is created, all system tables under this database are automatically created.
By default, common users have read-only permissions for tables in this database. However, once granted, they can modify, delete, or create tables under this database.
+
diff --git a/versioned_docs/version-2.1/admin-manual/trouble-shooting/memory-management/overview.md b/versioned_docs/version-2.1/admin-manual/trouble-shooting/memory-management/overview.md
index 1961a93a6a2..db8b308dfdd 100644
--- a/versioned_docs/version-2.1/admin-manual/trouble-shooting/memory-management/overview.md
+++ b/versioned_docs/version-2.1/admin-manual/trouble-shooting/memory-management/overview.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Memory Management",
"language": "en",
- "description": "Memory management is one of the most important components of Doris. During the operation of Doris,"
+ "description": "Memory management is one of the most important components of Doris. During the operation of Doris,",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
Memory management is one of the most important components of Doris. During the operation of Doris, both load and query rely on a large number of memory operations. The quality of memory management directly affects the stability and performance of Doris.
As an OLAP database based on the MPP architecture, Apache Doris will stream and calculate between operators after loading data from disk to memory, and store the intermediate results of calculation in memory. This method reduces frequent disk I/O operations and makes full use of the parallel computing capabilities of multiple machines and multiple cores, which can show huge advantages in performance.
@@ -143,3 +146,4 @@ Refer to [Memory problem FAQ](./memory-issue-faq.md) to analyze common memory pr
## Memory control strategy
Refer to [Memory Control Strategy](./memory-feature/memory-control-strategy.md) for an introduction to memory allocation, monitoring, and recycling, which ensure the efficient and controllable memory of the Doris BE process.
+
diff --git a/versioned_docs/version-2.1/admin-manual/workload-management/job-scheduler.md b/versioned_docs/version-2.1/admin-manual/workload-management/job-scheduler.md
index 4f2051725db..82e715ff95d 100644
--- a/versioned_docs/version-2.1/admin-manual/workload-management/job-scheduler.md
+++ b/versioned_docs/version-2.1/admin-manual/workload-management/job-scheduler.md
@@ -1,11 +1,14 @@
---
{
- "title": "Job Scheduler",
+ "title": "Job Scheduler | Workload Management",
"language": "en",
- "description": "In the context of increasing demands for refined data management, scheduled scheduling plays an important role."
+ "description": "In the context of increasing demands for refined data management, scheduled scheduling plays an important role.",
+ "sidebar_label": "Job Scheduler"
}
---
+# Job Scheduler
+
## Background
In the context of increasing demands for refined data management, scheduled scheduling plays an important role. It is typically applied in the following scenarios:
@@ -216,3 +219,4 @@ In the future, Doris Job Scheduler will also support the following features:
- Support for JOB workflow orchestration, i.e., DAG JOB. This means we can implement internal data warehouse task orchestration, and with the Catalog functionality, it will more efficiently complete data processing and analysis tasks.
- Support for scheduling import tasks, UPDATE, and DELETE operations.
+
diff --git a/versioned_docs/version-2.1/admin-manual/workload-management/workload-management-summary.md b/versioned_docs/version-2.1/admin-manual/workload-management/workload-management-summary.md
index 42798c68505..f14edf75ec4 100644
--- a/versioned_docs/version-2.1/admin-manual/workload-management/workload-management-summary.md
+++ b/versioned_docs/version-2.1/admin-manual/workload-management/workload-management-summary.md
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Workload Management",
"language": "en",
- "description": "Workload management is a very important feature of Doris, playing a critical role in the overall system management."
+ "description": "Workload management is a very important feature of Doris, playing a critical role in the overall system management.",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
Workload management is a very important feature of Doris, playing a critical role in the overall system management. Through reasonable workload management strategies, resource utilization can be optimized, system stability enhanced, and response time reduced. It has the following abilities:
- Resource Isolation: By dividing into multiple groups and setting resource (CPU, Memory, IO) limits for each group, it ensures that there is no interference between multiple users or different tasks (such as read and write operations) of the same user.
@@ -39,3 +42,4 @@ The following table records the characteristics and advantageous scenarios of di
- Soft Limit: The soft limit is a resource limit that can be exceeded, usually representing the recommended upper limit of resource usage. When the system is not busy, if a tenant requests more resources than the soft limit, it can borrow resources from other groups. When the system is busy and there is resource contention, if a tenant requests resources exceeding the soft limit, it will not be able to obtain additional resources.
When using the Resource Group / Compute Group method to partition resources, only the hard limit mode is supported. When using the Workload Group method to partition resources, both the soft limit and hard limit of Workload Group are supported. The soft limit of Workload Group is usually used for sudden resource control, such as temporary query peaks or short-term increases in data writing.
+
diff --git a/versioned_docs/version-2.1/data-operate/export/export-best-practice.md b/versioned_docs/version-2.1/data-operate/export/export-best-practice.md
index e52c95d2a42..4feaba0c383 100644
--- a/versioned_docs/version-2.1/data-operate/export/export-best-practice.md
+++ b/versioned_docs/version-2.1/data-operate/export/export-best-practice.md
@@ -1,11 +1,14 @@
---
{
- "title": "Best Practices",
+ "title": "Best Practices | Export",
"language": "en",
- "description": "This document mainly introduces how to determine whether resource utilization is reasonable during data export operations,"
+ "description": "This document mainly introduces how to determine whether resource utilization is reasonable during data export operations,",
+ "sidebar_label": "Best Practices"
}
---
+# Best Practices
+
This document mainly introduces how to determine whether resource utilization is reasonable during data export operations, and how to adjust resource utilization to achieve better data export efficiency.
## SELECT INTO OUTFILE
@@ -94,3 +97,4 @@ This document mainly introduces how to determine whether resource utilization is
- `async_task_consumer_thread_num`
This is an FE configuration parameter that indicates the number of Export Tasks that the current cluster can run concurrently. The default value is 64. An Export Job is split into multiple Export Tasks based on concurrency. All Export Tasks share this threshold. To increase the overall number of concurrent export tasks that the cluster can execute, increase this parameter and restart the FE node.
+
diff --git a/versioned_docs/version-2.1/data-operate/export/export-manual.md b/versioned_docs/version-2.1/data-operate/export/export-manual.md
index ccbfdef9a9f..7a204755e09 100644
--- a/versioned_docs/version-2.1/data-operate/export/export-manual.md
+++ b/versioned_docs/version-2.1/data-operate/export/export-manual.md
@@ -1,11 +1,14 @@
---
{
- "title": "EXPORT",
+ "title": "Export Manual | Export",
"language": "en",
- "description": "This document will introduce how to use the EXPORT command to export the data stored in Doris."
+ "description": "This document will introduce how to use the EXPORT command to export the data stored in Doris.",
+ "sidebar_label": "Export Manual"
}
---
+# Export Manual
+
This document will introduce how to use the `EXPORT` command to export the data stored in Doris.
`Export` is a function provided by Doris for asynchronously exporting data. This function can export the data of the tables or partitions specified by users in the specified file format to the target storage systems, including object storage, HDFS or local file system.
@@ -386,3 +389,4 @@ The specific BE node IP can be viewed in the `OutfileInfo` column in the `SHOW E
:::caution
This function is not applicable to the production environment, and please ensure the permissions of the export directory and data security on your own.
:::
+
diff --git a/versioned_docs/version-2.1/data-operate/import/complex-types/array.md b/versioned_docs/version-2.1/data-operate/import/complex-types/array.md
index 98c07bc1bd2..01eb71cd774 100644
--- a/versioned_docs/version-2.1/data-operate/import/complex-types/array.md
+++ b/versioned_docs/version-2.1/data-operate/import/complex-types/array.md
@@ -1,11 +1,14 @@
---
{
- "title": "ARRAY",
+ "title": "ARRAY | Complex Types",
"language": "en",
- "description": "ARRAY<T> An array of T-type items, it cannot be used as a key column."
+ "description": "ARRAY<T> An array of T-type items, it cannot be used as a key column.",
+ "sidebar_label": "ARRAY"
}
---
+# ARRAY
+
`ARRAY<T>` An array of T-type items, it cannot be used as a key column.
- Before version 2.0, it was only supported in the Duplicate model table.
@@ -127,3 +130,4 @@ mysql> SELECT * FROM array_test;
+------+-----------------+
4 rows in set (0.01 sec)
```
+
diff --git a/versioned_docs/version-2.1/data-operate/import/complex-types/json.md b/versioned_docs/version-2.1/data-operate/import/complex-types/json.md
index 9a129e4fa9e..10e6712853d 100644
--- a/versioned_docs/version-2.1/data-operate/import/complex-types/json.md
+++ b/versioned_docs/version-2.1/data-operate/import/complex-types/json.md
@@ -1,11 +1,14 @@
---
{
- "title": "JSON",
+ "title": "JSON | Complex Types",
"language": "en",
- "description": "The JSON data type stores JSON data efficiently in a binary format and allows access to its internal fields through JSON functions."
+ "description": "The JSON data type stores JSON data efficiently in a binary format and allows access to its internal fields through JSON functions.",
+ "sidebar_label": "JSON"
}
---
+# JSON
+
The JSON data type stores JSON data efficiently in a binary format and allows access to its internal fields through JSON functions.
By default, it supports up to 1048576 bytes (1MB), and can be increased up to 2147483643 bytes (2GB). This can be adjusted via the string_type_length_soft_limit_bytes configuration.
@@ -129,3 +132,4 @@ mysql> SELECT * FROM json_test;
+------+-------------------------------+
5 rows in set (0.01 sec)
```
+
diff --git a/versioned_docs/version-2.1/data-operate/import/complex-types/map.md b/versioned_docs/version-2.1/data-operate/import/complex-types/map.md
index fc0e3b26b97..cfe3b43782f 100644
--- a/versioned_docs/version-2.1/data-operate/import/complex-types/map.md
+++ b/versioned_docs/version-2.1/data-operate/import/complex-types/map.md
@@ -1,11 +1,14 @@
---
{
- "title": "MAP",
+ "title": "MAP | Complex Types",
"language": "en",
- "description": "MAP<K, V> A Map of K, V items, it cannot be used as a key column. Now MAP can only be used in Duplicate and Unique Model Tables."
+ "description": "MAP<K, V> A Map of K, V items, it cannot be used as a key column. Now MAP can only be used in Duplicate and Unique Model Tables.",
+ "sidebar_label": "MAP"
}
---
+# MAP
+
`MAP<K, V>` A Map of K, V items, it cannot be used as a key column. Now MAP can only be used in Duplicate and Unique Model Tables.
K,V could be any of:
@@ -124,3 +127,4 @@ mysql> SELECT * FROM map_test;
+------+-------------------------+
4 rows in set (0.01 sec)
```
+
diff --git a/versioned_docs/version-2.1/data-operate/import/complex-types/struct.md b/versioned_docs/version-2.1/data-operate/import/complex-types/struct.md
index d927c84bcd1..78737252e20 100644
--- a/versioned_docs/version-2.1/data-operate/import/complex-types/struct.md
+++ b/versioned_docs/version-2.1/data-operate/import/complex-types/struct.md
@@ -1,11 +1,14 @@
---
{
- "title": "STRUCT",
+ "title": "STRUCT | Complex Types",
"language": "en",
- "description": "STRUCT<fieldname:fieldtype [COMMENT 'commentstring'], ... > Represents value with structure described by multiple fields,"
+ "description": "STRUCT<fieldname:fieldtype [COMMENT 'commentstring'], ... > Represents value with structure described by multiple fields,",
+ "sidebar_label": "STRUCT"
}
---
+# STRUCT
+
`STRUCT<field_name:field_type [COMMENT 'comment_string'], ... >` Represents value with structure described by multiple fields, which can be viewed as a collection of multiple columns.
- It cannot be used as a Key column. Now STRUCT can only be used in Duplicate Model Tables.
@@ -136,3 +139,4 @@ mysql> SELECT * FROM struct_test;
+------+--------------------------------------+
5 rows in set (0.00 sec)
```
+
diff --git a/versioned_docs/version-2.1/data-operate/import/data-source/google-cloud-storage.md b/versioned_docs/version-2.1/data-operate/import/data-source/google-cloud-storage.md
index 1af77e03847..26166feaa94 100644
--- a/versioned_docs/version-2.1/data-operate/import/data-source/google-cloud-storage.md
+++ b/versioned_docs/version-2.1/data-operate/import/data-source/google-cloud-storage.md
@@ -1,11 +1,14 @@
---
{
- "title": "Google Cloud Storage",
+ "title": "Google Cloud Storage | Data Source",
"language": "en",
- "description": "Doris provides two ways to load files from Google Cloud Storage:"
+ "description": "Doris provides two ways to load files from Google Cloud Storage:",
+ "sidebar_label": "Google Cloud Storage"
}
---
+# Google Cloud Storage
+
Doris provides two ways to load files from Google Cloud Storage:
- Use S3 Load to load Google Cloud Storage files into Doris, which is an asynchronous load method.
- Use TVF to load Google Cloud Storage files into Doris, which is a synchronous load method.
@@ -170,3 +173,4 @@ mysql> select * from test_s3load;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/versioned_docs/version-2.1/data-operate/import/data-source/hdfs.md b/versioned_docs/version-2.1/data-operate/import/data-source/hdfs.md
index 00e68dc7011..54cf9ab69e1 100644
--- a/versioned_docs/version-2.1/data-operate/import/data-source/hdfs.md
+++ b/versioned_docs/version-2.1/data-operate/import/data-source/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Data Source",
"language": "en",
- "description": "Doris provides two ways to load files from HDFS:"
+ "description": "Doris provides two ways to load files from HDFS:",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
Doris provides two ways to load files from HDFS:
- Use HDFS Load to load HDFS files into Doris, which is an asynchronous load method.
- Use TVF to load HDFS files into Doris, which is a synchronous load method.
@@ -162,3 +165,4 @@ mysql> select * from test_hdfsload;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/versioned_docs/version-2.1/data-operate/import/data-source/minio.md b/versioned_docs/version-2.1/data-operate/import/data-source/minio.md
index 02491676a1d..f931df4c21c 100644
--- a/versioned_docs/version-2.1/data-operate/import/data-source/minio.md
+++ b/versioned_docs/version-2.1/data-operate/import/data-source/minio.md
@@ -1,11 +1,14 @@
---
{
- "title": "MinIO",
+ "title": "MinIO | Data Source",
"language": "en",
- "description": "Doris provides two ways to load files from MinIO:"
+ "description": "Doris provides two ways to load files from MinIO:",
+ "sidebar_label": "MinIO"
}
---
+# MinIO
+
Doris provides two ways to load files from MinIO:
- Use S3 Load to load MinIO files into Doris, which is an asynchronous load method.
- Use TVF to load MinIO files into Doris, which is a synchronous load method.
@@ -193,3 +196,4 @@ mysql> select * from test_s3load;
+---------+-----------+------+
10 rows in set (0.04 sec)
```
+
diff --git a/versioned_docs/version-2.1/data-operate/import/file-format/json.md b/versioned_docs/version-2.1/data-operate/import/file-format/json.md
index eae1058a066..9cbb375102b 100644
--- a/versioned_docs/version-2.1/data-operate/import/file-format/json.md
+++ b/versioned_docs/version-2.1/data-operate/import/file-format/json.md
@@ -1,8 +1,9 @@
---
{
- "title": "JSON",
+ "title": "JSON | File Format",
"language": "en",
- "description": "This document explains how to load JSON format data files into Doris."
+ "description": "This document explains how to load JSON format data files into Doris.",
+ "sidebar_label": "JSON"
}
---
@@ -435,3 +436,4 @@ FROM S3
"json_root" = "$.events",
...
);
+
diff --git a/versioned_docs/version-2.1/data-operate/import/file-format/orc.md b/versioned_docs/version-2.1/data-operate/import/file-format/orc.md
index d863f73c90f..09f027cf67b 100644
--- a/versioned_docs/version-2.1/data-operate/import/file-format/orc.md
+++ b/versioned_docs/version-2.1/data-operate/import/file-format/orc.md
@@ -1,11 +1,14 @@
---
{
- "title": "ORC",
+ "title": "ORC | File Format",
"language": "en",
- "description": "This document explains how to load ORC format data files in Doris."
+ "description": "This document explains how to load ORC format data files in Doris.",
+ "sidebar_label": "ORC"
}
---
+# ORC
+
This document explains how to load ORC format data files in Doris.
## Supported Loading Methods
@@ -56,3 +59,4 @@ FROM S3
"format" = "orc",
...
);
+
diff --git a/versioned_docs/version-2.1/data-operate/import/file-format/parquet.md b/versioned_docs/version-2.1/data-operate/import/file-format/parquet.md
index 1ef73fa955b..3a47ffcead0 100644
--- a/versioned_docs/version-2.1/data-operate/import/file-format/parquet.md
+++ b/versioned_docs/version-2.1/data-operate/import/file-format/parquet.md
@@ -1,11 +1,14 @@
---
{
- "title": "Parquet",
+ "title": "Parquet | File Format",
"language": "en",
- "description": "This document explains how to load Parquet format data files in Doris."
+ "description": "This document explains how to load Parquet format data files in Doris.",
+ "sidebar_label": "Parquet"
}
---
+# Parquet
+
This document explains how to load Parquet format data files in Doris.
## Supported Loading Methods
@@ -55,4 +58,4 @@ FROM S3
"path" = "s3://bucket/example.parquet",
"format" = "parquet",
...
-);
\ No newline at end of file
+);
diff --git a/versioned_docs/version-2.1/data-operate/scheduler/job-scheduler.md b/versioned_docs/version-2.1/data-operate/scheduler/job-scheduler.md
index 581bdeb709b..b28a1cdc4e7 100644
--- a/versioned_docs/version-2.1/data-operate/scheduler/job-scheduler.md
+++ b/versioned_docs/version-2.1/data-operate/scheduler/job-scheduler.md
@@ -1,11 +1,14 @@
---
{
- "title": "Job Scheduler",
+ "title": "Job Scheduler | Scheduler",
"language": "en",
- "description": "In the context of increasingly refined data management needs, scheduled tasks play a crucial role."
+ "description": "In the context of increasingly refined data management needs, scheduled tasks play a crucial role.",
+ "sidebar_label": "Job Scheduler"
}
---
+# Job Scheduler
+
## Background
In the context of increasingly refined data management needs, scheduled tasks play a crucial role. They are typically applied in the following scenarios:
@@ -184,3 +187,4 @@ Conclusion
## Future Plans
Doris Job Scheduler is a powerful and flexible task scheduling tool essential for data processing. Beyond common scenarios like data lake analysis and internal ETL, it plays a crucial role in implementing asynchronous materialized views. Asynchronous materialized views store precomputed result sets, and their update frequency is closely tied to source table changes. Frequent updates to source table data necess
+
diff --git a/versioned_docs/version-2.1/gettingStarted/quick-start.mdx b/versioned_docs/version-2.1/gettingStarted/quick-start.mdx
index 4aedbe576af..c71eb01b230 100644
--- a/versioned_docs/version-2.1/gettingStarted/quick-start.mdx
+++ b/versioned_docs/version-2.1/gettingStarted/quick-start.mdx
@@ -1,11 +1,14 @@
---
{
- "title": "Quick Start",
+ "title": "Quick Start | GettingStarted",
"language": "en",
- "description": "Starting from Doris version 2.1.8, Docker can be used for rapid deployment."
+ "description": "Starting from Doris version 2.1.8, Docker can be used for rapid deployment.",
+ "sidebar_label": "Quick Start"
}
---
+# Quick Start
+
:::caution Warning:
The following rapid deployment methods are intended solely for local development and testing, and should not be used in production environments. The reasons are as follows:
@@ -246,3 +249,4 @@ Download the corresponding binary installation package from the Apache Doris web
+
diff --git a/versioned_docs/version-2.1/lakehouse/file-formats/orc.md b/versioned_docs/version-2.1/lakehouse/file-formats/orc.md
index 3a3b014bbda..63a8b3e8e0b 100644
--- a/versioned_docs/version-2.1/lakehouse/file-formats/orc.md
+++ b/versioned_docs/version-2.1/lakehouse/file-formats/orc.md
@@ -1,11 +1,14 @@
---
{
- "title": "ORC",
+ "title": "ORC | File Formats",
"language": "en",
- "description": "This document introduces the support for reading and writing ORC file formats in Doris. It applies to the following functionalities:"
+ "description": "This document introduces the support for reading and writing ORC file formats in Doris. It applies to the following functionalities:",
+ "sidebar_label": "ORC"
}
---
+# ORC
+
This document introduces the support for reading and writing ORC file formats in Doris. It applies to the following functionalities:
* Reading and writing data in the Catalog.
@@ -60,3 +63,4 @@ This document introduces the support for reading and writing ORC file formats in
* `orc_natural_read_size_mb` (2.1+, 3.0+)
The maximum number of bytes that the ORC Reader reads at one time. Default is 8 MB.
+
diff --git a/versioned_docs/version-2.1/lakehouse/file-formats/parquet.md b/versioned_docs/version-2.1/lakehouse/file-formats/parquet.md
index 729af5b5e77..4db89664bb7 100644
--- a/versioned_docs/version-2.1/lakehouse/file-formats/parquet.md
+++ b/versioned_docs/version-2.1/lakehouse/file-formats/parquet.md
@@ -1,11 +1,14 @@
---
{
- "title": "Parquet",
+ "title": "Parquet | File Formats",
"language": "zh-CN",
- "description": "This document introduces the support for reading and writing Parquet file formats in Doris. It applies to the following features:"
+ "description": "This document introduces the support for reading and writing Parquet file formats in Doris. It applies to the following features:",
+ "sidebar_label": "Parquet"
}
---
+# Parquet
+
This document introduces the support for reading and writing Parquet file formats in Doris. It applies to the following features:
* Reading and writing data in the Catalog.
@@ -54,3 +57,4 @@ This document introduces the support for reading and writing Parquet file format
The maximum buffer size allocated when reading a Column within a Parquet Row Group. Default is 8M.
+
diff --git a/versioned_docs/version-2.1/lakehouse/statistics.md b/versioned_docs/version-2.1/lakehouse/statistics.md
index d8579e5efb4..d7219d555a3 100644
--- a/versioned_docs/version-2.1/lakehouse/statistics.md
+++ b/versioned_docs/version-2.1/lakehouse/statistics.md
@@ -1,11 +1,15 @@
---
{
- "title": "Statistics",
+ "title": "Statistics | Lakehouse",
"language": "en",
- "description": "Doris supports automatic or manual statistics collection for tables from external data sources like Hive, Iceberg and Paimon."
+ "description": "Doris supports automatic or manual statistics collection for tables from external data sources like Hive, Iceberg and Paimon.",
+ "sidebar_label": "Statistics"
}
---
+# Statistics
+
Doris supports automatic or manual statistics collection for tables from external data sources like Hive, Iceberg and Paimon. The accuracy of statistics directly determines the accuracy of cost estimation, which is crucial for selecting the optimal query plan. This can significantly improve query execution efficiency, especially in complex query scenarios.
For details, please refer to the [Statistics](../query-acceleration/optimization-technology-principle/statistics#外表收集) document in the "External Table Collection" section.
+
diff --git a/versioned_docs/version-2.1/lakehouse/storages/gcs.md b/versioned_docs/version-2.1/lakehouse/storages/gcs.md
index 1503817c0dd..2e52959ec73 100644
--- a/versioned_docs/version-2.1/lakehouse/storages/gcs.md
+++ b/versioned_docs/version-2.1/lakehouse/storages/gcs.md
@@ -1,10 +1,14 @@
---
{
- "title": "Google Cloud Storage",
+ "title": "Google Cloud Storage | Storages",
"language": "zh-CN",
- "description": "The document is under development."
+ "description": "The document is under development.",
+ "sidebar_label": "Google Cloud Storage"
}
---
+# Google Cloud Storage
+
The document is under development.
+
diff --git a/versioned_docs/version-2.1/lakehouse/storages/hdfs.md b/versioned_docs/version-2.1/lakehouse/storages/hdfs.md
index ca80c24a5fd..792d2d4519b 100644
--- a/versioned_docs/version-2.1/lakehouse/storages/hdfs.md
+++ b/versioned_docs/version-2.1/lakehouse/storages/hdfs.md
@@ -1,11 +1,14 @@
---
{
- "title": "HDFS",
+ "title": "HDFS | Storages",
"language": "en",
- "description": "This document describes the parameters required for accessing HDFS. These parameters apply to:"
+ "description": "This document describes the parameters required for accessing HDFS. These parameters apply to:",
+ "sidebar_label": "HDFS"
}
---
+# HDFS
+
This document describes the parameters required for accessing HDFS. These parameters apply to:
* Catalog properties
@@ -215,4 +218,4 @@ The Java version uses Java to access HDFS and can simulate the logic of Doris FE
The CPP version accesses HDFS through C++ calling libhdfs and can simulate the logic of Doris BE side accessing HDFS.
-For specific usage, please refer to the README in each code repository.
\ No newline at end of file
+For specific usage, please refer to the README in each code repository.
diff --git a/versioned_docs/version-2.1/lakehouse/storages/minio.md b/versioned_docs/version-2.1/lakehouse/storages/minio.md
index 0dec6403993..ae8e0160735 100644
--- a/versioned_docs/version-2.1/lakehouse/storages/minio.md
+++ b/versioned_docs/version-2.1/lakehouse/storages/minio.md
@@ -1,11 +1,14 @@
---
{
- "title": "MinIO",
+ "title": "MinIO | Storages",
"language": "en",
- "description": "This document describes the parameters required to access MinIO, which apply to the following scenarios:"
+ "description": "This document describes the parameters required to access MinIO, which apply to the following scenarios:",
+ "sidebar_label": "MinIO"
}
---
+# MinIO
+
This document describes the parameters required to access MinIO, which apply to the following scenarios:
- Catalog properties
@@ -56,3 +59,4 @@ For versions before 3.1:
* It is recommended to use the `minio.` prefix for configuration parameters to ensure consistency and clarity with MinIO.
* For versions before 3.1, please use the legacy name `s3.` as the prefix.
* Connection pool parameters can be adjusted according to concurrency requirements to avoid connection
+
diff --git a/versioned_docs/version-2.1/lakehouse/storages/s3.md b/versioned_docs/version-2.1/lakehouse/storages/s3.md
index a85b20c2a88..1f2ba5d54e5 100644
--- a/versioned_docs/version-2.1/lakehouse/storages/s3.md
+++ b/versioned_docs/version-2.1/lakehouse/storages/s3.md
@@ -1,11 +1,14 @@
---
{
- "title": "S3",
+ "title": "S3 | Storages",
"language": "en",
- "description": "This document describes the parameters required for accessing AWS S3. These parameters apply to:"
+ "description": "This document describes the parameters required for accessing AWS S3. These parameters apply to:",
+ "sidebar_label": "S3"
}
---
+# S3
+
This document describes the parameters required for accessing AWS S3. These parameters apply to:
- Catalog properties.
@@ -152,4 +155,4 @@ Based on read-only permissions, additionally allows deleting, creating, and modi
2. Principle of Least Privilege
- If only querying, do not grant write permissions.
-
\ No newline at end of file
+
diff --git a/versioned_docs/version-2.1/log-storage-analysis.md b/versioned_docs/version-2.1/log-storage-analysis.md
index 9c489566ed4..da9022444dc 100644
--- a/versioned_docs/version-2.1/log-storage-analysis.md
+++ b/versioned_docs/version-2.1/log-storage-analysis.md
@@ -1,8 +1,9 @@
---
{
- "title": "Log Storage and Analysis",
+ "title": "Log Storage and Analysis | Doris Docs",
"language": "en",
- "description": "Logs record key events in the system and contain crucial information such as the events' subject, time, location, and content."
+ "description": "Logs record key events in the system and contain crucial information such as the events' subject, time, location, and content.",
+ "sidebar_label": "Log Storage and Analysis"
}
---
@@ -569,3 +570,4 @@ Some third-party vendors offer visual log analysis development platforms based o
- Display of top field values in search results for finding anomalies and further drilling down for analysis
Please contact dev@doris.apache.org to find more.
+
diff --git a/versioned_docs/version-2.1/observability/overview.mdx b/versioned_docs/version-2.1/observability/overview.mdx
index aa1bf540c92..af61b9b52d5 100644
--- a/versioned_docs/version-2.1/observability/overview.mdx
+++ b/versioned_docs/version-2.1/observability/overview.mdx
@@ -1,11 +1,14 @@
---
{
- "title": "Overview",
+ "title": "Overview | Observability",
"language": "en",
- "description": "Observability refers to the ability to infer a system's internal state through its external output data. An observability platform collects, stores,"
+ "description": "Observability refers to the ability to infer a system's internal state through its external output data. An observability platform collects, stores,",
+ "sidebar_label": "Overview"
}
---
+# Overview
+
## What Is Observability?
Observability refers to the ability to infer a system's internal state through its external output data. An observability platform collects, stores, and visualizes three core data: Logs, Traces, and Metrics. This helps teams gain a comprehensive understanding of the operational status of distributed systems, supports resource optimization, fault prediction, root cause analysis, improves system reliability, and enhances user experience.
@@ -152,3 +155,4 @@ Grafana connects to Doris via MySQL datasource, offering unified visualization a
While Grafana's log visualization and analysis capabilities are relatively basic compared to Kibana, third-party vendors have implemented Kibana-like Discover features. These will soon be integrated into Grafana's Doris datasource, enhancing unified observability visualization. Future enhancements will include Elasticsearch protocol compatibility, enabling native Kibana connections to Doris. For ELK users, replacing Elasticsearch with Doris maintains existing logging and visualization ha [...]
... 4989 lines suppressed ...
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org