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 2022/04/28 07:22:39 UTC
[incubator-doris] branch master updated: [refactor][doc]The new version of the document is online (#9272)
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/incubator-doris.git
The following commit(s) were added to refs/heads/master by this push:
new 267e8b67c2 [refactor][doc]The new version of the document is online (#9272)
267e8b67c2 is described below
commit 267e8b67c210eaccebf35dbaaf9e749b3d1a0246
Author: jiafeng.zhang <zh...@gmail.com>
AuthorDate: Thu Apr 28 15:22:34 2022 +0800
[refactor][doc]The new version of the document is online (#9272)
replace the `docs/` with `new-docs/`
---
docs/.markdownlintignore | 2 -
docs/.vuepress/sidebar/en.js | 940 +-
docs/.vuepress/sidebar/zh-CN.js | 887 +-
docs/en/README.md | 2 +-
.../cluster-management/elastic-expansion.md | 0
.../cluster-management/load-balancing.md | 0
.../en/admin-manual/cluster-management/upgrade.md | 0
.../en/admin-manual/config/be-config.md | 0
.../en/admin-manual/config/fe-config.md | 0
.../en/admin-manual/config/user-property.md | 0
.../en/admin-manual/data-admin/backup.md | 0
.../en/admin-manual/data-admin/delete-recover.md | 0
.../en/admin-manual/data-admin/restore.md | 0
.../http-actions/cancel-label.md | 0
.../http-actions/check-reset-rpc-cache.md | 0
.../http-actions/compaction-action.md | 0
.../http-actions/connection-action.md | 0
.../http-actions/fe-get-log-file.md | 0
.../http-actions/fe/backends-action.md | 0
.../http-actions/fe/bootstrap-action.md | 0
.../http-actions/fe/cancel-load-action.md | 0
.../http-actions/fe/check-decommission-action.md | 0
.../http-actions/fe/check-storage-type-action.md | 0
.../http-actions/fe/config-action.md | 0
.../http-actions/fe/connection-action.md | 0
.../http-actions/fe/get-ddl-stmt-action.md | 0
.../http-actions/fe/get-load-info-action.md | 0
.../http-actions/fe/get-load-state.md | 0
.../http-actions/fe/get-log-file-action.md | 0
.../http-actions/fe/get-small-file.md | 0
.../http-actions/fe/ha-action.md | 0
.../http-actions/fe/hardware-info-action.md | 0
.../http-actions/fe/health-action.md | 0
.../http-actions/fe/log-action.md | 0
.../http-actions/fe/logout-action.md | 0
.../http-actions/fe/manager/cluster-action.md | 0
.../http-actions/fe/manager/node-action.md | 0
.../fe/manager/query-profile-action.md | 0
.../http-actions/fe/meta-action.md | 0
.../http-actions/fe/meta-info-action.md | 0
.../http-actions/fe/meta-replay-state-action.md | 0
.../http-actions/fe/profile-action.md | 0
.../http-actions/fe/query-detail-action.md | 0
.../http-actions/fe/query-profile-action.md | 0
.../http-actions/fe/row-count-action.md | 0
.../http-actions/fe/session-action.md | 0
.../http-actions/fe/set-config-action.md | 0
.../http-actions/fe/show-data-action.md | 0
.../http-actions/fe/show-meta-info-action.md | 0
.../http-actions/fe/show-proc-action.md | 0
.../http-actions/fe/show-runtime-info-action.md | 0
.../http-actions/fe/statement-execution-action.md | 0
.../http-actions/fe/system-action.md | 0
.../http-actions/fe/table-query-plan-action.md | 0
.../http-actions/fe/table-row-count-action.md | 0
.../http-actions/fe/table-schema-action.md | 0
.../http-actions/fe/upload-action.md | 0
.../http-actions/get-load-state.md | 0
.../http-actions/get-tablets.md | 0
.../http-actions/profile-action.md | 0
.../http-actions/query-detail-action.md | 0
.../http-actions/restore-tablet.md | 0
.../http-actions/show-data-action.md | 0
.../http-actions/tablet-migration-action.md | 0
.../http-actions/tablets_distribution.md | 0
.../maint-monitor/be-olap-error-code.md | 0
.../en/admin-manual/maint-monitor/disk-capacity.md | 0
.../maint-monitor}/doris-error-code.md | 0
.../maint-monitor/metadata-operation.md | 0
.../maint-monitor}/monitor-alert.md | 0
.../maint-monitor}/monitor-metrics/be-metrics.md | 0
.../maint-monitor}/monitor-metrics/fe-metrics.md | 0
.../maint-monitor}/multi-tenant.md | 0
.../admin-manual/maint-monitor/tablet-meta-tool.md | 0
.../maint-monitor/tablet-repair-and-balance.md | 0
.../maint-monitor}/tablet-restore-tool.md | 0
{new-docs => docs}/en/admin-manual/multi-tenant.md | 0
{new-docs => docs}/en/admin-manual/optimization.md | 0
.../en/admin-manual/privilege-ldap/ldap.md | 0
.../admin-manual/privilege-ldap/user-privilege.md | 0
.../en/admin-manual/query-profile.md | 0
.../en/admin-manual/sql-interception.md | 0
.../alter-table/alter-table-bitmap-index.md | 80 -
.../alter-table/alter-table-replace-table.md | 72 -
.../alter-table/alter-table-rollup.md | 188 -
.../alter-table/alter-table-schema-change.md | 231 -
.../alter-table/alter-table-temp-partition.md | 288 -
docs/en/administrator-guide/backup-restore.md | 195 -
.../en/administrator-guide/block-rule/sql-block.md | 93 -
docs/en/administrator-guide/broker.md | 289 -
docs/en/administrator-guide/bucket-shuffle-join.md | 105 -
docs/en/administrator-guide/colocation-join.md | 409 -
docs/en/administrator-guide/config/be_config.md | 1526 -
docs/en/administrator-guide/config/fe_config.md | 2210 --
.../en/administrator-guide/config/user_property.md | 73 -
docs/en/administrator-guide/dynamic-partition.md | 464 -
docs/en/administrator-guide/export-manual.md | 198 -
docs/en/administrator-guide/ldap.md | 175 -
.../load-data/batch-delete-manual.md | 204 -
.../load-data/binlog-load-manual.md | 523 -
.../load-data/broker-load-manual.md | 536 -
.../administrator-guide/load-data/delete-manual.md | 194 -
.../load-data/insert-into-manual.md | 297 -
.../load-data/load-json-format.md | 467 -
.../administrator-guide/load-data/load-manual.md | 228 -
.../load-data/routine-load-manual.md | 334 -
.../load-data/s3-load-manual.md | 93 -
.../load-data/sequence-column-manual.md | 208 -
.../load-data/spark-load-manual.md | 632 -
.../load-data/stream-load-manual.md | 374 -
docs/en/administrator-guide/materialized_view.md | 486 -
docs/en/administrator-guide/multi-tenant.md | 222 -
.../operation/be-olap-error-code.md | 256 -
.../administrator-guide/operation/disk-capacity.md | 169 -
.../operation/metadata-operation.md | 404 -
.../operation/tablet-meta-tool.md | 145 -
.../operation/tablet-repair-and-balance.md | 774 -
docs/en/administrator-guide/outfile.md | 195 -
docs/en/administrator-guide/privilege.md | 224 -
docs/en/administrator-guide/query_cache.md | 138 -
docs/en/administrator-guide/resource-management.md | 169 -
docs/en/administrator-guide/running-profile.md | 276 -
docs/en/administrator-guide/runtime-filter.md | 284 -
docs/en/administrator-guide/small-file-mgr.md | 104 -
docs/en/administrator-guide/sql-mode.md | 76 -
docs/en/administrator-guide/time-zone.md | 98 -
docs/en/administrator-guide/update.md | 126 -
docs/en/administrator-guide/variables.md | 499 -
.../en/advanced/alter-table/replace-table.md | 0
.../en/advanced/alter-table/schema-change.md | 0
.../en/advanced/best-practice/debug-log.md | 0
.../en/advanced/best-practice/import-analysis.md | 0
.../en/advanced/best-practice/query-analysis.md | 0
{new-docs => docs}/en/advanced/broker.md | 0
.../en/advanced/cache/partition-cache.md | 0
.../en/advanced/cache/query-cache.md | 0
.../join-optimization/bucket-shuffle-join.md | 0
.../advanced/join-optimization/colocation-join.md | 0
.../advanced/join-optimization/runtime-filter.md | 0
.../en/advanced/materialized-view.md | 0
.../orthogonal-bitmap-manual.md | 0
.../en/advanced/orthogonal-hll-manual.md | 0
.../en/advanced/partition/dynamic-partition.md | 0
.../en/advanced/partition/table-temp-partition.md | 0
{new-docs => docs}/en/advanced/resource.md | 0
{new-docs => docs}/en/advanced/small-file-mgr.md | 0
{new-docs => docs}/en/advanced/time-zone.md | 0
{new-docs => docs}/en/advanced/variables.md | 0
.../vectorized-execution-engine.md | 0
docs/en/benchmark/samples.md | 56 -
{new-docs => docs}/en/benchmark/ssb.md | 0
docs/en/benchmark/star-schema-benchmark.md | 181 -
docs/en/benchmark/systemd.md | 31 -
{new-docs => docs}/en/benchmark/tpc-h.md | 0
.../commit-format-specification.md | 6 +-
.../release-and-verify/release-complete.md | 6 +-
.../en/data-operate/export/export-manual.md | 0
.../export}/export_with_mysql_dump.md | 0
.../en/data-operate/export/outfile.md | 0
.../import/import-scenes/external-storage-load.md | 0
.../import/import-scenes/external-table-load.md | 0
.../data-operate/import/import-scenes/jdbc-load.md | 0
.../import/import-scenes/kafka-load.md | 0
.../import/import-scenes/load-atomicity.md | 0
.../import/import-scenes/load-data-convert.md | 0
.../import/import-scenes/load-strict-mode.md | 0
.../import/import-scenes/local-file-load.md | 0
.../import/import-way/binlog-load-manual.md | 0
.../import/import-way/broker-load-manual.md | 0
.../import/import-way/insert-into-manual.md | 0
.../import/import-way/load-json-format.md | 0
.../import/import-way/routine-load-manual.md | 0
.../import/import-way/s3-load-manual.md | 0
.../import/import-way/spark-load-manual.md | 0
.../import/import-way/stream-load-manual.md | 0
.../en/data-operate/import/load-manual.md | 0
.../update-delete/batch-delete-manual.md | 0
.../en/data-operate/update-delete/delete-manual.md | 0
.../update-delete/sequence-column-manual.md | 0
.../en/data-operate/update-delete/update.md | 0
{new-docs => docs}/en/data-table/advance-usage.md | 0
{new-docs => docs}/en/data-table/basic-usage.md | 0
{new-docs => docs}/en/data-table/best-practice.md | 0
{new-docs => docs}/en/data-table/data-model.md | 0
{new-docs => docs}/en/data-table/data-partition.md | 0
{new-docs => docs}/en/data-table/hit-the-rollup.md | 0
.../en/data-table/index/bitmap-index.md | 0
.../index}/bloomfilter.md | 0
.../en/data-table/index/prefix-index.md | 0
docs/en/developer-guide/be-vscode-dev.md | 4 +-
docs/en/developer-guide/benchmark-tool.md | 8 +-
docs/en/developer-guide/cpp-diagnostic-code.md | 2 +-
docs/en/developer-guide/fe-idea-dev.md | 10 +-
docs/en/developer-guide/fe-vscode-dev.md | 2 +-
.../{extending-doris => ecosystem}/audit-plugin.md | 0
{new-docs => docs}/en/ecosystem/datax.md | 0
.../ecosystem/doris-manager/cluster-managenent.md | 69 +
.../ecosystem/doris-manager/compiling-deploying.md | 112 +
docs/en/ecosystem/doris-manager/initializing.md | 43 +
docs/en/ecosystem/doris-manager/space-list.md | 234 +
.../en/ecosystem/doris-manager/space-management.md | 53 +
docs/en/ecosystem/doris-manager/system-settings.md | 91 +
.../en/ecosystem/external-table/doris-on-es.md | 0
.../en/ecosystem/external-table/hive-of-doris.md | 0
.../ecosystem/external-table/iceberg-of-doris.md | 0
.../en/ecosystem/external-table/odbc-of-doris.md | 0
.../en/ecosystem/flink-doris-connector.md | 0
{new-docs => docs}/en/ecosystem/logstash.md | 0
.../plugin-development-manual.md | 0
.../en/ecosystem/seatunnel/flink-sink.md | 0
.../en/ecosystem/seatunnel/spark-sink.md | 0
.../en/ecosystem/spark-doris-connector.md | 0
.../en/ecosystem/udf/contribute-udf.md | 0
.../ecosystem/udf/native-user-defined-function.md | 0
.../ecosystem/udf/remote-user-defined-function.md | 0
docs/en/extending-doris/datax.md | 104 -
docs/en/extending-doris/doris-on-es.md | 589 -
docs/en/extending-doris/flink-doris-connector.md | 496 -
docs/en/extending-doris/hive-bitmap-udf.md | 97 -
docs/en/extending-doris/hive-of-doris.md | 117 -
docs/en/extending-doris/iceberg-of-doris.md | 211 -
docs/en/extending-doris/logstash.md | 198 -
docs/en/extending-doris/odbc-of-doris.md | 374 -
docs/en/extending-doris/seatunnel/flink-sink.md | 116 -
docs/en/extending-doris/seatunnel/spark-sink.md | 123 -
docs/en/extending-doris/spark-doris-connector.md | 286 -
docs/en/extending-doris/udf/contribute-udf.md | 124 -
.../udf/java-user-defined-function.md | 89 -
.../udf/native-user-defined-function.md | 264 -
.../udf/remote-user-defined-function.md | 109 -
{new-docs => docs}/en/faq/data-faq.md | 0
docs/en/faq/error.md | 153 -
docs/en/faq/faq.md | 297 -
{new-docs => docs}/en/faq/install-faq.md | 0
{new-docs => docs}/en/faq/sql-faq.md | 0
{new-docs => docs}/en/get-starting/get-starting.md | 4 +-
docs/en/getting-started/advance-usage.md | 280 -
docs/en/getting-started/basic-usage.md | 382 -
docs/en/getting-started/best-practice.md | 198 -
docs/en/getting-started/data-model-rollup.md | 636 -
docs/en/getting-started/data-partition.md | 398 -
docs/en/getting-started/hit-the-rollup.md | 298 -
{new-docs => docs}/en/install/install-deploy.md | 0
.../en/install/source-install/compilation-arm.md | 0
.../compilation-with-ldb-toolchain.md | 0
.../en/install/source-install/compilation.md | 0
docs/en/installing/compilation-arm.md | 258 -
docs/en/installing/compilation.md | 263 -
docs/en/installing/install-deploy.md | 490 -
docs/en/installing/upgrade.md | 86 -
docs/en/internal/Flink doris connector Design.md | 259 -
docs/en/internal/doris_storage_optimization.md | 235 -
docs/en/internal/grouping_sets_design.md | 501 -
docs/en/internal/metadata-design.md | 127 -
.../aggregate-functions/approx_count_distinct.md | 0
.../sql-functions/aggregate-functions/avg.md | 0
.../aggregate-functions/bitmap_union.md | 0
.../sql-functions/aggregate-functions/count.md | 0
.../aggregate-functions/group_concat.md | 0
.../aggregate-functions/hll_union_agg.md | 0
.../sql-functions/aggregate-functions/max.md | 0
.../sql-functions/aggregate-functions/max_by.md | 0
.../sql-functions/aggregate-functions/min.md | 0
.../sql-functions/aggregate-functions/min_by.md | 0
.../aggregate-functions/percentile.md | 0
.../aggregate-functions/percentile_approx.md | 0
.../sql-functions/aggregate-functions/stddev.md | 0
.../aggregate-functions/stddev_samp.md | 0
.../sql-functions/aggregate-functions/sum.md | 0
.../sql-functions/aggregate-functions/topn.md | 0
.../sql-functions/aggregate-functions/var_samp.md | 0
.../sql-functions/aggregate-functions/variance.md | 0
.../sql-functions/bitmap-functions/bitmap_and.md | 0
.../bitmap-functions/bitmap_and_count.md | 0
.../bitmap-functions/bitmap_and_not.md | 0
.../bitmap-functions/bitmap_and_not_count.md | 0
.../bitmap-functions/bitmap_contains.md | 0
.../sql-functions/bitmap-functions/bitmap_empty.md | 0
.../bitmap-functions/bitmap_from_string.md | 0
.../bitmap-functions/bitmap_has_all.md | 0
.../bitmap-functions/bitmap_has_any.md | 0
.../sql-functions/bitmap-functions/bitmap_hash.md | 0
.../bitmap-functions/bitmap_intersect.md | 0
.../sql-functions/bitmap-functions/bitmap_max.md | 0
.../sql-functions/bitmap-functions/bitmap_min.md | 0
.../sql-functions/bitmap-functions/bitmap_not.md | 0
.../sql-functions/bitmap-functions/bitmap_or.md | 0
.../bitmap-functions/bitmap_or_count.md | 0
.../bitmap-functions/bitmap_subset_in_range.md | 0
.../bitmap-functions/bitmap_subset_limit.md | 0
.../bitmap-functions/bitmap_to_string.md | 0
.../sql-functions/bitmap-functions/bitmap_union.md | 0
.../sql-functions/bitmap-functions/bitmap_xor.md | 0
.../bitmap-functions/bitmap_xor_count.md | 0
.../orthogonal_bitmap_intersect.md | 0
.../orthogonal_bitmap_intersect_count.md | 0
.../orthogonal_bitmap_union_count.md | 0
.../sql-functions/bitmap-functions/sub_bitmap.md | 0
.../sql-functions/bitmap-functions/to_bitmap.md | 0
.../sql-functions/bitwise-functions/bitand.md | 0
.../sql-functions/bitwise-functions/bitnot.md | 0
.../sql-functions/bitwise-functions/bitor.md | 0
.../sql-functions/bitwise-functions/bitxor.md | 0
.../sql-functions/cast.md | 0
.../sql-functions/conditional-functions/case.md | 0
.../conditional-functions/coalesce.md | 0
.../sql-functions/conditional-functions/if.md | 0
.../sql-functions/conditional-functions/ifnull.md | 0
.../sql-functions/conditional-functions/nullif.md | 0
.../date-time-functions/convert_tz.md | 0
.../sql-functions/date-time-functions/curdate.md | 0
.../date-time-functions/current_timestamp.md | 0
.../sql-functions/date-time-functions/curtime.md | 0
.../sql-functions/date-time-functions/date_add.md | 0
.../date-time-functions/date_format.md | 0
.../sql-functions/date-time-functions/date_sub.md | 0
.../sql-functions/date-time-functions/datediff.md | 0
.../sql-functions/date-time-functions/day.md | 0
.../sql-functions/date-time-functions/dayname.md | 0
.../date-time-functions/dayofmonth.md | 0
.../sql-functions/date-time-functions/dayofweek.md | 0
.../sql-functions/date-time-functions/dayofyear.md | 0
.../sql-functions/date-time-functions/from_days.md | 0
.../date-time-functions/from_unixtime.md | 0
.../sql-functions/date-time-functions/hour.md | 0
.../sql-functions/date-time-functions/makedate.md | 0
.../sql-functions/date-time-functions/minute.md | 0
.../sql-functions/date-time-functions/month.md | 0
.../sql-functions/date-time-functions/monthname.md | 0
.../sql-functions/date-time-functions/now.md | 0
.../sql-functions/date-time-functions/second.md | 0
.../date-time-functions/str_to_date.md | 0
.../date-time-functions/time_round.md | 0
.../sql-functions/date-time-functions/timediff.md | 0
.../date-time-functions/timestampadd.md | 0
.../date-time-functions/timestampdiff.md | 0
.../sql-functions/date-time-functions/to_date.md | 0
.../sql-functions/date-time-functions/to_days.md | 0
.../date-time-functions/unix_timestamp.md | 0
.../date-time-functions/utc_timestamp.md | 0
.../sql-functions/date-time-functions/week.md | 0
.../sql-functions/date-time-functions/weekday.md | 0
.../date-time-functions/weekofyear.md | 0
.../sql-functions/date-time-functions/year.md | 0
.../sql-functions/date-time-functions/yearweek.md | 0
.../sql-functions/digital-masking.md | 0
.../sql-functions/encrypt-digest-functions/aes.md | 0
.../sql-functions/encrypt-digest-functions/md5.md | 0
.../encrypt-digest-functions/md5sum.md | 0
.../sql-functions/encrypt-digest-functions/sm3.md | 0
.../encrypt-digest-functions/sm3sum.md | 0
.../sql-functions/encrypt-digest-functions/sm4.md | 0
.../encrypt-dixgest-functions}/aes.md | 0
.../encrypt-dixgest-functions}/md5.md | 0
.../encrypt-dixgest-functions}/md5sum.md | 0
.../encrypt-dixgest-functions}/sm3.md | 0
.../encrypt-dixgest-functions}/sm3sum.md | 0
.../encrypt-dixgest-functions}/sm4.md | 0
.../hash-functions/murmur_hash3_32.md | 0
.../json-functions/get_json_double.md | 0
.../sql-functions/json-functions/get_json_int.md | 0
.../json-functions/get_json_string.md | 0
.../sql-functions/json-functions/json_array.md | 0
.../sql-functions/json-functions/json_object.md | 0
.../sql-functions/json-functions/json_quote.md | 0
.../sql-functions/math-functions/conv.md | 0
.../sql-functions/math-functions/pmod.md | 0
.../sql-functions/spatial-functions/st_astext.md | 0
.../sql-functions/spatial-functions/st_circle.md | 0
.../sql-functions/spatial-functions/st_contains.md | 0
.../spatial-functions/st_distance_sphere.md | 0
.../spatial-functions/st_geometryfromtext.md | 0
.../spatial-functions/st_linefromtext.md | 0
.../sql-functions/spatial-functions/st_point.md | 0
.../sql-functions/spatial-functions/st_polygon.md | 0
.../sql-functions/spatial-functions/st_x.md | 0
.../sql-functions/spatial-functions/st_y.md | 0
.../append_trailing_char_if_absent.md | 0
.../sql-functions/string-functions/ascii.md | 0
.../sql-functions/string-functions/bit_length.md | 0
.../sql-functions/string-functions/char_length.md | 0
.../sql-functions/string-functions/concat.md | 0
.../sql-functions/string-functions/concat_ws.md | 0
.../sql-functions/string-functions/ends_with.md | 0
.../sql-functions/string-functions/find_in_set.md | 0
.../sql-functions/string-functions/hex.md | 0
.../sql-functions/string-functions/instr.md | 0
.../sql-functions/string-functions/lcase.md | 0
.../sql-functions/string-functions/left.md | 0
.../sql-functions/string-functions/length.md | 0
.../sql-functions/string-functions/like/like.md | 0
.../string-functions/like/not_like.md | 0
.../sql-functions/string-functions/locate.md | 0
.../sql-functions/string-functions/lower.md | 0
.../sql-functions/string-functions/lpad.md | 0
.../sql-functions/string-functions/ltrim.md | 0
.../sql-functions/string-functions/money_format.md | 0
.../string-functions/null_or_empty.md | 0
.../string-functions/regexp/not_regexp.md | 0
.../string-functions/regexp/regexp.md | 0
.../string-functions/regexp/regexp_extract.md | 0
.../string-functions/regexp/regexp_replace.md | 0
.../sql-functions/string-functions/repeat.md | 0
.../sql-functions/string-functions/replace.md | 0
.../sql-functions/string-functions/reverse.md | 0
.../sql-functions/string-functions/right.md | 0
.../sql-functions/string-functions/rpad.md | 0
.../sql-functions/string-functions/split_part.md | 0
.../sql-functions/string-functions/starts_with.md | 0
.../sql-functions/string-functions/strleft.md | 0
.../sql-functions/string-functions/strright.md | 0
.../sql-functions/string-functions/substring.md | 0
.../sql-functions/string-functions/unhex.md | 0
.../table-functions/explode-bitmap.md | 0
.../table-functions/explode-json-array.md | 0
.../table-functions/explode-numbers.md | 0
.../sql-functions/table-functions/explode-split.md | 0
.../table-functions/outer-combinator.md | 0
.../sql-functions/window-function.md | 0
.../Account-Management-Statements/CREATE-ROLE.md | 0
.../Account-Management-Statements/CREATE-USER.md | 0
.../Account-Management-Statements/DROP-ROLE.md | 0
.../Account-Management-Statements/DROP-USER.md | 0
.../Account-Management-Statements/GRANT.md | 0
.../Account-Management-Statements/LDAP.md | 0
.../Account-Management-Statements/REVOKE.md | 0
.../Account-Management-Statements/SET-PASSWORD.md | 0
.../Account-Management-Statements/SET-PROPERTY.md | 0
.../ALTER-SYSTEM-ADD-BACKEND.md | 0
.../ALTER-SYSTEM-ADD-BROKER.md | 0
.../ALTER-SYSTEM-ADD-FOLLOWER.md | 0
.../ALTER-SYSTEM-ADD-OBSERVER.md | 0
.../ALTER-SYSTEM-DECOMMISSION-BACKEND.md | 0
.../ALTER-SYSTEM-DROP-BACKEND.md | 0
.../ALTER-SYSTEM-DROP-BROKER.md | 0
.../ALTER-SYSTEM-DROP-FOLLOWER.md | 0
.../ALTER-SYSTEM-DROP-OBSERVER.md | 0
.../ALTER-SYSTEM-MODIFY-BACKEND.md | 0
.../ALTER-SYSTEM-MODIFY-BROKER.md | 0
.../CANCEL-ALTER-SYSTEM.md | 0
.../Alter/ALTER-DATABASE.md | 0
.../Alter/ALTER-SQL-BLOCK-RULE.md | 0
.../Alter/ALTER-TABLE-BITMAP.md | 0
.../Alter/ALTER-TABLE-COLUMN.md | 0
.../Alter/ALTER-TABLE-PARTITION.md | 0
.../Alter/ALTER-TABLE-PROPERTY.md | 0
.../Alter/ALTER-TABLE-RENAME.md | 0
.../Alter/ALTER-TABLE-REPLACE.md | 0
.../Alter/ALTER-TABLE-ROLLUP.md | 0
.../Data-Definition-Statements/Alter/ALTER-VIEW.md | 0
.../Alter/CANCEL-ALTER-TABLE.md | 0
.../Backup-and-Restore/BACKUP.md | 0
.../Backup-and-Restore/CANCEL-BACKUP.md | 0
.../Backup-and-Restore/CANCEL-RESTORE.md | 0
.../Backup-and-Restore/CREATE-REPOSITORY.md | 0
.../Backup-and-Restore/DROP-REPOSITORY.md | 0
.../Backup-and-Restore/RECOVER.md | 0
.../Backup-and-Restore/RESTORE.md | 0
.../Create/CREATE-DATABASE.md | 0
.../Create/CREATE-ENCRYPT-KEY.md | 0
.../Create/CREATE-EXTERNAL-TABLE.md | 0
.../Create/CREATE-FILE.md | 0
.../Create/CREATE-FUNCTION.md | 0
.../Create/CREATE-INDEX.md | 0
.../Create/CREATE-MATERIALIZED-VIEW.md | 0
.../Create/CREATE-RESOURCE.md | 0
.../Create/CREATE-SQL-BLOCK-RULE.md | 0
.../Create/CREATE-TABLE-LIKE.md | 0
.../Create/CREATE-TABLE.md | 0
.../Create/CREATE-VIEW.md | 0
.../Drop/DROP-DATABASE.md | 0
.../Drop/DROP-ENCRYPT-KEY.md | 0
.../Data-Definition-Statements/Drop/DROP-FILE.md | 0
.../Drop/DROP-FUNCTION.md | 0
.../Data-Definition-Statements/Drop/DROP-INDEX.md | 0
.../Drop/DROP-MATERIALIZED-VIEW.md | 0
.../Drop/DROP-RESOURCE.md | 0
.../Drop/DROP-SQL-BLOCK-RULE.md | 0
.../Data-Definition-Statements/Drop/DROP-TABLE.md | 0
.../Drop/TRUNCATE-TABLE.md | 0
.../Load/ALTER-ROUTINE-LOAD.md | 0
.../Load/BROKER-LOAD.md | 0
.../Load/CANCEL-LOAD.md | 0
.../Load/CREATE-ROUTINE-LOAD.md | 0
.../Load/CREATE-SYNC-JOB.md | 0
.../Load/MULTI-LOAD.md | 0
.../Load/PAUSE-ROUTINE-LOAD.md | 0
.../Load/PAUSE-SYNC-JOB.md | 0
.../Load/RESUME-ROUTINE-LOAD.md | 0
.../Load/RESUME-SYNC-JOB.md | 0
.../Load/STOP-ROUTINE-LOAD.md | 0
.../Load/STOP-SYNC-JOB.md | 0
.../Load/STREAM-LOAD.md | 0
.../Manipulation/DELETE.md | 0
.../Manipulation/INSERT.md | 0
.../Manipulation/UPDATE.md | 0
.../Data-Manipulation-Statements/OUTFILE.md | 0
.../sql-reference-v2/Data-Types}/BIGINT.md | 0
.../sql-reference-v2/Data-Types}/BITMAP.md | 0
.../sql-reference-v2/Data-Types}/BOOLEAN.md | 0
.../sql-reference-v2/Data-Types}/CHAR.md | 0
.../sql-reference-v2/Data-Types}/DATE.md | 0
.../sql-reference-v2/Data-Types}/DATETIME.md | 0
.../sql-reference-v2/Data-Types}/DECIMAL.md | 0
.../sql-reference-v2/Data-Types}/DOUBLE.md | 0
.../sql-reference-v2/Data-Types}/FLOAT.md | 0
.../sql-reference-v2/Data-Types}/HLL.md | 0
.../sql-reference-v2/Data-Types}/INT.md | 0
.../sql-reference-v2/Data-Types}/QUANTILE_STATE.md | 0
.../sql-reference-v2/Data-Types}/SMALLINT.md | 0
.../sql-reference-v2/Data-Types}/STRING.md | 0
.../sql-reference-v2/Data-Types}/TINYINT.md | 0
.../sql-reference-v2/Data-Types}/VARCHAR.md | 0
.../ADMIN-CANCEL-REPAIR.md | 0
.../ADMIN-CHECK-TABLET.md | 0
.../ADMIN-CLEAN-TRASH.md | 0
.../ADMIN-REPAIR-TABLE.md | 0
.../ADMIN-SET-CONFIG.md | 0
.../ADMIN-SET-REPLICA-STATUS.md | 0
.../ADMIN-SHOW-CONFIG.md | 0
.../ADMIN-SHOW-REPLICA-DISTRIBUTION.md | 0
.../ADMIN-SHOW-REPLICA-STATUS.md | 0
.../ADMIN-SHOW-TABLET-STORAGE-FORMAT.md} | 0
.../ENABLE-FEATURE.md | 0
.../INSTALL-PLUGIN.md | 0
.../Database-Administration-Statements/KILL.md | 0
.../Database-Administration-Statements/RECOVER.md | 0
.../SET-VARIABLE.md | 0
.../UNINSTALL-PLUGIN.md | 0
.../SHOW-ALTER-TABLE-MATERIALIZED-VIEW.md | 0
.../sql-reference-v2/Show-Statements/SHOW-ALTER.md | 0
.../Show-Statements/SHOW-BACKENDS.md | 0
.../Show-Statements/SHOW-BACKUP.md | 0
.../Show-Statements/SHOW-BROKER.md | 0
.../Show-Statements/SHOW-CHARSET.md | 0
.../Show-Statements/SHOW-COLLATION.md | 0
.../Show-Statements/SHOW-COLUMNS.md | 0
.../Show-Statements/SHOW-CREATE-DATABASE.md | 0
.../Show-Statements/SHOW-CREATE-FUNCTION.md | 0
.../Show-Statements/SHOW-CREATE-ROUTINE-LOAD.md | 0
.../Show-Statements/SHOW-CREATE-TABLE.md | 0
.../sql-reference-v2/Show-Statements/SHOW-DATA.md | 0
.../Show-Statements/SHOW-DATABASE-ID.md | 0
.../Show-Statements/SHOW-DATABASES.md | 0
.../Show-Statements/SHOW-DELETE.md | 0
.../Show-Statements/SHOW-DYNAMIC-PARTITION.md | 0
.../Show-Statements/SHOW-ENCRYPT-KEY.md | 0
.../Show-Statements/SHOW-ENGINES.md | 0
.../Show-Statements/SHOW-EVENTS.md | 0
.../Show-Statements/SHOW-EXPORT.md | 0
.../sql-reference-v2/Show-Statements/SHOW-FILE.md | 0
.../Show-Statements/SHOW-FRONTENDS.md | 0
.../Show-Statements/SHOW-FUNCTIONS.md | 0
.../Show-Statements/SHOW-GRANTS.md | 0
.../sql-reference-v2/Show-Statements/SHOW-INDEX.md | 0
.../Show-Statements/SHOW-LAST-INSERT.md | 0
.../Show-Statements/SHOW-LOAD-PROFILE.md | 0
.../Show-Statements/SHOW-LOAD-WARNINGS.md | 0
.../sql-reference-v2/Show-Statements/SHOW-LOAD.md | 0
.../Show-Statements/SHOW-MIGRATIONS.md | 0
.../Show-Statements/SHOW-OPEN-TABLES.md | 0
.../Show-Statements/SHOW-PARTITION-ID.md | 0
.../Show-Statements/SHOW-PARTITIONS.md | 0
.../Show-Statements/SHOW-PLUGINS.md | 0
.../sql-reference-v2/Show-Statements/SHOW-PROC.md | 0
.../Show-Statements/SHOW-PROCEDURE.md | 0
.../Show-Statements/SHOW-PROCESSLIST.md | 0
.../Show-Statements/SHOW-PROPERTY.md | 0
.../Show-Statements/SHOW-QUERY-PROFILE.md | 0
.../Show-Statements/SHOW-REPOSITORIES.md | 0
.../Show-Statements/SHOW-RESOURCES.md | 0
.../Show-Statements/SHOW-RESTORE.md | 0
.../sql-reference-v2/Show-Statements/SHOW-ROLES.md | 0
.../Show-Statements/SHOW-ROLLUP.md | 0
.../Show-Statements/SHOW-ROUTINE-LOAD-TASK.md | 0
.../Show-Statements/SHOW-ROUTINE-LOAD.md | 0
.../Show-Statements/SHOW-SMALL-FILES.md | 0
.../Show-Statements/SHOW-SNAPSHOT.md | 0
.../Show-Statements/SHOW-SQL-BLOCK-RULE.md | 0
.../Show-Statements/SHOW-STATUS.md | 0
.../Show-Statements/SHOW-STREAM-LOAD.md | 0
.../Show-Statements/SHOW-SYNC-JOB.md | 0
.../Show-Statements/SHOW-TABLE-ID.md | 0
.../Show-Statements/SHOW-TABLE-STATUS.md | 0
.../Show-Statements/SHOW-TABLET.md | 0
.../Show-Statements/SHOW-TRANSACTION.md | 0
.../sql-reference-v2/Show-Statements/SHOW-TRASH.md | 0
.../Show-Statements/SHOW-TRIGGERS.md | 0
.../sql-reference-v2}/Show-Statements/SHOW-USER.md | 0
.../Show-Statements/SHOW-VARIABLES.md | 0
.../sql-reference-v2/Show-Statements/SHOW-VIEW.md | 0
.../Show-Statements/SHOW-WARNING.md | 0
.../Show-Statements/SHOW-WHITE-LIST.md | 0
.../Utility-Statements/DESCRIBE.md | 0
.../sql-reference-v2/Utility-Statements/HELP.md | 0
.../sql-reference-v2/Utility-Statements/USE.md | 0
.../Account-Management-Statements/ALTER-USER.md | 38 -
.../Account-Management-Statements/CREATE-ROLE.md | 38 -
.../Account-Management-Statements/CREATE-USER.md | 38 -
.../Account-Management-Statements/DROP-ROLE.md | 38 -
.../Account-Management-Statements/DROP-USER.md | 38 -
.../Account-Management-Statements/GRANT.md | 38 -
.../Account-Management-Statements/LDAP.md | 38 -
.../Account-Management-Statements/REVOKE.md | 38 -
.../Account-Management-Statements/SET-PASSWORD.md | 38 -
.../Account-Management-Statements/SET-PROPERTY.md | 38 -
.../ALTER-SYSTEM-ADD-BACKEND.md | 38 -
.../ALTER-SYSTEM-ADD-FOLLOWER.md | 38 -
.../ALTER-SYSTEM-ADD-OBSERVER.md | 38 -
.../ALTER-SYSTEM-DECOMMISSION-BACKEND.md | 38 -
.../ALTER-SYSTEM-DROP-BACKEND.md | 38 -
.../ALTER-SYSTEM-DROP-FOLLOWER.md | 38 -
.../ALTER-SYSTEM-DROP-OBSERVER.md | 38 -
.../CANCEL-ALTER-SYSTEM.md | 38 -
.../Alter/ALTER-DATABASE.md | 38 -
.../Alter/ALTER-TABLE-COLUMN.md | 38 -
.../Alter/ALTER-TABLE-PARTITION.md | 38 -
.../Alter/ALTER-TABLE-PROPERTY.md | 38 -
.../Alter/ALTER-TABLE-RENAME.md | 38 -
.../Alter/ALTER-TABLE-REPLACE.md | 38 -
.../Alter/ALTER-TABLE-ROLLUP.md | 38 -
.../Data-Definition-Statements/Alter/ALTER-VIEW.md | 38 -
.../Alter/CANCEL-ALTER-TABLE.md | 38 -
.../Backup-and-Restore/BACKUP.md | 38 -
.../Backup-and-Restore/CANCEL-BACKUP.md | 38 -
.../Backup-and-Restore/CANCEL-RESTORE.md | 38 -
.../Backup-and-Restore/CREATE-REPOSITORY.md | 38 -
.../Backup-and-Restore/DROP-REPOSITORY.md | 38 -
.../Backup-and-Restore/RESTORE.md | 38 -
.../Create/CREATE-DATABASE.md | 38 -
.../Create/CREATE-ENCRYPT-KEY.md | 38 -
.../Create/CREATE-FILE.md | 38 -
.../Create/CREATE-FUNCTION.md | 38 -
.../Create/CREATE-INDEX.md | 38 -
.../Create/CREATE-MATERIALIZED-VIEW.md | 38 -
.../Create/CREATE-RESOURCE.md | 38 -
.../Create/CREATE-TABLE-LIKE.md | 38 -
.../Create/CREATE-TABLE.md | 568 -
.../Create/CREATE-VIEW.md | 38 -
.../Drop/DROP-DATABASE.md | 38 -
.../Drop/DROP-ENCRYPT-KEY.md | 38 -
.../Data-Definition-Statements/Drop/DROP-FILE.md | 38 -
.../Drop/DROP-FUNCTION.md | 38 -
.../Data-Definition-Statements/Drop/DROP-INDEX.md | 38 -
.../Drop/DROP-MATERIALIZED-VIEW.md | 38 -
.../Drop/DROP-RESOURCE.md | 38 -
.../Data-Definition-Statements/Drop/DROP-TABLE.md | 38 -
.../Drop/TRUNCATE-TABLE.md | 38 -
.../Load/ALTER-ROUTINE-LOAD.md | 38 -
.../Load/BROKER-LOAD.md | 38 -
.../Load/CANCEL-LOAD.md | 38 -
.../Load/CREATE-ROUTINE-LOAD.md | 38 -
.../Load/PAUSE-ROUTINE-LOAD.md | 38 -
.../Load/RESUME-ROUTINE-LOAD.md | 38 -
.../Load/STOP-ROUTINE-LOAD.md | 38 -
.../Load/STREAM-LOAD.md | 38 -
.../Manipulation/DELETE.md | 38 -
.../Manipulation/INSERT.md | 38 -
.../Manipulation/UPDATE.md | 38 -
.../ADMIN-CANCEL-REPAIR.md | 38 -
.../ADMIN-CHECK-TABLET.md | 38 -
.../ADMIN-REPAIR-TABLE.md | 38 -
.../ADMIN-SET-CONFIG.md | 38 -
.../ADMIN-SET-REPLICA-STATUS.md | 38 -
.../ADMIN-SHOW-CONFIG.md | 38 -
.../ADMIN-SHOW-REPLICA-DISTRIBUTION.md | 38 -
.../ADMIN-SHOW-REPLICA-STATUS.md | 38 -
.../INSTALL-PLUGIN.md | 38 -
.../Database-Administration-Statements/KILL.md | 38 -
.../Database-Administration-Statements/RECOVER.md | 38 -
.../SET-VARIABLE.md | 38 -
.../UNINSTALL-PLUGIN.md | 38 -
.../sql-statements/Show-Statements/SHOW-ALTER.md | 38 -
.../Show-Statements/SHOW-BACKENDS.md | 38 -
.../sql-statements/Show-Statements/SHOW-BACKUP.md | 38 -
.../sql-statements/Show-Statements/SHOW-BROKER.md | 38 -
.../sql-statements/Show-Statements/SHOW-COLUMNS.md | 38 -
.../Show-Statements/SHOW-CREATE-DATABASE.md | 38 -
.../Show-Statements/SHOW-CREATE-FUNCTION.md | 38 -
.../Show-Statements/SHOW-CREATE-ROUTINE-LOAD.md | 38 -
.../Show-Statements/SHOW-CREATE-TABLE.md | 38 -
.../sql-statements/Show-Statements/SHOW-DATA.md | 38 -
.../Show-Statements/SHOW-DATABASE-ID.md | 38 -
.../Show-Statements/SHOW-DATABASES.md | 38 -
.../sql-statements/Show-Statements/SHOW-DELETE.md | 38 -
.../Show-Statements/SHOW-DYNAMIC-PARTITION.md | 38 -
.../Show-Statements/SHOW-ENCRYPT-KEY.md | 38 -
.../sql-statements/Show-Statements/SHOW-EXPORT.md | 38 -
.../Show-Statements/SHOW-FRONTENDS.md | 38 -
.../Show-Statements/SHOW-FUNCTIONS.md | 38 -
.../sql-statements/Show-Statements/SHOW-GRANTS.md | 38 -
.../sql-statements/Show-Statements/SHOW-INDEX.md | 38 -
.../Show-Statements/SHOW-LOAD-PROFILE.md | 38 -
.../Show-Statements/SHOW-LOAD-WARNINGS.md | 38 -
.../sql-statements/Show-Statements/SHOW-LOAD.md | 38 -
.../Show-Statements/SHOW-MIGRATIONS.md | 38 -
.../Show-Statements/SHOW-PARTITION-ID.md | 38 -
.../Show-Statements/SHOW-PARTITIONS.md | 38 -
.../sql-statements/Show-Statements/SHOW-PLUGINS.md | 38 -
.../sql-statements/Show-Statements/SHOW-PROC.md | 38 -
.../Show-Statements/SHOW-PROCESSLIST.md | 38 -
.../Show-Statements/SHOW-PROPERTY.md | 83 -
.../Show-Statements/SHOW-REPOSITORIES.md | 38 -
.../Show-Statements/SHOW-RESOURCES.md | 38 -
.../sql-statements/Show-Statements/SHOW-RESTORE.md | 38 -
.../sql-statements/Show-Statements/SHOW-ROLES.md | 38 -
.../Show-Statements/SHOW-ROUTINE-LOAD-TASK.md | 38 -
.../Show-Statements/SHOW-ROUTINE-LOAD.md | 38 -
.../Show-Statements/SHOW-SMALL-FILES.md | 38 -
.../Show-Statements/SHOW-SNAPSHOT.md | 38 -
.../sql-statements/Show-Statements/SHOW-STATUS.md | 38 -
.../Show-Statements/SHOW-STREAM-LOAD.md | 38 -
.../Show-Statements/SHOW-TABLE-ID.md | 38 -
.../Show-Statements/SHOW-TABLE-STATUS.md | 38 -
.../sql-statements/Show-Statements/SHOW-TABLET.md | 38 -
.../Show-Statements/SHOW-TRANSACTION.md | 38 -
.../Show-Statements/SHOW-VARIABLES.md | 38 -
.../sql-statements/Show-Statements/SHOW-VIEW.md | 38 -
.../sql-statements/Utility-Statements/DESCRIBE.md | 38 -
.../sql-statements/Utility-Statements/HELP.md | 38 -
.../sql-statements/Utility-Statements/USE.md | 38 -
.../Account Management/CREATE ROLE.md | 45 -
.../Account Management/CREATE USER.md | 74 -
.../sql-statements/Account Management/DROP ROLE.md | 43 -
.../sql-statements/Account Management/DROP USER.md | 49 -
.../sql-statements/Account Management/GRANT.md | 81 -
.../sql-statements/Account Management/REVOKE.md | 48 -
.../Account Management/SET PASSWORD.md | 55 -
.../Account Management/SET PROPERTY.md | 108 -
.../Account Management/SHOW GRANTS.md | 56 -
.../Account Management/SHOW ROLES.md | 41 -
.../Administration/ADMIN CANCEL REBALANCE DISK.md | 51 -
.../Administration/ADMIN CANCEL REPAIR.md | 47 -
.../Administration/ADMIN CHECK TABLET.md | 57 -
.../Administration/ADMIN CLEAN TRASH.md | 47 -
.../sql-statements/Administration/ADMIN COMPACT.md | 52 -
.../Administration/ADMIN REBALANCE DISK.md | 52 -
.../sql-statements/Administration/ADMIN REPAIR.md | 52 -
.../Administration/ADMIN SET CONFIG.md | 44 -
.../Administration/ADMIN SET REPLICA STATUS.md | 62 -
.../Administration/ADMIN SHOW CONFIG.md | 63 -
.../ADMIN SHOW REPLICA DISTRIBUTION.md | 51 -
.../Administration/ADMIN SHOW REPLICA STATUS.md | 64 -
.../Administration/ADMIN-DIAGNOSE-TABLET.md | 59 -
.../sql-statements/Administration/ALTER CLUSTER.md | 49 -
.../sql-statements/Administration/ALTER SYSTEM.md | 141 -
.../Administration/CANCEL DECOMMISSION.md | 40 -
.../Administration/CREATE CLUSTER.md | 60 -
.../sql-statements/Administration/CREATE FILE.md | 76 -
.../sql-statements/Administration/DROP CLUSTER.md | 43 -
.../sql-statements/Administration/DROP FILE.md | 51 -
.../sql-statements/Administration/ENTER.md | 44 -
.../Administration/INSTALL PLUGIN.md | 63 -
.../sql-statements/Administration/LINK DATABASE.md | 49 -
.../Administration/MIGRATE DATABASE.md | 45 -
.../Administration/SET LDAP_ADMIN_PASSWORD.md | 45 -
.../sql-statements/Administration/SHOW BACKENDS.md | 48 -
.../sql-statements/Administration/SHOW BROKER.md | 40 -
.../sql-statements/Administration/SHOW FILE.md | 52 -
.../Administration/SHOW FRONTENDS.md | 43 -
.../Administration/SHOW FULL COLUMNS.md | 42 -
.../sql-statements/Administration/SHOW INDEX.md | 46 -
.../Administration/SHOW MIGRATIONS.md | 37 -
.../sql-statements/Administration/SHOW PLUGINS.md | 45 -
.../Administration/SHOW TABLE STATUS.md | 55 -
.../sql-statements/Administration/SHOW TRASH.md | 53 -
.../sql-statements/Administration/SHOW VIEW.md | 46 -
.../Administration/UNINSTALL PLUGIN.md | 47 -
.../Data Definition/ALTER DATABASE.md | 56 -
.../Data Definition/ALTER RESOURCE.md | 48 -
.../sql-statements/Data Definition/ALTER TABLE.md | 445 -
.../sql-statements/Data Definition/ALTER VIEW.md | 51 -
.../sql-statements/Data Definition/BACKUP.md | 71 -
.../sql-statements/Data Definition/CANCEL ALTER.md | 70 -
.../Data Definition/CANCEL BACKUP.md | 39 -
.../Data Definition/CANCEL RESTORE.md | 42 -
.../Data Definition/CREATE DATABASE.md | 69 -
.../Data Definition/CREATE ENCRYPTKEY.md | 80 -
.../sql-statements/Data Definition/CREATE INDEX.md | 45 -
.../Data Definition/CREATE MATERIALIZED VIEW.md | 238 -
.../Data Definition/CREATE REPOSITORY.md | 87 -
.../Data Definition/CREATE RESOURCE.md | 134 -
.../Data Definition/CREATE TABLE LIKE.md | 78 -
.../sql-statements/Data Definition/CREATE TABLE.md | 879 -
.../sql-statements/Data Definition/CREATE VIEW.md | 68 -
.../Data Definition/Colocate Join.md | 98 -
.../Data Definition/DROP DATABASE.md | 43 -
.../Data Definition/DROP ENCRYPTKEY.md | 55 -
.../sql-statements/Data Definition/DROP INDEX.md | 37 -
.../Data Definition/DROP MATERIALIZED VIEW.md | 110 -
.../Data Definition/DROP REPOSITORY.md | 41 -
.../Data Definition/DROP RESOURCE.md | 46 -
.../sql-statements/Data Definition/DROP TABLE.md | 46 -
.../sql-statements/Data Definition/DROP VIEW.md | 40 -
.../sql-statements/Data Definition/HLL.md | 111 -
.../sql-statements/Data Definition/RECOVER.md | 54 -
.../Data Definition/REFRESH DATABASE.md | 45 -
.../Data Definition/REFRESH TABLE.md | 45 -
.../sql-statements/Data Definition/RESTORE.md | 87 -
.../Data Definition/SHOW ENCRYPTKEYS.md | 68 -
.../Data Definition/SHOW RESOURCES.md | 67 -
.../Data Definition/TRUNCATE TABLE.md | 52 -
.../Data Definition/create-function.md | 152 -
.../Data Definition/drop-function.md | 54 -
.../Data Definition/show-functions.md | 83 -
.../sql-statements/Data Manipulation/BEGIN.md | 92 -
.../Data Manipulation/BROKER LOAD.md | 587 -
.../Data Manipulation/CANCEL DELETE.md | 36 -
.../Data Manipulation/CANCEL LABEL.md | 53 -
.../Data Manipulation/CANCEL LOAD.md | 45 -
.../Data Manipulation/CREATE SYNC JOB.md | 165 -
.../sql-statements/Data Manipulation/DELETE.md | 66 -
.../sql-statements/Data Manipulation/EXPORT.md | 125 -
.../Data Manipulation/GET LABEL STATE.md | 58 -
.../sql-statements/Data Manipulation/GROUP BY.md | 168 -
.../sql-statements/Data Manipulation/LOAD.md | 291 -
.../sql-statements/Data Manipulation/MINI LOAD.md | 132 -
.../sql-statements/Data Manipulation/MULTI LOAD.md | 107 -
.../sql-statements/Data Manipulation/OUTFILE.md | 207 -
.../Data Manipulation/PAUSE ROUTINE LOAD.md | 40 -
.../Data Manipulation/PAUSE SYNC JOB.md | 48 -
.../Data Manipulation/RESTORE TABLET.md | 41 -
.../Data Manipulation/RESUME ROUTINE LOAD.md | 40 -
.../Data Manipulation/RESUME SYNC JOB.md | 46 -
.../Data Manipulation/ROUTINE LOAD.md | 588 -
.../sql-statements/Data Manipulation/SHOW ALTER.md | 55 -
.../Data Manipulation/SHOW BACKUP.md | 62 -
.../Data Manipulation/SHOW CREATE FUNCTION.md | 43 -
.../Data Manipulation/SHOW CREATE ROUTINE LOAD.md | 45 -
.../Data Manipulation/SHOW DATA SKEW.md | 50 -
.../sql-statements/Data Manipulation/SHOW DATA.md | 110 -
.../Data Manipulation/SHOW DATABASE ID.md | 38 -
.../Data Manipulation/SHOW DATABASES.md | 35 -
.../Data Manipulation/SHOW DELETE.md | 39 -
.../SHOW DYNAMIC PARTITION TABLES.md | 36 -
.../Data Manipulation/SHOW EXPORT.md | 70 -
.../sql-statements/Data Manipulation/SHOW LOAD.md | 74 -
.../Data Manipulation/SHOW PARTITION ID.md | 38 -
.../Data Manipulation/SHOW PARTITIONS.md | 48 -
.../Data Manipulation/SHOW PROPERTY.md | 42 -
.../Data Manipulation/SHOW REPOSITORIES.md | 49 -
.../Data Manipulation/SHOW RESTORE.md | 67 -
.../Data Manipulation/SHOW ROUTINE LOAD TASK.md | 35 -
.../Data Manipulation/SHOW ROUTINE LOAD.md | 107 -
.../Data Manipulation/SHOW SNAPSHOT.md | 56 -
.../Data Manipulation/SHOW STREAM LOAD.md | 68 -
.../Data Manipulation/SHOW SYNC JOB.md | 49 -
.../Data Manipulation/SHOW TABLE CREATION.md | 82 -
.../Data Manipulation/SHOW TABLE ID.md | 38 -
.../Data Manipulation/SHOW TABLES.md | 34 -
.../Data Manipulation/SHOW TABLET.md | 39 -
.../Data Manipulation/SHOW TABLETS.md | 56 -
.../Data Manipulation/SHOW TRANSACTION.md | 100 -
.../Data Manipulation/SHOW-LAST-INSERT.md | 67 -
.../Data Manipulation/STOP ROUTINE LOAD.md | 35 -
.../Data Manipulation/STOP SYNC JOB.md | 44 -
.../Data Manipulation/STREAM LOAD.md | 286 -
.../sql-statements/Data Manipulation/UPDATE.md | 75 -
.../Data Manipulation/alter-routine-load.md | 115 -
.../sql-statements/Data Manipulation/insert.md | 110 -
.../Data Manipulation/lateral-view.md | 94 -
.../sql-statements/Utility/util_stmt.md | 39 -
{new-docs => docs}/en/summary/basic-summary.md | 0
.../en/summary/system-architecture.md | 4 +-
docs/zh-CN/README.md | 2 +-
.../cluster-management/elastic-expansion.md | 0
.../cluster-management/load-balancing.md | 0
.../admin-manual/cluster-management/upgrade.md | 0
.../zh-CN/admin-manual/config/be-config.md | 0
.../zh-CN/admin-manual/config/fe-config.md | 0
.../zh-CN/admin-manual/config/user-property.md | 0
.../zh-CN/admin-manual/data-admin/backup.md | 0
.../admin-manual/data-admin/delete-recover.md | 0
.../zh-CN/admin-manual/data-admin/restore.md | 0
.../http-actions/cancel-label.md | 0
.../http-actions/check-reset-rpc-cache.md | 0
.../http-actions/compaction-action.md | 0
.../http-actions/connection-action.md | 0
.../http-actions/fe-get-log-file.md | 0
.../http-actions/fe/backends-action.md | 0
.../http-actions/fe/bootstrap-action.md | 0
.../http-actions/fe/cancel-load-action.md | 0
.../http-actions/fe/check-decommission-action.md | 0
.../http-actions/fe/check-storage-type-action.md | 0
.../http-actions/fe/config-action.md | 0
.../http-actions/fe/connection-action.md | 0
.../http-actions/fe/get-ddl-stmt-action.md | 0
.../http-actions/fe/get-load-info-action.md | 0
.../http-actions/fe/get-load-state.md | 0
.../http-actions/fe/get-log-file-action.md | 0
.../http-actions/fe/get-small-file.md | 0
.../http-actions/fe/ha-action.md | 0
.../http-actions/fe/hardware-info-action.md | 0
.../http-actions/fe/health-action.md | 0
.../http-actions/fe/log-action.md | 0
.../http-actions/fe/logout-action.md | 0
.../http-actions/fe/manager/cluster-action.md | 0
.../http-actions/fe/manager/node-action.md | 0
.../fe/manager/query-profile-action.md | 0
.../http-actions/fe/meta-action.md | 0
.../http-actions/fe/meta-info-action.md | 0
.../http-actions/fe/meta-replay-state-action.md | 0
.../http-actions/fe/profile-action.md | 0
.../http-actions/fe/query-detail-action.md | 0
.../http-actions/fe/query-profile-action.md | 0
.../http-actions/fe/row-count-action.md | 0
.../http-actions/fe/session-action.md | 0
.../http-actions/fe/set-config-action.md | 0
.../http-actions/fe/show-data-action.md | 0
.../http-actions/fe/show-meta-info-action.md | 0
.../http-actions/fe/show-proc-action.md | 0
.../http-actions/fe/show-runtime-info-action.md | 0
.../http-actions/fe/statement-execution-action.md | 0
.../http-actions/fe/system-action.md | 0
.../http-actions/fe/table-query-plan-action.md | 0
.../http-actions/fe/table-row-count-action.md | 0
.../http-actions/fe/table-schema-action.md | 0
.../http-actions/fe/upload-action.md | 0
.../http-actions/get-load-state.md | 0
.../http-actions/get-tablets.md | 0
.../http-actions/profile-action.md | 0
.../http-actions/query-detail-action.md | 0
.../http-actions/restore-tablet.md | 0
.../http-actions/show-data-action.md | 0
.../http-actions/tablet-migration-action.md | 0
.../http-actions/tablets_distribution.md | 0
.../maint-monitor/be-olap-error-code.md | 0
.../admin-manual/maint-monitor/disk-capacity.md | 0
.../admin-manual/maint-monitor/doris-error-code.md | 0
.../maint-monitor/metadata-operation.md | 0
.../maint-monitor}/monitor-alert.md | 0
.../maint-monitor}/monitor-metrics/be-metrics.md | 0
.../maint-monitor}/monitor-metrics/fe-metrics.md | 0
.../maint-monitor}/tablet-meta-tool.md | 0
.../maint-monitor/tablet-repair-and-balance.md | 0
.../maint-monitor}/tablet-restore-tool.md | 0
.../zh-CN/admin-manual/multi-tenant.md | 0
.../zh-CN/admin-manual/optimization.md | 0
.../zh-CN/admin-manual/privilege-ldap/ldap.md | 0
.../admin-manual/privilege-ldap/user-privilege.md | 0
.../query-profile.md} | 7 +-
.../zh-CN/admin-manual/sql-interception.md | 0
.../alter-table/alter-table-bitmap-index.md | 82 -
.../alter-table/alter-table-replace-table.md | 73 -
.../alter-table/alter-table-rollup.md | 194 -
.../alter-table/alter-table-schema-change.md | 249 -
.../alter-table/alter-table-temp-partition.md | 298 -
docs/zh-CN/administrator-guide/backup-restore.md | 193 -
.../administrator-guide/block-rule/sql-block.md | 93 -
docs/zh-CN/administrator-guide/bloomfilter.md | 133 -
docs/zh-CN/administrator-guide/broker.md | 282 -
.../administrator-guide/bucket-shuffle-join.md | 106 -
docs/zh-CN/administrator-guide/colocation-join.md | 409 -
docs/zh-CN/administrator-guide/config/be_config.md | 1543 -
docs/zh-CN/administrator-guide/config/fe_config.md | 2234 --
.../administrator-guide/config/user_property.md | 73 -
.../zh-CN/administrator-guide/dynamic-partition.md | 460 -
docs/zh-CN/administrator-guide/export-manual.md | 202 -
.../administrator-guide/export_with_mysql_dump.md | 41 -
docs/zh-CN/administrator-guide/ldap.md | 177 -
.../load-data/batch-delete-manual.md | 205 -
.../load-data/binlog-load-manual.md | 502 -
.../load-data/broker-load-manual.md | 544 -
.../administrator-guide/load-data/delete-manual.md | 189 -
.../load-data/insert-into-manual.md | 310 -
.../load-data/load-json-format.md | 470 -
.../administrator-guide/load-data/load-manual.md | 227 -
.../load-data/routine-load-manual.md | 335 -
.../load-data/s3-load-manual.md | 94 -
.../load-data/sequence-column-manual.md | 208 -
.../load-data/spark-load-manual.md | 596 -
.../load-data/stream-load-manual.md | 415 -
.../zh-CN/administrator-guide/materialized_view.md | 488 -
docs/zh-CN/administrator-guide/multi-tenant.md | 222 -
.../operation/be-olap-error-code.md | 265 -
.../administrator-guide/operation/disk-capacity.md | 163 -
.../operation/doris-error-code.md | 179 -
.../operation/metadata-operation.md | 403 -
.../administrator-guide/operation/multi-tenant.md | 239 -
.../operation/tablet-repair-and-balance.md | 775 -
.../orthogonal-bitmap-manual.md | 161 -
docs/zh-CN/administrator-guide/outfile.md | 192 -
docs/zh-CN/administrator-guide/partition_cache.md | 197 -
docs/zh-CN/administrator-guide/privilege.md | 234 -
docs/zh-CN/administrator-guide/query_cache.md | 155 -
.../administrator-guide/resource-management.md | 170 -
docs/zh-CN/administrator-guide/runtime-filter.md | 282 -
docs/zh-CN/administrator-guide/segment-v2-usage.md | 157 -
docs/zh-CN/administrator-guide/small-file-mgr.md | 104 -
docs/zh-CN/administrator-guide/sql-mode.md | 76 -
docs/zh-CN/administrator-guide/time-zone.md | 91 -
docs/zh-CN/administrator-guide/update.md | 126 -
docs/zh-CN/administrator-guide/variables.md | 492 -
.../zh-CN/advanced/alter-table/replace-table.md | 0
.../zh-CN/advanced/alter-table/schema-change.md | 0
.../zh-CN/advanced/best-practice/debug-log.md | 0
.../advanced/best-practice/import-analysis.md | 0
.../zh-CN/advanced/best-practice/query-analysis.md | 0
{new-docs => docs}/zh-CN/advanced/broker.md | 0
.../zh-CN/advanced/cache/partition-cache.md | 0
.../join-optimization/bucket-shuffle-join.md | 0
.../advanced/join-optimization/colocation-join.md | 0
.../advanced/join-optimization/runtime-filter.md | 0
.../zh-CN/advanced/materialized-view.md | 0
.../zh-CN/advanced/orthogonal-bitmap-manual.md | 0
.../zh-CN/advanced/partition/dynamic-partition.md | 0
.../advanced/partition/table-tmp-partition.md | 0
{new-docs => docs}/zh-CN/advanced/resource.md | 0
.../zh-CN/advanced/small-file-mgr.md | 0
{new-docs => docs}/zh-CN/advanced/time-zone.md | 0
{new-docs => docs}/zh-CN/advanced/variables.md | 0
.../vectorized-execution-engine.md | 0
docs/zh-CN/benchmark/samples.md | 57 -
{new-docs => docs}/zh-CN/benchmark/ssb.md | 0
docs/zh-CN/benchmark/star-schema-benchmark.md | 182 -
docs/zh-CN/benchmark/systemd.md | 31 -
{new-docs => docs}/zh-CN/benchmark/tpc-h.md | 0
.../zh-CN/data-operate/export/export-manual.md | 0
.../data-operate/export/export_with_mysql_dump.md | 0
.../zh-CN/data-operate/export/outfile.md | 0
.../import/import-scenes/external-storage-load.md | 0
.../import/import-scenes/external-table-load.md | 0
.../data-operate/import/import-scenes/jdbc-load.md | 0
.../import/import-scenes/kafka-load.md | 0
.../import/import-scenes/load-atomicity.md | 0
.../import/import-scenes/load-data-convert.md | 0
.../import/import-scenes/load-strict-mode.md | 0
.../import/import-scenes/local-file-load.md | 0
.../import/import-way/binlog-load-manual.md | 0
.../import/import-way/broker-load-manual.md | 0
.../import/import-way/insert-into-manual.md | 0
.../import/import-way/load-json-format.md | 0
.../import/import-way/routine-load-manual.md | 0
.../import/import-way/s3-load-manual.md | 0
.../import/import-way/spark-load-manual.md | 0
.../import/import-way/stream-load-manual.md | 0
.../zh-CN/data-operate/import/load-manual.md | 0
.../update-delete/batch-delete-manual.md | 0
.../data-operate/update-delete/delete-manual.md | 0
.../update-delete/sequence-column-manual.md | 0
.../zh-CN/data-operate/update-delete/update.md | 0
.../zh-CN/data-table/advance-usage.md | 0
{new-docs => docs}/zh-CN/data-table/basic-usage.md | 0
.../zh-CN/data-table/best-practice.md | 0
{new-docs => docs}/zh-CN/data-table/data-model.md | 0
.../zh-CN/data-table/data-partition.md | 0
.../zh-CN/data-table/hit-the-rollup.md | 0
.../zh-CN/data-table/index/bitmap-index.md | 0
.../zh-CN/data-table/index/bloomfilter.md | 0
.../zh-CN/data-table/index/prefix-index.md | 0
{new-docs => docs}/zh-CN/ecosystem/audit-plugin.md | 0
{new-docs => docs}/zh-CN/ecosystem/datax.md | 0
.../doris-manager/cluster-managenent.md | 0
.../doris-manager/compiling-deploying.md | 0
.../doris-manager/initializing.md | 0
.../doris-manager/space-list.md | 0
.../doris-manager/space-management.md | 0
.../doris-manager/system-settings.md | 0
.../zh-CN/ecosystem/external-table/doris-on-es.md | 0
.../ecosystem/external-table/hive-of-doris.md | 0
.../ecosystem/external-table/iceberg-of-doris.md | 0
.../ecosystem/external-table/odbc-of-doris.md | 0
.../zh-CN/ecosystem/flink-doris-connector.md | 0
{new-docs => docs}/zh-CN/ecosystem/logstash.md | 0
.../zh-CN/ecosystem/plugin-development-manual.md | 0
.../zh-CN/ecosystem/seatunnel/flink-sink.md | 0
.../zh-CN/ecosystem/seatunnel/spark-sink.md | 0
.../zh-CN/ecosystem/spark-doris-connector.md | 0
.../zh-CN/ecosystem/udf/contribute-udf.md | 0
.../ecosystem/udf/native-user-defined-function.md | 0
.../ecosystem/udf/remote-user-defined-function.md | 0
docs/zh-CN/extending-doris/audit-plugin.md | 119 -
docs/zh-CN/extending-doris/datax.md | 104 -
docs/zh-CN/extending-doris/doris-on-es.md | 588 -
.../zh-CN/extending-doris/flink-doris-connector.md | 497 -
docs/zh-CN/extending-doris/hive-bitmap-udf.md | 104 -
docs/zh-CN/extending-doris/hive-of-doris.md | 117 -
docs/zh-CN/extending-doris/iceberg-of-doris.md | 210 -
docs/zh-CN/extending-doris/logstash.md | 198 -
docs/zh-CN/extending-doris/odbc-of-doris.md | 361 -
.../extending-doris/plugin-development-manual.md | 312 -
docs/zh-CN/extending-doris/seatunnel/flink-sink.md | 116 -
docs/zh-CN/extending-doris/seatunnel/spark-sink.md | 124 -
.../zh-CN/extending-doris/spark-doris-connector.md | 291 -
docs/zh-CN/extending-doris/udf/contribute-udf.md | 124 -
.../udf/java-user-defined-function.md | 88 -
.../udf/native-user-defined-function.md | 267 -
.../udf/remote-user-defined-function.md | 110 -
{new-docs => docs}/zh-CN/faq/data-faq.md | 0
docs/zh-CN/faq/error.md | 151 -
docs/zh-CN/faq/faq.md | 297 -
{new-docs => docs}/zh-CN/faq/install-faq.md | 0
{new-docs => docs}/zh-CN/faq/sql-faq.md | 0
.../zh-CN/get-starting/get-starting.md | 4 +-
docs/zh-CN/getting-started/advance-usage.md | 280 -
docs/zh-CN/getting-started/basic-usage.md | 381 -
docs/zh-CN/getting-started/best-practice.md | 197 -
docs/zh-CN/getting-started/data-model-rollup.md | 638 -
docs/zh-CN/getting-started/data-partition.md | 401 -
docs/zh-CN/getting-started/hit-the-rollup.md | 296 -
{new-docs => docs}/zh-CN/install/install-deploy.md | 0
.../install/source-install/compilation-arm.md | 0
.../compilation-with-ldb-toolchain.md | 0
.../zh-CN/install/source-install/compilation.md | 0
docs/zh-CN/installing/compilation-arm.md | 256 -
.../installing/compilation-with-ldb-toolchain.md | 127 -
docs/zh-CN/installing/compilation.md | 261 -
docs/zh-CN/installing/install-deploy.md | 475 -
docs/zh-CN/installing/upgrade.md | 86 -
docs/zh-CN/internal/doris_storage_optimization.md | 234 -
.../zh-CN/internal/flink_doris_connector_design.md | 272 -
docs/zh-CN/internal/grouping_sets_design.md | 517 -
docs/zh-CN/internal/metadata-design.md | 126 -
docs/zh-CN/internal/spark_load.md | 212 -
.../aggregate-functions/approx_count_distinct.md | 0
.../sql-functions/aggregate-functions/avg.md | 0
.../aggregate-functions/bitmap_union.md | 0
.../sql-functions/aggregate-functions/count.md | 0
.../aggregate-functions/group_concat.md | 0
.../aggregate-functions/hll_union_agg.md | 0
.../sql-functions/aggregate-functions/max.md | 0
.../sql-functions/aggregate-functions/max_by.md | 0
.../sql-functions/aggregate-functions/min.md | 0
.../sql-functions/aggregate-functions/min_by.md | 0
.../aggregate-functions/percentile.md | 0
.../aggregate-functions/percentile_approx.md | 0
.../sql-functions/aggregate-functions/stddev.md | 0
.../aggregate-functions/stddev_samp.md | 0
.../sql-functions/aggregate-functions/sum.md | 0
.../sql-functions/aggregate-functions/topn.md | 0
.../sql-functions/aggregate-functions/var_samp.md | 0
.../sql-functions/aggregate-functions/variance.md | 0
.../sql-functions/bitmap-functions/bitmap_and.md | 0
.../bitmap-functions/bitmap_and_count.md | 0
.../bitmap-functions/bitmap_and_not.md | 0
.../bitmap-functions/bitmap_and_not_count.md | 0
.../bitmap-functions/bitmap_contains.md | 0
.../sql-functions/bitmap-functions/bitmap_empty.md | 0
.../bitmap-functions/bitmap_from_string.md | 0
.../bitmap-functions/bitmap_has_all.md | 0
.../bitmap-functions/bitmap_has_any.md | 0
.../sql-functions/bitmap-functions/bitmap_hash.md | 0
.../bitmap-functions/bitmap_intersect.md | 0
.../sql-functions/bitmap-functions/bitmap_max.md | 0
.../sql-functions/bitmap-functions/bitmap_min.md | 0
.../sql-functions/bitmap-functions/bitmap_not.md | 0
.../sql-functions/bitmap-functions/bitmap_or.md | 0
.../bitmap-functions/bitmap_or_count.md | 0
.../bitmap-functions/bitmap_subset_in_range.md | 0
.../bitmap-functions/bitmap_subset_limit.md | 0
.../bitmap-functions/bitmap_to_string.md | 0
.../sql-functions/bitmap-functions/bitmap_union.md | 0
.../sql-functions/bitmap-functions/bitmap_xor.md | 0
.../bitmap-functions/bitmap_xor_count.md | 0
.../orthogonal_bitmap_intersect.md | 0
.../orthogonal_bitmap_intersect_count.md | 0
.../orthogonal_bitmap_union_count.md | 0
.../sql-functions/bitmap-functions/sub_bitmap.md | 0
.../sql-functions/bitmap-functions/to_bitmap.md | 0
.../sql-functions/bitwise-functions/bitand.md | 0
.../sql-functions/bitwise-functions/bitnot.md | 0
.../sql-functions/bitwise-functions/bitor.md | 0
.../sql-functions/bitwise-functions/bitxor.md | 0
.../sql-functions/cast.md | 0
.../sql-functions/conditional-functions/case.md | 0
.../conditional-functions/coalesce.md | 0
.../sql-functions/conditional-functions/if.md | 0
.../sql-functions/conditional-functions/ifnull.md | 0
.../sql-functions/conditional-functions/nullif.md | 0
.../date-time-functions/convert_tz.md | 0
.../sql-functions/date-time-functions/curdate.md | 0
.../date-time-functions/current_timestamp.md | 0
.../sql-functions/date-time-functions/curtime.md | 0
.../sql-functions/date-time-functions/date_add.md | 0
.../date-time-functions/date_format.md | 0
.../sql-functions/date-time-functions/date_sub.md | 0
.../sql-functions/date-time-functions/datediff.md | 0
.../sql-functions/date-time-functions/day.md | 0
.../sql-functions/date-time-functions/dayname.md | 0
.../date-time-functions/dayofmonth.md | 0
.../sql-functions/date-time-functions/dayofweek.md | 0
.../sql-functions/date-time-functions/dayofyear.md | 0
.../sql-functions/date-time-functions/from_days.md | 0
.../date-time-functions/from_unixtime.md | 0
.../sql-functions/date-time-functions/hour.md | 0
.../sql-functions/date-time-functions/makedate.md | 0
.../sql-functions/date-time-functions/minute.md | 0
.../sql-functions/date-time-functions/month.md | 0
.../sql-functions/date-time-functions/monthname.md | 0
.../sql-functions/date-time-functions/now.md | 0
.../sql-functions/date-time-functions/second.md | 0
.../date-time-functions/str_to_date.md | 0
.../date-time-functions/time_round.md | 0
.../sql-functions/date-time-functions/timediff.md | 0
.../date-time-functions/timestampadd.md | 0
.../date-time-functions/timestampdiff.md | 0
.../sql-functions/date-time-functions/to_date.md | 0
.../sql-functions/date-time-functions/to_days.md | 0
.../date-time-functions/unix_timestamp.md | 0
.../date-time-functions/utc_timestamp.md | 0
.../sql-functions/date-time-functions/week.md | 0
.../sql-functions/date-time-functions/weekday.md | 0
.../date-time-functions/weekofyear.md | 0
.../sql-functions/date-time-functions/year.md | 0
.../sql-functions/date-time-functions/yearweek.md | 0
.../sql-functions/digital-masking.md | 0
.../sql-functions/encrypt-digest-functions/aes.md | 0
.../sql-functions/encrypt-digest-functions/md5.md | 0
.../encrypt-digest-functions/md5sum.md | 0
.../sql-functions/encrypt-digest-functions/sm3.md | 0
.../encrypt-digest-functions/sm3sum.md | 0
.../sql-functions/encrypt-digest-functions/sm4.md | 0
.../encrypt-dixgest-functions}/aes.md | 0
.../encrypt-dixgest-functions}/md5.md | 0
.../encrypt-dixgest-functions}/md5sum.md | 0
.../encrypt-dixgest-functions}/sm3.md | 0
.../encrypt-dixgest-functions}/sm3sum.md | 0
.../encrypt-dixgest-functions}/sm4.md | 0
.../hash-functions/murmur_hash3_32.md | 0
.../json-functions/get_json_double.md | 0
.../sql-functions/json-functions/get_json_int.md | 0
.../json-functions/get_json_string.md | 0
.../sql-functions/json-functions/json_array.md | 0
.../sql-functions/json-functions/json_object.md | 0
.../sql-functions/json-functions/json_quote.md | 0
.../sql-functions/math-functions/conv.md | 0
.../sql-functions/math-functions/pmod.md | 0
.../sql-functions/spatial-functions/st_astext.md | 0
.../sql-functions/spatial-functions/st_circle.md | 0
.../sql-functions/spatial-functions/st_contains.md | 0
.../spatial-functions/st_distance_sphere.md | 0
.../spatial-functions/st_geometryfromtext.md | 0
.../spatial-functions/st_linefromtext.md | 0
.../sql-functions/spatial-functions/st_point.md | 0
.../sql-functions/spatial-functions/st_polygon.md | 0
.../sql-functions/spatial-functions/st_x.md | 0
.../sql-functions/spatial-functions/st_y.md | 0
.../append_trailing_char_if_absent.md | 0
.../sql-functions/string-functions/ascii.md | 0
.../sql-functions/string-functions/bit_length.md | 0
.../sql-functions/string-functions/char_length.md | 0
.../sql-functions/string-functions/concat.md | 0
.../sql-functions/string-functions/concat_ws.md | 0
.../sql-functions/string-functions/ends_with.md | 0
.../sql-functions/string-functions/find_in_set.md | 0
.../sql-functions/string-functions/hex.md | 0
.../sql-functions/string-functions/instr.md | 0
.../sql-functions/string-functions/lcase.md | 0
.../sql-functions/string-functions/left.md | 0
.../sql-functions/string-functions/length.md | 0
.../sql-functions/string-functions/like/like.md | 0
.../string-functions/like/not_like.md | 0
.../sql-functions/string-functions/locate.md | 0
.../sql-functions/string-functions/lower.md | 0
.../sql-functions/string-functions/lpad.md | 0
.../sql-functions/string-functions/ltrim.md | 0
.../sql-functions/string-functions/money_format.md | 0
.../string-functions/null_or_empty.md | 0
.../string-functions/regexp/not_regexp.md | 0
.../string-functions/regexp/regexp.md | 0
.../string-functions/regexp/regexp_extract.md | 0
.../string-functions/regexp/regexp_replace.md | 0
.../sql-functions/string-functions/repeat.md | 0
.../sql-functions/string-functions/replace.md | 0
.../sql-functions/string-functions/reverse.md | 0
.../sql-functions/string-functions/right.md | 0
.../sql-functions/string-functions/rpad.md | 0
.../sql-functions/string-functions/split_part.md | 0
.../sql-functions/string-functions/starts_with.md | 0
.../sql-functions/string-functions/strleft.md | 0
.../sql-functions/string-functions/strright.md | 0
.../sql-functions/string-functions/substring.md | 0
.../sql-functions/string-functions/unhex.md | 0
.../table-functions/explode-bitmap.md | 0
.../table-functions/explode-json-array.md | 0
.../table-functions/explode-numbers.md | 0
.../sql-functions/table-functions/explode-split.md | 0
.../table-functions/outer-combinator.md | 0
.../sql-functions/window-function.md | 0
.../Account-Management-Statements/CREATE-ROLE.md | 0
.../Account-Management-Statements/CREATE-USER.md | 0
.../Account-Management-Statements/DROP-ROLE.md | 0
.../Account-Management-Statements/DROP-USER.md | 0
.../Account-Management-Statements/GRANT.md | 0
.../Account-Management-Statements/LDAP.md | 0
.../Account-Management-Statements/REVOKE.md | 0
.../Account-Management-Statements/SET-PASSWORD.md | 0
.../Account-Management-Statements/SET-PROPERTY.md | 0
.../ALTER-SYSTEM-ADD-BACKEND.md | 0
.../ALTER-SYSTEM-ADD-BROKER.md | 0
.../ALTER-SYSTEM-ADD-FOLLOWER.md | 0
.../ALTER-SYSTEM-ADD-OBSERVER.md | 0
.../ALTER-SYSTEM-DECOMMISSION-BACKEND.md | 0
.../ALTER-SYSTEM-DROP-BACKEND.md | 0
.../ALTER-SYSTEM-DROP-BROKER.md | 0
.../ALTER-SYSTEM-DROP-FOLLOWER.md | 0
.../ALTER-SYSTEM-DROP-OBSERVER.md | 0
.../ALTER-SYSTEM-MODIFY-BACKEND.md | 0
.../ALTER-SYSTEM-MODIFY-BROKER.md | 0
.../CANCEL-ALTER-SYSTEM.md | 0
.../Alter/ALTER-DATABASE.md | 0
.../Alter/ALTER-SQL-BLOCK-RULE.md | 0
.../Alter/ALTER-TABLE-BITMAP.md | 0
.../Alter/ALTER-TABLE-COLUMN.md | 0
.../Alter/ALTER-TABLE-PARTITION.md | 0
.../Alter/ALTER-TABLE-PROPERTY.md | 0
.../Alter/ALTER-TABLE-RENAME.md | 0
.../Alter/ALTER-TABLE-REPLACE.md | 0
.../Alter/ALTER-TABLE-ROLLUP.md | 0
.../Data-Definition-Statements/Alter/ALTER-VIEW.md | 0
.../Alter/CANCEL-ALTER-TABLE.md | 0
.../Backup-and-Restore/BACKUP.md | 0
.../Backup-and-Restore/CANCEL-BACKUP.md | 0
.../Backup-and-Restore/CANCEL-RESTORE.md | 0
.../Backup-and-Restore/CREATE-REPOSITORY.md | 0
.../Backup-and-Restore/DROP-REPOSITORY.md | 0
.../Backup-and-Restore/RECOVER.md | 0
.../Backup-and-Restore/RESTORE.md | 0
.../Create/CREATE-DATABASE.md | 0
.../Create/CREATE-ENCRYPT-KEY.md | 0
.../Create/CREATE-EXTERNAL-TABLE.md | 0
.../Create/CREATE-FILE.md | 0
.../Create/CREATE-FUNCTION.md | 0
.../Create/CREATE-INDEX.md | 0
.../Create/CREATE-MATERIALIZED-VIEW.md | 0
.../Create/CREATE-RESOURCE.md | 0
.../Create/CREATE-SQL-BLOCK-RULE.md | 0
.../Create/CREATE-TABLE-LIKE.md | 0
.../Create/CREATE-TABLE.md | 0
.../Create/CREATE-VIEW.md | 0
.../Drop/DROP-DATABASE.md | 0
.../Drop/DROP-ENCRYPT-KEY.md | 0
.../Data-Definition-Statements/Drop/DROP-FILE.md | 0
.../Drop/DROP-FUNCTION.md | 0
.../Data-Definition-Statements/Drop/DROP-INDEX.md | 0
.../Drop/DROP-MATERIALIZED-VIEW.md | 0
.../Drop/DROP-RESOURCE.md | 0
.../Drop/DROP-SQL-BLOCK-RULE.md | 0
.../Data-Definition-Statements/Drop/DROP-TABLE.md | 0
.../Drop/TRUNCATE-TABLE.md | 0
.../Load/ALTER-ROUTINE-LOAD.md | 0
.../Load/BROKER-LOAD.md | 0
.../Load/CANCEL-LOAD.md | 0
.../Load/CREATE-ROUTINE-LOAD.md | 0
.../Load/CREATE-SYNC-JOB.md | 0
.../Load/MULTI-LOAD.md | 0
.../Load/PAUSE-ROUTINE-LOAD.md | 0
.../Load/PAUSE-SYNC-JOB.md | 0
.../Load/RESUME-ROUTINE-LOAD.md | 0
.../Load/RESUME-SYNC-JOB.md | 0
.../Load/STOP-ROUTINE-LOAD.md | 0
.../Load/STOP-SYNC-JOB.md | 0
.../Load/STREAM-LOAD.md | 0
.../Manipulation/DELETE.md | 0
.../Manipulation/INSERT.md | 0
.../Manipulation/UPDATE.md | 0
.../Data-Manipulation-Statements/OUTFILE.md | 0
.../sql-reference-v2/Data-Types}/BIGINT.md | 0
.../sql-reference-v2/Data-Types}/BITMAP.md | 0
.../sql-reference-v2/Data-Types}/BOOLEAN.md | 0
.../sql-reference-v2/Data-Types}/CHAR.md | 0
.../sql-reference-v2/Data-Types}/DATE.md | 0
.../sql-reference-v2/Data-Types}/DATETIME.md | 0
.../sql-reference-v2/Data-Types}/DECIMAL.md | 0
.../sql-reference-v2/Data-Types}/DOUBLE.md | 0
.../sql-reference-v2/Data-Types}/FLOAT.md | 0
.../sql-reference-v2/Data-Types}/HLL.md | 0
.../sql-reference-v2/Data-Types}/INT.md | 0
.../sql-reference-v2/Data-Types}/LARGEINT.md | 0
.../sql-reference-v2/Data-Types}/QUANTILE_STATE.md | 0
.../sql-reference-v2/Data-Types}/SMALLINT.md | 0
.../sql-reference-v2/Data-Types}/STRING.md | 0
.../sql-reference-v2/Data-Types}/TINYINT.md | 0
.../sql-reference-v2/Data-Types}/VARCHAR.md | 0
.../ADMIN-CANCEL-REPAIR.md | 0
.../ADMIN-CHECK-TABLET.md | 0
.../ADMIN-CLEAN-TRASH.md | 0
.../ADMIN-REPAIR-TABLE.md | 0
.../ADMIN-SET-CONFIG.md | 0
.../ADMIN-SET-REPLICA-STATUS.md | 0
.../ADMIN-SHOW-CONFIG.md | 0
.../ADMIN-SHOW-REPLICA-DISTRIBUTION.md | 0
.../ADMIN-SHOW-REPLICA-STATUS.md | 0
.../ADMIN-SHOW-TABLET-STORAGE-FORMAT.md} | 0
.../ENABLE-FEATURE.md | 0
.../INSTALL-PLUGIN.md | 0
.../Database-Administration-Statements/KILL.md | 0
.../Database-Administration-Statements/RECOVER.md | 0
.../SET-VARIABLE.md | 0
.../UNINSTALL-PLUGIN.md | 0
.../SHOW-ALTER-TABLE-MATERIALIZED-VIEW.md | 0
.../sql-reference-v2/Show-Statements/SHOW-ALTER.md | 0
.../Show-Statements/SHOW-BACKENDS.md | 0
.../Show-Statements/SHOW-BACKUP.md | 0
.../Show-Statements/SHOW-BROKER.md | 0
.../Show-Statements/SHOW-CHARSET.md | 0
.../Show-Statements/SHOW-COLLATION.md | 0
.../Show-Statements/SHOW-COLUMNS.md | 0
.../Show-Statements/SHOW-CREATE-DATABASE.md | 0
.../Show-Statements/SHOW-CREATE-FUNCTION.md | 0
.../Show-Statements/SHOW-CREATE-ROUTINE-LOAD.md | 0
.../Show-Statements/SHOW-CREATE-TABLE.md | 0
.../sql-reference-v2/Show-Statements/SHOW-DATA.md | 0
.../Show-Statements/SHOW-DATABASE-ID.md | 0
.../Show-Statements/SHOW-DATABASES.md | 0
.../Show-Statements/SHOW-DELETE.md | 0
.../Show-Statements/SHOW-DYNAMIC-PARTITION.md | 0
.../Show-Statements/SHOW-ENCRYPT-KEY.md | 0
.../Show-Statements/SHOW-ENGINES.md | 0
.../Show-Statements/SHOW-EVENTS.md | 0
.../Show-Statements/SHOW-EXPORT.md | 0
.../sql-reference-v2/Show-Statements/SHOW-FILE.md | 0
.../Show-Statements/SHOW-FRONTENDS.md | 0
.../Show-Statements/SHOW-FUNCTIONS.md | 0
.../Show-Statements/SHOW-GRANTS.md | 0
.../sql-reference-v2/Show-Statements/SHOW-INDEX.md | 0
.../Show-Statements/SHOW-LAST-INSERT.md | 0
.../Show-Statements/SHOW-LOAD-PROFILE.md | 0
.../Show-Statements/SHOW-LOAD-WARNINGS.md | 0
.../sql-reference-v2/Show-Statements/SHOW-LOAD.md | 0
.../Show-Statements/SHOW-MIGRATIONS.md | 0
.../Show-Statements/SHOW-OPEN-TABLES.md | 0
.../Show-Statements/SHOW-PARTITION-ID.md | 0
.../Show-Statements/SHOW-PARTITIONS.md | 0
.../Show-Statements/SHOW-PLUGINS.md | 0
.../sql-reference-v2/Show-Statements/SHOW-PROC.md | 0
.../Show-Statements/SHOW-PROCEDURE.md | 0
.../Show-Statements/SHOW-PROCESSLIST.md | 0
.../Show-Statements/SHOW-PROPERTY.md | 0
.../Show-Statements/SHOW-QUERY-PROFILE.md | 0
.../Show-Statements/SHOW-REPOSITORIES.md | 0
.../Show-Statements/SHOW-RESOURCES.md | 0
.../Show-Statements/SHOW-RESTORE.md | 0
.../sql-reference-v2/Show-Statements/SHOW-ROLES.md | 0
.../Show-Statements/SHOW-ROLLUP.md | 0
.../Show-Statements/SHOW-ROUTINE-LOAD-TASK.md | 0
.../Show-Statements/SHOW-ROUTINE-LOAD.md | 0
.../Show-Statements/SHOW-SMALL-FILES.md | 0
.../Show-Statements/SHOW-SNAPSHOT.md | 0
.../Show-Statements/SHOW-SQL-BLOCK-RULE.md | 0
.../Show-Statements/SHOW-STATUS.md | 0
.../Show-Statements/SHOW-STREAM-LOAD.md | 0
.../Show-Statements/SHOW-SYNC-JOB.md | 0
.../Show-Statements/SHOW-TABLE-ID.md | 0
.../Show-Statements/SHOW-TABLE-STATUS.md | 0
.../Show-Statements/SHOW-TABLET.md | 0
.../Show-Statements/SHOW-TRANSACTION.md | 0
.../sql-reference-v2/Show-Statements/SHOW-TRASH.md | 0
.../Show-Statements/SHOW-TRIGGERS.md | 0
.../sql-reference-v2/Show-Statements/SHOW-USER.md | 0
.../Show-Statements/SHOW-VARIABLES.md | 0
.../sql-reference-v2/Show-Statements/SHOW-VIEW.md | 0
.../Show-Statements/SHOW-WARNING.md | 0
.../Show-Statements/SHOW-WHITE-LIST.md | 0
.../Utility-Statements/DESCRIBE.md | 0
.../sql-reference-v2/Utility-Statements/HELP.md | 0
.../sql-reference-v2/Utility-Statements/USE.md | 0
.../Account-Management-Statements/ALTER-USER.md | 38 -
.../Account-Management-Statements/CREATE-ROLE.md | 38 -
.../Account-Management-Statements/CREATE-USER.md | 38 -
.../Account-Management-Statements/DROP-ROLE.md | 38 -
.../Account-Management-Statements/DROP-USER.md | 38 -
.../Account-Management-Statements/GRANT.md | 38 -
.../Account-Management-Statements/LDAP.md | 38 -
.../Account-Management-Statements/REVOKE.md | 38 -
.../Account-Management-Statements/SET-PASSWORD.md | 38 -
.../Account-Management-Statements/SET-PROPERTY.md | 38 -
.../ALTER-SYSTEM-ADD-BACKEND.md | 38 -
.../ALTER-SYSTEM-ADD-FOLLOWER.md | 38 -
.../ALTER-SYSTEM-ADD-OBSERVER.md | 38 -
.../ALTER-SYSTEM-DECOMMISSION-BACKEND.md | 38 -
.../ALTER-SYSTEM-DROP-BACKEND.md | 38 -
.../ALTER-SYSTEM-DROP-FOLLOWER.md | 38 -
.../ALTER-SYSTEM-DROP-OBSERVER.md | 38 -
.../CANCEL-ALTER-SYSTEM.md | 38 -
.../Alter/ALTER-DATABASE.md | 38 -
.../Alter/ALTER-TABLE-COLUMN.md | 38 -
.../Alter/ALTER-TABLE-PARTITION.md | 38 -
.../Alter/ALTER-TABLE-PROPERTY.md | 38 -
.../Alter/ALTER-TABLE-RENAME.md | 38 -
.../Alter/ALTER-TABLE-REPLACE.md | 38 -
.../Alter/ALTER-TABLE-ROLLUP.md | 38 -
.../Data-Definition-Statements/Alter/ALTER-VIEW.md | 38 -
.../Alter/CANCEL-ALTER-TABLE.md | 38 -
.../Backup-and-Restore/BACKUP.md | 38 -
.../Backup-and-Restore/CANCEL-BACKUP.md | 38 -
.../Backup-and-Restore/CANCEL-RESTORE.md | 38 -
.../Backup-and-Restore/CREATE-REPOSITORY.md | 38 -
.../Backup-and-Restore/DROP-REPOSITORY.md | 38 -
.../Backup-and-Restore/RESTORE.md | 38 -
.../Create/CREATE-DATABASE.md | 38 -
.../Create/CREATE-ENCRYPT-KEY.md | 38 -
.../Create/CREATE-FILE.md | 38 -
.../Create/CREATE-FUNCTION.md | 38 -
.../Create/CREATE-INDEX.md | 38 -
.../Create/CREATE-MATERIALIZED-VIEW.md | 38 -
.../Create/CREATE-RESOURCE.md | 38 -
.../Create/CREATE-TABLE-LIKE.md | 38 -
.../Create/CREATE-TABLE.md | 569 -
.../Create/CREATE-VIEW.md | 38 -
.../Drop/DROP-DATABASE.md | 38 -
.../Drop/DROP-ENCRYPT-KEY.md | 38 -
.../Data-Definition-Statements/Drop/DROP-FILE.md | 38 -
.../Drop/DROP-FUNCTION.md | 38 -
.../Data-Definition-Statements/Drop/DROP-INDEX.md | 38 -
.../Drop/DROP-MATERIALIZED-VIEW.md | 38 -
.../Drop/DROP-RESOURCE.md | 38 -
.../Data-Definition-Statements/Drop/DROP-TABLE.md | 38 -
.../Drop/TRUNCATE-TABLE.md | 38 -
.../Load/ALTER-ROUTINE-LOAD.md | 38 -
.../Load/BROKER-LOAD.md | 38 -
.../Load/CANCEL-LOAD.md | 38 -
.../Load/CREATE-ROUTINE-LOAD.md | 38 -
.../Load/PAUSE-ROUTINE-LOAD.md | 38 -
.../Load/RESUME-ROUTINE-LOAD.md | 38 -
.../Load/STOP-ROUTINE-LOAD.md | 38 -
.../Load/STREAM-LOAD.md | 38 -
.../Manipulation/DELETE.md | 38 -
.../Manipulation/INSERT.md | 38 -
.../Manipulation/UPDATE.md | 38 -
.../ADMIN-CANCEL-REPAIR.md | 38 -
.../ADMIN-CHECK-TABLET.md | 38 -
.../ADMIN-REPAIR-TABLE.md | 38 -
.../ADMIN-SET-CONFIG.md | 38 -
.../ADMIN-SET-REPLICA-STATUS.md | 38 -
.../ADMIN-SHOW-CONFIG.md | 38 -
.../ADMIN-SHOW-REPLICA-DISTRIBUTION.md | 38 -
.../ADMIN-SHOW-REPLICA-STATUS.md | 38 -
.../INSTALL-PLUGIN.md | 38 -
.../Database-Administration-Statements/KILL.md | 38 -
.../Database-Administration-Statements/RECOVER.md | 38 -
.../SET-VARIABLE.md | 38 -
.../UNINSTALL-PLUGIN.md | 38 -
.../sql-statements/Show-Statements/SHOW-ALTER.md | 38 -
.../Show-Statements/SHOW-BACKENDS.md | 38 -
.../sql-statements/Show-Statements/SHOW-BACKUP.md | 38 -
.../sql-statements/Show-Statements/SHOW-BROKER.md | 38 -
.../sql-statements/Show-Statements/SHOW-COLUMNS.md | 38 -
.../Show-Statements/SHOW-CREATE-DATABASE.md | 38 -
.../Show-Statements/SHOW-CREATE-FUNCTION.md | 38 -
.../Show-Statements/SHOW-CREATE-ROUTINE-LOAD.md | 38 -
.../Show-Statements/SHOW-CREATE-TABLE.md | 38 -
.../sql-statements/Show-Statements/SHOW-DATA.md | 38 -
.../Show-Statements/SHOW-DATABASE-ID.md | 38 -
.../Show-Statements/SHOW-DATABASES.md | 38 -
.../sql-statements/Show-Statements/SHOW-DELETE.md | 38 -
.../Show-Statements/SHOW-DYNAMIC-PARTITION.md | 38 -
.../Show-Statements/SHOW-ENCRYPT-KEY.md | 38 -
.../sql-statements/Show-Statements/SHOW-ENGINES.md | 38 -
.../sql-statements/Show-Statements/SHOW-EVENTS.md | 38 -
.../sql-statements/Show-Statements/SHOW-EXPORT.md | 38 -
.../Show-Statements/SHOW-FRONTENDS.md | 38 -
.../Show-Statements/SHOW-FUNCTIONS.md | 38 -
.../sql-statements/Show-Statements/SHOW-GRANTS.md | 38 -
.../sql-statements/Show-Statements/SHOW-INDEX.md | 38 -
.../Show-Statements/SHOW-LOAD-PROFILE.md | 38 -
.../Show-Statements/SHOW-LOAD-WARNINGS.md | 38 -
.../sql-statements/Show-Statements/SHOW-LOAD.md | 38 -
.../Show-Statements/SHOW-MIGRATIONS.md | 38 -
.../Show-Statements/SHOW-OPEN-TABLES.md | 38 -
.../Show-Statements/SHOW-PARTITION-ID.md | 38 -
.../Show-Statements/SHOW-PARTITIONS.md | 38 -
.../sql-statements/Show-Statements/SHOW-PLUGINS.md | 38 -
.../sql-statements/Show-Statements/SHOW-PROC.md | 38 -
.../Show-Statements/SHOW-PROCESSLIST.md | 38 -
.../Show-Statements/SHOW-PROPERTY.md | 83 -
.../Show-Statements/SHOW-REPOSITORIES.md | 38 -
.../Show-Statements/SHOW-RESOURCES.md | 38 -
.../sql-statements/Show-Statements/SHOW-RESTORE.md | 38 -
.../sql-statements/Show-Statements/SHOW-ROLES.md | 38 -
.../Show-Statements/SHOW-ROUTINE-LOAD-TASK.md | 38 -
.../Show-Statements/SHOW-ROUTINE-LOAD.md | 38 -
.../Show-Statements/SHOW-SMALL-FILES.md | 38 -
.../Show-Statements/SHOW-SNAPSHOT.md | 38 -
.../sql-statements/Show-Statements/SHOW-STATUS.md | 38 -
.../Show-Statements/SHOW-STREAM-LOAD.md | 38 -
.../Show-Statements/SHOW-TABLE-ID.md | 38 -
.../Show-Statements/SHOW-TABLE-STATUS.md | 38 -
.../sql-statements/Show-Statements/SHOW-TABLET.md | 38 -
.../Show-Statements/SHOW-TRANSACTION.md | 38 -
.../sql-statements/Show-Statements/SHOW-USER.md | 38 -
.../Show-Statements/SHOW-VARIABLES.md | 38 -
.../sql-statements/Show-Statements/SHOW-VIEW.md | 38 -
.../sql-statements/Utility-Statements/DESCRIBE.md | 38 -
.../sql-statements/Utility-Statements/HELP.md | 38 -
.../sql-statements/Utility-Statements/USE.md | 38 -
.../Account Management/CREATE ROLE.md | 45 -
.../Account Management/CREATE USER.md | 76 -
.../sql-statements/Account Management/DROP ROLE.md | 44 -
.../sql-statements/Account Management/DROP USER.md | 50 -
.../sql-statements/Account Management/GRANT.md | 110 -
.../sql-statements/Account Management/REVOKE.md | 55 -
.../Account Management/SET PASSWORD.md | 56 -
.../Account Management/SET PROPERTY.md | 108 -
.../Account Management/SHOW GRANTS.md | 57 -
.../Account Management/SHOW ROLES.md | 42 -
.../Administration/ADMIN CANCEL REBALANCE DISK.md | 52 -
.../Administration/ADMIN CANCEL REPAIR.md | 48 -
.../Administration/ADMIN CHECK TABLET.md | 57 -
.../Administration/ADMIN CLEAN TRASH.md | 47 -
.../sql-statements/Administration/ADMIN COMPACT.md | 53 -
.../Administration/ADMIN REBALANCE DISK.md | 54 -
.../sql-statements/Administration/ADMIN REPAIR.md | 53 -
.../Administration/ADMIN SET CONFIG.md | 44 -
.../Administration/ADMIN SET REPLICA STATUS.md | 62 -
.../Administration/ADMIN SHOW CONFIG.md | 63 -
.../ADMIN SHOW REPLICA DISTRIBUTION.md | 52 -
.../Administration/ADMIN SHOW REPLICA STATUS.md | 65 -
.../Administration/ADMIN-DIAGNOSE-TABLET.md | 59 -
.../sql-statements/Administration/ALTER CLUSTER.md | 54 -
.../sql-statements/Administration/ALTER SYSTEM.md | 140 -
.../Administration/CANCEL DECOMMISSION.md | 41 -
.../Administration/CREATE CLUSTER.md | 62 -
.../sql-statements/Administration/CREATE FILE.md | 77 -
.../sql-statements/Administration/DROP CLUSTER.md | 44 -
.../sql-statements/Administration/DROP FILE.md | 51 -
.../sql-statements/Administration/ENTER.md | 44 -
.../Administration/INSTALL PLUGIN.md | 63 -
.../sql-statements/Administration/LINK DATABASE.md | 51 -
.../Administration/MIGRATE DATABASE.md | 47 -
.../Administration/SET LDAP_ADMIN_PASSWORD.md | 45 -
.../sql-statements/Administration/SHOW BACKENDS.md | 49 -
.../sql-statements/Administration/SHOW BROKER.md | 41 -
.../sql-statements/Administration/SHOW FILE.md | 53 -
.../Administration/SHOW FRONTENDS.md | 44 -
.../Administration/SHOW FULL COLUMNS.md | 40 -
.../sql-statements/Administration/SHOW INDEX.md | 44 -
.../Administration/SHOW MIGRATIONS.md | 38 -
.../sql-statements/Administration/SHOW PLUGINS.md | 45 -
.../Administration/SHOW TABLE STATUS.md | 48 -
.../sql-statements/Administration/SHOW TRASH.md | 49 -
.../sql-statements/Administration/SHOW VIEW.md | 39 -
.../Administration/UNINSTALL PLUGIN.md | 47 -
.../Data Definition/ALTER DATABASE.md | 62 -
.../Data Definition/ALTER RESOURCE.md | 48 -
.../sql-statements/Data Definition/ALTER TABLE.md | 441 -
.../sql-statements/Data Definition/ALTER VIEW.md | 52 -
.../sql-statements/Data Definition/BACKUP.md | 71 -
.../sql-statements/Data Definition/CANCEL ALTER.md | 69 -
.../Data Definition/CANCEL BACKUP.md | 39 -
.../Data Definition/CANCEL RESTORE.md | 42 -
.../Data Definition/CREATE DATABASE.md | 69 -
.../Data Definition/CREATE ENCRYPTKEY.md | 80 -
.../sql-statements/Data Definition/CREATE INDEX.md | 45 -
.../Data Definition/CREATE MATERIALIZED VIEW.md | 237 -
.../Data Definition/CREATE REPOSITORY.md | 88 -
.../Data Definition/CREATE RESOURCE.md | 132 -
.../Data Definition/CREATE TABLE LIKE.md | 78 -
.../sql-statements/Data Definition/CREATE TABLE.md | 912 -
.../sql-statements/Data Definition/CREATE VIEW.md | 64 -
.../Data Definition/DROP DATABASE.md | 42 -
.../Data Definition/DROP ENCRYPTKEY.md | 55 -
.../sql-statements/Data Definition/DROP INDEX.md | 37 -
.../Data Definition/DROP MATERIALIZED VIEW.md | 108 -
.../Data Definition/DROP REPOSITORY.md | 42 -
.../Data Definition/DROP RESOURCE.md | 44 -
.../sql-statements/Data Definition/DROP TABLE.md | 46 -
.../sql-statements/Data Definition/DROP VIEW.md | 40 -
.../sql-statements/Data Definition/HLL.md | 109 -
.../sql-statements/Data Definition/RECOVER.md | 54 -
.../Data Definition/REFRESH DATABASE.md | 46 -
.../Data Definition/REFRESH TABLE.md | 46 -
.../sql-statements/Data Definition/RESTORE.md | 88 -
.../Data Definition/SHOW ENCRYPTKEYS.md | 68 -
.../Data Definition/SHOW RESOURCES.md | 66 -
.../Data Definition/TRUNCATE TABLE.md | 53 -
.../Data Definition/create-function.md | 153 -
.../Data Definition/drop-function.md | 56 -
.../Data Definition/show-functions.md | 85 -
.../sql-statements/Data Manipulation/BEGIN.md | 93 -
.../Data Manipulation/BROKER LOAD.md | 603 -
.../Data Manipulation/CANCEL LOAD.md | 46 -
.../Data Manipulation/CREATE SYNC JOB.md | 166 -
.../sql-statements/Data Manipulation/DELETE.md | 66 -
.../sql-statements/Data Manipulation/EXPORT.md | 126 -
.../sql-statements/Data Manipulation/GROUP BY.md | 170 -
.../sql-statements/Data Manipulation/LOAD.md | 298 -
.../sql-statements/Data Manipulation/MINI LOAD.md | 139 -
.../sql-statements/Data Manipulation/MULTI LOAD.md | 108 -
.../Data Manipulation/PAUSE ROUTINE LOAD.md | 40 -
.../Data Manipulation/PAUSE SYNC JOB.md | 43 -
.../Data Manipulation/RESUME ROUTINE LOAD.md | 41 -
.../Data Manipulation/RESUME SYNC JOB.md | 44 -
.../Data Manipulation/ROUTINE LOAD.md | 544 -
.../sql-statements/Data Manipulation/SHOW ALTER.md | 55 -
.../Data Manipulation/SHOW BACKUP.md | 63 -
.../Data Manipulation/SHOW CREATE FUNCTION.md | 43 -
.../Data Manipulation/SHOW CREATE ROUTINE LOAD.md | 44 -
.../Data Manipulation/SHOW DATA SKEW.md | 50 -
.../sql-statements/Data Manipulation/SHOW DATA.md | 113 -
.../Data Manipulation/SHOW DATABASE ID.md | 39 -
.../Data Manipulation/SHOW DATABASES.md | 35 -
.../Data Manipulation/SHOW DELETE.md | 39 -
.../SHOW DYNAMIC PARTITION TABLES.md | 39 -
.../Data Manipulation/SHOW EXPORT.md | 69 -
.../sql-statements/Data Manipulation/SHOW LOAD.md | 75 -
.../Data Manipulation/SHOW PARTITION ID.md | 39 -
.../Data Manipulation/SHOW PARTITIONS.md | 49 -
.../Data Manipulation/SHOW PROPERTY.md | 42 -
.../Data Manipulation/SHOW REPOSITORIES.md | 49 -
.../Data Manipulation/SHOW RESTORE.md | 67 -
.../Data Manipulation/SHOW ROUTINE LOAD TASK.md | 35 -
.../Data Manipulation/SHOW ROUTINE LOAD.md | 108 -
.../Data Manipulation/SHOW SNAPSHOT.md | 57 -
.../Data Manipulation/SHOW STREAM LOAD.md | 69 -
.../Data Manipulation/SHOW SYNC JOB.md | 49 -
.../Data Manipulation/SHOW TABLE CREATION.md | 82 -
.../Data Manipulation/SHOW TABLE ID.md | 39 -
.../Data Manipulation/SHOW TABLES.md | 35 -
.../Data Manipulation/SHOW TABLET.md | 40 -
.../Data Manipulation/SHOW TABLETS.md | 65 -
.../Data Manipulation/SHOW TRANSACTION.md | 101 -
.../Data Manipulation/SHOW-LAST-INSERT.md | 68 -
.../sql-statements/Data Manipulation/SPARK LOAD.md | 265 -
.../Data Manipulation/STOP ROUTINE LOAD.md | 36 -
.../Data Manipulation/STOP SYNC JOB.md | 44 -
.../Data Manipulation/STREAM LOAD.md | 226 -
.../sql-statements/Data Manipulation/UPDATE.md | 75 -
.../Data Manipulation/alter-routine-load.md | 119 -
.../sql-statements/Data Manipulation/insert.md | 111 -
.../Data Manipulation/lateral-view.md | 94 -
.../sql-statements/Utility/DESCRIBE.md | 48 -
{new-docs => docs}/zh-CN/summary/basic-summary.md | 4 +-
.../zh-CN/summary/system-architecture.md | 5 +-
new-docs/.markdownlint.yml | 19 -
new-docs/.vuepress/components/CaseList.vue | 105 -
new-docs/.vuepress/config.js | 130 -
new-docs/.vuepress/sidebar/en.js | 947 -
new-docs/.vuepress/sidebar/zh-CN.js | 947 -
new-docs/.vuepress/theme/components/Footer.vue | 89 -
new-docs/.vuepress/theme/components/Home.vue | 454 -
new-docs/.vuepress/theme/index.js | 21 -
new-docs/.vuepress/theme/layouts/Article.vue | 71 -
new-docs/.vuepress/theme/layouts/ArticleList.vue | 141 -
new-docs/.vuepress/theme/layouts/Layout.vue | 57 -
new-docs/.vuepress/theme/styles/index.styl | 21 -
new-docs/.vuepress/vuepress.textClipping | Bin 199 -> 0 bytes
new-docs/README.md | 255 -
new-docs/build_help_zip.sh | 44 -
new-docs/en/README.md | 95 -
.../en/admin-manual/http-actions/cancel-label.md | 64 -
.../http-actions/check-reset-rpc-cache.md | 47 -
.../admin-manual/http-actions/compaction-action.md | 211 -
.../admin-manual/http-actions/connection-action.md | 42 -
.../admin-manual/http-actions/fe-get-log-file.md | 74 -
.../http-actions/fe/backends-action.md | 70 -
.../http-actions/fe/bootstrap-action.md | 121 -
.../http-actions/fe/cancel-load-action.md | 96 -
.../http-actions/fe/check-decommission-action.md | 84 -
.../http-actions/fe/check-storage-type-action.md | 84 -
.../admin-manual/http-actions/fe/config-action.md | 83 -
.../http-actions/fe/connection-action.md | 82 -
.../http-actions/fe/get-ddl-stmt-action.md | 92 -
.../http-actions/fe/get-load-info-action.md | 95 -
.../admin-manual/http-actions/fe/get-load-state.md | 88 -
.../http-actions/fe/get-log-file-action.md | 113 -
.../admin-manual/http-actions/fe/get-small-file.md | 102 -
.../en/admin-manual/http-actions/fe/ha-action.md | 95 -
.../http-actions/fe/hardware-info-action.md | 79 -
.../admin-manual/http-actions/fe/health-action.md | 61 -
.../en/admin-manual/http-actions/fe/log-action.md | 98 -
.../admin-manual/http-actions/fe/logout-action.md | 59 -
.../http-actions/fe/manager/cluster-action.md | 77 -
.../http-actions/fe/manager/node-action.md | 435 -
.../fe/manager/query-profile-action.md | 308 -
.../en/admin-manual/http-actions/fe/meta-action.md | 64 -
.../http-actions/fe/meta-info-action.md | 232 -
.../http-actions/fe/meta-replay-state-action.md | 61 -
.../admin-manual/http-actions/fe/profile-action.md | 80 -
.../http-actions/fe/query-detail-action.md | 116 -
.../http-actions/fe/query-profile-action.md | 108 -
.../http-actions/fe/row-count-action.md | 84 -
.../admin-manual/http-actions/fe/session-action.md | 75 -
.../http-actions/fe/set-config-action.md | 150 -
.../http-actions/fe/show-data-action.md | 111 -
.../http-actions/fe/show-meta-info-action.md | 138 -
.../http-actions/fe/show-proc-action.md | 104 -
.../http-actions/fe/show-runtime-info-action.md | 84 -
.../http-actions/fe/statement-execution-action.md | 102 -
.../admin-manual/http-actions/fe/system-action.md | 93 -
.../http-actions/fe/table-query-plan-action.md | 113 -
.../http-actions/fe/table-row-count-action.md | 88 -
.../http-actions/fe/table-schema-action.md | 155 -
.../admin-manual/http-actions/fe/upload-action.md | 159 -
.../en/admin-manual/http-actions/get-load-state.md | 59 -
.../en/admin-manual/http-actions/get-tablets.md | 65 -
.../en/admin-manual/http-actions/profile-action.md | 120 -
.../http-actions/query-detail-action.md | 61 -
.../en/admin-manual/http-actions/restore-tablet.md | 41 -
.../admin-manual/http-actions/show-data-action.md | 35 -
.../http-actions/tablet-migration-action.md | 89 -
.../http-actions/tablets_distribution.md | 124 -
.../admin-manual/maint-monitor/doris-error-code.md | 178 -
.../en/admin-manual/maint-monitor/monitor-alert.md | 309 -
.../maint-monitor/monitor-metrics/be-metrics.md | 84 -
.../maint-monitor/monitor-metrics/fe-metrics.md | 155 -
.../en/admin-manual/maint-monitor/multi-tenant.md | 238 -
.../maint-monitor/tablet-restore-tool.md | 136 -
new-docs/en/advanced/orthogonal-bitmap-manual.md | 159 -
.../data-operate/export/export_with_mysql_dump.md | 41 -
new-docs/en/data-table/index/bloomfilter.md | 133 -
new-docs/en/ecosystem/audit-plugin.md | 100 -
new-docs/en/ecosystem/plugin-development-manual.md | 314 -
.../compilation-with-ldb-toolchain.md | 127 -
.../aggregate-functions/approx_count_distinct.md | 49 -
.../sql-functions/aggregate-functions/avg.md | 59 -
.../aggregate-functions/bitmap_union.md | 146 -
.../sql-functions/aggregate-functions/count.md | 61 -
.../aggregate-functions/group_concat.md | 70 -
.../aggregate-functions/hll_union_agg.md | 52 -
.../sql-functions/aggregate-functions/max.md | 46 -
.../sql-functions/aggregate-functions/min.md | 46 -
.../aggregate-functions/percentile.md | 58 -
.../aggregate-functions/percentile_approx.md | 56 -
.../sql-functions/aggregate-functions/stddev.md | 53 -
.../aggregate-functions/stddev_samp.md | 46 -
.../sql-functions/aggregate-functions/sum.md | 46 -
.../sql-functions/aggregate-functions/topn.md | 61 -
.../sql-functions/aggregate-functions/var_samp.md | 46 -
.../sql-functions/aggregate-functions/variance.md | 53 -
.../sql-functions/bitmap-functions/bitmap_and.md | 83 -
.../bitmap-functions/bitmap_and_count.md | 84 -
.../bitmap-functions/bitmap_and_not.md | 48 -
.../bitmap-functions/bitmap_and_not_count.md | 49 -
.../bitmap-functions/bitmap_contains.md | 55 -
.../sql-functions/bitmap-functions/bitmap_empty.md | 52 -
.../bitmap-functions/bitmap_from_string.md | 63 -
.../bitmap-functions/bitmap_has_all.md | 56 -
.../bitmap-functions/bitmap_has_any.md | 55 -
.../sql-functions/bitmap-functions/bitmap_hash.md | 52 -
.../bitmap-functions/bitmap_intersect.md | 61 -
.../sql-functions/bitmap-functions/bitmap_max.md | 55 -
.../sql-functions/bitmap-functions/bitmap_min.md | 55 -
.../sql-functions/bitmap-functions/bitmap_not.md | 55 -
.../sql-functions/bitmap-functions/bitmap_or.md | 83 -
.../bitmap-functions/bitmap_or_count.md | 77 -
.../bitmap-functions/bitmap_subset_in_range.md | 57 -
.../bitmap-functions/bitmap_subset_limit.md | 59 -
.../bitmap-functions/bitmap_to_string.md | 70 -
.../sql-functions/bitmap-functions/bitmap_union.md | 59 -
.../sql-functions/bitmap-functions/bitmap_xor.md | 76 -
.../bitmap-functions/bitmap_xor_count.md | 83 -
.../orthogonal_bitmap_intersect.md | 47 -
.../orthogonal_bitmap_intersect_count.md | 46 -
.../orthogonal_bitmap_union_count.md | 46 -
.../sql-functions/bitmap-functions/sub_bitmap.md | 61 -
.../sql-functions/bitmap-functions/to_bitmap.md | 61 -
.../sql-functions/bitwise-functions/bitand.md | 57 -
.../sql-functions/bitwise-functions/bitnot.md | 57 -
.../sql-functions/bitwise-functions/bitor.md | 57 -
.../sql-functions/bitwise-functions/bitxor.md | 57 -
new-docs/en/sql-manual/sql-functions/cast.md | 83 -
.../sql-functions/conditional-functions/case.md | 72 -
.../conditional-functions/coalesce.md | 47 -
.../sql-functions/conditional-functions/if.md | 50 -
.../sql-functions/conditional-functions/ifnull.md | 54 -
.../sql-functions/conditional-functions/nullif.md | 61 -
.../date-time-functions/convert_tz.md | 55 -
.../sql-functions/date-time-functions/curdate.md | 54 -
.../date-time-functions/current_timestamp.md | 47 -
.../sql-functions/date-time-functions/curtime.md | 48 -
.../sql-functions/date-time-functions/date_add.md | 53 -
.../date-time-functions/date_format.md | 166 -
.../sql-functions/date-time-functions/date_sub.md | 53 -
.../sql-functions/date-time-functions/datediff.md | 59 -
.../sql-functions/date-time-functions/day.md | 49 -
.../sql-functions/date-time-functions/dayname.md | 49 -
.../date-time-functions/dayofmonth.md | 50 -
.../sql-functions/date-time-functions/dayofweek.md | 55 -
.../sql-functions/date-time-functions/dayofyear.md | 50 -
.../sql-functions/date-time-functions/from_days.md | 46 -
.../date-time-functions/from_unixtime.md | 67 -
.../sql-functions/date-time-functions/hour.md | 48 -
.../sql-functions/date-time-functions/makedate.md | 45 -
.../sql-functions/date-time-functions/minute.md | 48 -
.../sql-functions/date-time-functions/month.md | 49 -
.../sql-functions/date-time-functions/monthname.md | 49 -
.../sql-functions/date-time-functions/now.md | 47 -
.../sql-functions/date-time-functions/second.md | 48 -
.../date-time-functions/str_to_date.md | 72 -
.../date-time-functions/time_round.md | 86 -
.../sql-functions/date-time-functions/timediff.md | 65 -
.../date-time-functions/timestampadd.md | 58 -
.../date-time-functions/timestampdiff.md | 67 -
.../sql-functions/date-time-functions/to_date.md | 48 -
.../sql-functions/date-time-functions/to_days.md | 50 -
.../date-time-functions/unix_timestamp.md | 86 -
.../date-time-functions/utc_timestamp.md | 50 -
.../sql-functions/date-time-functions/week.md | 67 -
.../sql-functions/date-time-functions/weekday.md | 66 -
.../date-time-functions/weekofyear.md | 50 -
.../sql-functions/date-time-functions/year.md | 50 -
.../sql-functions/date-time-functions/yearweek.md | 79 -
.../en/sql-manual/sql-functions/digital-masking.md | 56 -
.../hash-functions/murmur_hash3_32.md | 61 -
.../json-functions/get_json_double.md | 74 -
.../sql-functions/json-functions/get_json_int.md | 74 -
.../json-functions/get_json_string.md | 84 -
.../sql-functions/json-functions/json_array.md | 70 -
.../sql-functions/json-functions/json_object.md | 71 -
.../sql-functions/json-functions/json_quote.md | 70 -
.../sql-functions/math-functions/conv.md | 60 -
.../sql-functions/math-functions/pmod.md | 54 -
.../sql-functions/spatial-functions/st_astext.md | 47 -
.../sql-functions/spatial-functions/st_circle.md | 48 -
.../sql-functions/spatial-functions/st_contains.md | 56 -
.../spatial-functions/st_distance_sphere.md | 47 -
.../spatial-functions/st_geometryfromtext.md | 47 -
.../spatial-functions/st_linefromtext.md | 47 -
.../sql-functions/spatial-functions/st_point.md | 48 -
.../sql-functions/spatial-functions/st_polygon.md | 48 -
.../sql-functions/spatial-functions/st_x.md | 47 -
.../sql-functions/spatial-functions/st_y.md | 47 -
.../append_trailing_char_if_absent.md | 60 -
.../sql-functions/string-functions/ascii.md | 54 -
.../sql-functions/string-functions/bit_length.md | 54 -
.../sql-functions/string-functions/char_length.md | 55 -
.../sql-functions/string-functions/concat.md | 61 -
.../sql-functions/string-functions/concat_ws.md | 63 -
.../sql-functions/string-functions/ends_with.md | 54 -
.../sql-functions/string-functions/find_in_set.md | 49 -
.../sql-functions/string-functions/hex.md | 85 -
.../sql-functions/string-functions/instr.md | 54 -
.../sql-functions/string-functions/lcase.md | 37 -
.../sql-functions/string-functions/left.md | 47 -
.../sql-functions/string-functions/length.md | 54 -
.../sql-functions/string-functions/like/like.md | 83 -
.../string-functions/like/not_like.md | 85 -
.../sql-functions/string-functions/locate.md | 61 -
.../sql-functions/string-functions/lower.md | 47 -
.../sql-functions/string-functions/lpad.md | 54 -
.../sql-functions/string-functions/ltrim.md | 47 -
.../sql-functions/string-functions/money_format.md | 61 -
.../string-functions/null_or_empty.md | 60 -
.../string-functions/regexp/not_regexp.md | 56 -
.../string-functions/regexp/regexp.md | 56 -
.../string-functions/regexp/regexp_extract.md | 54 -
.../string-functions/regexp/regexp_replace.md | 54 -
.../sql-functions/string-functions/repeat.md | 54 -
.../sql-functions/string-functions/replace.md | 46 -
.../sql-functions/string-functions/reverse.md | 56 -
.../sql-functions/string-functions/right.md | 47 -
.../sql-functions/string-functions/rpad.md | 54 -
.../sql-functions/string-functions/split_part.md | 69 -
.../sql-functions/string-functions/starts_with.md | 54 -
.../sql-functions/string-functions/strleft.md | 47 -
.../sql-functions/string-functions/strright.md | 48 -
.../sql-functions/string-functions/substring.md | 77 -
.../sql-functions/string-functions/unhex.md | 63 -
.../table-functions/explode-bitmap.md | 157 -
.../table-functions/explode-json-array.md | 286 -
.../sql-functions/table-functions/explode-split.md | 112 -
.../en/sql-manual/sql-functions/window-function.md | 487 -
.../ALTER-SYSTEM-MODIFY-BROKER.md | 38 -
.../sql-reference-v2/Data-Types/BIGINT.md | 33 -
.../sql-reference-v2/Data-Types/BITMAP.md | 48 -
.../sql-reference-v2/Data-Types/BOOLEAN.md | 33 -
.../sql-manual/sql-reference-v2/Data-Types/CHAR.md | 33 -
.../sql-manual/sql-reference-v2/Data-Types/DATE.md | 41 -
.../sql-reference-v2/Data-Types/DATETIME.md | 34 -
.../sql-reference-v2/Data-Types/DECIMAL.md | 34 -
.../sql-reference-v2/Data-Types/DOUBLE.md | 33 -
.../sql-reference-v2/Data-Types/FLOAT.md | 33 -
.../sql-manual/sql-reference-v2/Data-Types/HLL.md | 49 -
.../sql-manual/sql-reference-v2/Data-Types/INT.md | 33 -
.../sql-reference-v2/Data-Types/QUANTILE_STATE.md | 62 -
.../sql-reference-v2/Data-Types/SMALLINT.md | 33 -
.../sql-reference-v2/Data-Types/STRING.md | 35 -
.../sql-reference-v2/Data-Types/TINYINT.md | 33 -
.../sql-reference-v2/Data-Types/VARCHAR.md | 35 -
.../ENABLE-FEATURE.md | 38 -
.../Show-Statements/SHOW-CHARSET.md | 38 -
.../Show-Statements/SHOW-COLLATION.md | 38 -
.../Show-Statements/SHOW-ENGINES.md | 38 -
.../Show-Statements/SHOW-EVENTS.md | 38 -
.../Show-Statements/SHOW-OPEN-TABLES.md | 38 -
.../Show-Statements/SHOW-PROCEDURE.md | 38 -
.../Show-Statements/SHOW-QUERY-PROFILE.md | 38 -
.../Show-Statements/SHOW-ROLLUP.md | 38 -
.../Show-Statements/SHOW-TRIGGERS.md | 38 -
.../sql-reference-v2/Show-Statements/SHOW-USER.md | 38 -
.../Show-Statements/SHOW-WARNING.md | 38 -
.../Show-Statements/SHOW-WHITE-LIST.md | 38 -
new-docs/en/summary/Doris System Architecture.md | 28 -
new-docs/package-lock.json | 28213 -------------------
new-docs/package.json | 38 -
new-docs/zh-CN/README.md | 95 -
.../admin-manual/http-actions/cancel-label.md | 59 -
.../http-actions/check-reset-rpc-cache.md | 46 -
.../admin-manual/http-actions/compaction-action.md | 212 -
.../admin-manual/http-actions/connection-action.md | 42 -
.../admin-manual/http-actions/fe-get-log-file.md | 80 -
.../http-actions/fe/backends-action.md | 70 -
.../http-actions/fe/bootstrap-action.md | 125 -
.../http-actions/fe/cancel-load-action.md | 96 -
.../http-actions/fe/check-decommission-action.md | 84 -
.../http-actions/fe/check-storage-type-action.md | 84 -
.../admin-manual/http-actions/fe/config-action.md | 83 -
.../http-actions/fe/connection-action.md | 82 -
.../http-actions/fe/get-ddl-stmt-action.md | 92 -
.../http-actions/fe/get-load-info-action.md | 95 -
.../admin-manual/http-actions/fe/get-load-state.md | 88 -
.../http-actions/fe/get-log-file-action.md | 112 -
.../admin-manual/http-actions/fe/get-small-file.md | 101 -
.../admin-manual/http-actions/fe/ha-action.md | 95 -
.../http-actions/fe/hardware-info-action.md | 80 -
.../admin-manual/http-actions/fe/health-action.md | 61 -
.../admin-manual/http-actions/fe/log-action.md | 98 -
.../admin-manual/http-actions/fe/logout-action.md | 59 -
.../http-actions/fe/manager/cluster-action.md | 77 -
.../http-actions/fe/manager/node-action.md | 435 -
.../fe/manager/query-profile-action.md | 308 -
.../admin-manual/http-actions/fe/meta-action.md | 60 -
.../http-actions/fe/meta-info-action.md | 232 -
.../http-actions/fe/meta-replay-state-action.md | 61 -
.../admin-manual/http-actions/fe/profile-action.md | 80 -
.../http-actions/fe/query-detail-action.md | 116 -
.../http-actions/fe/query-profile-action.md | 108 -
.../http-actions/fe/row-count-action.md | 84 -
.../admin-manual/http-actions/fe/session-action.md | 75 -
.../http-actions/fe/set-config-action.md | 149 -
.../http-actions/fe/show-data-action.md | 111 -
.../http-actions/fe/show-meta-info-action.md | 138 -
.../http-actions/fe/show-proc-action.md | 104 -
.../http-actions/fe/show-runtime-info-action.md | 84 -
.../http-actions/fe/statement-execution-action.md | 102 -
.../admin-manual/http-actions/fe/system-action.md | 93 -
.../http-actions/fe/table-query-plan-action.md | 113 -
.../http-actions/fe/table-row-count-action.md | 88 -
.../http-actions/fe/table-schema-action.md | 155 -
.../admin-manual/http-actions/fe/upload-action.md | 159 -
.../admin-manual/http-actions/get-load-state.md | 59 -
.../zh-CN/admin-manual/http-actions/get-tablets.md | 65 -
.../admin-manual/http-actions/profile-action.md | 120 -
.../http-actions/query-detail-action.md | 59 -
.../admin-manual/http-actions/restore-tablet.md | 43 -
.../admin-manual/http-actions/show-data-action.md | 35 -
.../http-actions/tablet-migration-action.md | 87 -
.../http-actions/tablets_distribution.md | 124 -
.../admin-manual/maint-monitor/monitor-alert.md | 309 -
.../maint-monitor/monitor-metrics/be-metrics.md | 84 -
.../maint-monitor/monitor-metrics/fe-metrics.md | 155 -
.../admin-manual/maint-monitor/tablet-meta-tool.md | 146 -
.../maint-monitor/tablet-restore-tool.md | 142 -
new-docs/zh-CN/admin-manual/query-profile.md | 27 -
.../aggregate-functions/approx_count_distinct.md | 48 -
.../sql-functions/aggregate-functions/avg.md | 57 -
.../aggregate-functions/bitmap_union.md | 146 -
.../sql-functions/aggregate-functions/count.md | 61 -
.../aggregate-functions/group_concat.md | 70 -
.../aggregate-functions/hll_union_agg.md | 52 -
.../sql-functions/aggregate-functions/max.md | 46 -
.../sql-functions/aggregate-functions/min.md | 46 -
.../aggregate-functions/percentile.md | 57 -
.../aggregate-functions/percentile_approx.md | 59 -
.../sql-functions/aggregate-functions/stddev.md | 53 -
.../aggregate-functions/stddev_samp.md | 46 -
.../sql-functions/aggregate-functions/sum.md | 46 -
.../sql-functions/aggregate-functions/topn.md | 60 -
.../sql-functions/aggregate-functions/var_samp.md | 47 -
.../sql-functions/aggregate-functions/variance.md | 54 -
.../sql-functions/bitmap-functions/bitmap_and.md | 83 -
.../bitmap-functions/bitmap_and_count.md | 84 -
.../bitmap-functions/bitmap_and_not.md | 48 -
.../bitmap-functions/bitmap_and_not_count.md | 48 -
.../bitmap-functions/bitmap_contains.md | 55 -
.../sql-functions/bitmap-functions/bitmap_empty.md | 52 -
.../bitmap-functions/bitmap_from_string.md | 63 -
.../bitmap-functions/bitmap_has_all.md | 56 -
.../bitmap-functions/bitmap_has_any.md | 55 -
.../sql-functions/bitmap-functions/bitmap_hash.md | 52 -
.../bitmap-functions/bitmap_intersect.md | 62 -
.../sql-functions/bitmap-functions/bitmap_max.md | 55 -
.../sql-functions/bitmap-functions/bitmap_min.md | 55 -
.../sql-functions/bitmap-functions/bitmap_not.md | 55 -
.../sql-functions/bitmap-functions/bitmap_or.md | 83 -
.../bitmap-functions/bitmap_or_count.md | 77 -
.../bitmap-functions/bitmap_subset_in_range.md | 57 -
.../bitmap-functions/bitmap_subset_limit.md | 59 -
.../bitmap-functions/bitmap_to_string.md | 69 -
.../sql-functions/bitmap-functions/bitmap_union.md | 59 -
.../sql-functions/bitmap-functions/bitmap_xor.md | 76 -
.../bitmap-functions/bitmap_xor_count.md | 84 -
.../orthogonal_bitmap_intersect.md | 47 -
.../orthogonal_bitmap_intersect_count.md | 46 -
.../orthogonal_bitmap_union_count.md | 47 -
.../sql-functions/bitmap-functions/sub_bitmap.md | 62 -
.../sql-functions/bitmap-functions/to_bitmap.md | 61 -
.../sql-functions/bitwise-functions/bitand.md | 57 -
.../sql-functions/bitwise-functions/bitnot.md | 57 -
.../sql-functions/bitwise-functions/bitor.md | 57 -
.../sql-functions/bitwise-functions/bitxor.md | 57 -
new-docs/zh-CN/sql-manual/sql-functions/cast.md | 82 -
.../sql-functions/conditional-functions/case.md | 72 -
.../conditional-functions/coalesce.md | 47 -
.../sql-functions/conditional-functions/if.md | 50 -
.../sql-functions/conditional-functions/ifnull.md | 54 -
.../sql-functions/conditional-functions/nullif.md | 61 -
.../date-time-functions/convert_tz.md | 55 -
.../sql-functions/date-time-functions/curdate.md | 55 -
.../date-time-functions/current_timestamp.md | 49 -
.../sql-functions/date-time-functions/curtime.md | 50 -
.../sql-functions/date-time-functions/date_add.md | 55 -
.../date-time-functions/date_format.md | 168 -
.../sql-functions/date-time-functions/date_sub.md | 55 -
.../sql-functions/date-time-functions/datediff.md | 58 -
.../sql-functions/date-time-functions/day.md | 49 -
.../sql-functions/date-time-functions/dayname.md | 50 -
.../date-time-functions/dayofmonth.md | 51 -
.../sql-functions/date-time-functions/dayofweek.md | 58 -
.../sql-functions/date-time-functions/dayofyear.md | 51 -
.../sql-functions/date-time-functions/from_days.md | 49 -
.../date-time-functions/from_unixtime.md | 80 -
.../sql-functions/date-time-functions/hour.md | 49 -
.../sql-functions/date-time-functions/makedate.md | 46 -
.../sql-functions/date-time-functions/minute.md | 49 -
.../sql-functions/date-time-functions/month.md | 51 -
.../sql-functions/date-time-functions/monthname.md | 51 -
.../sql-functions/date-time-functions/now.md | 49 -
.../sql-functions/date-time-functions/second.md | 49 -
.../date-time-functions/str_to_date.md | 72 -
.../date-time-functions/time_round.md | 86 -
.../sql-functions/date-time-functions/timediff.md | 65 -
.../date-time-functions/timestampadd.md | 59 -
.../date-time-functions/timestampdiff.md | 67 -
.../sql-functions/date-time-functions/to_date.md | 48 -
.../sql-functions/date-time-functions/to_days.md | 51 -
.../date-time-functions/unix_timestamp.md | 86 -
.../date-time-functions/utc_timestamp.md | 53 -
.../sql-functions/date-time-functions/week.md | 68 -
.../sql-functions/date-time-functions/weekday.md | 68 -
.../date-time-functions/weekofyear.md | 52 -
.../sql-functions/date-time-functions/year.md | 51 -
.../sql-functions/date-time-functions/yearweek.md | 80 -
.../sql-manual/sql-functions/digital-masking.md | 56 -
.../hash-functions/murmur_hash3_32.md | 61 -
.../json-functions/get_json_double.md | 74 -
.../sql-functions/json-functions/get_json_int.md | 74 -
.../json-functions/get_json_string.md | 84 -
.../sql-functions/json-functions/json_array.md | 70 -
.../sql-functions/json-functions/json_object.md | 70 -
.../sql-functions/json-functions/json_quote.md | 70 -
.../sql-functions/math-functions/conv.md | 60 -
.../sql-functions/math-functions/pmod.md | 53 -
.../sql-functions/spatial-functions/st_astext.md | 47 -
.../sql-functions/spatial-functions/st_circle.md | 48 -
.../sql-functions/spatial-functions/st_contains.md | 54 -
.../spatial-functions/st_distance_sphere.md | 47 -
.../spatial-functions/st_geometryfromtext.md | 47 -
.../spatial-functions/st_linefromtext.md | 47 -
.../sql-functions/spatial-functions/st_point.md | 48 -
.../sql-functions/spatial-functions/st_polygon.md | 47 -
.../sql-functions/spatial-functions/st_x.md | 47 -
.../sql-functions/spatial-functions/st_y.md | 47 -
.../append_trailing_char_if_absent.md | 60 -
.../sql-functions/string-functions/ascii.md | 54 -
.../sql-functions/string-functions/bit_length.md | 54 -
.../sql-functions/string-functions/char_length.md | 54 -
.../sql-functions/string-functions/concat.md | 61 -
.../sql-functions/string-functions/concat_ws.md | 63 -
.../sql-functions/string-functions/ends_with.md | 53 -
.../sql-functions/string-functions/find_in_set.md | 47 -
.../sql-functions/string-functions/hex.md | 85 -
.../sql-functions/string-functions/instr.md | 54 -
.../sql-functions/string-functions/lcase.md | 37 -
.../sql-functions/string-functions/left.md | 47 -
.../sql-functions/string-functions/length.md | 54 -
.../sql-functions/string-functions/like/like.md | 83 -
.../string-functions/like/not_like.md | 85 -
.../sql-functions/string-functions/locate.md | 61 -
.../sql-functions/string-functions/lower.md | 47 -
.../sql-functions/string-functions/lpad.md | 54 -
.../sql-functions/string-functions/ltrim.md | 47 -
.../sql-functions/string-functions/money_format.md | 61 -
.../string-functions/null_or_empty.md | 60 -
.../string-functions/regexp/not_regexp.md | 56 -
.../string-functions/regexp/regexp.md | 56 -
.../string-functions/regexp/regexp_extract.md | 51 -
.../string-functions/regexp/regexp_replace.md | 54 -
.../sql-functions/string-functions/repeat.md | 54 -
.../sql-functions/string-functions/replace.md | 46 -
.../sql-functions/string-functions/reverse.md | 56 -
.../sql-functions/string-functions/right.md | 47 -
.../sql-functions/string-functions/rpad.md | 54 -
.../sql-functions/string-functions/split_part.md | 69 -
.../sql-functions/string-functions/starts_with.md | 53 -
.../sql-functions/string-functions/strleft.md | 47 -
.../sql-functions/string-functions/strright.md | 47 -
.../sql-functions/string-functions/substring.md | 72 -
.../sql-functions/string-functions/unhex.md | 63 -
.../table-functions/explode-bitmap.md | 157 -
.../table-functions/explode-json-array.md | 286 -
.../table-functions/explode-numbers.md | 57 -
.../sql-functions/table-functions/explode-split.md | 112 -
.../sql-manual/sql-functions/window-function.md | 487 -
.../ALTER-SYSTEM-MODIFY-BROKER.md | 38 -
.../sql-reference-v2/Data-Types/BIGINT.md | 34 -
.../sql-reference-v2/Data-Types/BITMAP.md | 48 -
.../sql-reference-v2/Data-Types/BOOLEAN.md | 34 -
.../sql-manual/sql-reference-v2/Data-Types/CHAR.md | 34 -
.../sql-manual/sql-reference-v2/Data-Types/DATE.md | 42 -
.../sql-reference-v2/Data-Types/DATETIME.md | 35 -
.../sql-reference-v2/Data-Types/DECIMAL.md | 35 -
.../sql-reference-v2/Data-Types/DOUBLE.md | 34 -
.../sql-reference-v2/Data-Types/FLOAT.md | 34 -
.../sql-manual/sql-reference-v2/Data-Types/HLL.md | 48 -
.../sql-manual/sql-reference-v2/Data-Types/INT.md | 34 -
.../sql-reference-v2/Data-Types/LARGEINT.md | 33 -
.../sql-reference-v2/Data-Types/QUANTILE_STATE.md | 58 -
.../sql-reference-v2/Data-Types/SMALLINT.md | 34 -
.../sql-reference-v2/Data-Types/STRING.md | 36 -
.../sql-reference-v2/Data-Types/TINYINT.md | 34 -
.../sql-reference-v2/Data-Types/VARCHAR.md | 36 -
.../ENABLE-FEATURE.md | 38 -
.../Show-Statements/SHOW-CHARSET.md | 38 -
.../Show-Statements/SHOW-COLLATION.md | 38 -
.../Show-Statements/SHOW-PROCEDURE.md | 38 -
.../Show-Statements/SHOW-QUERY-PROFILE.md | 38 -
.../Show-Statements/SHOW-ROLLUP.md | 38 -
.../Show-Statements/SHOW-TRIGGERS.md | 38 -
.../Show-Statements/SHOW-WARNING.md | 38 -
.../Show-Statements/SHOW-WHITE-LIST.md | 38 -
2222 files changed, 1757 insertions(+), 150909 deletions(-)
diff --git a/docs/.markdownlintignore b/docs/.markdownlintignore
deleted file mode 100644
index 1aea57f9f2..0000000000
--- a/docs/.markdownlintignore
+++ /dev/null
@@ -1,2 +0,0 @@
-node_modules
-.vuepress
diff --git a/docs/.vuepress/sidebar/en.js b/docs/.vuepress/sidebar/en.js
index 5f960c8f3b..46c3afb7a6 100644
--- a/docs/.vuepress/sidebar/en.js
+++ b/docs/.vuepress/sidebar/en.js
@@ -17,7 +17,7 @@
*/
module.exports = [
- {
+ {
title: "Downloads",
directoryPath: "downloads/",
initialOpenGroupIndex: -1,
@@ -25,246 +25,232 @@ module.exports = [
sidebarDepth: 1,
},
{
- title: "Compilation and Deployment",
- directoryPath: "installing/",
+ title: "Getting Started",
+ directoryPath: "get-starting/",
initialOpenGroupIndex: -1,
children: [
- "compilation",
- "compilation-with-ldb-toolchain",
- "compilation-arm",
- "install-deploy",
- "upgrade",
+ "get-starting"
],
},
{
- title: "Getting Started",
- directoryPath: "getting-started/",
+ title: "Doris Architecture",
+ directoryPath: "summary/",
initialOpenGroupIndex: -1,
children: [
- "basic-usage",
- "advance-usage",
- "data-model-rollup",
- "data-partition",
- "hit-the-rollup",
- "best-practice",
+ "basic-summary",
+ "system-architecture"
],
},
{
- title: "Administrator Guide",
- directoryPath: "administrator-guide/",
+ title: "Install and deploy",
+ directoryPath: "install/",
initialOpenGroupIndex: -1,
children: [
+ "install-deploy",
{
- title: "Load Data",
- directoryPath: "load-data/",
+ title: "Compile",
+ directoryPath: "source-install/",
initialOpenGroupIndex: -1,
children: [
- "load-manual",
- "batch-delete-manual",
- "binlog-load-manual",
- "broker-load-manual",
- "routine-load-manual",
- "sequence-column-manual",
- "spark-load-manual",
- "stream-load-manual",
- "s3-load-manual",
- "delete-manual",
- "insert-into-manual",
- "load-json-format",
+ "compilation",
+ "compilation-with-ldb-toolchain",
+ "compilation-arm"
],
sidebarDepth: 2,
},
+ ]
+ },
+ {
+ title: "Table Design",
+ directoryPath: "data-table/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "data-model",
+ "data-partition",
+ "basic-usage",
+ "advance-usage",
+ "hit-the-rollup",
+ "best-practice",
{
- title: "Schema Change",
- directoryPath: "alter-table/",
+ title: "Index",
+ directoryPath: "index/",
initialOpenGroupIndex: -1,
children: [
- "alter-table-bitmap-index",
- "alter-table-replace-table",
- "alter-table-rollup",
- "alter-table-schema-change",
- "alter-table-temp-partition",
+ "bloomfilter",
+ "prefix-index",
+ "bitmap-index"
],
- sidebarDepth: 2,
},
- "materialized_view",
+ ],
+ },
+ {
+ title: "Data Operate",
+ directoryPath: "data-operate/",
+ initialOpenGroupIndex: -1,
+ children: [
{
- title: "HTTP API",
- directoryPath: "http-actions/",
+ title: "Import",
+ directoryPath: "import/",
initialOpenGroupIndex: -1,
children: [
+ "load-manual",
{
- title: "FE",
- directoryPath: "fe/",
+ title: "Import Scenes",
+ directoryPath: "import-scenes/",
initialOpenGroupIndex: -1,
children: [
- {
- title: "MANAGER",
- directoryPath: "manager/",
- initialOpenGroupIndex: -1,
- children: [
- "cluster-action",
- "node-action",
- "query-profile-action",
- ],
- },
- "backends-action",
- "bootstrap-action",
- "cancel-load-action",
- "check-decommission-action",
- "check-storage-type-action",
- "config-action",
- "connection-action",
- "get-ddl-stmt-action",
- "get-load-info-action",
- "get-load-state",
- "get-log-file-action",
- "get-small-file",
- "ha-action",
- "hardware-info-action",
- "health-action",
- "log-action",
- "logout-action",
- "meta-action",
- "meta-info-action",
- "meta-replay-state-action",
- "profile-action",
- "query-detail-action",
- "query-profile-action",
- "row-count-action",
- "session-action",
- "set-config-action",
- "show-data-action",
- "show-meta-info-action",
- "show-proc-action",
- "show-runtime-info-action",
- "statement-execution-action",
- "system-action",
- "table-query-plan-action",
- "table-row-count-action",
- "table-schema-action",
- "upload-action",
+ "local-file-load",
+ "external-storage-load",
+ "kafka-load",
+ "external-table-load",
+ "jdbc-load",
+ "load-atomicity",
+ "load-data-convert",
+ "load-strict-mode",
],
},
- "cancel-label",
- "check-reset-rpc-cache",
- "compaction-action",
- "connection-action",
- "fe-get-log-file",
- "get-load-state",
- "get-tablets",
- "profile-action",
- "query-detail-action",
- "restore-tablet",
- "show-data-action",
- "tablet-migration-action",
- "tablets_distribution",
- ],
- sidebarDepth: 1,
- },
- {
- title: "Maintainence Operation",
- directoryPath: "operation/",
- initialOpenGroupIndex: -1,
- children: [
- "doris-error-code",
- "be-olap-error-code",
- "disk-capacity",
- "metadata-operation",
- "monitor-alert",
- "multi-tenant",
- "tablet-meta-tool",
- "tablet-repair-and-balance",
- "tablet-restore-tool",
{
- title: "Metrics",
- directoryPath: "monitor-metrics/",
+ title: "Import Way",
+ directoryPath: "import-way/",
initialOpenGroupIndex: -1,
children: [
- "be-metrics",
- "fe-metrics",
+ "binlog-load-manual",
+ "broker-load-manual",
+ "routine-load-manual",
+ "spark-load-manual",
+ "stream-load-manual",
+ "s3-load-manual",
+ "insert-into-manual",
+ "load-json-format",
],
- },
+ },
],
- sidebarDepth: 2,
},
{
- title: "Configuration",
- directoryPath: "config/",
+ title: "Export",
+ directoryPath: "export/",
initialOpenGroupIndex: -1,
children: [
- "be_config",
- "fe_config",
- "user_property",
+ "export-manual",
+ "outfile",
+ "export_with_mysql_dump",
],
- sidebarDepth: 1,
},
{
- title: "Block Rule",
- directoryPath: "block-rule/",
+ title: "Update and Delete",
+ directoryPath: "update-delete/",
initialOpenGroupIndex: -1,
children: [
- "sql-block",
+ "update",
+ "sequence-column-manual",
+ "delete-manual",
+ "batch-delete-manual"
],
- sidebarDepth: 1,
},
- "backup-restore",
- "bloomfilter",
- "broker",
- "colocation-join",
- "bucket-shuffle-join",
- "vectorized-execution-engine",
- "dynamic-partition",
- "export-manual",
- "export_with_mysql_dump",
- "outfile",
- "privilege",
- "ldap",
- "resource-management",
- "running-profile",
- "runtime-filter",
- "small-file-mgr",
- "sql-mode",
- "time-zone",
- "variables",
- "update",
- "multi-tenant",
- "orthogonal-bitmap-manual",
],
- sidebarDepth: 1,
},
{
- title: "Benchmark & Sample",
- directoryPath: "benchmark/",
+ title: "Advanced usage",
+ directoryPath: "advanced/",
initialOpenGroupIndex: -1,
children: [
- "star-schema-benchmark",
- "systemd",
- "samples"
+ "materialized-view",
+ {
+ title: "Alter Table",
+ directoryPath: "alter-table/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "schema-change",
+ "replace-table"
+ ],
+ },
+ {
+ title: "Doris Partition",
+ directoryPath: "partition/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "dynamic-partition",
+ "table-temp-partition"
+ ],
+ },
+ {
+ title: "Join Optimization",
+ directoryPath: "join-optimization/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "bucket-shuffle-join",
+ "colocation-join",
+ "runtime-filter"
+ ],
+ },
+ {
+ title: "Date Cache",
+ directoryPath: "cache/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "partition-cache"
+ ],
+ },
+ "vectorized-execution-engine",
+ "broker",
+ "resource",
+ "orthogonal-bitmap-manual",
+ "variables",
+ "time-zone",
+ "small-file-mgr",
+ {
+ title: "Best Practice",
+ directoryPath: "best-practice/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "query-analysis",
+ "import-analysis",
+ "debug-log"
+ ]
+ }
],
},
{
- title: "Extending Ability",
- directoryPath: "extending-doris/",
+ title: "Ecosystem",
+ directoryPath: "ecosystem/",
initialOpenGroupIndex: -1,
children: [
+ {
+ title: "Expansion table",
+ directoryPath: "external-table/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "doris-on-es",
+ "odbc-of-doris",
+ "hive-of-doris",
+ "iceberg-of-doris"
+ ],
+ },
"audit-plugin",
- "doris-on-es",
- "logstash",
- "odbc-of-doris",
- "hive-of-doris",
- "iceberg-of-doris",
- "plugin-development-manual",
- "spark-doris-connector",
"flink-doris-connector",
+ "spark-doris-connector",
"datax",
+ "logstash",
+ {
+ title: "Doris Manager",
+ directoryPath: "doris-manager/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "compiling-deploying",
+ "initializing",
+ "cluster-managenent",
+ "space-list",
+ "space-management",
+ "system-settings"
+ ],
+ },
{
- title: "Seatunnel",
+ title: "SeaTunnel",
directoryPath: "seatunnel/",
initialOpenGroupIndex: -1,
children: [
- "spark-sink",
"flink-sink",
+ "spark-sink"
],
},
{
@@ -272,27 +258,16 @@ module.exports = [
directoryPath: "udf/",
initialOpenGroupIndex: -1,
children: [
- "contribute-udf",
"native-user-defined-function",
"remote-user-defined-function",
- "java-user-defined-function",
+ "contribute-udf"
],
},
],
},
{
- title: "Design Documents",
- directoryPath: "internal/",
- initialOpenGroupIndex: -1,
- children: [
- "doris_storage_optimization",
- "grouping_sets_design",
- "metadata-design",
- ],
- },
- {
- title: "SQL Manual",
- directoryPath: "sql-reference/",
+ title: "SQL manual",
+ directoryPath: "sql-manual/",
initialOpenGroupIndex: -1,
children: [
{
@@ -301,7 +276,7 @@ module.exports = [
initialOpenGroupIndex: -1,
children: [
{
- title: "Date Time Functions",
+ title: "Date Functions",
directoryPath: "date-time-functions/",
initialOpenGroupIndex: -1,
children: [
@@ -343,7 +318,7 @@ module.exports = [
],
},
{
- title: "Sptial Functions",
+ title: "GIS Functions",
directoryPath: "spatial-functions/",
initialOpenGroupIndex: -1,
children: [
@@ -395,7 +370,7 @@ module.exports = [
"substring",
"unhex",
{
- title: "fuzzy match",
+ title: "Fuzzy Match",
directoryPath: "like/",
initialOpenGroupIndex: -1,
children: [
@@ -404,7 +379,7 @@ module.exports = [
],
},
{
- title: "regular match",
+ title: "Regular Match",
directoryPath: "regexp/",
initialOpenGroupIndex: -1,
children: [
@@ -428,7 +403,9 @@ module.exports = [
"group_concat",
"hll_union_agg",
"max",
+ "max_by",
"min",
+ "min_by",
"percentile",
"percentile_approx",
"stddev",
@@ -440,7 +417,7 @@ module.exports = [
],
},
{
- title: "bitmap functions",
+ title: "Bitmap Functions",
directoryPath: "bitmap-functions/",
initialOpenGroupIndex: -1,
children: [
@@ -474,7 +451,7 @@ module.exports = [
],
},
{
- title: "bitwise function",
+ title: "Bitwise Functions",
directoryPath: "bitwise-functions/",
initialOpenGroupIndex: -1,
children: [
@@ -485,7 +462,7 @@ module.exports = [
],
},
{
- title: "conditional function",
+ title: "Condition Functions",
directoryPath: "conditional-functions/",
children: [
"case",
@@ -496,7 +473,7 @@ module.exports = [
],
},
{
- title: "json function",
+ title: "JSON Functions",
directoryPath: "json-functions/",
initialOpenGroupIndex: -1,
children: [
@@ -508,19 +485,6 @@ module.exports = [
"json_quote",
],
},
- {
- title: "Encryption and Digest Functions",
- directoryPath: "encrypt-digest-functions/",
- initialOpenGroupIndex: -1,
- children: [
- "aes",
- "md5",
- "md5sum",
- "sm4",
- "sm3",
- "sm3sum"
- ],
- },
{
title: "Hash Functions",
directoryPath: "hash-functions/",
@@ -537,14 +501,26 @@ module.exports = [
],
},
{
- title: "table functions",
+ title: "Encryption Functions",
+ directoryPath: "encrypt-dixgest-functions/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "aes",
+ "md5",
+ "md5sum",
+ "sm4",
+ "sm3",
+ "sm3sum"
+ ],
+ },
+ {
+ title: "Table Functions",
directoryPath: "table-functions/",
initialOpenGroupIndex: -1,
children: [
"explode-bitmap",
"explode-split",
"explode-json-array",
- "explode-numbers",
"outer-combinator"
],
},
@@ -554,175 +530,244 @@ module.exports = [
],
},
{
- title: "SQL Statements",
- directoryPath: "sql-statements/",
+ title: "SQL Reference",
+ directoryPath: "sql-reference-v2/",
initialOpenGroupIndex: -1,
children: [
{
title: "Account Management",
- directoryPath: "Account Management/",
+ directoryPath: "Account-Management-Statements/",
initialOpenGroupIndex: -1,
children: [
- "CREATE ROLE",
- "CREATE USER",
- "DROP ROLE",
- "DROP USER",
+ "CREATE-USER",
+ "CREATE-ROLE",
+ "DROP-ROLE",
+ "DROP-USER",
"GRANT",
"REVOKE",
- "SET PASSWORD",
- "SET PROPERTY",
- "SHOW GRANTS",
- "SHOW ROLES",
+ "SET-PASSWORD",
+ "SET-PROPERTY",
+ "LDAP",
],
},
{
- title: "Administration",
- directoryPath: "Administration/",
+ title: "Cluster management",
+ directoryPath: "Cluster-Management-Statements/",
initialOpenGroupIndex: -1,
children: [
- "ADMIN CANCEL REBALANCE DISK",
- "ADMIN CANCEL REPAIR",
- "ADMIN CLEAN TRASH",
- "ADMIN CHECK TABLET",
- "ADMIN COMPACT",
- "ADMIN REBALANCE DISK",
- "ADMIN REPAIR",
- "ADMIN SET CONFIG",
- "ADMIN SET REPLICA STATUS",
- "ADMIN SHOW CONFIG",
- "ADMIN SHOW REPLICA DISTRIBUTION",
- "ADMIN SHOW REPLICA STATUS",
- "ADMIN-DIAGNOSE-TABLET",
- "ADMIN SHOW TABLET STORAGE FORMAT",
- "ALTER CLUSTER",
- "ALTER SYSTEM",
- "CANCEL DECOMMISSION",
- "CREATE CLUSTER",
- "CREATE FILE",
- "DROP CLUSTER",
- "DROP FILE",
- "ENTER",
- "INSTALL PLUGIN",
- "LINK DATABASE",
- "MIGRATE DATABASE",
- "SET LDAP_ADMIN_PASSWORD",
- "SHOW BACKENDS",
- "SHOW BROKER",
- "SHOW FILE",
- "SHOW FRONTENDS",
- "SHOW FULL COLUMNS",
- "SHOW INDEX",
- "SHOW MIGRATIONS",
- "SHOW PLUGINS",
- "SHOW TABLE STATUS",
- "SHOW TRASH",
- "UNINSTALL PLUGIN",
+ "ALTER-SYSTEM-ADD-BACKEND",
+ "ALTER-SYSTEM-ADD-FOLLOWER",
+ "ALTER-SYSTEM-ADD-OBSERVER",
+ "ALTER-SYSTEM-DECOMMISSION-BACKEND",
+ "ALTER-SYSTEM-DROP-BACKEND",
+ "ALTER-SYSTEM-DROP-FOLLOWER",
+ "ALTER-SYSTEM-DROP-OBSERVER",
+ "ALTER-SYSTEM-MODIFY-BROKER",
+ "CANCEL-ALTER-SYSTEM",
],
},
{
- title: "Data Definition",
- directoryPath: "Data Definition/",
+ title: "DDL",
+ directoryPath: "Data-Definition-Statements/",
initialOpenGroupIndex: -1,
children: [
- "ALTER DATABASE",
- "ALTER RESOURCE",
- "ALTER TABLE",
- "ALTER VIEW",
- "BACKUP",
- "CANCEL ALTER",
- "CANCEL BACKUP",
- "CREATE ENCRYPTKEY",
- "CANCEL RESTORE",
- "CREATE DATABASE",
- "CREATE INDEX",
- "CREATE MATERIALIZED VIEW",
- "CREATE REPOSITORY",
- "CREATE RESOURCE",
- "CREATE TABLE LIKE",
- "CREATE TABLE",
- "CREATE VIEW",
- "Colocate Join",
- "DROP DATABASE",
- "DROP ENCRYPTKEY",
- "DROP INDEX",
- "DROP MATERIALIZED VIEW",
- "DROP REPOSITORY",
- "DROP RESOURCE",
- "DROP TABLE",
- "DROP VIEW",
- "HLL",
+ {
+ title: "Alter",
+ directoryPath: "Alter/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "ALTER-DATABASE",
+ "ALTER-SQL-BLOCK-RULE",
+ "ALTER-TABLE-COLUMN",
+ "ALTER-TABLE-PARTITION",
+ "ALTER-TABLE-PROPERTY",
+ "ALTER-TABLE-RENAME",
+ "ALTER-TABLE-REPLACE",
+ "ALTER-TABLE-ROLLUP",
+ "ALTER-VIEW",
+ "CANCEL-ALTER-TABLE",
+ ],
+ },
+ {
+ title: "Backup and Restore",
+ directoryPath: "Backup-and-Restore/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "BACKUP",
+ "CANCEL-BACKUP",
+ "CANCEL-RESTORE",
+ "CREATE-REPOSITORY",
+ "DROP-REPOSITORY",
+ "RESTORE",
+ ],
+ },
+ {
+ title: "Create",
+ directoryPath: "Create/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "CREATE-DATABASE",
+ "CREATE-ENCRYPT-KEY",
+ "CREATE-FILE",
+ "CREATE-FUNCTION",
+ "CREATE-INDEX",
+ "CREATE-MATERIALIZED-VIEW",
+ "CREATE-RESOURCE",
+ "CREATE-SQL-BLOCK-RULE",
+ "CREATE-TABLE-LIKE",
+ "CREATE-TABLE",
+ "CREATE-VIEW",
+ "CREATE-EXTERNAL-TABLE",
+ ],
+ },
+ {
+ title: "Drop",
+ directoryPath: "Drop/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "DROP-DATABASE",
+ "DROP-ENCRYPT-KEY",
+ "DROP-FILE",
+ "DROP-FUNCTION",
+ "DROP-INDEX",
+ "DROP-MATERIALIZED-VIEW",
+ "DROP-RESOURCE",
+ "DROP-SQL-BLOCK-RULE",
+ "DROP-TABLE",
+ "TRUNCATE-TABLE",
+ ],
+ },
+ ],
+ },
+ {
+ title: "DML",
+ directoryPath: "Data-Manipulation-Statements/",
+ initialOpenGroupIndex: -1,
+ children: [
+ {
+ title: "Load",
+ directoryPath: "Load/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "ALTER-ROUTINE-LOAD",
+ "BROKER-LOAD",
+ "CANCEL-LOAD",
+ "CREATE-ROUTINE-LOAD",
+ "PAUSE-ROUTINE-LOAD",
+ "RESUME-ROUTINE-LOAD",
+ "STOP-ROUTINE-LOAD",
+ "STREAM-LOAD",
+ "PAUSE-SYNC-JOB",
+ "RESUME-SYNC-JOB",
+ "STOP-SYNC-JOB",
+ "CREATE-SYNC-JOB",
+ ],
+ },
+ {
+ title: "Manipulation",
+ directoryPath: "Manipulation/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "DELETE",
+ "INSERT",
+ "UPDATE",
+ ],
+ },
+ "OUTFILE"
+ ],
+ },
+ {
+ title: "Database Administration",
+ directoryPath: "Database-Administration-Statements/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "ADMIN-CANCEL-REPAIR",
+ "ADMIN-CHECK-TABLET",
+ "ADMIN-REPAIR-TABLE",
+ "ADMIN-SET-CONFIG",
+ "ADMIN-SET-REPLICA-STATUS",
+ "ADMIN-SHOW-CONFIG",
+ "ADMIN-SHOW-REPLICA-DISTRIBUTION",
+ "ADMIN-SHOW-REPLICA-STATUS",
+ "ENABLE-FEATURE",
+ "INSTALL-PLUGIN",
+ "KILL",
"RECOVER",
- "REFRESH DATABASE",
- "REFRESH TABLE",
- "RESTORE",
- "SHOW ENCRYPTKEYS",
- "SHOW RESOURCES",
- "TRUNCATE TABLE",
- "create-function",
- "drop-function",
- "show-functions",
+ "SET-VARIABLE",
+ "UNINSTALL-PLUGIN",
],
},
{
- title: "Data Manipulation",
- directoryPath: "Data Manipulation/",
+ title: "Show",
+ directoryPath: "Show-Statements/",
initialOpenGroupIndex: -1,
children: [
- "BEGIN",
- "BROKER LOAD",
- "CANCEL DELETE",
- "CANCEL LABEL",
- "CANCEL LOAD",
- "CREATE SYNC JOB",
- "DELETE",
- "EXPORT",
- "GET LABEL STATE",
- "GROUP BY",
- "LOAD",
- "MINI LOAD",
- "MULTI LOAD",
- "PAUSE ROUTINE LOAD",
- "PAUSE SYNC JOB",
- "RESTORE TABLET",
- "RESUME ROUTINE LOAD",
- "RESUME SYNC JOB",
- "ROUTINE LOAD",
- "SHOW ALTER",
- "SHOW BACKUP",
- "SHOW CREATE FUNCTION",
- "SHOW CREATE ROUTINE LOAD",
- "SHOW DATA",
- "SHOW DATA SKEW",
- "SHOW DATABASES",
- "SHOW DELETE",
- "SHOW DYNAMIC PARTITION TABLES",
- "SHOW EXPORT",
- "SHOW LOAD",
- "SHOW PARTITIONS",
- "SHOW PROPERTY",
- "SHOW REPOSITORIES",
- "SHOW RESTORE",
- "SHOW ROUTINE LOAD TASK",
- "SHOW ROUTINE LOAD",
- "SHOW SNAPSHOT",
- "SHOW SYNC JOB",
- "SHOW TABLES",
- "SHOW TABLE CREATION",
- "SHOW TABLET",
- "SHOW TRANSACTION",
- "SHOW-LAST-INSERT",
- "STOP ROUTINE LOAD",
- "STOP SYNC JOB",
- "STREAM LOAD",
- "alter-routine-load",
- "insert",
- "UPDATE",
- "lateral-view",
+ "SHOW-ALTER",
+ "SHOW-BACKENDS",
+ "SHOW-BACKUP",
+ "SHOW-BROKER",
+ "SHOW-CHARSET",
+ "SHOW-COLLATION",
+ "SHOW-COLUMNS",
+ "SHOW-CREATE-DATABASE",
+ "SHOW-CREATE-FUNCTION",
+ "SHOW-CREATE-ROUTINE-LOAD",
+ "SHOW-CREATE-TABLE",
+ "SHOW-DATA",
+ "SHOW-DATABASE-ID",
+ "SHOW-DATABASES",
+ "SHOW-DELETE",
+ "SHOW-DYNAMIC-PARTITION",
+ "SHOW-ENCRYPT-KEY",
+ "SHOW-ENGINES",
+ "SHOW-EVENTS",
+ "SHOW-EXPORT",
+ "SHOW-FRONTENDS",
+ "SHOW-FUNCTIONS",
+ "SHOW-GRANTS",
+ "SHOW-INDEX",
+ "SHOW-LOAD-PROFILE",
+ "SHOW-LOAD-WARNINGS",
+ "SHOW-LOAD",
+ "SHOW-MIGRATIONS",
+ "SHOW-OPEN-TABLES",
+ "SHOW-PARTITION-ID",
+ "SHOW-PARTITIONS",
+ "SHOW-PLUGINS",
+ "SHOW-PROC",
+ "SHOW-PROCEDURE",
+ "SHOW-PROCESSLIST",
+ "SHOW-PROPERTY",
+ "SHOW-QUERY-PROFILE",
+ "SHOW-REPOSITORIES",
+ "SHOW-RESOURCES",
+ "SHOW-RESTORE",
+ "SHOW-ROLES",
+ "SHOW-ROLLUP",
+ "SHOW-ROUTINE-LOAD-TASK",
+ "SHOW-ROUTINE-LOAD",
+ "SHOW-SMALL-FILES",
+ "SHOW-SNAPSHOT",
+ "SHOW-SQL-BLOCK-RULE",
+ "SHOW-STATUS",
+ "SHOW-STREAM-LOAD",
+ "SHOW-SYNC-JOB",
+ "SHOW-TABLE-ID",
+ "SHOW-TABLE-STATUS",
+ "SHOW-TABLET",
+ "SHOW-TRANSACTION",
+ "SHOW-TRIGGERS",
+ "SHOW-TRASH",
+ "SHOW-USER",
+ "SHOW-VARIABLES",
+ "SHOW-VIEW",
+ "SHOW-WARNING",
+ "SHOW-WHITE-LIST",
],
},
{
title: "Data Types",
- directoryPath: "Data Types/",
+ directoryPath: "Data-Types/",
initialOpenGroupIndex: -1,
children: [
"BIGINT",
@@ -744,15 +789,186 @@ module.exports = [
},
{
title: "Utility",
- directoryPath: "Utility/",
+ directoryPath: "Utility-Statements/",
initialOpenGroupIndex: -1,
- children: ["util_stmt"],
+ children: [
+ "DESCRIBE",
+ "HELP",
+ "USE",
+ ],
},
],
},
],
},
{
+ title: "Admin Manual",
+ directoryPath: "admin-manual/",
+ initialOpenGroupIndex: -1,
+ children: [
+ {
+ title: "cluster management",
+ directoryPath: "cluster-management/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "upgrade",
+ "elastic-expansion",
+ "load-balancing"
+ ],
+ },
+ {
+ title: "Data Admin",
+ directoryPath: "data-admin/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "backup",
+ "restore",
+ "delete-recover"
+ ],
+ },
+ "sql-interception",
+ "query-profile",
+ "optimization",
+ {
+ title: "Maintenance and Monitor",
+ directoryPath: "maint-monitor/",
+ initialOpenGroupIndex: -1,
+ children: [
+ {
+ title: "Monitor Metrics",
+ directoryPath: "monitor-metrics/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "fe-metrics",
+ "be-metrics"
+ ],
+ },
+ "disk-capacity",
+ "metadata-operation",
+ "tablet-meta-tool",
+ "tablet-repair-and-balance",
+ "tablet-restore-tool",
+ "monitor-alert",
+ "doris-error-code",
+ "be-olap-error-code"
+ ],
+ },
+ {
+ title: "Config",
+ directoryPath: "config/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "fe-config",
+ "be-config",
+ "user-property"
+ ],
+ },
+ {
+ title: "User Privilege and Ldap",
+ directoryPath: "privilege-ldap/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "user-privilege",
+ "ldap"
+ ],
+ },
+ "multi-tenant",
+ {
+ title: "HTTP API",
+ directoryPath: "http-actions/",
+ initialOpenGroupIndex: -1,
+ children: [
+ {
+ title: "FE",
+ directoryPath: "fe/",
+ initialOpenGroupIndex: -1,
+ children: [
+ {
+ title: "MANAGER",
+ directoryPath: "manager/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "cluster-action",
+ "node-action",
+ "query-profile-action",
+ ],
+ },
+ "backends-action",
+ "bootstrap-action",
+ "cancel-load-action",
+ "check-decommission-action",
+ "check-storage-type-action",
+ "config-action",
+ "connection-action",
+ "get-ddl-stmt-action",
+ "get-load-info-action",
+ "get-load-state",
+ "get-log-file-action",
+ "get-small-file",
+ "ha-action",
+ "hardware-info-action",
+ "health-action",
+ "log-action",
+ "logout-action",
+ "meta-action",
+ "meta-info-action",
+ "meta-replay-state-action",
+ "profile-action",
+ "query-detail-action",
+ "query-profile-action",
+ "row-count-action",
+ "session-action",
+ "set-config-action",
+ "show-data-action",
+ "show-meta-info-action",
+ "show-proc-action",
+ "show-runtime-info-action",
+ "statement-execution-action",
+ "system-action",
+ "table-query-plan-action",
+ "table-row-count-action",
+ "table-schema-action",
+ "upload-action",
+ ],
+ },
+ "cancel-label",
+ "check-reset-rpc-cache",
+ "compaction-action",
+ "connection-action",
+ "fe-get-log-file",
+ "get-load-state",
+ "get-tablets",
+ "profile-action",
+ "query-detail-action",
+ "restore-tablet",
+ "show-data-action",
+ "tablet-migration-action",
+ "tablets_distribution",
+ ],
+ sidebarDepth: 1,
+ },
+ ],
+ },
+ {
+ title: "FQA",
+ directoryPath: "faq/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "install-faq",
+ "data-faq",
+ "sql-faq"
+ ],
+ },
+ {
+ title: "Benchmark",
+ directoryPath: "benchmark/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "ssb",
+ "tpc-h"
+ ],
+ },
+ {
title: "Doris User",
directoryPath: "case-user/",
initialOpenGroupIndex: -1,
@@ -780,15 +996,6 @@ module.exports = [
"bitmap-hll-file-format",
],
},
- {
- title: "FAQ",
- directoryPath: "faq/",
- initialOpenGroupIndex: -1,
- children: [
- "faq",
- "error"
- ],
- },
{
title: "Apache Community",
directoryPath: "community/",
@@ -817,6 +1024,7 @@ module.exports = [
"release-prepare",
"release-doris-core",
"release-doris-connectors",
+ "release-doris-manager",
"release-complete",
"release-verify",
],
@@ -824,4 +1032,4 @@ module.exports = [
"security",
],
},
-]
+];
diff --git a/docs/.vuepress/sidebar/zh-CN.js b/docs/.vuepress/sidebar/zh-CN.js
index 324b9a7809..0cbc7b0edb 100644
--- a/docs/.vuepress/sidebar/zh-CN.js
+++ b/docs/.vuepress/sidebar/zh-CN.js
@@ -25,288 +25,249 @@ module.exports = [
sidebarDepth: 1,
},
{
- title: "编译与部署",
- directoryPath: "installing/",
+ title: "快速开始",
+ directoryPath: "get-starting/",
initialOpenGroupIndex: -1,
children: [
- "compilation",
- "compilation-with-ldb-toolchain",
- "compilation-arm",
- "install-deploy",
- "upgrade",
+ "get-starting"
],
},
{
- title: "开始使用",
- directoryPath: "getting-started/",
+ title: "Doris架构",
+ directoryPath: "summary/",
initialOpenGroupIndex: -1,
children: [
- "basic-usage",
- "advance-usage",
- "data-model-rollup",
- "data-partition",
- "hit-the-rollup",
+ "basic-summary",
+ "system-architecture"
],
},
{
- title: "操作手册",
- directoryPath: "administrator-guide/",
+ title: "安装部署",
+ directoryPath: "install/",
initialOpenGroupIndex: -1,
children: [
+ "install-deploy",
{
- title: "数据导入",
- directoryPath: "load-data/",
+ title: "源码编译",
+ directoryPath: "source-install/",
initialOpenGroupIndex: -1,
children: [
- "load-manual",
- "batch-delete-manual",
- "binlog-load-manual",
- "broker-load-manual",
- "routine-load-manual",
- "sequence-column-manual",
- "spark-load-manual",
- "stream-load-manual",
- "s3-load-manual",
- "delete-manual",
- "insert-into-manual",
- "load-json-format",
+ "compilation",
+ "compilation-with-ldb-toolchain",
+ "compilation-arm"
],
sidebarDepth: 2,
},
+ ]
+ },
+ {
+ title: "数据表设计",
+ directoryPath: "data-table/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "data-model",
+ "data-partition",
+ "basic-usage",
+ "advance-usage",
+ "hit-the-rollup",
+ "best-practice",
{
- title: "表结构变更",
- directoryPath: "alter-table/",
+ title: "索引",
+ directoryPath: "index/",
initialOpenGroupIndex: -1,
children: [
- "alter-table-bitmap-index",
- "alter-table-replace-table",
- "alter-table-rollup",
- "alter-table-schema-change",
- "alter-table-temp-partition",
+ "bloomfilter",
+ "prefix-index",
+ "bitmap-index"
],
- sidebarDepth: 2,
},
- "materialized_view",
+ ],
+ },
+ {
+ title: "数据操作",
+ directoryPath: "data-operate/",
+ initialOpenGroupIndex: -1,
+ children: [
{
- title: "HTTP API",
- directoryPath: "http-actions/",
+ title: "数据导入",
+ directoryPath: "import/",
initialOpenGroupIndex: -1,
children: [
+ "load-manual",
{
- title: "FE",
- directoryPath: "fe/",
+ title: "按场景导入",
+ directoryPath: "import-scenes/",
initialOpenGroupIndex: -1,
children: [
- {
- title: "MANAGER",
- directoryPath: "manager/",
- initialOpenGroupIndex: -1,
- children: [
- "cluster-action",
- "node-action",
- "query-profile-action",
- ],
- },
- "backends-action",
- "bootstrap-action",
- "cancel-load-action",
- "check-decommission-action",
- "check-storage-type-action",
- "config-action",
- "connection-action",
- "get-ddl-stmt-action",
- "get-load-info-action",
- "get-load-state",
- "get-log-file-action",
- "get-small-file",
- "ha-action",
- "hardware-info-action",
- "health-action",
- "log-action",
- "logout-action",
- "meta-action",
- "meta-info-action",
- "meta-replay-state-action",
- "profile-action",
- "query-detail-action",
- "query-profile-action",
- "row-count-action",
- "session-action",
- "set-config-action",
- "show-data-action",
- "show-meta-info-action",
- "show-proc-action",
- "show-runtime-info-action",
- "statement-execution-action",
- "system-action",
- "table-query-plan-action",
- "table-row-count-action",
- "table-schema-action",
- "upload-action",
+ "local-file-load",
+ "external-storage-load",
+ "kafka-load",
+ "external-table-load",
+ "jdbc-load",
+ "load-atomicity",
+ "load-data-convert",
+ "load-strict-mode",
],
},
- "cancel-label",
- "check-reset-rpc-cache",
- "compaction-action",
- "connection-action",
- "fe-get-log-file",
- "get-load-state",
- "get-tablets",
- "profile-action",
- "query-detail-action",
- "restore-tablet",
- "show-data-action",
- "tablet-migration-action",
- "tablets_distribution",
- ],
- sidebarDepth: 1,
- },
- {
- title: "运维操作",
- directoryPath: "operation/",
- initialOpenGroupIndex: -1,
- children: [
- "doris-error-code",
- "be-olap-error-code",
- "disk-capacity",
- "metadata-operation",
- "monitor-alert",
- "multi-tenant",
- "tablet-meta-tool",
- "tablet-repair-and-balance",
- "tablet-restore-tool",
{
- title: "监控项",
- directoryPath: "monitor-metrics/",
+ title: "按方式导入",
+ directoryPath: "import-way/",
initialOpenGroupIndex: -1,
children: [
- "be-metrics",
- "fe-metrics",
+ "binlog-load-manual",
+ "broker-load-manual",
+ "routine-load-manual",
+ "spark-load-manual",
+ "stream-load-manual",
+ "s3-load-manual",
+ "insert-into-manual",
+ "load-json-format",
],
- },
+ },
],
- sidebarDepth: 2,
},
{
- title: "配置文件",
- directoryPath: "config/",
+ title: "Export导出",
+ directoryPath: "export/",
initialOpenGroupIndex: -1,
children: [
- "be_config",
- "fe_config",
- "user_property",
+ "export-manual",
+ "outfile",
+ "export_with_mysql_dump",
],
- sidebarDepth: 1,
},
{
- title: "拦截规则",
- directoryPath: "block-rule/",
+ title: "数据更新及删除",
+ directoryPath: "update-delete/",
initialOpenGroupIndex: -1,
children: [
- "sql-block",
+ "update",
+ "sequence-column-manual",
+ "delete-manual",
+ "batch-delete-manual"
],
- sidebarDepth: 1,
},
- "backup-restore",
- "bloomfilter",
- "broker",
- "colocation-join",
- "bucket-shuffle-join",
- "vectorized-execution-engine",
- "dynamic-partition",
- "export-manual",
- "export_with_mysql_dump",
- "outfile",
- "partition_cache",
- "privilege",
- "ldap",
- "resource-management",
- "running-profile",
- "runtime-filter",
- "segment-v2-usage",
- "small-file-mgr",
- "sql-mode",
- "time-zone",
- "variables",
- "update",
- "multi-tenant",
- "orthogonal-bitmap-manual",
],
- sidebarDepth: 1,
},
{
- title: "性能测试及示例",
- directoryPath: "benchmark/",
+ title: "进阶使用",
+ directoryPath: "advanced/",
initialOpenGroupIndex: -1,
children: [
- "star-schema-benchmark",
- "systemd",
- "samples"
+ "materialized-view",
+ {
+ title: "表结构变更",
+ directoryPath: "alter-table/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "schema-change",
+ "replace-table"
+ ],
+ },
+ {
+ title: "Doris表分区",
+ directoryPath: "partition/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "dynamic-partition",
+ "table-tmp-partition"
+ ],
+ },
+ {
+ title: "Join优化",
+ directoryPath: "join-optimization/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "bucket-shuffle-join",
+ "colocation-join",
+ "runtime-filter"
+ ],
+ },
+ {
+ title: "数据缓存",
+ directoryPath: "cache/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "partition-cache"
+ ],
+ },
+ "vectorized-execution-engine",
+ "broker",
+ "resource",
+ "orthogonal-bitmap-manual",
+ "variables",
+ "time-zone",
+ "small-file-mgr",
+ {
+ title: "最佳实践",
+ directoryPath: "best-practice/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "query-analysis",
+ "import-analysis",
+ "debug-log"
+ ],
+ }
],
},
{
- title: "扩展功能",
- directoryPath: "extending-doris/",
+ title: "生态扩展",
+ directoryPath: "ecosystem/",
initialOpenGroupIndex: -1,
children: [
+ {
+ title: "扩展表",
+ directoryPath: "external-table/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "doris-on-es",
+ "odbc-of-doris",
+ "hive-of-doris",
+ "iceberg-of-doris"
+ ],
+ },
"audit-plugin",
- "doris-on-es",
- "logstash",
- "odbc-of-doris",
- "hive-of-doris",
- "iceberg-of-doris",
- "plugin-development-manual",
- "spark-doris-connector",
"flink-doris-connector",
+ "spark-doris-connector",
"datax",
+ "logstash",
{
title: "Doris Manager",
directoryPath: "doris-manager/",
+ initialOpenGroupIndex: -1,
children: [
"compiling-deploying",
"initializing",
- "space-list",
- "system-settings",
"cluster-managenent",
- "space-management"
+ "space-list",
+ "space-management",
+ "system-settings"
],
},
{
- title: "Seatunnel",
+ title: "SeaTunnel",
directoryPath: "seatunnel/",
initialOpenGroupIndex: -1,
children: [
- "spark-sink",
"flink-sink",
+ "spark-sink"
],
},
{
- title: "UDF",
+ title: "自定义函数",
directoryPath: "udf/",
initialOpenGroupIndex: -1,
children: [
- "contribute-udf",
"native-user-defined-function",
"remote-user-defined-function",
- "java-user-defined-function",
+ "contribute-udf"
],
},
],
},
{
- title: "设计文档",
- directoryPath: "internal/",
- initialOpenGroupIndex: -1,
- children: [
- "doris_storage_optimization",
- "grouping_sets_design",
- "metadata-design",
- "spark_load",
- ],
- },
- {
- title: "SQL 手册",
- directoryPath: "sql-reference/",
+ title: "SQL手册",
+ directoryPath: "sql-manual/",
initialOpenGroupIndex: -1,
children: [
{
@@ -442,7 +403,9 @@ module.exports = [
"group_concat",
"hll_union_agg",
"max",
+ "max_by",
"min",
+ "min_by",
"percentile",
"percentile_approx",
"stddev",
@@ -539,7 +502,7 @@ module.exports = [
},
{
title: "加密和信息摘要函数",
- directoryPath: "encrypt-digest-functions/",
+ directoryPath: "encrypt-dixgest-functions/",
initialOpenGroupIndex: -1,
children: [
"aes",
@@ -558,7 +521,6 @@ module.exports = [
"explode-bitmap",
"explode-split",
"explode-json-array",
- "explode-numbers",
"outer-combinator"
],
},
@@ -568,171 +530,244 @@ module.exports = [
],
},
{
- title: "语法帮助",
- directoryPath: "sql-statements/",
+ title: "SQL手册",
+ directoryPath: "sql-reference-v2/",
initialOpenGroupIndex: -1,
children: [
{
- title: "用户账户管理",
- directoryPath: "Account Management/",
+ title: "账户管理",
+ directoryPath: "Account-Management-Statements/",
initialOpenGroupIndex: -1,
children: [
- "CREATE ROLE",
- "CREATE USER",
- "DROP ROLE",
- "DROP USER",
+ "CREATE-USER",
+ "CREATE-ROLE",
+ "DROP-ROLE",
+ "DROP-USER",
"GRANT",
"REVOKE",
- "SET PASSWORD",
- "SET PROPERTY",
- "SHOW GRANTS",
- "SHOW ROLES",
+ "SET-PASSWORD",
+ "SET-PROPERTY",
+ "LDAP",
],
},
{
title: "集群管理",
- directoryPath: "Administration/",
+ directoryPath: "Cluster-Management-Statements/",
initialOpenGroupIndex: -1,
children: [
- "ADMIN CANCEL REBALANCE DISK",
- "ADMIN CANCEL REPAIR",
- "ADMIN CLEAN TRASH",
- "ADMIN CHECK TABLET",
- "ADMIN COMPACT",
- "ADMIN REBALANCE DISK",
- "ADMIN REPAIR",
- "ADMIN SET CONFIG",
- "ADMIN SET REPLICA STATUS",
- "ADMIN SHOW CONFIG",
- "ADMIN SHOW REPLICA DISTRIBUTION",
- "ADMIN SHOW REPLICA STATUS",
- "ADMIN-DIAGNOSE-TABLET",
- "ADMIN SHOW TABLET STORAGE FORMAT",
- "ALTER CLUSTER",
- "ALTER SYSTEM",
- "CANCEL DECOMMISSION",
- "CREATE CLUSTER",
- "CREATE FILE",
- "DROP CLUSTER",
- "DROP FILE",
- "ENTER",
- "INSTALL PLUGIN",
- "LINK DATABASE",
- "MIGRATE DATABASE",
- "SET LDAP_ADMIN_PASSWORD",
- "SHOW BACKENDS",
- "SHOW BROKER",
- "SHOW FILE",
- "SHOW FRONTENDS",
- "SHOW FULL COLUMNS",
- "SHOW INDEX",
- "SHOW MIGRATIONS",
- "SHOW PLUGINS",
- "SHOW TABLE STATUS",
- "SHOW TRASH",
- "UNINSTALL PLUGIN",
+ "ALTER-SYSTEM-ADD-BACKEND",
+ "ALTER-SYSTEM-ADD-FOLLOWER",
+ "ALTER-SYSTEM-ADD-OBSERVER",
+ "ALTER-SYSTEM-DECOMMISSION-BACKEND",
+ "ALTER-SYSTEM-DROP-BACKEND",
+ "ALTER-SYSTEM-DROP-FOLLOWER",
+ "ALTER-SYSTEM-DROP-OBSERVER",
+ "ALTER-SYSTEM-MODIFY-BROKER",
+ "CANCEL-ALTER-SYSTEM",
],
},
{
title: "DDL",
- directoryPath: "Data Definition/",
+ directoryPath: "Data-Definition-Statements/",
initialOpenGroupIndex: -1,
children: [
- "ALTER DATABASE",
- "ALTER RESOURCE",
- "ALTER TABLE",
- "ALTER VIEW",
- "BACKUP",
- "CANCEL ALTER",
- "CANCEL BACKUP",
- "CANCEL RESTORE",
- "CREATE DATABASE",
- "CREATE ENCRYPTKEY",
- "CREATE INDEX",
- "CREATE MATERIALIZED VIEW",
- "CREATE REPOSITORY",
- "CREATE RESOURCE",
- "CREATE TABLE LIKE",
- "CREATE TABLE",
- "CREATE VIEW",
- "DROP DATABASE",
- "DROP ENCRYPTKEY",
- "DROP INDEX",
- "DROP MATERIALIZED VIEW",
- "DROP REPOSITORY",
- "DROP RESOURCE",
- "DROP TABLE",
- "DROP VIEW",
- "HLL",
- "RECOVER",
- "REFRESH DATABASE",
- "REFRESH TABLE",
- "RESTORE",
- "SHOW ENCRYPTKEYS",
- "SHOW RESOURCES",
- "TRUNCATE TABLE",
- "create-function",
- "drop-function",
- "show-functions",
+ {
+ title: "Alter",
+ directoryPath: "Alter/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "ALTER-DATABASE",
+ "ALTER-SQL-BLOCK-RULE",
+ "ALTER-TABLE-COLUMN",
+ "ALTER-TABLE-PARTITION",
+ "ALTER-TABLE-PROPERTY",
+ "ALTER-TABLE-RENAME",
+ "ALTER-TABLE-REPLACE",
+ "ALTER-TABLE-ROLLUP",
+ "ALTER-VIEW",
+ "CANCEL-ALTER-TABLE",
+ ],
+ },
+ {
+ title: "备份及恢复",
+ directoryPath: "Backup-and-Restore/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "BACKUP",
+ "CANCEL-BACKUP",
+ "CANCEL-RESTORE",
+ "CREATE-REPOSITORY",
+ "DROP-REPOSITORY",
+ "RESTORE",
+ ],
+ },
+ {
+ title: "Create",
+ directoryPath: "Create/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "CREATE-DATABASE",
+ "CREATE-ENCRYPT-KEY",
+ "CREATE-FILE",
+ "CREATE-FUNCTION",
+ "CREATE-INDEX",
+ "CREATE-MATERIALIZED-VIEW",
+ "CREATE-RESOURCE",
+ "CREATE-SQL-BLOCK-RULE",
+ "CREATE-TABLE-LIKE",
+ "CREATE-TABLE",
+ "CREATE-VIEW",
+ "CREATE-EXTERNAL-TABLE",
+ ],
+ },
+ {
+ title: "Drop",
+ directoryPath: "Drop/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "DROP-DATABASE",
+ "DROP-ENCRYPT-KEY",
+ "DROP-FILE",
+ "DROP-FUNCTION",
+ "DROP-INDEX",
+ "DROP-MATERIALIZED-VIEW",
+ "DROP-RESOURCE",
+ "DROP-SQL-BLOCK-RULE",
+ "DROP-TABLE",
+ "TRUNCATE-TABLE",
+ ],
+ },
],
},
{
title: "DML",
- directoryPath: "Data Manipulation/",
+ directoryPath: "Data-Manipulation-Statements/",
+ initialOpenGroupIndex: -1,
+ children: [
+ {
+ title: "Load",
+ directoryPath: "Load/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "ALTER-ROUTINE-LOAD",
+ "BROKER-LOAD",
+ "CANCEL-LOAD",
+ "CREATE-ROUTINE-LOAD",
+ "PAUSE-ROUTINE-LOAD",
+ "RESUME-ROUTINE-LOAD",
+ "STOP-ROUTINE-LOAD",
+ "STREAM-LOAD",
+ "PAUSE-SYNC-JOB",
+ "RESUME-SYNC-JOB",
+ "STOP-SYNC-JOB",
+ "CREATE-SYNC-JOB",
+ ],
+ },
+ {
+ title: "操作",
+ directoryPath: "Manipulation/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "DELETE",
+ "INSERT",
+ "UPDATE",
+ ],
+ },
+ "OUTFILE"
+ ],
+ },
+ {
+ title: "数据库管理",
+ directoryPath: "Database-Administration-Statements/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "ADMIN-CANCEL-REPAIR",
+ "ADMIN-CHECK-TABLET",
+ "ADMIN-REPAIR-TABLE",
+ "ADMIN-SET-CONFIG",
+ "ADMIN-SET-REPLICA-STATUS",
+ "ADMIN-SHOW-CONFIG",
+ "ADMIN-SHOW-REPLICA-DISTRIBUTION",
+ "ADMIN-SHOW-REPLICA-STATUS",
+ "ENABLE-FEATURE",
+ "INSTALL-PLUGIN",
+ "KILL",
+ "RECOVER",
+ "SET-VARIABLE",
+ "UNINSTALL-PLUGIN",
+ ],
+ },
+ {
+ title: "Show",
+ directoryPath: "Show-Statements/",
initialOpenGroupIndex: -1,
children: [
- "BEGIN",
- "BROKER LOAD",
- "CANCEL LOAD",
- "CREATE SYNC JOB",
- "DELETE",
- "EXPORT",
- "GROUP BY",
- "LOAD",
- "MINI LOAD",
- "MULTI LOAD",
- "PAUSE ROUTINE LOAD",
- "PAUSE SYNC JOB",
- "RESUME ROUTINE LOAD",
- "RESUME SYNC JOB",
- "ROUTINE LOAD",
- "SHOW ALTER",
- "SHOW BACKUP",
- "SHOW CREATE FUNCTION",
- "SHOW CREATE ROUTINE LOAD",
- "SHOW DATA",
- "SHOW DATA SKEW",
- "SHOW DATABASES",
- "SHOW DELETE",
- "SHOW DYNAMIC PARTITION TABLES",
- "SHOW EXPORT",
- "SHOW LOAD",
- "SHOW PARTITIONS",
- "SHOW PROPERTY",
- "SHOW REPOSITORIES",
- "SHOW RESTORE",
- "SHOW ROUTINE LOAD TASK",
- "SHOW ROUTINE LOAD",
- "SHOW SNAPSHOT",
- "SHOW SYNC JOB",
- "SHOW TABLES",
- "SHOW TABLE CREATION",
- "SHOW TABLET",
- "SHOW TRANSACTION",
- "SHOW-LAST-INSERT",
- "SPARK LOAD",
- "STOP ROUTINE LOAD",
- "STOP SYNC JOB",
- "STREAM LOAD",
- "alter-routine-load",
- "insert",
- "UPDATE",
- "lateral-view",
+ "SHOW-ALTER",
+ "SHOW-BACKENDS",
+ "SHOW-BACKUP",
+ "SHOW-BROKER",
+ "SHOW-CHARSET",
+ "SHOW-COLLATION",
+ "SHOW-COLUMNS",
+ "SHOW-CREATE-DATABASE",
+ "SHOW-CREATE-FUNCTION",
+ "SHOW-CREATE-ROUTINE-LOAD",
+ "SHOW-CREATE-TABLE",
+ "SHOW-DATA",
+ "SHOW-DATABASE-ID",
+ "SHOW-DATABASES",
+ "SHOW-DELETE",
+ "SHOW-DYNAMIC-PARTITION",
+ "SHOW-ENCRYPT-KEY",
+ "SHOW-ENGINES",
+ "SHOW-EVENTS",
+ "SHOW-EXPORT",
+ "SHOW-FRONTENDS",
+ "SHOW-FUNCTIONS",
+ "SHOW-GRANTS",
+ "SHOW-INDEX",
+ "SHOW-LOAD-PROFILE",
+ "SHOW-LOAD-WARNINGS",
+ "SHOW-LOAD",
+ "SHOW-MIGRATIONS",
+ "SHOW-OPEN-TABLES",
+ "SHOW-PARTITION-ID",
+ "SHOW-PARTITIONS",
+ "SHOW-PLUGINS",
+ "SHOW-PROC",
+ "SHOW-PROCEDURE",
+ "SHOW-PROCESSLIST",
+ "SHOW-PROPERTY",
+ "SHOW-QUERY-PROFILE",
+ "SHOW-REPOSITORIES",
+ "SHOW-RESOURCES",
+ "SHOW-RESTORE",
+ "SHOW-ROLES",
+ "SHOW-ROLLUP",
+ "SHOW-ROUTINE-LOAD-TASK",
+ "SHOW-ROUTINE-LOAD",
+ "SHOW-SMALL-FILES",
+ "SHOW-SNAPSHOT",
+ "SHOW-SQL-BLOCK-RULE",
+ "SHOW-STATUS",
+ "SHOW-STREAM-LOAD",
+ "SHOW-SYNC-JOB",
+ "SHOW-TABLE-ID",
+ "SHOW-TABLE-STATUS",
+ "SHOW-TABLET",
+ "SHOW-TRANSACTION",
+ "SHOW-TRIGGERS",
+ "SHOW-TRASH",
+ "SHOW-USER",
+ "SHOW-VARIABLES",
+ "SHOW-VIEW",
+ "SHOW-WARNING",
+ "SHOW-WHITE-LIST",
],
},
{
title: "数据类型",
- directoryPath: "Data Types/",
+ directoryPath: "Data-Types/",
initialOpenGroupIndex: -1,
children: [
"BIGINT",
@@ -746,7 +781,6 @@ module.exports = [
"FLOAT",
"HLL",
"INT",
- "LARGEINT",
"SMALLINT",
"STRING",
"TINYINT",
@@ -755,14 +789,185 @@ module.exports = [
},
{
title: "辅助命令",
- directoryPath: "Utility/",
+ directoryPath: "Utility-Statements/",
initialOpenGroupIndex: -1,
- children: ["DESCRIBE"],
+ children: [
+ "DESCRIBE",
+ "HELP",
+ "USE"
+ ],
},
],
},
],
},
+ {
+ title: "管理手册",
+ directoryPath: "admin-manual/",
+ initialOpenGroupIndex: -1,
+ children: [
+ {
+ title: "集群管理",
+ directoryPath: "cluster-management/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "upgrade",
+ "elastic-expansion",
+ "load-balancing"
+ ],
+ },
+ {
+ title: "数据管理",
+ directoryPath: "data-admin/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "backup",
+ "restore",
+ "delete-recover"
+ ],
+ },
+ "sql-interception",
+ "query-profile",
+ "optimization",
+ {
+ title: "运维监控",
+ directoryPath: "maint-monitor/",
+ initialOpenGroupIndex: -1,
+ children: [
+ {
+ title: "监控指标",
+ directoryPath: "monitor-metrics/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "fe-metrics",
+ "be-metrics"
+ ],
+ },
+ "disk-capacity",
+ "metadata-operation",
+ "tablet-meta-tool",
+ "tablet-repair-and-balance",
+ "tablet-restore-tool",
+ "monitor-alert",
+ "doris-error-code",
+ "be-olap-error-code"
+ ],
+ },
+ {
+ title: "配置管理",
+ directoryPath: "config/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "fe-config",
+ "be-config",
+ "user-property"
+ ],
+ },
+ {
+ title: "用户权限及认证",
+ directoryPath: "privilege-ldap/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "user-privilege",
+ "ldap"
+ ],
+ },
+ "multi-tenant",
+ {
+ title: "HTTP API",
+ directoryPath: "http-actions/",
+ initialOpenGroupIndex: -1,
+ children: [
+ {
+ title: "FE",
+ directoryPath: "fe/",
+ initialOpenGroupIndex: -1,
+ children: [
+ {
+ title: "MANAGER",
+ directoryPath: "manager/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "cluster-action",
+ "node-action",
+ "query-profile-action",
+ ],
+ },
+ "backends-action",
+ "bootstrap-action",
+ "cancel-load-action",
+ "check-decommission-action",
+ "check-storage-type-action",
+ "config-action",
+ "connection-action",
+ "get-ddl-stmt-action",
+ "get-load-info-action",
+ "get-load-state",
+ "get-log-file-action",
+ "get-small-file",
+ "ha-action",
+ "hardware-info-action",
+ "health-action",
+ "log-action",
+ "logout-action",
+ "meta-action",
+ "meta-info-action",
+ "meta-replay-state-action",
+ "profile-action",
+ "query-detail-action",
+ "query-profile-action",
+ "row-count-action",
+ "session-action",
+ "set-config-action",
+ "show-data-action",
+ "show-meta-info-action",
+ "show-proc-action",
+ "show-runtime-info-action",
+ "statement-execution-action",
+ "system-action",
+ "table-query-plan-action",
+ "table-row-count-action",
+ "table-schema-action",
+ "upload-action",
+ ],
+ },
+ "cancel-label",
+ "check-reset-rpc-cache",
+ "compaction-action",
+ "connection-action",
+ "fe-get-log-file",
+ "get-load-state",
+ "get-tablets",
+ "profile-action",
+ "query-detail-action",
+ "restore-tablet",
+ "show-data-action",
+ "tablet-migration-action",
+ "tablets_distribution",
+ ],
+ sidebarDepth: 1,
+ },
+ ],
+ },
+ {
+ title: "常见问题",
+ directoryPath: "faq/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "install-faq",
+ "data-faq",
+ "sql-faq"
+ ],
+ },
+ {
+ title: "性能测试",
+ directoryPath: "benchmark/",
+ initialOpenGroupIndex: -1,
+ children: [
+ "ssb",
+ "tpc-h"
+ ],
+ },
{
title: "Doris用户",
directoryPath: "case-user/",
@@ -792,15 +997,6 @@ module.exports = [
"regression-testing",
],
},
- {
- title: "FAQ 常见问题",
- directoryPath: "faq/",
- initialOpenGroupIndex: -1,
- children: [
- "faq",
- "error"
- ],
- },
{
title: "Apache 社区",
directoryPath: "community/",
@@ -829,6 +1025,7 @@ module.exports = [
"release-prepare",
"release-doris-core",
"release-doris-connectors",
+ "release-doris-manager",
"release-complete",
"release-verify",
],
diff --git a/docs/en/README.md b/docs/en/README.md
index 40040ee870..d5ddba4ad6 100644
--- a/docs/en/README.md
+++ b/docs/en/README.md
@@ -89,7 +89,7 @@ cases:
- logo: /images/home/logo-youdao.png
alt: 有道
actionText: Quick Start →
-actionLink: /en/installing/compilation
+actionLink: /en/get-starting/get-starting
articleText: Latest News
articleLink: /en/article/article-list
---
diff --git a/new-docs/en/admin-manual/cluster-management/elastic-expansion.md b/docs/en/admin-manual/cluster-management/elastic-expansion.md
similarity index 100%
rename from new-docs/en/admin-manual/cluster-management/elastic-expansion.md
rename to docs/en/admin-manual/cluster-management/elastic-expansion.md
diff --git a/new-docs/en/admin-manual/cluster-management/load-balancing.md b/docs/en/admin-manual/cluster-management/load-balancing.md
similarity index 100%
rename from new-docs/en/admin-manual/cluster-management/load-balancing.md
rename to docs/en/admin-manual/cluster-management/load-balancing.md
diff --git a/new-docs/en/admin-manual/cluster-management/upgrade.md b/docs/en/admin-manual/cluster-management/upgrade.md
similarity index 100%
rename from new-docs/en/admin-manual/cluster-management/upgrade.md
rename to docs/en/admin-manual/cluster-management/upgrade.md
diff --git a/new-docs/en/admin-manual/config/be-config.md b/docs/en/admin-manual/config/be-config.md
similarity index 100%
rename from new-docs/en/admin-manual/config/be-config.md
rename to docs/en/admin-manual/config/be-config.md
diff --git a/new-docs/en/admin-manual/config/fe-config.md b/docs/en/admin-manual/config/fe-config.md
similarity index 100%
rename from new-docs/en/admin-manual/config/fe-config.md
rename to docs/en/admin-manual/config/fe-config.md
diff --git a/new-docs/en/admin-manual/config/user-property.md b/docs/en/admin-manual/config/user-property.md
similarity index 100%
rename from new-docs/en/admin-manual/config/user-property.md
rename to docs/en/admin-manual/config/user-property.md
diff --git a/new-docs/en/admin-manual/data-admin/backup.md b/docs/en/admin-manual/data-admin/backup.md
similarity index 100%
rename from new-docs/en/admin-manual/data-admin/backup.md
rename to docs/en/admin-manual/data-admin/backup.md
diff --git a/new-docs/en/admin-manual/data-admin/delete-recover.md b/docs/en/admin-manual/data-admin/delete-recover.md
similarity index 100%
rename from new-docs/en/admin-manual/data-admin/delete-recover.md
rename to docs/en/admin-manual/data-admin/delete-recover.md
diff --git a/new-docs/en/admin-manual/data-admin/restore.md b/docs/en/admin-manual/data-admin/restore.md
similarity index 100%
rename from new-docs/en/admin-manual/data-admin/restore.md
rename to docs/en/admin-manual/data-admin/restore.md
diff --git a/docs/en/administrator-guide/http-actions/cancel-label.md b/docs/en/admin-manual/http-actions/cancel-label.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/cancel-label.md
rename to docs/en/admin-manual/http-actions/cancel-label.md
diff --git a/docs/en/administrator-guide/http-actions/check-reset-rpc-cache.md b/docs/en/admin-manual/http-actions/check-reset-rpc-cache.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/check-reset-rpc-cache.md
rename to docs/en/admin-manual/http-actions/check-reset-rpc-cache.md
diff --git a/docs/en/administrator-guide/http-actions/compaction-action.md b/docs/en/admin-manual/http-actions/compaction-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/compaction-action.md
rename to docs/en/admin-manual/http-actions/compaction-action.md
diff --git a/docs/en/administrator-guide/http-actions/connection-action.md b/docs/en/admin-manual/http-actions/connection-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/connection-action.md
rename to docs/en/admin-manual/http-actions/connection-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe-get-log-file.md b/docs/en/admin-manual/http-actions/fe-get-log-file.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe-get-log-file.md
rename to docs/en/admin-manual/http-actions/fe-get-log-file.md
diff --git a/docs/en/administrator-guide/http-actions/fe/backends-action.md b/docs/en/admin-manual/http-actions/fe/backends-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/backends-action.md
rename to docs/en/admin-manual/http-actions/fe/backends-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/bootstrap-action.md b/docs/en/admin-manual/http-actions/fe/bootstrap-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/bootstrap-action.md
rename to docs/en/admin-manual/http-actions/fe/bootstrap-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/cancel-load-action.md b/docs/en/admin-manual/http-actions/fe/cancel-load-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/cancel-load-action.md
rename to docs/en/admin-manual/http-actions/fe/cancel-load-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/check-decommission-action.md b/docs/en/admin-manual/http-actions/fe/check-decommission-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/check-decommission-action.md
rename to docs/en/admin-manual/http-actions/fe/check-decommission-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/check-storage-type-action.md b/docs/en/admin-manual/http-actions/fe/check-storage-type-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/check-storage-type-action.md
rename to docs/en/admin-manual/http-actions/fe/check-storage-type-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/config-action.md b/docs/en/admin-manual/http-actions/fe/config-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/config-action.md
rename to docs/en/admin-manual/http-actions/fe/config-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/connection-action.md b/docs/en/admin-manual/http-actions/fe/connection-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/connection-action.md
rename to docs/en/admin-manual/http-actions/fe/connection-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/get-ddl-stmt-action.md b/docs/en/admin-manual/http-actions/fe/get-ddl-stmt-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/get-ddl-stmt-action.md
rename to docs/en/admin-manual/http-actions/fe/get-ddl-stmt-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/get-load-info-action.md b/docs/en/admin-manual/http-actions/fe/get-load-info-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/get-load-info-action.md
rename to docs/en/admin-manual/http-actions/fe/get-load-info-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/get-load-state.md b/docs/en/admin-manual/http-actions/fe/get-load-state.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/get-load-state.md
rename to docs/en/admin-manual/http-actions/fe/get-load-state.md
diff --git a/docs/en/administrator-guide/http-actions/fe/get-log-file-action.md b/docs/en/admin-manual/http-actions/fe/get-log-file-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/get-log-file-action.md
rename to docs/en/admin-manual/http-actions/fe/get-log-file-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/get-small-file.md b/docs/en/admin-manual/http-actions/fe/get-small-file.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/get-small-file.md
rename to docs/en/admin-manual/http-actions/fe/get-small-file.md
diff --git a/docs/en/administrator-guide/http-actions/fe/ha-action.md b/docs/en/admin-manual/http-actions/fe/ha-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/ha-action.md
rename to docs/en/admin-manual/http-actions/fe/ha-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/hardware-info-action.md b/docs/en/admin-manual/http-actions/fe/hardware-info-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/hardware-info-action.md
rename to docs/en/admin-manual/http-actions/fe/hardware-info-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/health-action.md b/docs/en/admin-manual/http-actions/fe/health-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/health-action.md
rename to docs/en/admin-manual/http-actions/fe/health-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/log-action.md b/docs/en/admin-manual/http-actions/fe/log-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/log-action.md
rename to docs/en/admin-manual/http-actions/fe/log-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/logout-action.md b/docs/en/admin-manual/http-actions/fe/logout-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/logout-action.md
rename to docs/en/admin-manual/http-actions/fe/logout-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/manager/cluster-action.md b/docs/en/admin-manual/http-actions/fe/manager/cluster-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/manager/cluster-action.md
rename to docs/en/admin-manual/http-actions/fe/manager/cluster-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/manager/node-action.md b/docs/en/admin-manual/http-actions/fe/manager/node-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/manager/node-action.md
rename to docs/en/admin-manual/http-actions/fe/manager/node-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/manager/query-profile-action.md b/docs/en/admin-manual/http-actions/fe/manager/query-profile-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/manager/query-profile-action.md
rename to docs/en/admin-manual/http-actions/fe/manager/query-profile-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/meta-action.md b/docs/en/admin-manual/http-actions/fe/meta-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/meta-action.md
rename to docs/en/admin-manual/http-actions/fe/meta-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/meta-info-action.md b/docs/en/admin-manual/http-actions/fe/meta-info-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/meta-info-action.md
rename to docs/en/admin-manual/http-actions/fe/meta-info-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/meta-replay-state-action.md b/docs/en/admin-manual/http-actions/fe/meta-replay-state-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/meta-replay-state-action.md
rename to docs/en/admin-manual/http-actions/fe/meta-replay-state-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/profile-action.md b/docs/en/admin-manual/http-actions/fe/profile-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/profile-action.md
rename to docs/en/admin-manual/http-actions/fe/profile-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/query-detail-action.md b/docs/en/admin-manual/http-actions/fe/query-detail-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/query-detail-action.md
rename to docs/en/admin-manual/http-actions/fe/query-detail-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/query-profile-action.md b/docs/en/admin-manual/http-actions/fe/query-profile-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/query-profile-action.md
rename to docs/en/admin-manual/http-actions/fe/query-profile-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/row-count-action.md b/docs/en/admin-manual/http-actions/fe/row-count-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/row-count-action.md
rename to docs/en/admin-manual/http-actions/fe/row-count-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/session-action.md b/docs/en/admin-manual/http-actions/fe/session-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/session-action.md
rename to docs/en/admin-manual/http-actions/fe/session-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/set-config-action.md b/docs/en/admin-manual/http-actions/fe/set-config-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/set-config-action.md
rename to docs/en/admin-manual/http-actions/fe/set-config-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/show-data-action.md b/docs/en/admin-manual/http-actions/fe/show-data-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/show-data-action.md
rename to docs/en/admin-manual/http-actions/fe/show-data-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/show-meta-info-action.md b/docs/en/admin-manual/http-actions/fe/show-meta-info-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/show-meta-info-action.md
rename to docs/en/admin-manual/http-actions/fe/show-meta-info-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/show-proc-action.md b/docs/en/admin-manual/http-actions/fe/show-proc-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/show-proc-action.md
rename to docs/en/admin-manual/http-actions/fe/show-proc-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/show-runtime-info-action.md b/docs/en/admin-manual/http-actions/fe/show-runtime-info-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/show-runtime-info-action.md
rename to docs/en/admin-manual/http-actions/fe/show-runtime-info-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/statement-execution-action.md b/docs/en/admin-manual/http-actions/fe/statement-execution-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/statement-execution-action.md
rename to docs/en/admin-manual/http-actions/fe/statement-execution-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/system-action.md b/docs/en/admin-manual/http-actions/fe/system-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/system-action.md
rename to docs/en/admin-manual/http-actions/fe/system-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/table-query-plan-action.md b/docs/en/admin-manual/http-actions/fe/table-query-plan-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/table-query-plan-action.md
rename to docs/en/admin-manual/http-actions/fe/table-query-plan-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/table-row-count-action.md b/docs/en/admin-manual/http-actions/fe/table-row-count-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/table-row-count-action.md
rename to docs/en/admin-manual/http-actions/fe/table-row-count-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/table-schema-action.md b/docs/en/admin-manual/http-actions/fe/table-schema-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/table-schema-action.md
rename to docs/en/admin-manual/http-actions/fe/table-schema-action.md
diff --git a/docs/en/administrator-guide/http-actions/fe/upload-action.md b/docs/en/admin-manual/http-actions/fe/upload-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/fe/upload-action.md
rename to docs/en/admin-manual/http-actions/fe/upload-action.md
diff --git a/docs/en/administrator-guide/http-actions/get-load-state.md b/docs/en/admin-manual/http-actions/get-load-state.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/get-load-state.md
rename to docs/en/admin-manual/http-actions/get-load-state.md
diff --git a/docs/en/administrator-guide/http-actions/get-tablets.md b/docs/en/admin-manual/http-actions/get-tablets.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/get-tablets.md
rename to docs/en/admin-manual/http-actions/get-tablets.md
diff --git a/docs/en/administrator-guide/http-actions/profile-action.md b/docs/en/admin-manual/http-actions/profile-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/profile-action.md
rename to docs/en/admin-manual/http-actions/profile-action.md
diff --git a/docs/en/administrator-guide/http-actions/query-detail-action.md b/docs/en/admin-manual/http-actions/query-detail-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/query-detail-action.md
rename to docs/en/admin-manual/http-actions/query-detail-action.md
diff --git a/docs/en/administrator-guide/http-actions/restore-tablet.md b/docs/en/admin-manual/http-actions/restore-tablet.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/restore-tablet.md
rename to docs/en/admin-manual/http-actions/restore-tablet.md
diff --git a/docs/en/administrator-guide/http-actions/show-data-action.md b/docs/en/admin-manual/http-actions/show-data-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/show-data-action.md
rename to docs/en/admin-manual/http-actions/show-data-action.md
diff --git a/docs/en/administrator-guide/http-actions/tablet-migration-action.md b/docs/en/admin-manual/http-actions/tablet-migration-action.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/tablet-migration-action.md
rename to docs/en/admin-manual/http-actions/tablet-migration-action.md
diff --git a/docs/en/administrator-guide/http-actions/tablets_distribution.md b/docs/en/admin-manual/http-actions/tablets_distribution.md
similarity index 100%
rename from docs/en/administrator-guide/http-actions/tablets_distribution.md
rename to docs/en/admin-manual/http-actions/tablets_distribution.md
diff --git a/new-docs/en/admin-manual/maint-monitor/be-olap-error-code.md b/docs/en/admin-manual/maint-monitor/be-olap-error-code.md
similarity index 100%
rename from new-docs/en/admin-manual/maint-monitor/be-olap-error-code.md
rename to docs/en/admin-manual/maint-monitor/be-olap-error-code.md
diff --git a/new-docs/en/admin-manual/maint-monitor/disk-capacity.md b/docs/en/admin-manual/maint-monitor/disk-capacity.md
similarity index 100%
rename from new-docs/en/admin-manual/maint-monitor/disk-capacity.md
rename to docs/en/admin-manual/maint-monitor/disk-capacity.md
diff --git a/docs/en/administrator-guide/operation/doris-error-code.md b/docs/en/admin-manual/maint-monitor/doris-error-code.md
similarity index 100%
rename from docs/en/administrator-guide/operation/doris-error-code.md
rename to docs/en/admin-manual/maint-monitor/doris-error-code.md
diff --git a/new-docs/en/admin-manual/maint-monitor/metadata-operation.md b/docs/en/admin-manual/maint-monitor/metadata-operation.md
similarity index 100%
rename from new-docs/en/admin-manual/maint-monitor/metadata-operation.md
rename to docs/en/admin-manual/maint-monitor/metadata-operation.md
diff --git a/docs/en/administrator-guide/operation/monitor-alert.md b/docs/en/admin-manual/maint-monitor/monitor-alert.md
similarity index 100%
rename from docs/en/administrator-guide/operation/monitor-alert.md
rename to docs/en/admin-manual/maint-monitor/monitor-alert.md
diff --git a/docs/en/administrator-guide/operation/monitor-metrics/be-metrics.md b/docs/en/admin-manual/maint-monitor/monitor-metrics/be-metrics.md
similarity index 100%
rename from docs/en/administrator-guide/operation/monitor-metrics/be-metrics.md
rename to docs/en/admin-manual/maint-monitor/monitor-metrics/be-metrics.md
diff --git a/docs/en/administrator-guide/operation/monitor-metrics/fe-metrics.md b/docs/en/admin-manual/maint-monitor/monitor-metrics/fe-metrics.md
similarity index 100%
rename from docs/en/administrator-guide/operation/monitor-metrics/fe-metrics.md
rename to docs/en/admin-manual/maint-monitor/monitor-metrics/fe-metrics.md
diff --git a/docs/en/administrator-guide/operation/multi-tenant.md b/docs/en/admin-manual/maint-monitor/multi-tenant.md
similarity index 100%
rename from docs/en/administrator-guide/operation/multi-tenant.md
rename to docs/en/admin-manual/maint-monitor/multi-tenant.md
diff --git a/new-docs/en/admin-manual/maint-monitor/tablet-meta-tool.md b/docs/en/admin-manual/maint-monitor/tablet-meta-tool.md
similarity index 100%
rename from new-docs/en/admin-manual/maint-monitor/tablet-meta-tool.md
rename to docs/en/admin-manual/maint-monitor/tablet-meta-tool.md
diff --git a/new-docs/en/admin-manual/maint-monitor/tablet-repair-and-balance.md b/docs/en/admin-manual/maint-monitor/tablet-repair-and-balance.md
similarity index 100%
rename from new-docs/en/admin-manual/maint-monitor/tablet-repair-and-balance.md
rename to docs/en/admin-manual/maint-monitor/tablet-repair-and-balance.md
diff --git a/docs/en/administrator-guide/operation/tablet-restore-tool.md b/docs/en/admin-manual/maint-monitor/tablet-restore-tool.md
similarity index 100%
rename from docs/en/administrator-guide/operation/tablet-restore-tool.md
rename to docs/en/admin-manual/maint-monitor/tablet-restore-tool.md
diff --git a/new-docs/en/admin-manual/multi-tenant.md b/docs/en/admin-manual/multi-tenant.md
similarity index 100%
rename from new-docs/en/admin-manual/multi-tenant.md
rename to docs/en/admin-manual/multi-tenant.md
diff --git a/new-docs/en/admin-manual/optimization.md b/docs/en/admin-manual/optimization.md
similarity index 100%
rename from new-docs/en/admin-manual/optimization.md
rename to docs/en/admin-manual/optimization.md
diff --git a/new-docs/en/admin-manual/privilege-ldap/ldap.md b/docs/en/admin-manual/privilege-ldap/ldap.md
similarity index 100%
rename from new-docs/en/admin-manual/privilege-ldap/ldap.md
rename to docs/en/admin-manual/privilege-ldap/ldap.md
diff --git a/new-docs/en/admin-manual/privilege-ldap/user-privilege.md b/docs/en/admin-manual/privilege-ldap/user-privilege.md
similarity index 100%
rename from new-docs/en/admin-manual/privilege-ldap/user-privilege.md
rename to docs/en/admin-manual/privilege-ldap/user-privilege.md
diff --git a/new-docs/en/admin-manual/query-profile.md b/docs/en/admin-manual/query-profile.md
similarity index 100%
rename from new-docs/en/admin-manual/query-profile.md
rename to docs/en/admin-manual/query-profile.md
diff --git a/new-docs/en/admin-manual/sql-interception.md b/docs/en/admin-manual/sql-interception.md
similarity index 100%
rename from new-docs/en/admin-manual/sql-interception.md
rename to docs/en/admin-manual/sql-interception.md
diff --git a/docs/en/administrator-guide/alter-table/alter-table-bitmap-index.md b/docs/en/administrator-guide/alter-table/alter-table-bitmap-index.md
deleted file mode 100644
index 34506e5e33..0000000000
--- a/docs/en/administrator-guide/alter-table/alter-table-bitmap-index.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-{
- "title": "Bitmap Index",
- "language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Bitmap Index
-Users can speed up queries by creating a bitmap index
-This document focuses on how to create an index job, as well as some considerations and frequently asked questions when creating an index.
-
-## Glossary
-* bitmap index: a fast data structure that speeds up queries
-
-## Basic Principles
-Creating and dropping index is essentially a schema change job. For details, please refer to
-[Schema Change](alter-table-schema-change.html).
-
-## Syntax
-There are two forms of index creation and modification related syntax, one is integrated with alter table statement, and the other is using separate
-create/drop index syntax
-1. Create Index
-
- Please refer to [CREATE INDEX](../../sql-reference/sql-statements/Data%20Definition/CREATE%20INDEX.html)
- or [ALTER TABLE](../../sql-reference/sql-statements/Data%20Definition/ALTER%20TABLE.html),
- You can also specify a bitmap index when creating a table, Please refer to [CREATE TABLE](../../sql-reference/sql-statements/Data%20Definition/CREATE%20TABLE.html)
-
-2. Show Index
-
- Please refer to [SHOW INDEX](../../sql-reference/sql-statements/Administration/SHOW%20INDEX.html)
-
-3. Drop Index
-
- Please refer to [DROP INDEX](../../sql-reference/sql-statements/Data%20Definition/DROP%20INDEX.html) or [ALTER TABLE](../../sql-reference/sql-statements/Data%20Definition/ALTER%20TABLE.html)
-
-## Create Job
-Please refer to [Schema Change](alter-table-schema-change.html)
-## View Job
-Please refer to [Schema Change](alter-table-schema-change.html)
-
-## Cancel Job
-Please refer to [Schema Change](alter-table-schema-change.html)
-
-## Notice
-* Currently only index of bitmap type is supported.
-* The bitmap index is only created on a single column.
-* Bitmap indexes can be applied to all columns of the `Duplicate` data model and key columns of the `Aggregate` and `Uniq` models.
-* The data types supported by bitmap indexes are as follows:
- * `TINYINT`
- * `SMALLINT`
- * `INT`
- * `UNSIGNEDINT`
- * `BIGINT`
- * `CHAR`
- * `VARCHAR`
- * `DATE`
- * `DATETIME`
- * `LARGEINT`
- * `DECIMAL`
- * `BOOL`
-* The bitmap index takes effect only in segmentV2. The table's storage format will be converted to V2 automatically when creating index.
diff --git a/docs/en/administrator-guide/alter-table/alter-table-replace-table.md b/docs/en/administrator-guide/alter-table/alter-table-replace-table.md
deleted file mode 100644
index 02532988d8..0000000000
--- a/docs/en/administrator-guide/alter-table/alter-table-replace-table.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-{
- "title": "Replace Table",
- "language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Replace Table
-
-In version 0.14, Doris supports atomic replacement of two tables.
-This operation only applies to OLAP tables.
-
-For partition level replacement operations, please refer to [Temporary Partition Document](./alter-table-temp-partition.md)
-
-## Syntax
-
-```
-ALTER TABLE [db.]tbl1 REPLACE WITH tbl2
-[PROPERTIES('swap' = 'true')];
-```
-
-Replace table `tbl1` with table `tbl2`.
-
-If the `swap` parameter is `true`, after replacement, the data in the table named `tbl1` is the data in the original `tbl2` table. The data in the table named `tbl2` is the data in the original table `tbl1`. That is, the data of the two tables are interchanged.
-
-If the `swap` parameter is `false`, after replacement, the data in the table named `tbl1` is the data in the original `tbl2` table. The table named `tbl2` is dropped.
-
-## Principle
-
-The replacement table function actually turns the following set of operations into an atomic operation.
-
-Suppose you want to replace table A with table B, and `swap` is `true`, the operation is as follows:
-
-1. Rename table B to table A.
-2. Rename table A to table B.
-
-If `swap` is `false`, the operation is as follows:
-
-1. Drop table A.
-2. Rename table B to table A.
-
-## Notice
-
-1. The `swap` parameter defaults to `true`. That is, the replacement table operation is equivalent to the exchange of two table data.
-2. If the `swap` parameter is set to `false`, the replaced table (table A) will be dropped and cannot be recovered.
-3. The replacement operation can only occur between two OLAP tables, and the table structure of the two tables is not checked for consistency.
-4. The replacement operation will not change the original permission settings. Because the permission check is based on the table name.
-
-## Best Practices
-
-1. Atomic Overwrite Operation
-
- In some cases, the user wants to be able to rewrite the data of a certain table, but if it is dropped and then imported, there will be a period of time in which the data cannot be viewed. At this time, the user can first use the `CREATE TABLE LIKE` statement to create a new table with the same structure, import the new data into the new table, and replace the old table atomically through the replacement operation to achieve the goal. For partition level atomic overwrite operation, pl [...]
diff --git a/docs/en/administrator-guide/alter-table/alter-table-rollup.md b/docs/en/administrator-guide/alter-table/alter-table-rollup.md
deleted file mode 100644
index a3df4c8dc2..0000000000
--- a/docs/en/administrator-guide/alter-table/alter-table-rollup.md
+++ /dev/null
@@ -1,188 +0,0 @@
----
-{
- "title": "Rollup",
- "language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Rollup
-
-Users can speed up queries by creating rollup tables. For the concept and usage of Rollup, please refer to [Data
- Model, ROLLUP and Prefix Index](../../getting-started/data-model-rollup_EN.md) and
- [Rollup and query](../../getting-started/hit-the-rollup_EN.md).
-
-This document focuses on how to create a Rollup job, as well as some considerations and frequently asked questions about creating a Rollup.
-
-## Glossary
-
-* Base Table: When each table is created, it corresponds to a base table. The base table stores the complete data of this table. Rollups are usually created based on the data in the base table (and can also be created from other rollups).
-* Index: Materialized index. Rollup or Base Table are both called materialized indexes.
-* Transaction: Each import task is a transaction, and each transaction has a unique incrementing Transaction ID.
-
-## Basic Principles
-
-The basic process of creating a Rollup is to generate a new Rollup data containing the specified column from the data in the Base table. Among them, two parts of data conversion are needed. One is the conversion of existing historical data, and the other is the conversion of newly arrived imported data during Rollup execution.
-
-```
-+----------+
-| Load Job |
-+----+-----+
- |
- | Load job generates both base and rollup index data
- |
- | +------------------+ +---------------+
- | | Base Index | | Base Index |
- +------> New Incoming Data| | History Data |
- | +------------------+ +------+--------+
- | |
- | | Convert history data
- | |
- | +------------------+ +------v--------+
- | | Rollup Index | | Rollup Index |
- +------> New Incoming Data| | History Data |
- +------------------+ +---------------+
-```
-
-Before starting the conversion of historical data, Doris will obtain a latest transaction ID. And wait for all import transactions before this Transaction ID to complete. This Transaction ID becomes a watershed. This means that Doris guarantees that all import tasks after the watershed will generate data for the Rollup Index at the same time. In this way, after the historical data conversion is completed, the data of the Rollup and Base tables can be guaranteed to be flush.
-
-## Create Job
-
-The specific syntax for creating a Rollup can be found in the description of the Rollup section in the help `HELP ALTER TABLE`.
-
-The creation of Rollup is an asynchronous process. After the job is submitted successfully, the user needs to use the `SHOW ALTER TABLE ROLLUP` command to view the progress of the job.
-
-## View Job
-
-`SHOW ALTER TABLE ROLLUP` You can view rollup jobs that are currently executing or completed. For example:
-
-```
- JobId: 20037
- TableName: tbl1
- CreateTime: 2019-08-06 15:38:49
- FinishedTime: N/A
- BaseIndexName: tbl1
-RollupIndexName: r1
- RollupId: 20038
- TransactionId: 10034
- State: PENDING
- Msg:
- Progress: N/A
- Timeout: 86400
-```
-
-* JobId: A unique ID for each Rollup job.
-* TableName: The table name of the base table corresponding to Rollup.
-* CreateTime: Job creation time.
-* FinishedTime: The end time of the job. If it is not finished, "N / A" is displayed.
-* BaseIndexName: The name of the source Index corresponding to Rollup.
-* RollupIndexName: The name of the Rollup.
-* RollupId: The unique ID of the Rollup.
-* TransactionId: the watershed transaction ID of the conversion history data.
-* State: The phase of the operation.
- * PENDING: The job is waiting in the queue to be scheduled.
- * WAITING_TXN: Wait for the import task before the watershed transaction ID to complete.
- * RUNNING: Historical data conversion.
- * FINISHED: The operation was successful.
- * CANCELLED: The job failed.
-* Msg: If the job fails, a failure message is displayed here.
-* Progress: operation progress. Progress is displayed only in the RUNNING state. Progress is displayed in M / N. Where N is the total number of copies of Rollup. M is the number of copies of historical data conversion completed.
-* Timeout: Job timeout time. Unit of second.
-
-## Cancel Job
-
-In the case that the job status is not FINISHED or CANCELLED, you can cancel the Rollup job with the following command:
-
-`CANCEL ALTER TABLE ROLLUP FROM tbl_name;`
-
-## Notice
-
-* A table can have only one Rollup job running at a time. And only one rollup can be created in a job.
-
-* Rollup operations do not block import and query operations.
-
-* If a DELETE operation has a Key column in a where condition that does not exist in a Rollup, the DELETE is not allowed.
-
- If a Key column does not exist in a Rollup, the DELETE operation cannot delete data from the Rollup, so the data consistency between the Rollup table and the Base table cannot be guaranteed.
-
-* Rollup columns must exist in the Base table.
-
- Rollup columns are always a subset of the Base table columns. Columns that do not exist in the Base table cannot appear.
-
-* If a rollup contains columns of the REPLACE aggregation type, the rollup must contain all the key columns.
-
- Assume the structure of the Base table is as follows:
-
- `` `(k1 INT, k2 INT, v1 INT REPLACE, v2 INT SUM)` ``
-
- If you need to create a Rollup that contains `v1` columns, you must include the` k1`, `k2` columns. Otherwise, the system cannot determine the value of `v1` listed in Rollup.
-
- Note that all Value columns in the Unique data model table are of the REPLACE aggregation type.
-
-* Rollup of the DUPLICATE data model table, you can specify the DUPLICATE KEY of the rollup.
-
- The DUPLICATE KEY in the DUPLICATE data model table is actually sorted. Rollup can specify its own sort order, but the sort order must be a prefix of the Rollup column order. If not specified, the system will check if the Rollup contains all sort columns of the Base table, and if it does not, it will report an error. For example:
-
- Base table structure: `(k1 INT, k2 INT, k3 INT) DUPLICATE KEY (k1, k2)`
-
- Rollup can be: `(k2 INT, k1 INT) DUPLICATE KEY (k2)`
-
-* Rollup does not need to include partitioned or bucket columns for the Base table.
-
-## FAQ
-
-* How many rollups can a table create
-
- There is theoretically no limit to the number of rollups a table can create, but too many rollups can affect import performance. Because when importing, data will be generated for all rollups at the same time. At the same time, Rollup will take up physical storage space. Usually the number of rollups for a table is less than 10.
-
-* Rollup creation speed
-
- Rollup creation speed is currently estimated at about 10MB / s based on the worst efficiency. To be conservative, users can set the timeout for jobs based on this rate.
-
-* Submitting job error `Table xxx is not stable. ...`
-
- Rollup can start only when the table data is complete and unbalanced. If some data shard copies of the table are incomplete, or if some copies are undergoing an equalization operation, the submission is rejected.
-
- Whether the data shard copy is complete can be checked with the following command:
-
- ```ADMIN SHOW REPLICA STATUS FROM tbl WHERE STATUS! =" OK ";```
-
- If a result is returned, there is a problem with the copy. These problems are usually fixed automatically by the system. You can also use the following commands to repair this table first:
-
- ```ADMIN REPAIR TABLE tbl1; ```
-
- You can check if there are running balancing tasks with the following command:
-
- ```SHOW PROC" / cluster_balance / pending_tablets ";```
-
- You can wait for the balancing task to complete, or temporarily disable the balancing operation with the following command:
-
- ```ADMIN SET FRONTEND CONFIG ("disable_balance" = "true");```
-
-## Configurations
-
-### FE Configurations
-
-* `alter_table_timeout_second`: The default timeout for the job is 86400 seconds.
-
-### BE Configurations
-
-* `alter_tablet_worker_count`: Number of threads used to perform historical data conversion on the BE side. The default is 3. If you want to speed up the rollup job, you can increase this parameter appropriately and restart the BE. But too many conversion threads can cause increased IO pressure and affect other operations. This thread is shared with the Schema Change job.
diff --git a/docs/en/administrator-guide/alter-table/alter-table-schema-change.md b/docs/en/administrator-guide/alter-table/alter-table-schema-change.md
deleted file mode 100644
index 31755b02a0..0000000000
--- a/docs/en/administrator-guide/alter-table/alter-table-schema-change.md
+++ /dev/null
@@ -1,231 +0,0 @@
----
-{
- "title": "Schema Change",
- "language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Schema Change
-
-Users can modify the schema of existing tables through the Schema Change operation. Doris currently supports the following modifications:
-
-* Add and delete columns
-* Modify column type
-* Adjust column order
-* Add and modify Bloom Filter
-* Add and delete bitmap index
-
-This document mainly describes how to create a Schema Change job, as well as some considerations and frequently asked questions about Schema Change.
-## Glossary
-
-* Base Table: When each table is created, it corresponds to a base table. The base table stores the complete data of this table. Rollups are usually created based on the data in the base table (and can also be created from other rollups).
-* Index: Materialized index. Rollup or Base Table are both called materialized indexes.
-* Transaction: Each import task is a transaction, and each transaction has a unique incrementing Transaction ID.
-* Rollup: Roll-up tables based on base tables or other rollups.
-
-## Basic Principles
-
-The basic process of executing a Schema Change is to generate a copy of the index data of the new schema from the data of the original index. Among them, two parts of data conversion are required. One is the conversion of existing historical data, and the other is the conversion of newly arrived imported data during the execution of Schema Change.
-```
-+----------+
-| Load Job |
-+----+-----+
- |
- | Load job generates both origin and new index data
- |
- | +------------------+ +---------------+
- | | Origin Index | | Origin Index |
- +------> New Incoming Data| | History Data |
- | +------------------+ +------+--------+
- | |
- | | Convert history data
- | |
- | +------------------+ +------v--------+
- | | New Index | | New Index |
- +------> New Incoming Data| | History Data |
- +------------------+ +---------------+
-```
-
-Before starting the conversion of historical data, Doris will obtain a latest transaction ID. And wait for all import transactions before this Transaction ID to complete. This Transaction ID becomes a watershed. This means that Doris guarantees that all import tasks after the watershed will generate data for both the original Index and the new Index. In this way, when the historical data conversion is completed, the data in the new Index can be guaranteed to be complete.
-## Create Job
-
-The specific syntax for creating a Schema Change can be found in the description of the Schema Change section in the help `HELP ALTER TABLE`.
-
-The creation of Schema Change is an asynchronous process. After the job is submitted successfully, the user needs to view the job progress through the `SHOW ALTER TABLE COLUMN` command.
-## View Job
-
-`SHOW ALTER TABLE COLUMN` You can view the Schema Change jobs that are currently executing or completed. When multiple indexes are involved in a Schema Change job, the command displays multiple lines, each corresponding to an index. For example:
-
-```
- JobId: 20021
- TableName: tbl1
- CreateTime: 2019-08-05 23:03:13
- FinishTime: 2019-08-05 23:03:42
- IndexName: tbl1
- IndexId: 20022
-OriginIndexId: 20017
-SchemaVersion: 2:792557838
-TransactionId: 10023
- State: FINISHED
- Msg:
- Progress: N/A
- Timeout: 86400
-```
-
-* JobId: A unique ID for each Schema Change job.
-* TableName: The table name of the base table corresponding to Schema Change.
-* CreateTime: Job creation time.
-* FinishedTime: The end time of the job. If it is not finished, "N / A" is displayed.
-* IndexName: The name of an Index involved in this modification.
-* IndexId: The unique ID of the new Index.
-* OriginIndexId: The unique ID of the old Index.
-* SchemaVersion: Displayed in M: N format. M is the version of this Schema Change, and N is the corresponding hash value. With each Schema Change, the version is incremented.
-* TransactionId: the watershed transaction ID of the conversion history data.
-* State: The phase of the operation.
- * PENDING: The job is waiting in the queue to be scheduled.
- * WAITING_TXN: Wait for the import task before the watershed transaction ID to complete.
- * RUNNING: Historical data conversion.
- * FINISHED: The operation was successful.
- * CANCELLED: The job failed.
-* Msg: If the job fails, a failure message is displayed here.
-* Progress: operation progress. Progress is displayed only in the RUNNING state. Progress is displayed in M / N. Where N is the total number of copies involved in the Schema Change. M is the number of copies of historical data conversion completed.
-* Timeout: Job timeout time. Unit of second.
-
-## Cancel Job
-
-In the case that the job status is not FINISHED or CANCELLED, you can cancel the Schema Change job with the following command:
-`CANCEL ALTER TABLE COLUMN FROM tbl_name;`
-
-## Best Practice
-
-Schema Change can make multiple changes to multiple indexes in one job. For example:
-Source Schema:
-
-```
-+-----------+-------+------+------+------+---------+-------+
-| IndexName | Field | Type | Null | Key | Default | Extra |
-+-----------+-------+------+------+------+---------+-------+
-| tbl1 | k1 | INT | No | true | N/A | |
-| | k2 | INT | No | true | N/A | |
-| | k3 | INT | No | true | N/A | |
-| | | | | | | |
-| rollup2 | k2 | INT | No | true | N/A | |
-| | | | | | | |
-| rollup1 | k1 | INT | No | true | N/A | |
-| | k2 | INT | No | true | N/A | |
-+-----------+-------+------+------+------+---------+-------+
-```
-
-You can add a row k4 to both rollup1 and rollup2 by adding the following k5 to rollup2:
-```
-ALTER TABLE tbl1
-ADD COLUMN k4 INT default "1" to rollup1,
-ADD COLUMN k4 INT default "1" to rollup2,
-ADD COLUMN k5 INT default "1" to rollup2;
-```
-
-When completion, the Schema becomes:
-
-```
-+-----------+-------+------+------+------+---------+-------+
-| IndexName | Field | Type | Null | Key | Default | Extra |
-+-----------+-------+------+------+------+---------+-------+
-| tbl1 | k1 | INT | No | true | N/A | |
-| | k2 | INT | No | true | N/A | |
-| | k3 | INT | No | true | N/A | |
-| | k4 | INT | No | true | 1 | |
-| | k5 | INT | No | true | 1 | |
-| | | | | | | |
-| rollup2 | k2 | INT | No | true | N/A | |
-| | k4 | INT | No | true | 1 | |
-| | k5 | INT | No | true | 1 | |
-| | | | | | | |
-| rollup1 | k1 | INT | No | true | N/A | |
-| | k2 | INT | No | true | N/A | |
-| | k4 | INT | No | true | 1 | |
-+-----------+-------+------+------+------+---------+-------+
-```
-
-As you can see, the base table tbl1 also automatically added k4, k5 columns. That is, columns added to any rollup are automatically added to the Base table.
-
-At the same time, columns that already exist in the Base table are not allowed to be added to Rollup. If you need to do this, you can re-create a Rollup with the new columns and then delete the original Rollup.
-## Notice
-
-* Only one Schema Change job can be running on a table at a time.
-
-* Schema Change operation does not block import and query operations.
-
-* The partition column and bucket column cannot be modified.
-
-* If there is a value column aggregated by REPLACE in the schema, the Key column is not allowed to be deleted.
-
- If the Key column is deleted, Doris cannot determine the value of the REPLACE column.
-
- All non-Key columns of the Unique data model table are REPLACE aggregated.
-
-* When adding a value column whose aggregation type is SUM or REPLACE, the default value of this column has no meaning to historical data.
-
- Because the historical data has lost the detailed information, the default value cannot actually reflect the aggregated value.
-
-* When modifying the column type, fields other than Type need to be completed according to the information on the original column.
-
- If you modify the column `k1 INT SUM NULL DEFAULT" 1 "` as type BIGINT, you need to execute the following command:
-
-```ALTER TABLE tbl1 MODIFY COLUMN `k1` BIGINT SUM NULL DEFAULT "1";```
-
- Note that in addition to the new column types, such as the aggregation mode, Nullable attributes, and default values must be completed according to the original information.
-
-* Modifying column names, aggregation types, nullable attributes, default values, and column comments is not supported.
-
-## FAQ
-
-* the execution speed of Schema Change
-
- At present, the execution speed of Schema Change is estimated to be about 10MB / s according to the worst efficiency. To be conservative, users can set the timeout for jobs based on this rate.
-
-* Submit job error `Table xxx is not stable. ...`
-
- Schema Change can only be started when the table data is complete and unbalanced. If some data shard copies of the table are incomplete, or if some copies are undergoing an equalization operation, the submission is rejected.
-
- Whether the data shard copy is complete can be checked with the following command:
- ```ADMIN SHOW REPLICA STATUS FROM tbl WHERE STATUS != "OK";```
-
- If a result is returned, there is a problem with the copy. These problems are usually fixed automatically by the system. You can also use the following commands to repair this table first:
- ```ADMIN REPAIR TABLE tbl1;```
-
- You can check if there are running balancing tasks with the following command:
-
- ```SHOW PROC "/cluster_balance/pending_tablets";```
-
- You can wait for the balancing task to complete, or temporarily disable the balancing operation with the following command:
-
- ```ADMIN SET FRONTEND CONFIG ("disable_balance" = "true");```
-
-## Configurations
-
-### FE Configurations
-
-* `alter_table_timeout_second`: The default timeout for the job is 86400 seconds.
-
-### BE Configurations
-
-* `alter_tablet_worker_count`: Number of threads used to perform historical data conversion on the BE side. The default is 3. If you want to speed up the Schema Change job, you can increase this parameter appropriately and restart the BE. But too many conversion threads can cause increased IO pressure and affect other operations. This thread is shared with the Rollup job.
diff --git a/docs/en/administrator-guide/alter-table/alter-table-temp-partition.md b/docs/en/administrator-guide/alter-table/alter-table-temp-partition.md
deleted file mode 100644
index 94f7440bf7..0000000000
--- a/docs/en/administrator-guide/alter-table/alter-table-temp-partition.md
+++ /dev/null
@@ -1,288 +0,0 @@
----
-{
- "title": "Temporary partition",
- "language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Temporary partition
-
-Since version 0.12, Doris supports temporary partitioning.
-
-A temporary partition belongs to a partitioned table. Only partitioned tables can create temporary partitions.
-
-## Rules
-
-* The partition columns of the temporary partition is the same as the formal partition and cannot be modified.
-* The partition ranges of all temporary partitions of a table cannot overlap, but the ranges of temporary partitions and formal partitions can overlap.
-* The partition name of the temporary partition cannot be the same as the formal partitions and other temporary partitions.
-
-## Supported operations
-
-The temporary partition supports add, delete, and replace operations.
-
-### Add temporary partition
-
-You can add temporary partitions to a table with the `ALTER TABLE ADD TEMPORARY PARTITION` statement:
-
-```
-ALTER TABLE tbl1 ADD TEMPORARY PARTITION tp1 VALUES LESS THAN ("2020-02-01");
-
-ALTER TABLE tbl2 ADD TEMPORARY PARTITION tp1 VALUES [("2020-01-01"), ("2020-02-01"));
-
-ALTER TABLE tbl1 ADD TEMPORARY PARTITION tp1 VALUES LESS THAN ("2020-02-01")
-("in_memory" = "true", "replication_num" = "1")
-DISTRIBUTED BY HASH (k1) BUCKETS 5;
-
-ALTER TABLE tbl3 ADD TEMPORARY PARTITION tp1 VALUES IN ("Beijing", "Shanghai");
-
-ALTER TABLE tbl4 ADD TEMPORARY PARTITION tp1 VALUES IN ((1, "Beijing"), (1, "Shanghai"));
-
-ALTER TABLE tbl3 ADD TEMPORARY PARTITION tp1 VALUES IN ("Beijing", "Shanghai")
-("in_memory" = "true", "replication_num" = "1")
-DISTRIBUTED BY HASH(k1) BUCKETS 5;
-
-```
-
-See `HELP ALTER TABLE;` for more help and examples.
-
-Some instructions for adding operations:
-
-* Adding a temporary partition is similar to adding a formal partition. The partition range of the temporary partition is independent of the formal partition.
-* Temporary partition can independently specify some attributes. Includes information such as the number of buckets, the number of replicas, whether it is a memory table, or the storage medium.
-
-### Delete temporary partition
-
-A table's temporary partition can be dropped with the `ALTER TABLE DROP TEMPORARY PARTITION` statement:
-
-```
-ALTER TABLE tbl1 DROP TEMPORARY PARTITION tp1;
-```
-
-See `HELP ALTER TABLE;` for more help and examples.
-
-Some instructions for the delete operation:
-
-* Deleting the temporary partition will not affect the data of the formal partition.
-
-### Replace partition
-
-You can replace formal partitions of a table with temporary partitions with the `ALTER TABLE REPLACE PARTITION` statement.
-
-```
-ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
-
-ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1, tp2, tp3);
-
-ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1, tp2)
-PROPERTIES (
- "strict_range" = "false",
- "use_temp_partition_name" = "true"
-);
-```
-
-See `HELP ALTER TABLE;` for more help and examples.
-
-The replace operation has two special optional parameters:
-
-1. `strict_range`
-
- The default is true.
-
- For Range partition, When this parameter is true, the range union of all formal partitions to be replaced needs to be the same as the range union of the temporary partitions to be replaced. When set to false, you only need to ensure that the range between the new formal partitions does not overlap after replacement.
-
- For List partition, this parameter is always true, and the enumeration values of all full partitions to be replaced must be identical to the enumeration values of the temporary partitions to be replaced.
-
- Here are some examples:
-
- * Example 1
-
- Range of partitions p1, p2, p3 to be replaced (=> union):
-
- ```
- (10, 20), [20, 30), [40, 50) => [10, 30), [40, 50)
- ```
-
- Replace the range of partitions tp1, tp2 (=> union):
-
- ```
- (10, 30), [40, 45), [45, 50) => [10, 30), [40, 50)
- ```
-
- The union of ranges is the same, so you can use tp1 and tp2 to replace p1, p2, p3.
-
- * Example 2
-
- Range of partition p1 to be replaced (=> union):
-
- ```
- (10, 50) => [10, 50)
- ```
-
- Replace the range of partitions tp1, tp2 (=> union):
-
- ```
- (10, 30), [40, 50) => [10, 30), [40, 50)
- ```
-
- The union of ranges is not the same. If `strict_range` is true, you cannot use tp1 and tp2 to replace p1. If false, and the two partition ranges `[10, 30), [40, 50)` and the other formal partitions do not overlap, they can be replaced.
-
- * Example 3
-
- Enumerated values of partitions p1, p2 to be replaced (=> union).
-
- ```
- (1, 2, 3), (4, 5, 6) => (1, 2, 3, 4, 5, 6)
- ```
-
- Replace the enumerated values of partitions tp1, tp2, tp3 (=> union).
-
- ```
- (1, 2, 3), (4), (5, 6) => (1, 2, 3, 4, 5, 6)
- ```
-
- The enumeration values are the same, you can use tp1, tp2, tp3 to replace p1, p2
-
- * Example 4
-
- Enumerated values of partitions p1, p2, p3 to be replaced (=> union).
-
- ```
- (("1", "beijing"), ("1", "shanghai")), (("2", "beijing"), ("2", "shanghai")), (("3", "beijing"), ("3", "shanghai")) => (("1", "beijing"), ("3", "shanghai")) "), ("1", "shanghai"), ("2", "beijing"), ("2", "shanghai"), ("3", "beijing"), ("3", "shanghai"))
- ```
-
- Replace the enumerated values of partitions tp1, tp2 (=> union).
-
- ```
- (("1", "beijing"), ("1", "shanghai")), (("2", "beijing"), ("2", "shanghai"), ("3", "beijing"), ("3", "shanghai")) => (("1", "beijing") , ("1", "shanghai"), ("2", "beijing"), ("2", "shanghai"), ("3", "beijing"), ("3", "shanghai"))
- ```
-
- The enumeration values are the same, you can use tp1, tp2 to replace p1, p2, p3
-
-2. `use_temp_partition_name`
-
- The default is false. When this parameter is false, and the number of partitions to be replaced is the same as the number of replacement partitions, the name of the formal partition after the replacement remains unchanged. If true, after replacement, the name of the formal partition is the name of the replacement partition. Here are some examples:
-
- * Example 1
-
- ```
- ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);
- ```
-
- `use_temp_partition_name` is false by default. After replacement, the partition name is still p1, but the related data and attributes are replaced with tp1.
-
- If `use_temp_partition_name` is true by default, the name of the partition is tp1 after replacement. The p1 partition no longer exists.
-
- * Example 2
-
- ```
- ALTER TABLE tbl1 REPLACE PARTITION (p1, p2) WITH TEMPORARY PARTITION (tp1);
- ```
-
- `use_temp_partition_name` is false by default, but this parameter is invalid because the number of partitions to be replaced and the number of replacement partitions are different. After the replacement, the partition name is tp1, and p1 and p2 no longer exist.
-
-Some instructions for the replacement operation:
-
-* After the partition is replaced successfully, the replaced partition will be deleted and cannot be recovered.
-
-## Load and query of temporary partitions
-
-Users can load data into temporary partitions or specify temporary partitions for querying.
-
-1. Load temporary partition
-
- The syntax for specifying a temporary partition is slightly different depending on the load method. Here is a simple illustration through an example:
-
- ```
- INSERT INTO tbl TEMPORARY PARTITION (tp1, tp2, ...) SELECT ....
- ```
-
- ```
- curl --location-trusted -u root: -H "label: 123" -H "temporary_partition: tp1, tp2, ..." -T testData http: // host: port / api / testDb / testTbl / _stream_load
- ```
-
- ```
- LOAD LABEL example_db.label1
- (
- DATA INFILE ("hdfs://hdfs_host:hdfs_port/user/palo/data/input/file")
- INTO TABLE `my_table`
- TEMPORARY PARTITION (tp1, tp2, ...)
- ...
- )
- WITH BROKER hdfs ("username" = "hdfs_user", "password" = "hdfs_password");
- ```
-
- ```
- CREATE ROUTINE LOAD example_db.test1 ON example_tbl
- COLUMNS (k1, k2, k3, v1, v2, v3 = k1 * 100),
- TEMPORARY PARTITIONS (tp1, tp2, ...),
- WHERE k1> 100
- PROPERTIES
- (...)
- FROM KAFKA
- (...);
- ```
-
-2. Query the temporary partition
-
- ```
- SELECT ... FROM
- tbl1 TEMPORARY PARTITION (tp1, tp2, ...)
- JOIN
- tbl2 TEMPORARY PARTITION (tp1, tp2, ...)
- ON ...
- WHERE ...;
- ```
-
-## Relationship to other operations
-
-### DROP
-
-* After using the `DROP` operation to directly drop the database or table, you can recover the database or table (within a limited time) through the `RECOVER` command, but the temporary partition will not be recovered.
-* After the formal partition is dropped using the `ALTER` command, the partition can be recovered by the `RECOVER` command (within a limited time). Operating a formal partition is not related to a temporary partition.
-* After the temporary partition is dropped using the `ALTER` command, the temporary partition cannot be recovered through the `RECOVER` command.
-
-### TRUNCATE
-
-* Use the `TRUNCATE` command to empty the table. The temporary partition of the table will be deleted and cannot be recovered.
-* When using `TRUNCATE` command to empty the formal partition, it will not affect the temporary partition.
-* You cannot use the `TRUNCATE` command to empty the temporary partition.
-
-### ALTER
-
-* When the table has a temporary partition, you cannot use the `ALTER` command to perform Schema Change, Rollup, etc. on the table.
-* You cannot add temporary partitions to a table while the table is undergoing a alter operation.
-
-
-## Best Practices
-
-1. Atomic overwrite
-
- In some cases, the user wants to be able to rewrite the data of a certain partition, but if it is dropped first and then loaded, there will be a period of time when the data cannot be seen. At this moment, the user can first create a corresponding temporary partition, load new data into the temporary partition, and then replace the original partition atomically through the `REPLACE` operation to achieve the purpose. For atomic overwrite operations of non-partitioned tables, please re [...]
-
-2. Modify the number of buckets
-
- In some cases, the user used an inappropriate number of buckets when creating a partition. The user can first create a temporary partition corresponding to the partition range and specify a new number of buckets. Then use the `INSERT INTO` command to load the data of the formal partition into the temporary partition. Through the replacement operation, the original partition is replaced atomically to achieve the purpose.
-
-3. Merge or split partitions
-
- In some cases, users want to modify the range of partitions, such as merging two partitions, or splitting a large partition into multiple smaller partitions. Then the user can first create temporary partitions corresponding to the merged or divided range, and then load the data of the formal partition into the temporary partition through the `INSERT INTO` command. Through the replacement operation, the original partition is replaced atomically to achieve the purpose.
\ No newline at end of file
diff --git a/docs/en/administrator-guide/backup-restore.md b/docs/en/administrator-guide/backup-restore.md
deleted file mode 100644
index 4e9ce83513..0000000000
--- a/docs/en/administrator-guide/backup-restore.md
+++ /dev/null
@@ -1,195 +0,0 @@
----
-{
- "title": "Backup and Recovery",
- "language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Backup and Recovery
-
-Doris supports the backup of current data in the form of files to remote storage systems via broker. The data can then be restored from the remote storage system to any Doris cluster by the restore command. With this feature, Doris can support regular snapshot backups of data. It can also be used to migrate data between different clusters.
-
-This feature requires Doris version 0.8.2+
-
-Using this function, brokers corresponding to remote storage need to be deployed. Such as BOS, HDFS, etc. You can view the currently deployed broker through `SHOW BROKER;`
-
-## Brief Principle Description
-
-### Backup
-
-The backup operation is to upload the data of the specified table or partition directly to the remote warehouse in the form of files stored by Doris for storage. When a user submits a Backup request, the following actions will be done within the system:
-
-1. Snapshot and snapshot upload
-
- The snapshot phase takes a snapshot of the specified table or partition data file. Later, backups are all snapshots. After the snapshot, changes to tables, imports, and other operations no longer affect the results of the backup. Snapshots only produce a hard link to the current data file, which takes very little time. Once the snapshots are completed, they are uploaded one by one. Snapshot upload is done concurrently by each Backend.
-
-2. Metadata preparation and upload
-
- After the data file snapshot is uploaded, Frontend first writes the corresponding metadata to the local file, and then uploads the local metadata file to the remote warehouse through broker. Finish the final backup job.
-
-3. Dynamic partition table description
-
- If the table is a dynamic partition table, the dynamic partition attribute will be automatically disabled after backup. When restoring, you need to manually enable the dynamic partition attribute of the table. The command is as follows:
-
- ```sql
- ALTER TABLE tbl1 SET ("dynamic_partition.enable"="true")
- ````
-
-### Restore
-
-Recovery operations need to specify a backup that already exists in a remote repository, and then restore the backup content to the local cluster. When a user submits a Restore request, the following actions will be done within the system:
-
-1. Create corresponding metadata locally
-
- This step starts by creating structures such as restoring the corresponding table partitions in the local cluster. When created, the table is visible, but not accessible.
-
-2. Local snapshot
-
- This step is to take a snapshot of the table created in the previous step. This is actually an empty snapshot (because the tables just created have no data), and its main purpose is to generate the corresponding snapshot directory on the Backend for receiving the snapshot files downloaded from the remote repository later.
-
-3. Download snapshots
-
- The snapshot files in the remote warehouse are downloaded to the corresponding snapshot directory generated in the previous step. This step is done concurrently by each backend.
-
-4. Effective snapshot
-
- When the snapshot download is complete, we map each snapshot to the metadata of the current local table. These snapshots are then reloaded to take effect and complete the final recovery operation.
-
-## Best Practices
-
-### Backup
-
-We currently support full backup at the minimum partition granularity (incremental backup may be supported in future versions). If data need to be backed up regularly, first of all, it is necessary to plan the partition and bucket allocation of tables reasonably, such as partitioning according to time. Then in the subsequent run process, periodic data backup is performed according to partition granularity.
-
-### Data migration
-
-Users can first backup the data to the remote warehouse, and then restore the data to another cluster through the remote warehouse to complete data migration. Because data backup is done in the form of snapshots, new imported data after the snapshot phase of the backup job will not be backed up. Therefore, after the snapshot is completed, the data imported on the original cluster needs to be imported on the new cluster as well until the recovery job is completed.
-
-It is suggested that the new and old clusters be imported in parallel for a period of time after the migration is completed. After completing data and business correctness checks, the business is migrated to the new cluster.
-
-## Highlights
-
-1. Backup and recovery-related operations are currently only allowed to be performed by users with ADMIN privileges.
-2. Within a database, only one backup or recovery job is allowed to be performed.
-3. Both backup and recovery support the operation at the minimum partition level. When the table has a large amount of data, it is recommended to perform partition-by-partition to reduce the cost of failed retries.
-4. Because backup and recovery operations, the operation is the actual data files. So when there are too many fragments of a table or too many small versions of a fragment, it may take a long time to backup or restore even if the total amount of data is very small. Users can estimate job execution time by `SHOW PARTITIONS FROM table_name;`, and `SHOW TABLET FROM table_name;`, viewing the number of partitions and the number of file versions of each partition. The number of files has a gre [...]
-5. When viewing the job status through `SHOW BACKUP` or `SHOW RESTORE`. It is possible to see an error message in the `TaskErrMsg` column. But as long as the `State` column does not
-`CANCELLED`, that means the job is still going on. These Tasks may succeed in retrying. Of course, some Task errors can also directly lead to job failure.
-6. If the recovery operation is a coverage operation (specifying the recovery data to an existing table or partition), then starting from the `COMMIT` phase of the recovery operation, the data covered on the current cluster may not be restored. At this time, if the recovery operation fails or is cancelled, it may cause the previous data to be damaged and inaccessible. In this case, the recovery operation can only be performed again and wait for the job to complete. Therefore, we recommen [...]
-
-## Relevant orders
-
-The commands related to the backup recovery function are as follows. The following commands, you can use `help cmd;'to view detailed help after connecting Doris through mysql-client.
-
-1. CREATE REPOSITORY
-
- Create a remote warehouse Path for backup or recovery. This command needs to access the remote storage through the Broker. Different brokers need to provide different parameters. For details, please refer to [Broker Document] (broker.md), or directly back up to the remote storage supporting AWS S3 protocol through S3 protocol. For details, please refer to [CREATE REPOSITORY DOCUMENT] (../sql-reference/sql-statements/Data%20Definition/CREATE%20REPOSITORY.md)
-
-
-1. BACKUP
-
- Perform a backup operation.
-
-3. SHOW BACKUP
-
- View the execution of the last backup job, including:
-
- * JobId: ID of this backup job.
- * SnapshotName: User-specified name of this backup job (Label).
- * DbName: The database corresponding to the backup job.
- * State: The current stage of the backup job:
- * PENDING: The initial state of the job.
- * SNAPSHOTING: Snapshot operation is in progress.
- * UPLOAD_SNAPSHOT: The snapshot is over and ready to upload.
- * UPLOADING: Uploading snapshots.
- * SAVE_META: Metadata files are being generated locally.
- * UPLOAD_INFO: Upload metadata files and information for this backup job.
- * FINISHED: The backup is complete.
- * CANCELLED: Backup failed or cancelled.
- * Backup Objs: List of tables and partitions involved in this backup.
- * CreateTime: Job creation time.
- * Snapshot Finished Time: Snapshot completion time.
- * Upload Finished Time: Snapshot upload completion time.
- * FinishedTime: The completion time of this assignment.
- * Unfinished Tasks: In the `SNAPSHOTTING`, `UPLOADING` and other stages, there will be multiple sub-tasks at the same time, the current stage shown here, the task ID of the unfinished sub-tasks.
- * TaskErrMsg: If there is a sub-task execution error, the error message corresponding to the sub-task will be displayed here.
- * Status: It is used to record some status information that may appear during the whole operation.
- * Timeout: The timeout time of a job in seconds.
-
-4. SHOW SNAPSHOT
-
- View the backup that already exists in the remote warehouse.
-
- * Snapshot: The name of the backup specified at the time of backup (Label).
- * Timestamp: Backup timestamp.
- * Status: Is the backup normal?
-
- If the where clause is specified after `SHOW SNAPSHOT', more detailed backup information can be displayed.
-
- * Database: The database corresponding to backup.
- * Details: Shows the complete data directory structure of the backup.
-
-5. RESTORE
-
- Perform a recovery operation.
-
-6. SHOW RESTORE
-
- View the execution of the last restore job, including:
-
- * JobId: ID of this resumption job.
- * Label: The name of the backup in the user-specified warehouse (Label).
- * Timestamp: The timestamp for backup in a user-specified warehouse.
- * DbName: Restore the database corresponding to the job.
- * State: The current stage of the recovery operation:
- * PENDING: The initial state of the job.
- * SNAPSHOTING: A snapshot of a new local table is in progress.
- * DOWNLOAD: The download snapshot task is being sent.
- * DOWNLOADING: Snapshot is downloading.
- * COMMIT: Prepare to take effect the downloaded snapshot.
- * COMMITTING: The downloaded snapshot is in effect.
- * FINISHED: Recovery is complete.
- * CANCELLED: Recovery failed or cancelled.
- * AllowLoad: Is import allowed during recovery?
- * ReplicationNum: Restores the specified number of copies.
- * Restore Objs: List of tables and partitions involved in this recovery.
- * CreateTime: Job creation time.
- * MetaPreparedTime: Completion time of local metadata generation.
- * Snapshot Finished Time: Local snapshot completion time.
- * Download Finished Time: The download completion time of the remote snapshot.
- * FinishedTime: The completion time of this assignment.
- * Unfinished Tasks: In the `SNAPSHOTTING`, `DOWNLOADING`, `COMMITTING`, and other stages, there will be multiple sub-tasks at the same time, the current stage shown here, the task ID of the unfinished sub-tasks.
- * TaskErrMsg: If there is a sub-task execution error, the error message corresponding to the sub-task will be displayed here.
- * Status: It is used to record some status information that may appear during the whole operation.
- * Timeout: The timeout time of a job in seconds.
-
-7. CANCEL BACKUP
-
- Cancel the backup job currently being performed.
-
-8. CANCEL RESTORE
-
- Cancel the recovery job currently being performed.
-
-9. DROP REPOSITORY
-
- Delete the created remote warehouse. Delete the warehouse, just delete the mapping of the warehouse in Doris, will not delete the actual warehouse data.
diff --git a/docs/en/administrator-guide/block-rule/sql-block.md b/docs/en/administrator-guide/block-rule/sql-block.md
deleted file mode 100644
index 0b167ae17c..0000000000
--- a/docs/en/administrator-guide/block-rule/sql-block.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-{
-"title": "SQL Block Rule",
-"language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# SQL Block Rule
-
-This function is only used to limit the query statement, and does not limit the execution of the explain statement.
-Support SQL block rule by user level:
-
-1. by regex way to deny specify SQL
-
-2. by setting partition_num, tablet_num, cardinality, check whether a sql reaches one of the limitations
- - partition_num, tablet_num, cardinality could be set together, and once reach one of them, the sql will be blocked.
-
-## Rule
-
-SQL block rule CRUD
-- create SQL block rule
- - sql: Regex pattern,Special characters need to be translated, "NULL" by default
- - sqlHash: Sql hash value, Used to match exactly, We print it in fe.audit.log, This parameter is the only choice between sql and sql, "NULL" by default
- - partition_num: Max number of partitions will be scanned by a scan node, 0L by default
- - tablet_num: Max number of tablets will be scanned by a scan node, 0L by default
- - cardinality: An inaccurate number of scan rows of a scan node, 0L by default
- - global: Whether global(all users)is in effect, false by default
- - enable: Whether to enable block rule,true by default
-```sql
-CREATE SQL_BLOCK_RULE test_rule
-PROPERTIES(
- "sql"="select * from order_analysis",
- "global"="false",
- "enable"="true",
- "sqlHash"=""
-)
-```
-When we execute the sql that we defined in the rule just now, an exception error will be returned. An example is as follows:
-```sql
-mysql> select * from order_analysis;
-ERROR 1064 (HY000): errCode = 2, detailMessage = sql match regex sql block rule: order_analysis_rule
-```
-
-- create test_rule2, limits the maximum number of scanning partitions to 30 and the maximum scanning cardinality to 10 billion rows. As shown in the following example:
-```sql
-CREATE SQL_BLOCK_RULE test_rule2 PROPERTIES("partition_num" = "30", "cardinality"="10000000000","global"="false","enable"="true")
-```
-
-- show configured SQL block rules, or show all rules if you do not specify a rule name
-
-```sql
-SHOW SQL_BLOCK_RULE [FOR RULE_NAME]
-```
-- alter SQL block rule,Allows changes sql/sqlHash/global/enable/partition_num/tablet_num/cardinality anyone
- - sql and sqlHash cannot be set both. It means if sql or sqlHash is set in a rule, another property will never be allowed to be altered
- - sql/sqlHash and partition_num/tablet_num/cardinality cannot be set together. For example, partition_num is set in a rule, then sql or sqlHash will never be allowed to be altered.
-```sql
-ALTER SQL_BLOCK_RULE test_rule PROPERTIES("sql"="select \\* from test_table","enable"="true")
-```
-
-```
-ALTER SQL_BLOCK_RULE test_rule2 PROPERTIES("partition_num" = "10","tablet_num"="300","enable"="true")
-```
-
-- drop SQL block rule,Support multiple rules, separated by `,`
-```sql
-DROP SQL_BLOCK_RULE test_rule1,test_rule2
-```
-
-## User bind rules
-If global=false is configured, the rules binding for the specified user needs to be configured, with multiple rules separated by ', '
-```sql
-SET PROPERTY [FOR 'jack'] 'sql_block_rules' = 'test_rule1,test_rule2'
-```
diff --git a/docs/en/administrator-guide/broker.md b/docs/en/administrator-guide/broker.md
deleted file mode 100644
index 0bac53bdc6..0000000000
--- a/docs/en/administrator-guide/broker.md
+++ /dev/null
@@ -1,289 +0,0 @@
----
-{
- "title": "Broker",
- "language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Broker
-
-Broker is an optional process in the Doris cluster. It is mainly used to support Doris to read and write files or directories on remote storage, such as HDFS, BOS, and AFS.
-
-Broker provides services through an RPC service port. It is a stateless JVM process that is responsible for encapsulating some POSIX-like file operations for read and write operations on remote storage, such as open, pred, pwrite, and so on.
-In addition, the Broker does not record any other information, so the connection information, file information, permission information, and so on stored remotely need to be passed to the Broker process in the RPC call through parameters in order for the Broker to read and write files correctly .
-
-Broker only acts as a data channel and does not participate in any calculations, so it takes up less memory. Usually one or more Broker processes are deployed in a Doris system. And the same type of Broker will form a group and set a ** Broker name **.
-
-Broker's position in the Doris system architecture is as follows:
-
-```
-+----+ +----+
-| FE | | BE |
-+-^--+ +--^-+
- | |
- | |
-+-v---------v-+
-| Broker |
-+------^------+
- |
- |
-+------v------+
-|HDFS/BOS/AFS |
-+-------------+
-```
-
-This document mainly introduces the parameters that Broker needs when accessing different remote storages, such as connection information,
-authorization information, and so on.
-
-## Supported Storage System
-
-Different types of brokers support different storage systems.
-
-1. Community HDFS
-
- * Support simple authentication access
- * Support kerberos authentication access
- * Support HDFS HA mode access
-
-2. Baidu HDFS / AFS (not supported by open source version)
-
- * Support UGI simple authentication access
-
-3. Baidu Object Storage BOS (not supported by open source version)
-
- * Support AK / SK authentication access
-
-## Function provided by Broker
-
-1. Broker Load
-
- The Broker Load function reads the file data on the remote storage through the Broker process and imports it into Doris. Examples are as follows:
-
- ```
- LOAD LABEL example_db.label6
- (
- DATA INFILE("bos://my_bucket/input/file")
- INTO TABLE `my_table`
- )
- WITH BROKER "broker_name"
- (
- "bos_endpoint" = "http://bj.bcebos.com",
- "bos_accesskey" = "xxxxxxxxxxxxxxxxxxxxxxxxxx",
- "bos_secret_accesskey" = "yyyyyyyyyyyyyyyyyyyy"
- )
- ```
-
- `WITH BROKER` and following Property Map are used to provide Broker's related information.
-
-2. Export
-
- The Export function export the data stored in Doris to a file stored in remote storage in text format through Broker process. Examples are as follows:
-
- ```
- EXPORT TABLE testTbl
- TO "hdfs://hdfs_host:port/a/b/c"
- WITH BROKER "broker_name"
- (
- "username" = "xxx",
- "password" = "yyy"
- );
- ```
-
- `WITH BROKER` and following Property Map are used to provide Broker's related information.
-
-3. Create Repository
-
- When users need to use the backup and restore function, they need to first create a "repository" with the `CREATE REPOSITORY` command,and the broker metadata and related information are recorded in the warehouse metadata.
- Subsequent backup and restore operations will use Broker to back up data to this warehouse, or read data from this warehouse to restore to Doris. Examples are as follows:
-
- ```
- CREATE REPOSITORY `bos_repo`
- WITH BROKER `broker_name`
- ON LOCATION "bos://doris_backup"
- PROPERTIES
- (
- "bos_endpoint" = "http://gz.bcebos.com",
- "bos_accesskey" = "xxxxxxxxxxxxxxxxxxxxxxxxxx",
- "bos_secret_accesskey" = "yyyyyyyyyyyyyyyyyyyy"
- );
- ```
-
- `WITH BROKER` and following Property Map are used to provide Broker's related information.
-
-
-## Broker Information
-
-Broker information includes two parts: ** Broker name ** and ** Certification information **. The general syntax is as follows:
-
-```
-WITH BROKER "broker_name"
-(
- "username" = "xxx",
- "password" = "yyy",
- "other_prop" = "prop_value",
- ...
-);
-```
-
-### Broker Name
-
-Usually the user needs to specify an existing Broker Name through the `WITH BROKER" broker_name "` clause in the operation command.
-Broker Name is a name that the user specifies when adding a Broker process through the ALTER SYSTEM ADD BROKER command.
-A name usually corresponds to one or more broker processes. Doris selects available broker processes based on the name.
-You can use the `SHOW BROKER` command to view the Brokers that currently exist in the cluster.
-
-**Note: Broker Name is just a user-defined name and does not represent the type of Broker.**
-
-### Certification Information
-
-Different broker types and different access methods need to provide different authentication information.
-Authentication information is usually provided as a Key-Value in the Property Map after `WITH BROKER" broker_name "`.
-
-#### Community HDFS
-
-1. Simple Authentication
-
- Simple authentication means that Hadoop configures `hadoop.security.authentication` to` simple`.
-
- Use system users to access HDFS. Or add in the environment variable started by Broker: ```HADOOP_USER_NAME```.
-
- ```
- (
- "username" = "user",
- "password" = ""
- );
- ```
-
- Just leave the password blank.
-
-2. Kerberos Authentication
-
- The authentication method needs to provide the following information::
-
- * `hadoop.security.authentication`: Specify the authentication method as kerberos.
- * `kerberos_principal`: Specify the principal of kerberos.
- * `kerberos_keytab`: Specify the path to the keytab file for kerberos. The file must be an absolute path to a file on the server where the broker process is located. And can be accessed by the Broker process.
- * `kerberos_keytab_content`: Specify the content of the keytab file in kerberos after base64 encoding. You can choose one of these with `kerberos_keytab` configuration.
-
- Examples are as follows:
-
- ```
- (
- "hadoop.security.authentication" = "kerberos",
- "kerberos_principal" = "doris@YOUR.COM",
- "kerberos_keytab" = "/home/doris/my.keytab"
- )
- ```
- ```
- (
- "hadoop.security.authentication" = "kerberos",
- "kerberos_principal" = "doris@YOUR.COM",
- "kerberos_keytab_content" = "ASDOWHDLAWIDJHWLDKSALDJSDIWALD"
- )
- ```
- If Kerberos authentication is used, the [krb5.conf](https://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html) file is required when deploying the Broker process.
- The krb5.conf file contains Kerberos configuration information, Normally, you should install your krb5.conf file in the directory /etc. You can override the default location by setting the environment variable KRB5_CONFIG.
- An example of the contents of the krb5.conf file is as follows:
- ```
- [libdefaults]
- default_realm = DORIS.HADOOP
- default_tkt_enctypes = des3-hmac-sha1 des-cbc-crc
- default_tgs_enctypes = des3-hmac-sha1 des-cbc-crc
- dns_lookup_kdc = true
- dns_lookup_realm = false
-
- [realms]
- DORIS.HADOOP = {
- kdc = kerberos-doris.hadoop.service:7005
- }
- ```
-
-3. HDFS HA Mode
-
- This configuration is used to access HDFS clusters deployed in HA mode.
-
- * `dfs.nameservices`: Specify the name of the hdfs service, custom, such as "dfs.nameservices" = "my_ha".
- * `dfs.ha.namenodes.xxx`: Custom namenode names. Multiple names are separated by commas, where xxx is the custom name in `dfs.nameservices`, such as" dfs.ha.namenodes.my_ha "=" my_nn ".
- * `dfs.namenode.rpc-address.xxx.nn`: Specify the rpc address information of namenode, Where nn represents the name of the namenode configured in `dfs.ha.namenodes.xxx`, such as: "dfs.namenode.rpc-address.my_ha.my_nn" = "host:port".
- * `dfs.client.failover.proxy.provider`: Specify the provider for the client to connect to the namenode. The default is: org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider.
-
- Examples are as follows:
-
- ```
- (
- "dfs.nameservices" = "my_ha",
- "dfs.ha.namenodes.my_ha" = "my_namenode1, my_namenode2",
- "dfs.namenode.rpc-address.my_ha.my_namenode1" = "nn1_host:rpc_port",
- "dfs.namenode.rpc-address.my_ha.my_namenode2" = "nn2_host:rpc_port",
- "dfs.client.failover.proxy.provider" = "org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider"
- )
- ```
-
- The HA mode can be combined with the previous two authentication methods for cluster access. If you access HA HDFS with simple authentication:
-
- ```
- (
- "username"="user",
- "password"="passwd",
- "dfs.nameservices" = "my_ha",
- "dfs.ha.namenodes.my_ha" = "my_namenode1, my_namenode2",
- "dfs.namenode.rpc-address.my_ha.my_namenode1" = "nn1_host:rpc_port",
- "dfs.namenode.rpc-address.my_ha.my_namenode2" = "nn2_host:rpc_port",
- "dfs.client.failover.proxy.provider" = "org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider"
- )
- ```
- The configuration for accessing the HDFS cluster can be written to the hdfs-site.xml file. When users use the Broker process to read data from the HDFS cluster, they only need to fill in the cluster file path and authentication information.
-
-#### Baidu Object Storage BOS
-
-**(Open source version is not supported)**
-
-1. Access via AK / SK
-
- * AK/SK: Access Key and Secret Key. You can check the user's AK / SK in Baidu Cloud Security Certification Center.
- * Region Endpoint: Endpoint of the BOS region.
- * For the regions supported by BOS and corresponding Endpoints, please see [Get access domain name](https://cloud.baidu.com/doc/BOS/s/Ck1rk80hn#%E8%8E%B7%E5%8F%96%E8%AE %BF%E9%97%AE%E5%9F%9F%E5%90%8D)
-
- Examples are as follows:
-
- ```
- (
- "bos_endpoint" = "http://bj.bcebos.com",
- "bos_accesskey" = "xxxxxxxxxxxxxxxxxxxxxxxxxx",
- "bos_secret_accesskey" = "yyyyyyyyyyyyyyyyyyyyyyyyyy"
- )
- ```
-
-#### Baidu HDFS/AFS
-
-**（Open source version is not supported）**
-
-Baidu AFS and HDFS only support simple authentication access using UGI. Examples are as follows:
-
-```
-(
- "username" = "user",
- "password" = "passwd"
-);
-```
-
-User and passwd are UGI configurations for Hadoop.
diff --git a/docs/en/administrator-guide/bucket-shuffle-join.md b/docs/en/administrator-guide/bucket-shuffle-join.md
deleted file mode 100644
index a2edaef4fc..0000000000
--- a/docs/en/administrator-guide/bucket-shuffle-join.md
+++ /dev/null
@@ -1,105 +0,0 @@
----
-{
- "title": "Bucket Shuffle Join",
- "language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Bucket Shuffle Join
-
-Bucket Shuffle Join is a new function officially added in Doris 0.14. The purpose is to provide local optimization for some join queries to reduce the time-consuming of data transmission between nodes and speed up the query.
-
-It's design, implementation can be referred to [ISSUE 4394](https://github.com/apache/incubator-doris/issues/4394).
-
-## Noun Interpretation
-
-* FE: Frontend, the front-end node of Doris. Responsible for metadata management and request access.
-* BE: Backend, Doris's back-end node. Responsible for query execution and data storage.
-* Left table: the left table in join query. Perform probe expr. The order can be adjusted by join reorder.
-* Right table: the right table in join query. Perform build expr The order can be adjusted by join reorder.
-
-## Principle
-The conventional distributed join methods supported by Doris is: `Shuffle Join, Broadcast Join`. Both of these join will lead to some network overhead.
-
-For example, there are join queries for table A and table B. the join method is hashjoin. The cost of different join types is as follows:
-* **Broadcast Join**: If table a has three executing hashjoinnodes according to the data distribution, table B needs to be sent to the three HashJoinNode. Its network overhead is `3B `, and its memory overhead is `3B`.
-* **Shuffle Join**: Shuffle join will distribute the data of tables A and B to the nodes of the cluster according to hash calculation, so its network overhead is `A + B` and memory overhead is `B`.
-
-The data distribution information of each Doris table is saved in FE. If the join statement hits the data distribution column of the left table, we should use the data distribution information to reduce the network and memory overhead of the join query. This is the source of the idea of bucket shuffle join.
-
-
-
-The picture above shows how the Bucket Shuffle Join works. The SQL query is A table join B table. The equivalent expression of join hits the data distribution column of A. According to the data distribution information of table A. Bucket Shuffle Join sends the data of table B to the corresponding data storage and calculation node of table A. The cost of Bucket Shuffle Join is as follows:
-
-* network cost: ``` B < min(3B, A + B) ```
-
-* memory cost: ``` B <= min(3B, B) ```
-
-Therefore, compared with Broadcast Join and Shuffle Join, Bucket shuffle join has obvious performance advantages. It reduces the time-consuming of data transmission between nodes and the memory cost of join. Compared with Doris's original join method, it has the following advantages
-
-* First of all, Bucket Shuffle Join reduces the network and memory cost which makes some join queries have better performance. Especially when FE can perform partition clipping and bucket clipping of the left table.
-* Secondly, unlike Colorate Join, it is not intrusive to the data distribution of tables, which is transparent to users. There is no mandatory requirement for the data distribution of the table, which is not easy to lead to the problem of data skew.
-* Finally, it can provide more optimization space for join reorder.
-
-## Usage
-
-### Set session variable
-
-Set session variable `enable_bucket_shuffle_join` to `true`, FE will automatically plan queries that can be converted to Bucket Shuffle Join.
-
-```
-set enable_bucket_shuffle_join = true;
-```
-
-In FE's distributed query planning, the priority order is Colorate Join -> Bucket Shuffle Join -> Broadcast Join -> Shuffle Join. However, if the user explicitly hints the type of join, for example:
-
-```
-select * from test join [shuffle] baseall on test.k1 = baseall.k1;
-```
-the above order of preference will not take effect.
-
-The session variable is set to `true` by default in version 0.14, while it needs to be set to `true` manually in version 0.13.
-
-### View the type of join
-
-You can use the `explain` command to check whether the join is a Bucket Shuffle Join
-
-```
-| 2:HASH JOIN [...]
-| | join op: INNER JOIN (BUCKET_SHUFFLE) [...]
-| | hash predicates: [...]
-| | colocate: false, reason: table not in the same group [...]
-| | equal join conjunct: `test`.`k1` = `baseall`.`k1`
-```
-
-The join type indicates that the join method to be used is:`BUCKET_SHUFFLE`.
-
-## Planning rules of Bucket Shuffle Join
-
-In most scenarios, users only need to turn on the session variable by default to transparently use the performance improvement brought by this join method. However, if we understand the planning rules of Bucket Shuffle Join, we can use it to write more efficient SQL.
-
-* Bucket Shuffle Join only works when the join condition is equivalent. The reason is similar to Colorate Join. They all rely on hash to calculate the determined data distribution.
-* The bucket column of two tables is included in the equivalent join condition. When the bucket column of the left table is an equivalent join condition, it has a high probability of being planned as a Bucket Shuffle Join.
-* Because the hash values of different data types have different calculation results. Bucket Shuffle Join requires that the bucket column type of the left table and the equivalent join column type of the right table should be consistent, otherwise the corresponding planning cannot be carried out.
-* Bucket Shuffle Join only works on Doris native OLAP tables. For ODBC, MySQL, ES External Table, when they are used as left tables, they cannot be planned as Bucket Shuffle Join.
-* For partitioned tables, because the data distribution rules of each partition may be different, the Bucket Shuffle Join can only guarantee that the left table is a single partition. Therefore, in SQL execution, we need to use the `where` condition as far as possible to make the partition clipping policy effective.
-* If the left table is a colorate table, the data distribution rules of each partition are determined. So the bucket shuffle join can perform better on the colorate table.
diff --git a/docs/en/administrator-guide/colocation-join.md b/docs/en/administrator-guide/colocation-join.md
deleted file mode 100644
index 390e2f27e6..0000000000
--- a/docs/en/administrator-guide/colocation-join.md
+++ /dev/null
@@ -1,409 +0,0 @@
----
-{
- "title": "Colocation Join",
- "language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Colocation Join
-
-Colocation Join is a new feature introduced in Doris 0.9. The purpose of this paper is to provide local optimization for some Join queries to reduce data transmission time between nodes and speed up queries.
-
-The original design, implementation and effect can be referred to [ISSUE 245](https://github.com/apache/incubator-doris/issues/245).
-
-The Colocation Join function has undergone a revision, and its design and use are slightly different from the original design. This document mainly introduces Colocation Join's principle, implementation, usage and precautions.
-
-## Noun Interpretation
-
-* FE: Frontend, the front-end node of Doris. Responsible for metadata management and request access.
-* BE: Backend, Doris's back-end node. Responsible for query execution and data storage.
-* Colocation Group (CG): A CG contains one or more tables. Tables within the same group have the same Colocation Group Schema and the same data fragmentation distribution.
-* Colocation Group Schema (CGS): Used to describe table in a CG and general Schema information related to Colocation. Including bucket column type, bucket number and copy number.
-
-## Principle
-
-The Colocation Join function is to make a CG of a set of tables with the same CGS. Ensure that the corresponding data fragments of these tables will fall on the same BE node. When tables in CG perform Join operations on bucket columns, local data Join can be directly performed to reduce data transmission time between nodes.
-
-The data of a table will eventually fall into a barrel according to the barrel column value Hash and the number of barrels modeled. Assuming that the number of buckets in a table is 8, there are eight buckets `[0, 1, 2, 3, 4, 5, 6, 7] `Buckets'. We call such a sequence a `Buckets Sequence`. Each Bucket has one or more Tablets. When a table is a single partitioned table, there is only one Tablet in a Bucket. If it is a multi-partition table, there will be more than one.
-
-In order for a table to have the same data distribution, the table in the same CG must ensure the following attributes are the same:
-
-1. Barrel row and number of barrels
-
- Bucket column, that is, the column specified in `DISTRIBUTED BY HASH (col1, col2,...)'in the table building statement. Bucket columns determine which column values are used to Hash data from a table into different Tablets. Tables in the same CG must ensure that the type and number of barrel columns are identical, and the number of barrels is identical, so that the data fragmentation of multiple tables can be controlled one by one.
-
-2. Number of copies
-
- The number of copies of all partitions of all tables in the same CG must be the same. If inconsistent, there may be a copy of a Tablet, and there is no corresponding copy of other table fragments on the same BE.
-
-Tables in the same CG do not require consistency in the number, scope, and type of partition columns.
-
-After fixing the number of bucket columns and buckets, the tables in the same CG will have the same Buckets Sequence. The number of replicas determines the number of replicas of Tablets in each bucket, which BE they are stored on. Suppose that Buckets Sequence is `[0, 1, 2, 3, 4, 5, 6, 7] `, and that BE nodes have `[A, B, C, D] `4. A possible distribution of data is as follows:
-
-```
-+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
-| 0 | | 1 | | 2 | | 3 | | 4 | | 5 | | 6 | | 7 |
-+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
-| A | | B | | C | | D | | A | | B | | C | | D |
-| | | | | | | | | | | | | | | |
-| B | | C | | D | | A | | B | | C | | D | | A |
-| | | | | | | | | | | | | | | |
-| C | | D | | A | | B | | C | | D | | A | | B |
-+---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+
-```
-
-The data of all tables in CG will be uniformly distributed according to the above rules, which ensures that the data with the same barrel column value are on the same BE node, and local data Join can be carried out.
-
-## Usage
-
-### Establishment of tables
-
-When creating a table, you can specify the attribute `"colocate_with"="group_name"` in `PROPERTIES`, which means that the table is a Colocation Join table and belongs to a specified Colocation Group.
-
-Examples:
-
-```
-CREATE TABLE tbl (k1 int, v1 int sum)
-DISTRIBUTED BY HASH(k1)
-BUCKETS 8
-PROPERTIES(
- "colocate_with" = "group1"
-);
-```
-
-If the specified group does not exist, Doris automatically creates a group that contains only the current table. If the Group already exists, Doris checks whether the current table satisfies the Colocation Group Schema. If satisfied, the table is created and added to the Group. At the same time, tables create fragments and replicas based on existing data distribution rules in Groups.
-Group belongs to a database, and its name is unique in a database. Internal storage is the full name of Group `dbId_groupName`, but users only perceive groupName.
-
-### Delete table
-
-When the last table in Group is deleted completely (deleting completely means deleting from the recycle bin). Usually, when a table is deleted by the `DROP TABLE` command, it will be deleted after the default one-day stay in the recycle bin, and the group will be deleted automatically.
-
-### View Group
-
-The following command allows you to view the existing Group information in the cluster.
-
-```
-SHOW PROC '/colocation_group';
-
-+-------------+--------------+--------------+------------+----------------+----------+----------+
-| GroupId | GroupName | TableIds | BucketsNum | ReplicationNum | DistCols | IsStable |
-+-------------+--------------+--------------+------------+----------------+----------+----------+
-| 10005.10008 | 10005_group1 | 10007, 10040 | 10 | 3 | int(11) | true |
-+-------------+--------------+--------------+------------+----------------+----------+----------+
-```
-
-* GroupId: The unique identity of a group's entire cluster, with DB ID in the first half and group ID in the second half.
-* GroupName: The full name of Group.
-* Tablet Ids: The group contains a list of Tables'ID.
-* Buckets Num: Number of barrels.
-* Replication Num: Number of copies.
-* DistCols: Distribution columns,
-* IsStable: Is the group stable (for the definition of stability, see section `Collocation replica balancing and repair').
-
-You can further view the data distribution of a group by following commands:
-
-```
-SHOW PROC '/colocation_group/10005.10008';
-
-+-------------+---------------------+
-| BucketIndex | BackendIds |
-+-------------+---------------------+
-| 0 | 10004, 10002, 10001 |
-| 1 | 10003, 10002, 10004 |
-| 2 | 10002, 10004, 10001 |
-| 3 | 10003, 10002, 10004 |
-| 4 | 10002, 10004, 10003 |
-| 5 | 10003, 10002, 10001 |
-| 6 | 10003, 10004, 10001 |
-| 7 | 10003, 10004, 10002 |
-+-------------+---------------------+
-```
-
-* BucketIndex: Subscript to the bucket sequence.
-* Backend Ids: A list of BE node IDs where data fragments are located in buckets.
-
-> The above commands require ADMIN privileges. Normal user view is not supported at this time.
-
-### Modify Colocate Group
-
-You can modify the Colocation Group property of a table that has been created. Examples:
-
-`ALTER TABLE tbl SET ("colocate_with" = "group2");`
-
-* If the table has not previously specified a Group, the command checks the Schema and adds the table to the Group (if the Group does not exist, it will be created).
-* If other groups are specified before the table, the command first removes the table from the original group and adds a new group (if the group does not exist, it will be created).
-
-You can also delete the Colocation attribute of a table by following commands:
-
-`ALTER TABLE tbl SET ("colocate_with" = "");`
-
-### Other related operations
-
-When an ADD PARTITION is added to a table with a Colocation attribute and the number of copies is modified, Doris checks whether the modification violates the Colocation Group Schema and rejects it if it does.
-
-## Colocation Duplicate Balancing and Repair
-
-Copy distribution of Colocation tables needs to follow the distribution specified in Group, so it is different from common fragmentation in replica repair and balancing.
-
-Group itself has a Stable attribute, when Stable is true, which indicates that all fragments of the table in the current Group are not changing, and the Colocation feature can be used normally. When Stable is false, it indicates that some tables in Group are being repaired or migrated. At this time, Colocation Join of related tables will degenerate into ordinary Join.
-
-### Replica Repair
-
-Copies can only be stored on specified BE nodes. So when a BE is unavailable (downtime, Decommission, etc.), a new BE is needed to replace it. Doris will first look for the BE with the lowest load to replace it. After replacement, all data fragments on the old BE in the Bucket will be repaired. During the migration process, Group is marked Unstable.
-
-### Duplicate Equilibrium
-
-Doris will try to distribute the fragments of the Collocation table evenly across all BE nodes. For the replica balancing of common tables, the granularity is single replica, that is to say, it is enough to find BE nodes with lower load for each replica alone. The equilibrium of the Colocation table is at the Bucket level, where all replicas within a Bucket migrate together. We adopt a simple equalization algorithm, which distributes Buckets Sequence evenly on all BEs, regardless of the [...]
-
-> Note 1: Current Colocation replica balancing and repair algorithms may not work well for heterogeneous deployed Oris clusters. The so-called heterogeneous deployment, that is, the BE node's disk capacity, number, disk type (SSD and HDD) is inconsistent. In the case of heterogeneous deployment, small BE nodes and large BE nodes may store the same number of replicas.
->
-> Note 2: When a group is in an Unstable state, the Join of the table in it will degenerate into a normal Join. At this time, the query performance of the cluster may be greatly reduced. If you do not want the system to balance automatically, you can set the FE configuration item `disable_colocate_balance` to prohibit automatic balancing. Then open it at the right time. (See Section `Advanced Operations` for details)
-
-## Query
-
-The Colocation table is queried in the same way as ordinary tables, and users do not need to perceive Colocation attributes. If the Group in which the Colocation table is located is in an Unstable state, it will automatically degenerate to a normal Join.
-
-Examples are given to illustrate:
-
-Table 1:
-
-```
-CREATE TABLE `tbl1` (
- `k1` date NOT NULL COMMENT "",
- `k2` int(11) NOT NULL COMMENT "",
- `v1` int(11) SUM NOT NULL COMMENT ""
-) ENGINE=OLAP
-AGGREGATE KEY(`k1`, `k2`)
-PARTITION BY RANGE(`k1`)
-(
- PARTITION p1 VALUES LESS THAN ('2019-05-31'),
- PARTITION p2 VALUES LESS THAN ('2019-06-30')
-)
-DISTRIBUTED BY HASH(`k2`) BUCKETS 8
-PROPERTIES (
- "colocate_with" = "group1"
-);
-```
-
-Table 2:
-
-```
-CREATE TABLE `tbl2` (
- `k1` datetime NOT NULL COMMENT "",
- `k2` int(11) NOT NULL COMMENT "",
- `v1` double SUM NOT NULL COMMENT ""
-) ENGINE=OLAP
-AGGREGATE KEY(`k1`, `k2`)
-DISTRIBUTED BY HASH(`k2`) BUCKETS 8
-PROPERTIES (
- "colocate_with" = "group1"
-);
-```
-
-View the query plan:
-
-```
-DESC SELECT * FROM tbl1 INNER JOIN tbl2 ON (tbl1.k2 = tbl2.k2);
-
-+----------------------------------------------------+
-| Explain String |
-+----------------------------------------------------+
-| PLAN FRAGMENT 0 |
-| OUTPUT EXPRS:`tbl1`.`k1` | |
-| PARTITION: RANDOM |
-| |
-| RESULT SINK |
-| |
-| 2:HASH JOIN |
-| | join op: INNER JOIN |
-| | hash predicates: |
-| | colocate: true |
-| | `tbl1`.`k2` = `tbl2`.`k2` |
-| | tuple ids: 0 1 |
-| | |
-| |----1:OlapScanNode |
-| | TABLE: tbl2 |
-| | PREAGGREGATION: OFF. Reason: null |
-| | partitions=0/1 |
-| | rollup: null |
-| | buckets=0/0 |
-| | cardinality=-1 |
-| | avgRowSize=0.0 |
-| | numNodes=0 |
-| | tuple ids: 1 |
-| | |
-| 0:OlapScanNode |
-| TABLE: tbl1 |
-| PREAGGREGATION: OFF. Reason: No AggregateInfo |
-| partitions=0/2 |
-| rollup: null |
-| buckets=0/0 |
-| cardinality=-1 |
-| avgRowSize=0.0 |
-| numNodes=0 |
-| tuple ids: 0 |
-+----------------------------------------------------+
-```
-
-If Colocation Join works, the Hash Join Node will show `colocate: true`.
-
-If not, the query plan is as follows:
-
-```
-+----------------------------------------------------+
-| Explain String |
-+----------------------------------------------------+
-| PLAN FRAGMENT 0 |
-| OUTPUT EXPRS:`tbl1`.`k1` | |
-| PARTITION: RANDOM |
-| |
-| RESULT SINK |
-| |
-| 2:HASH JOIN |
-| | join op: INNER JOIN (BROADCAST) |
-| | hash predicates: |
-| | colocate: false, reason: group is not stable |
-| | `tbl1`.`k2` = `tbl2`.`k2` |
-| | tuple ids: 0 1 |
-| | |
-| |----3:EXCHANGE |
-| | tuple ids: 1 |
-| | |
-| 0:OlapScanNode |
-| TABLE: tbl1 |
-| PREAGGREGATION: OFF. Reason: No AggregateInfo |
-| partitions=0/2 |
-| rollup: null |
-| buckets=0/0 |
-| cardinality=-1 |
-| avgRowSize=0.0 |
-| numNodes=0 |
-| tuple ids: 0 |
-| |
-| PLAN FRAGMENT 1 |
-| OUTPUT EXPRS: |
-| PARTITION: RANDOM |
-| |
-| STREAM DATA SINK |
-| EXCHANGE ID: 03 |
-| UNPARTITIONED |
-| |
-| 1:OlapScanNode |
-| TABLE: tbl2 |
-| PREAGGREGATION: OFF. Reason: null |
-| partitions=0/1 |
-| rollup: null |
-| buckets=0/0 |
-| cardinality=-1 |
-| avgRowSize=0.0 |
-| numNodes=0 |
-| tuple ids: 1 |
-+----------------------------------------------------+
-```
-
-The HASH JOIN node displays the corresponding reason: `colocate: false, reason: group is not stable`. At the same time, an EXCHANGE node will be generated.
-
-
-## Advanced Operations
-
-### FE Configuration Item
-
-* disable\_colocate\_relocate
-
-Whether to close Doris's automatic Colocation replica repair. The default is false, i.e. not closed. This parameter only affects the replica repair of the Colocation table, but does not affect the normal table.
-
-* disable\_colocate\_balance
-
-Whether to turn off automatic Colocation replica balancing for Doris. The default is false, i.e. not closed. This parameter only affects the replica balance of the Collocation table, but does not affect the common table.
-
-User can set these configurations at runtime. See `HELP ADMIN SHOW CONFIG;` and `HELP ADMIN SET CONFIG;`.
-
-* disable\_colocate\_join
-
-Whether to turn off the Colocation Join function or not. In 0.10 and previous versions, the default is true, that is, closed. In a later version, it will default to false, that is, open.
-
-* use\_new\_tablet\_scheduler
-
-In 0.10 and previous versions, the new replica scheduling logic is incompatible with the Colocation Join function, so in 0.10 and previous versions, if `disable_colocate_join = false`, you need to set `use_new_tablet_scheduler = false`, that is, close the new replica scheduler. In later versions, `use_new_tablet_scheduler` will be equal to true.
-
-###HTTP Restful API
-
-Doris provides several HTTP Restful APIs related to Colocation Join for viewing and modifying Colocation Group.
-
-The API is implemented on the FE side and accessed using `fe_host: fe_http_port`. ADMIN privileges are required.
-
-1. View all Colocation information for the cluster
-
- ```
- GET /api/colocate
-
- Return the internal Colocation info in JSON format:
-
- {
- "msg": "success",
- "code": 0,
- "data": {
- "infos": [
- ["10003.12002", "10003_group1", "10037, 10043", "1", "1", "int(11)", "true"]
- ],
- "unstableGroupIds": [],
- "allGroupIds": [{
- "dbId": 10003,
- "grpId": 12002
- }]
- },
- "count": 0
- }
- ```
-2. Mark Group as Stable or Unstable
-
- * Mark as Stable
-
- ```
- POST /api/colocate/group_stable?db_id=10005&group_id=10008
-
- Returns: 200
- ```
-
- * Mark as Unstable
-
- ```
- DELETE /api/colocate/group_stable?db_id=10005&group_id=10008
-
- Returns: 200
- ```
-
-3. Setting Data Distribution for Group
-
- The interface can force the number distribution of a group.
-
- ```
- POST /api/colocate/bucketseq?db_id=10005&group_id=10008
-
- Body:
- [[10004,10002],[10003,10002],[10002,10004],[10003,10002],[10002,10004],[10003,10002],[10003,10004],[10003,10004],[10003,10004],[10002,10004]]
-
- Returns: 200
- ```
- Body is a Buckets Sequence represented by a nested array and the ID of the BE where the fragments are distributed in each Bucket.
-
- Note that using this command, you may need to set the FE configuration `disable_colocate_relocate` and `disable_colocate_balance` to true. That is to shut down the system for automatic Colocation replica repair and balancing. Otherwise, it may be automatically reset by the system after modification.
diff --git a/docs/en/administrator-guide/config/be_config.md b/docs/en/administrator-guide/config/be_config.md
deleted file mode 100644
index aa5a4dce50..0000000000
--- a/docs/en/administrator-guide/config/be_config.md
+++ /dev/null
@@ -1,1526 +0,0 @@
----
-{
- "title": "BE Configuration",
- "language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-<!-- Please sort the configuration alphabetically -->
-
-# BE Configuration
-
-This document mainly introduces the relevant configuration items of BE.
-
-The BE configuration file `be.conf` is usually stored in the `conf/` directory of the BE deployment path. In version 0.14, another configuration file `be_custom.conf` will be introduced. The configuration file is used to record the configuration items that are dynamically configured and persisted by the user during operation.
-
-After the BE process is started, it will read the configuration items in `be.conf` first, and then read the configuration items in `be_custom.conf`. The configuration items in `be_custom.conf` will overwrite the same configuration items in `be.conf`.
-
-The location of the `be_custom.conf` file can be configured in `be.conf` through the `custom_config_dir` configuration item.
-
-## View configuration items
-
-Users can view the current configuration items by visiting BE's web page:
-
-`http://be_host:be_webserver_port/varz`
-
-## Set configuration items
-
-There are two ways to configure BE configuration items:
-
-1. Static configuration
-
- Add and set configuration items in the `conf/be.conf` file. The configuration items in `be.conf` will be read when BE starts. Configuration items not in `be.conf` will use default values.
-
-2. Dynamic configuration
-
- After BE starts, the configuration items can be dynamically set with the following commands.
-
- ```
- curl -X POST http://{be_ip}:{be_http_port}/api/update_config?{key}={value}'
- ```
-
- In version 0.13 and before, the configuration items modified in this way will become invalid after the BE process restarts. In 0.14 and later versions, the modified configuration can be persisted through the following command. The modified configuration items are stored in the `be_custom.conf` file.
-
- ```
- curl -X POST http://{be_ip}:{be_http_port}/api/update_config?{key}={value}&persis=true'
- ```
-
-## Examples
-
-1. Modify `max_compaction_concurrency` statically
-
- By adding in the `be.conf` file:
-
- ```max_compaction_concurrency=5```
-
- Then restart the BE process to take effect the configuration.
-
-2. Modify `streaming_load_max_mb` dynamically
-
- After BE starts, the configuration item `streaming_load_max_mb` is dynamically set by the following command:
-
- ```
- curl -X POST http://{be_ip}:{be_http_port}/api/update_config?streaming_load_max_mb=1024
- ```
-
- The return value is as follows, indicating that the setting is successful.
-
- ```
- {
- "status": "OK",
- "msg": ""
- }
- ```
-
- The configuration will become invalid after the BE restarts. If you want to persist the modified results, use the following command:
-
- ```
- curl -X POST http://{be_ip}:{be_http_port}/api/update_config?streaming_load_max_mb=1024\&persist=true
- ```
-
-## Configurations
-
-### `alter_tablet_worker_count`
-
-Default: 3
-
-The number of threads making schema changes
-
-### `base_compaction_check_interval_seconds`
-
-Default: 60 （s）
-
-BaseCompaction thread polling interval
-
-### `base_compaction_interval_seconds_since_last_operation`
-
-Default: 86400
-
-One of the triggering conditions of BaseCompaction: the interval since the last BaseCompaction
-
-### `base_compaction_num_cumulative_deltas`
-
-Default: 5
-
-One of the triggering conditions of BaseCompaction: The limit of the number of Cumulative files to be reached. After reaching this limit, BaseCompaction will be triggered
-
-### base_compaction_trace_threshold
-
-* Type: int32
-* Description: Threshold to logging base compaction's trace information, in seconds
-* Default value: 10
-
-Base compaction is a long time cost background task, this configuration is the threshold to logging trace information. Trace information in log file looks like:
-
-```
-W0610 11:26:33.804431 56452 storage_engine.cpp:552] Trace:
-0610 11:23:03.727535 (+ 0us) storage_engine.cpp:554] start to perform base compaction
-0610 11:23:03.728961 (+ 1426us) storage_engine.cpp:560] found best tablet 546859
-0610 11:23:03.728963 (+ 2us) base_compaction.cpp:40] got base compaction lock
-0610 11:23:03.729029 (+ 66us) base_compaction.cpp:44] rowsets picked
-0610 11:24:51.784439 (+108055410us) compaction.cpp:46] got concurrency lock and start to do compaction
-0610 11:24:51.784818 (+ 379us) compaction.cpp:74] prepare finished
-0610 11:26:33.359265 (+101574447us) compaction.cpp:87] merge rowsets finished
-0610 11:26:33.484481 (+125216us) compaction.cpp:102] output rowset built
-0610 11:26:33.484482 (+ 1us) compaction.cpp:106] check correctness finished
-0610 11:26:33.513197 (+ 28715us) compaction.cpp:110] modify rowsets finished
-0610 11:26:33.513300 (+ 103us) base_compaction.cpp:49] compaction finished
-0610 11:26:33.513441 (+ 141us) base_compaction.cpp:56] unused rowsets have been moved to GC queue
-Metrics: {"filtered_rows":0,"input_row_num":3346807,"input_rowsets_count":42,"input_rowsets_data_size":1256413170,"input_segments_num":44,"merge_rowsets_latency_us":101574444,"merged_rows":0,"output_row_num":3346807,"output_rowset_data_size":1228439659,"output_segments_num":6}
-```
-
-### `base_compaction_write_mbytes_per_sec`
-
-Default: 5（MB）
-
-Maximum disk write speed per second of BaseCompaction task
-
-### `base_cumulative_delta_ratio`
-
-Default: 0.3 （30%）
-
-One of the trigger conditions of BaseCompaction: Cumulative file size reaches the proportion of Base file
-
-### `be_port`
-
-* Type: int32
-* Description: The port of the thrift server on BE which used to receive requests from FE
-* Default value: 9060
-
-### `be_service_threads`
-
-* Type: int32
-* Description: The number of execution threads of the thrift server service on BE which represents the number of threads that can be used to execute FE requests.
-* Default value: 64
-
-### `brpc_max_body_size`
-
-This configuration is mainly used to modify the parameter `max_body_size` of brpc.
-
-Sometimes the query fails and an error message of `body_size is too large` will appear in the BE log. This may happen when the SQL mode is "multi distinct + no group by + more than 1T of data".
-
-This error indicates that the packet size of brpc exceeds the configured value. At this time, you can avoid this error by increasing the configuration.
-
-### `brpc_socket_max_unwritten_bytes`
-
-This configuration is mainly used to modify the parameter `socket_max_unwritten_bytes` of brpc.
-
-Sometimes the query fails and an error message of `The server is overcrowded` will appear in the BE log. This means there are too many messages to buffer at the sender side, which may happen when the SQL needs to send large bitmap value. You can avoid this error by increasing the configuration.
-
-### `transfer_data_by_brpc_attachment`
-
-* Type: bool
-* Description: This configuration is used to control whether to transfer the RowBatch in the ProtoBuf Request to the Controller Attachment and then send it through brpc. When the length of ProtoBuf Request exceeds 2G, an error will be reported: Bad request, error_text=[E1003]Fail to compress request, Putting RowBatch in Controller Attachment will be faster and avoid this error.
-* Default value: false
-
-### `brpc_num_threads`
-
-This configuration is mainly used to modify the number of bthreads for brpc. The default value is set to -1, which means the number of bthreads is #cpu-cores.
-
-User can set this configuration to a larger value to get better QPS performance. For more information, please refer to `https://github.com/apache/incubator-brpc/blob/master/docs/cn/benchmark.md`
-
-### `brpc_port`
-
-* Type: int32
-* Description: The port of BRPC on BE, used for communication between BEs
-* Default value: 9060
-
-### `buffer_pool_clean_pages_limit`
-
-默认值: 20G
-
-Clean up pages that may be saved by the buffer pool
-
-### `buffer_pool_limit`
-
-* Type: string
-* Description: The largest allocatable memory of the buffer pool
-* Default value: 20%
-
-The maximum amount of memory available in the BE buffer pool. The buffer pool is a new memory management structure of BE, which manages the memory by the buffer page and enables spill data to disk. The memory for all concurrent queries will be allocated from the buffer pool. The current buffer pool only works on **AggregationNode** and **ExchangeNode**.
-
-### `check_auto_compaction_interval_seconds`
-
-* Type: int32
-* Description: Check the configuration of auto compaction in seconds when auto compaction disabled.
-* Default value: 5
-
-### `check_consistency_worker_count`
-
-Default: 1
-
-The number of worker threads to calculate the checksum of the tablet
-
-### `chunk_reserved_bytes_limit`
-
-Default: 2147483648
-
-The reserved bytes limit of Chunk Allocator is 2GB by default. Increasing this variable can improve performance, but it will get more free memory that other modules cannot use.
-
-### `clear_transaction_task_worker_count`
-
-Default: 1
-
-Number of threads used to clean up transactions
-
-### `clone_worker_count`
-
-Default: 3
-
-Number of threads used to perform cloning tasks
-
-### `cluster_id`
-
-* Type: int32
-* Description: Configure the cluster id to which the BE belongs.
-* Default value: -1
-
-This value is usually delivered by the FE to the BE by the heartbeat, no need to configure. When it is confirmed that a BE belongs to a certain Drois cluster, it can be configured. The cluster_id file under the data directory needs to be modified to make sure same as this parament.
-
-### `column_dictionary_key_ratio_threshold`
-
-Default: 0
-
-The value ratio of string type, less than this ratio, using dictionary compression algorithm
-
-### `column_dictionary_key_size_threshold`
-
-Default: 0
-
-Dictionary compression column size, less than this value using dictionary compression algorithm
-
-### `compaction_tablet_compaction_score_factor`
-
-* Type: int32
-* Description: Coefficient for compaction score when calculating tablet score to find a tablet for compaction.
-* Default value: 1
-
-### `compaction_tablet_scan_frequency_factor`
-
-* Type: int32
-* Description: Coefficient for tablet scan frequency when calculating tablet score to find a tablet for compaction.
-* Default value: 0
-
-Tablet scan frequency can be taken into consideration when selecting an tablet for compaction and preferentially do compaction for those tablets which are scanned frequently during a latest period of time at the present.
-Tablet score can be calculated like this:
-
-tablet_score = compaction_tablet_scan_frequency_factor * tablet_scan_frequency + compaction_tablet_compaction_score_factor * compaction_score
-
-### `compaction_task_num_per_disk`
-
-* Type: int32
-* Description: The number of compaction tasks which execute in parallel for a disk(HDD).
-* Default value: 2
-
-### `compaction_task_num_per_fast_disk`
-
-* Type: int32
-* Description: The number of compaction tasks which execute in parallel for a fast disk(SSD).
-* Default value: 4
-
-### `compress_rowbatches`
-
-* Type: bool
-* Description: enable to use Snappy compression algorithm for data compression when serializing RowBatch
-* Default value: true
-
-### `create_tablet_worker_count`
-
-Default: 3
-
-Number of worker threads for BE to create a tablet
-
-### `cumulative_compaction_rounds_for_each_base_compaction_round`
-
-* Type: int32
-* Description: How many rounds of cumulative compaction for each round of base compaction when compaction tasks generation.
-* Default value: 9
-
-### `disable_auto_compaction`
-
-* Type: bool
-* Description: Whether disable automatic compaction task
-* Default value: false
-
-Generally it needs to be turned off. When you want to manually operate the compaction task in the debugging or test environment, you can turn on the configuration.
-
-### `cumulative_compaction_budgeted_bytes`
-
-Default: 104857600
-
-One of the trigger conditions of BaseCompaction: Singleton file size limit, 100MB
-
-### `cumulative_compaction_check_interval_seconds`
-
-Default: 10 (s)
-
-CumulativeCompaction thread polling interval
-
-### `cumulative_compaction_skip_window_seconds`
-
-Default: 30（s）
-
-CumulativeCompaction skips the most recently released increments to prevent compacting versions that may be queried (in case the query planning phase takes some time). Change the parameter is to set the skipped window time size
-
-### cumulative_compaction_trace_threshold
-
-* Type: int32
-* Description: Threshold to logging cumulative compaction's trace information, in seconds
-* Default value: 10
-
-Similar to `base_compaction_trace_threshold`.
-
-### disable_compaction_trace_log
-
-* Type: bool
-* Description: disable the trace log of compaction
-* Default value: true
-
-If set to true, the `cumulative_compaction_trace_threshold` and `base_compaction_trace_threshold` won't work and log is disabled.
-
-### `cumulative_compaction_policy`
-
-* Type: string
-* Description: Configure the merge policy of the cumulative compaction stage. Currently, two merge policy have been implemented, num_based and size_based.
-* Default value: size_based
-
-In detail, ordinary is the initial version of the cumulative compaction merge policy. After a cumulative compaction, the base compaction process is directly performed. The size_based policy is an optimized version of the ordinary strategy. Versions are merged only when the disk volume of the rowset is of the same order of magnitude. After the compaction, the output rowset which satisfies the conditions is promoted to the base compaction stage. In the case of a large number of small batch [...]
-
-### `cumulative_size_based_promotion_size_mbytes`
-
-* Type: int64
-* Description: Under the size_based policy, the total disk size of the output rowset of cumulative compaction exceeds this configuration size, and the rowset will be used for base compaction. The unit is m bytes.
-* Default value: 1024
-
-In general, if the configuration is less than 2G, in order to prevent the cumulative compression time from being too long, resulting in the version backlog.
-
-### `cumulative_size_based_promotion_ratio`
-
-* Type: double
-* Description: Under the size_based policy, when the total disk size of the cumulative compaction output rowset exceeds the configuration ratio of the base version rowset, the rowset will be used for base compaction.
-* Default value: 0.05
-
-Generally, it is recommended that the configuration should not be higher than 0.1 and lower than 0.02.
-
-### `cumulative_size_based_promotion_min_size_mbytes`
-
-* Type: int64
-* Description: Under the size_based strategy, if the total disk size of the output rowset of the cumulative compaction is lower than this configuration size, the rowset will not undergo base compaction and is still in the cumulative compaction process. The unit is m bytes.
-* Default value: 64
-
-Generally, the configuration is within 512m. If the configuration is too large, the size of the early base version is too small, and base compaction has not been performed.
-
-### `cumulative_size_based_compaction_lower_size_mbytes`
-
-* Type: int64
-* Description: Under the size_based strategy, when the cumulative compaction is merged, the selected rowsets to be merged have a larger disk size than this configuration, then they are divided and merged according to the level policy. When it is smaller than this configuration, merge directly. The unit is m bytes.
-* Default value: 64
-
-Generally, the configuration is within 128m. Over configuration will cause more cumulative compaction write amplification.
-
-### `custom_config_dir`
-
-Configure the location of the `be_custom.conf` file. The default is in the `conf/` directory.
-
-In some deployment environments, the `conf/` directory may be overwritten due to system upgrades. This will cause the user modified configuration items to be overwritten. At this time, we can store `be_custom.conf` in another specified directory to prevent the configuration file from being overwritten.
-
-### `default_num_rows_per_column_file_block`
-
-* Type: int32
-* Description: Configure how many rows of data are contained in a single RowBlock.
-* Default value: 1024
-
-### `default_rowset_type`
-
-* Type: string
-* Description: Identifies the storage format selected by BE by default. The configurable parameters are: "**ALPHA**", "**BETA**". Mainly play the following two roles
-1. When the storage_format of the table is set to Default, select the storage format of BE through this configuration.
-2. Select the storage format of when BE performing Compaction
-* Default value: BETA
-
-### `delete_worker_count`
-
-Default: 3
-
-Number of threads performing data deletion tasks
-
-### `disable_mem_pools`
-
-Default: false
-
-Whether to disable the memory cache pool, it is not disabled by default
-
-### `disable_storage_page_cache`
-
-* Type: bool
-* Description: Disable to use page cache for index caching, this configuration only takes effect in BETA storage format, usually it is recommended to false
-* Default value: false
-
-### `disk_stat_monitor_interval`
-
-Default: 5（s）
-
-Disk status check interval
-
-### `doris_cgroups`
-
-Default: empty
-
-Cgroups assigned to doris
-
-### `doris_max_pushdown_conjuncts_return_rate`
-
-* Type: int32
-* Description: When BE performs HashJoin, it will adopt a dynamic partitioning method to push the join condition to OlapScanner. When the data scanned by OlapScanner is larger than 32768 rows, BE will check the filter condition. If the filter rate of the filter condition is lower than this configuration, Doris will stop using the dynamic partition clipping condition for data filtering.
-* Default value: 90
-
-### `doris_max_scan_key_num`
-
-* Type: int
-* Description: Used to limit the maximum number of scan keys that a scan node can split in a query request. When a conditional query request reaches the scan node, the scan node will try to split the conditions related to the key column in the query condition into multiple scan key ranges. After that, these scan key ranges will be assigned to multiple scanner threads for data scanning. A larger value usually means that more scanner threads can be used to increase the parallelism of the s [...]
-* Default value: 1024
-
-When the concurrency cannot be improved in high concurrency scenarios, try to reduce this value and observe the impact.
-
-### `doris_scan_range_row_count`
-
-* Type: int32
-* Description: When BE performs data scanning, it will split the same scanning range into multiple ScanRanges. This parameter represents the scan data range of each ScanRange. This parameter can limit the time that a single OlapScanner occupies the io thread.
-* Default value: 524288
-
-### `doris_scanner_queue_size`
-
-* Type: int32
-* Description: The length of the RowBatch buffer queue between TransferThread and OlapScanner. When Doris performs data scanning, it is performed asynchronously. The Rowbatch scanned by OlapScanner will be placed in the scanner buffer queue, waiting for the upper TransferThread to take it away.
-* Default value: 1024
-
-### `doris_scanner_row_num`
-
-Default: 16384
-
-The maximum number of data rows returned by each scanning thread in a single execution
-
-### `doris_scanner_thread_pool_queue_size`
-
-* Type: int32
-* Description: The queue length of the Scanner thread pool. In Doris' scanning tasks, each Scanner will be submitted as a thread task to the thread pool waiting to be scheduled, and after the number of submitted tasks exceeds the length of the thread pool queue, subsequent submitted tasks will be blocked until there is a empty slot in the queue.
-* Default value: 102400
-
-### `doris_scanner_thread_pool_thread_num`
-
-* Type: int32
-* Description: The number of threads in the Scanner thread pool. In Doris' scanning tasks, each Scanner will be submitted as a thread task to the thread pool to be scheduled. This parameter determines the size of the Scanner thread pool.
-* Default value: 48
-
-### `download_low_speed_limit_kbps`
-
-Default: 50 (KB/s)
-
-Minimum download speed
-
-### `download_low_speed_time`
-
-Default: 300（s）
-
-Download time limit, 300 seconds by default
-
-### `download_worker_count`
-
-Default: 1
-
-The number of download threads, the default is 1
-
-### `drop_tablet_worker_count`
-
-Default: 3
-
-Number of threads to delete tablet
-
-### `enable_metric_calculator`
-
-Default: true
-
-If set to true, the metric calculator will run to collect BE-related indicator information, if set to false, it will not run
-
-### `enable_partitioned_aggregation`
-
-* Type: bool
-* Description: Whether the BE node implements the aggregation operation by PartitionAggregateNode, if false, AggregateNode will be executed to complete the aggregation. It is not recommended to set it to false in non-special demand scenarios.
-* Default value: true
-
-### `enable_prefetch`
-* Type: bool
-* Description: When using PartitionedHashTable for aggregation and join calculations, whether to perform HashBuket prefetch. Recommended to be set to true
-* Default value: true
-
-### `enable_quadratic_probing`
-
-* Type: bool
-* Description: When a Hash conflict occurs when using PartitionedHashTable, enable to use the square detection method to resolve the Hash conflict. If the value is false, linear detection is used to resolve the Hash conflict. For the square detection method, please refer to: [quadratic_probing](https://en.wikipedia.org/wiki/Quadratic_probing)
-* Default value: true
-
-### `enable_system_metrics`
-
-Default: true
-
-User control to turn on and off system indicators.
-
-### `enable_token_check`
-
-Default: true
-
-Used for forward compatibility, will be removed later.
-
-### `es_http_timeout_ms`
-
-Default: 5000 （ms）
-
-The timeout period for connecting to ES via http, the default is 5 seconds.
-
-### `es_scroll_keepalive`
-
-Default: 5m
-
-es scroll Keeplive hold time, the default is 5 minutes
-
-### `etl_thread_pool_queue_size`
-
-Default: 256
-
-The size of the ETL thread pool
-
-### `etl_thread_pool_size`
-
-### `exchg_node_buffer_size_bytes`
-
-* Type: int32
-* Description: The size of the Buffer queue of the ExchangeNode node, in bytes. After the amount of data sent from the Sender side is larger than the Buffer size of ExchangeNode, subsequent data sent will block until the Buffer frees up space for writing.
-* Default value: 10485760
-
-### `file_descriptor_cache_capacity`
-
-Default: 32768
-
-File handle cache capacity, 32768 file handles are cached by default.
-
-### `cache_clean_interval`
-
-Default: 1800(s)
-
-File handle cache cleaning interval, used to clean up file handles that have not been used for a long time.
-Also the clean interval of Segment Cache.
-
-### `flush_thread_num_per_store`
-
-Default: 2
-
-The number of threads used to refresh the memory table per store
-
-### `force_recovery`
-
-### `fragment_pool_queue_size`
-
-Default: 2048
-
-The upper limit of query requests that can be processed on a single node
-
-### `fragment_pool_thread_num_min`
-
-Default: 64
-
-### `fragment_pool_thread_num_max`
-
-Default: 256
-
-The above two parameters are to set the number of query threads. By default, a minimum of 64 threads will be started, subsequent query requests will dynamically create threads, and a maximum of 256 threads will be created.
-
-### `heartbeat_service_port`
-* Type: int32
-* Description: Heartbeat service port (thrift) on BE, used to receive heartbeat from FE
-* Default value: 9050
-
-### `heartbeat_service_thread_count`
-
-* Type: int32
-* Description: The number of threads that execute the heartbeat service on BE. the default is 1, it is not recommended to modify
-* Default value: 1
-
-### `ignore_broken_disk`
-
-Default: false
-
-When BE start, If there is a broken disk, BE process will exit by default.Otherwise, we will ignore the broken disk
-
-### `ignore_load_tablet_failure`
-When BE starts, it will check all the paths under the storage_root_path in configuration.
-
-`ignore_broken_disk=true`
-
-If the path does not exist or the file under the path cannot be read or written (broken disk), it will be ignored. If there are any other available paths, the startup will not be interrupted.
-
-`ignore_broken_disk=false`
-
-If the path does not exist or the file under the path cannot be read or written (bad disk), the startup will fail and exit.
-
-The default value is false.
-```
-load tablets from header failed, failed tablets size: xxx, path=xxx
-```
-
-Indicates how many tablets in the data directory failed to load. At the same time, the log will also contain specific information about the tablet that failed to load. At this time, manual intervention is required to troubleshoot the cause of the error. After investigation, there are usually two ways to recover:
-
-1. The tablet information cannot be repaired. If the other copies are normal, you can delete the wrong tablet with the `meta_tool` tool.
-2. Set `ignore_load_tablet_failure` to true, BE will ignore these faulty tablets and start normally
-
-### ignore_rowset_stale_unconsistent_delete
-
-* Type: boolean
-* Description:It is used to decide whether to delete the outdated merged rowset if it cannot form a consistent version path.
-* Default: false
-
-The merged expired rowset version path will be deleted after half an hour. In abnormal situations, deleting these versions will result in the problem that the consistent path of the query cannot be constructed. When the configuration is false, the program check is strict and the program will directly report an error and exit.
-When configured as true, the program will run normally and ignore this error. In general, ignoring this error will not affect the query, only when the merged version is dispatched by fe, -230 error will appear.
-
-### inc_rowset_expired_sec
-
-Default: 1800 （s）
-
-Import activated data, storage engine retention time, used for incremental cloning
-
-### `index_stream_cache_capacity`
-
-Default: 10737418240
-
-BloomFilter/Min/Max and other statistical information cache capacity
-
-### `kafka_broker_version_fallback`
-
-Default: 0.10.0
-
-If the dependent Kafka version is lower than the Kafka client version that routine load depends on, the value set by the fallback version kafka_broker_version_fallback will be used, and the valid values are: 0.9.0, 0.8.2, 0.8.1, 0.8.0.
-
-### `load_data_reserve_hours`
-
-Default: 4（hour）
-
-Used for mini load. The mini load data file will be deleted after this time
-
-### `load_error_log_reserve_hours`
-
-Default: 48 （hour）
-
-The load error log will be deleted after this time
-
-### `load_process_max_memory_limit_bytes`
-
-Default: 107374182400
-
-The upper limit of memory occupied by all imported threads on a single node, default value: 100G
-
-Set these default values very large, because we don't want to affect load performance when users upgrade Doris. If necessary, the user should set these configurations correctly.
-
-### `load_process_max_memory_limit_percent`
-
-Default: 80 (%)
-
-The percentage of the upper memory limit occupied by all imported threads on a single node, the default is 80%
-
-Set these default values very large, because we don't want to affect load performance when users upgrade Doris. If necessary, the user should set these configurations correctly
-
-### `log_buffer_level`
-
-Default: empty
-
-The log flushing strategy is kept in memory by default
-
-### `madvise_huge_pages`
-
-Default: false
-
-Whether to use linux memory huge pages, not enabled by default
-
-### `make_snapshot_worker_count`
-
-Default: 5
-
-Number of threads making snapshots
-
-### `max_client_cache_size_per_host`
-
-Default: 10
-
-The maximum number of client caches per host. There are multiple client caches in BE, but currently we use the same cache size configuration. If necessary, use different configurations to set up different client-side caches
-
-### `max_compaction_threads`
-
-* Type: int32
-* Description: The maximum of thread number in compaction thread pool.
-* Default value: 10
-
-### `max_consumer_num_per_group`
-
-Default: 3
-
-The maximum number of consumers in a data consumer group, used for routine load
-
-### `min_cumulative_compaction_num_singleton_deltas`
-
-Default: 5
-
-Cumulative compaction strategy: the minimum number of incremental files
-
-### `max_cumulative_compaction_num_singleton_deltas`
-
-Default: 1000
-
-Cumulative compaction strategy: the maximum number of incremental files
-
-### `max_download_speed_kbps`
-
-Default: 50000 （KB/s）
-
-Maximum download speed limit
-
-### `max_free_io_buffers`
-
-Default: 128
-
-For each io buffer size, the maximum number of buffers that IoMgr will reserve ranges from 1024B to 8MB buffers, up to about 2GB buffers.
-
-### `max_garbage_sweep_interval`
-
-Default: 3600
-
-The maximum interval for disk garbage cleaning, the default is one hour
-
-### `max_memory_sink_batch_count`
-
-Default: 20
-
-The maximum external scan cache batch count, which means that the cache max_memory_cache_batch_count * batch_size row, the default is 20, and the default value of batch_size is 1024, which means that 20 * 1024 rows will be cached
-
-### `max_percentage_of_error_disk`
-
-* Type: int32
-* Description: The storage engine allows the percentage of damaged hard disks to exist. After the damaged hard disk exceeds the changed ratio, BE will automatically exit.
-* Default value: 0
-
-### `max_pushdown_conditions_per_column`
-
-* Type: int
-* Description: Used to limit the maximum number of conditions that can be pushed down to the storage engine for a single column in a query request. During the execution of the query plan, the filter conditions on some columns can be pushed down to the storage engine, so that the index information in the storage engine can be used for data filtering, reducing the amount of data that needs to be scanned by the query. Such as equivalent conditions, conditions in IN predicates, etc. In most [...]
-* Default value: 1024
-
-* Example
-
- The table structure is `id INT, col2 INT, col3 varchar (32), ...`.
-
- The query is `... WHERE id IN (v1, v2, v3, ...)`
-
- If the number of conditions in the IN predicate exceeds the configuration, try to increase the configuration value and observe whether the query response has improved.
-
-### `max_runnings_transactions_per_txn_map`
-
-Default: 100
-
-Max number of txns for every txn_partition_map in txn manager, this is a self protection to avoid too many txns saving in manager
-
-### `max_send_batch_parallelism_per_job`
-
-* Type: int
-* Description: Max send batch parallelism for OlapTableSink. The value set by the user for `send_batch_parallelism` is not allowed to exceed `max_send_batch_parallelism_per_job`, if exceed, the value of `send_batch_parallelism` would be `max_send_batch_parallelism_per_job`.
-* Default value: 5
-
-### `max_tablet_num_per_shard`
-
-Default: 1024
-
-The number of sliced tablets, plan the layout of the tablet, and avoid too many tablet subdirectories in the repeated directory
-
-### `max_tablet_version_num`
-
-* Type: int
-* Description: Limit the number of versions of a single tablet. It is used to prevent a large number of version accumulation problems caused by too frequent import or untimely compaction. When the limit is exceeded, the import task will be rejected.
-* Default value: 500
-
-### `mem_limit`
-
-* Type: string
-* Description: Limit the percentage of the server's maximum memory used by the BE process. It is used to prevent BE memory from occupying to many the machine's memory. This parameter must be greater than 0. When the percentage is greater than 100%, the value will default to 100%.
-* Default value: 80%
-
-### `memory_limitation_per_thread_for_schema_change`
-
-Default: 2 （G）
-
-Maximum memory allowed for a single schema change task
-
-### `memory_maintenance_sleep_time_s`
-
-Default: 10
-
-Sleep time (in seconds) between memory maintenance iterations
-
-### `memory_max_alignment`
-
-Default: 16
-
-Maximum alignment memory
-
-### `read_size`
-
-Default: 8388608
-
-The read size is the read size sent to the os. There is a trade-off between latency and the whole process, getting to keep the disk busy but not introducing seeks. For 8 MB reads, random io and sequential io have similar performance
-
-### `min_buffer_size`
-
-Default: 1024
-
-Minimum read buffer size (in bytes)
-
-### `min_compaction_failure_interval_sec`
-
-* Type: int32
-* Description: During the cumulative compaction process, when the selected tablet fails to be merged successfully, it will wait for a period of time before it may be selected again. The waiting period is the value of this configuration.
-* Default value: 5
-* Unit: seconds
-
-### `min_compaction_threads`
-
-* Type: int32
-* Description: The minimum of thread number in compaction thread pool.
-* Default value: 10
-
-### `min_file_descriptor_number`
-
-Default: 60000
-
-The lower limit required by the file handle limit of the BE process
-
-### `min_garbage_sweep_interval`
-
-Default: 180
-
-The minimum interval between disk garbage cleaning, time seconds
-
-### `mmap_buffers`
-
-Default: false
-
-Whether to use mmap to allocate memory, not used by default
-
-### `num_cores`
-
-* Type: int32
-* Description: The number of CPU cores that BE can use. When the value is 0, BE will obtain the number of CPU cores of the machine from /proc/cpuinfo.
-* Default value: 0
-
-### `num_disks`
-
-Defalut: 0
-
-Control the number of disks on the machine. If it is 0, it comes from the system settings
-
-### `num_threads_per_core`
-
-Default: 3
-
-Control the number of threads that each core runs. Usually choose 2 times or 3 times the number of cores. This keeps the core busy without causing excessive jitter
-
-### `num_threads_per_disk`
-
-Default: 0
-
-The maximum number of threads per disk is also the maximum queue depth of each disk
-
-### `number_tablet_writer_threads`
-
-Default: 16
-
-Number of tablet write threads
-
-### `path_gc_check`
-
-Default: true
-
-Whether to enable the recycle scan data thread check, it is enabled by default
-
-### `path_gc_check_interval_second`
-
-Default: 86400
-
-Recycle scan data thread check interval, in seconds
-
-### `path_gc_check_step`
-
-Default: 1000
-
-### `path_gc_check_step_interval_ms`
-
-Default: 10 (ms)
-
-### `path_scan_interval_second`
-
-Default: 86400
-
-### `pending_data_expire_time_sec`
-
-Default: 1800
-
-The maximum duration of unvalidated data retained by the storage engine, the default unit: seconds
-
-### `periodic_counter_update_period_ms`
-
-Default: 500
-
-Update rate counter and sampling counter cycle, default unit: milliseconds
-
-### `plugin_path`
-
-Default: ${DORIS_HOME}/plugin
-
-pliugin path
-
-### `port`
-
-* Type: int32
-* Description: The port used in UT. Meaningless in the actual environment and can be ignored.
-* Default value: 20001
-
-### `pprof_profile_dir`
-
-Default : ${DORIS_HOME}/log
-
-pprof profile save directory
-
-### `priority_networks`
-
-Default: empty
-
-Declare a selection strategy for those servers with many IPs. Note that at most one ip should match this list. This is a semicolon-separated list in CIDR notation, such as 10.10.10.0/24. If there is no IP matching this rule, one will be randomly selected
-
-### `priority_queue_remaining_tasks_increased_frequency`
-
-Default: 512
-
- the increased frequency of priority for remaining tasks in BlockingPriorityQueue
-
-### `publish_version_worker_count`
-
-Default: 8
-
-the count of thread to publish version
-
-### `pull_load_task_dir`
-
-Default: ${DORIS_HOME}/var/pull_load
-
-Pull the directory of the laod task
-
-### `push_worker_count_high_priority`
-
-Default: 3
-
-Import the number of threads for processing HIGH priority tasks
-
-### `push_worker_count_normal_priority`
-
-Default: 3
-
-Import the number of threads for processing NORMAL priority tasks
-
-### `push_write_mbytes_per_sec`
-
-+ Type: int32
-+ Description: Load data speed control, the default is 10MB per second. Applicable to all load methods.
-+ Unit: MB
-+ Default value: 10
-
-### `query_scratch_dirs`
-
-+ Type: string
-+ Description: The directory selected by BE to store temporary data during spill to disk. which is similar to the storage path configuration, multiple directories are separated by ;.
-+ Default value: ${DORIS_HOME}
-
-### `release_snapshot_worker_count`
-
-Default: 5
-
-Number of threads releasing snapshots
-
-### `report_disk_state_interval_seconds`
-
-Default: 60
-
-The interval time for the agent to report the disk status to FE, unit (seconds)
-
-### `report_tablet_interval_seconds`
-
-Default: 60
-
-The interval time for the agent to report the olap table to the FE, in seconds
-
-### `report_task_interval_seconds`
-
-Default: 10
-
-The interval time for the agent to report the task signature to FE, unit (seconds)
-
-### `result_buffer_cancelled_interval_time`
-
-Default: 300
-
-Result buffer cancellation time (unit: second)
-
-### `routine_load_thread_pool_size`
-
-Default: 10
-
-The thread pool size of the routine load task. This should be greater than the FE configuration'max_concurrent_task_num_per_be' (default 5)
-
-### `row_nums_check`
-
-Default: true
-
-Check row nums for BE/CE and schema change. true is open, false is closed
-
-### `row_step_for_compaction_merge_log`
-
-* Type: int64
-* Description: Merge log will be printed for each "row_step_for_compaction_merge_log" rows merged during compaction. If the value is set to 0, merge log will not be printed.
-* Default value: 0
-* Dynamically modify: true
-
-### `scan_context_gc_interval_min`
-
-Default: 5
-
-This configuration is used for the context gc thread scheduling cycle. Note: The unit is minutes, and the default is 5 minutes
-
-### `send_batch_thread_pool_thread_num`
-
-* Type: int32
-* Description: The number of threads in the SendBatch thread pool. In NodeChannels' sending data tasks, the SendBatch operation of each NodeChannel will be submitted as a thread task to the thread pool to be scheduled. This parameter determines the size of the SendBatch thread pool.
-* Default value: 256
-
-### `send_batch_thread_pool_queue_size`
-
-* Type: int32
-* Description: The queue length of the SendBatch thread pool. In NodeChannels' sending data tasks, the SendBatch operation of each NodeChannel will be submitted as a thread task to the thread pool waiting to be scheduled, and after the number of submitted tasks exceeds the length of the thread pool queue, subsequent submitted tasks will be blocked until there is a empty slot in the queue.
-
-### `sleep_one_second`
-
-+ Type: int32
-+ Description: Global variables, used for BE thread sleep for 1 seconds, should not be modified
-+ Default value: 1
-
-### `small_file_dir`
-
-Default: ${DORIS_HOME}/lib/small_file/
-
-Directory for saving files downloaded by SmallFileMgr
-
-### `snapshot_expire_time_sec`
-
-Default: 172800
-
-Snapshot file cleaning interval, default value: 48 hours
-
-### `status_report_interval`
-
-Default: 5
-
-Interval between profile reports; unit: seconds
-
-### `storage_flood_stage_left_capacity_bytes`
-
-Default: 1073741824
-
-The min bytes that should be left of a data dir,default value:1G
-
-### `storage_flood_stage_usage_percent`
-
-Default: 95 （95%）
-
-The storage_flood_stage_usage_percent and storage_flood_stage_left_capacity_bytes configurations limit the maximum usage of the capacity of the data directory.
-
-### `storage_medium_migrate_count`
-
-Default: 1
-
-the count of thread to clone
-
-### `storage_page_cache_limit`
-
-Default: 20%
-
-Cache for storage page size
-
-### `index_page_cache_percentage`
-* Type: int32
-* Description: Index page cache as a percentage of total storage page cache, value range is [0, 100]
-* Default value: 10
-
-### `storage_root_path`
-
-* Type: string
-
-* Description: data root path, separate by ';'.you can specify the storage medium of each root path, HDD or SSD. you can add capacity limit at the end of each root path, seperate by ','
-
- eg.1: `storage_root_path=/home/disk1/doris.HDD,50;/home/disk2/doris.SSD,1;/home/disk2/doris`
-
- * 1./home/disk1/doris.HDD,50, indicates capacity limit is 50GB, HDD;
- * 2./home/disk2/doris.SSD,1, indicates capacity limit is 1GB, SSD;
- * 3./home/disk2/doris, indicates capacity limit is disk capacity, HDD(default)
-
- eg.2: `storage_root_path=/home/disk1/doris,medium:hdd,capacity:50;/home/disk2/doris,medium:ssd,capacity:50`
-
- * 1./home/disk1/doris,medium:hdd,capacity:10,capacity limit is 10GB, HDD;
- * 2./home/disk2/doris,medium:ssd,capacity:50,capacity limit is 50GB, SSD;
-
-* Default: ${DORIS_HOME}
-
-### `storage_strict_check_incompatible_old_format`
-* Type: bool
-* Description: Used to check incompatible old format strictly
-* Default value: true
-* Dynamically modify: false
-
-This config is used to check incompatible old format hdr_ format whether doris uses strict way. When config is true,
-process will log fatal and exit. When config is false, process will only log warning.
-
-### `streaming_load_max_mb`
-
-* Type: int64
-* Description: Used to limit the maximum amount of csv data allowed in one Stream load. The unit is MB.
-* Default value: 10240
-* Dynamically modify: yes
-
-Stream Load is generally suitable for loading data less than a few GB, not suitable for loading` too large data.
-
-### `streaming_load_json_max_mb`
-
-* Type: int64
-* Description: it is used to limit the maximum amount of json data allowed in one Stream load. The unit is MB.
-* Default value: 100
-* Dynamically modify: yes
-
-Some data formats, such as JSON, cannot be split. Doris must read all the data into the memory before parsing can begin. Therefore, this value is used to limit the maximum amount of data that can be loaded in a single Stream load.
-
-### `streaming_load_rpc_max_alive_time_sec`
-
-Default: 1200
-
-The lifetime of TabletsChannel. If the channel does not receive any data at this time, the channel will be deleted, unit: second
-
-### `sync_tablet_meta`
-
-Default: false
-
-Whether the storage engine opens sync and keeps it to the disk
-
-### `sys_log_dir`
-
-* Type: string
-* Description: Storage directory of BE log data
-* Default: ${DORIS_HOME}/log
-
-### `sys_log_level`
-
-INFO
-
-Log Level: INFO < WARNING < ERROR < FATAL
-
-### `sys_log_roll_mode`
-
-Default: SIZE-MB-1024
-
-The size of the log split, one log file is split every 1G
-
-### `sys_log_roll_num`
-
-Default: 10
-
-Number of log files kept
-
-### `sys_log_verbose_level`
-
-Defaultl: 10
-
-Log display level, used to control the log output at the beginning of VLOG in the code
-
-### `sys_log_verbose_modules`
-
-Default: empty
-
-Log printing module, writing olap will only print the log under the olap module
-
-### `tablet_map_shard_size`
-
-Default: 1
-
-tablet_map_lock fragment size, the value is 2^n, n=0,1,2,3,4, this is for better tablet management
-
-### `tablet_meta_checkpoint_min_interval_secs`
-
-Default: 600（s）
-
-The polling interval of the TabletMeta Checkpoint thread
-
-### `tablet_meta_checkpoint_min_new_rowsets_num`
-
-### `tablet_scan_frequency_time_node_interval_second`
-
-* Type: int64
-* Description: Time interval to record the metric 'query_scan_count' and timestamp in second for the purpose of calculating tablet scan frequency during a latest period of time at the present.
-* Default: 300
-
-### `tablet_stat_cache_update_interval_second`
-
-默认值: 10
-
-The minimum number of Rowsets for TabletMeta Checkpoint
-
-### `tablet_rowset_stale_sweep_time_sec`
-
-* Type: int64
-* Description: It is used to control the expiration time of cleaning up the merged rowset version. When the current time now() minus the max created rowset‘s create time in a version path is greater than tablet_rowset_stale_sweep_time_sec, the current path is cleaned up and these merged rowsets are deleted, the unit is second.
-* Default: 1800
-
-When writing is too frequent and the disk time is insufficient, you can configure less tablet_rowset_stale_sweep_time_sec. However, if this time is less than 5 minutes, it may cause fe to query the version that has been merged, causing a query -230 error.
-
-### `tablet_writer_open_rpc_timeout_sec`
-
-Default: 300
-
-Update interval of tablet state cache, unit: second
-
-### `tablet_writer_ignore_eovercrowded`
-
-* Type: bool
-* Description: Used to ignore brpc error '[E1011]The server is overcrowded' when writing data.
-* Default value: false
-
-When meet '[E1011]The server is overcrowded' error, you can tune the configuration `brpc_socket_max_unwritten_bytes`, but it can't be modified at runtime. Set it to `true` to avoid writing failed temporarily. Notice that, it only effects `write`, other rpc requests will still check if overcrowded.
-
-### `tc_free_memory_rate`
-
-Default: 20 (%)
-
-Available memory, value range: [0-100]
-
-### `tc_max_total_thread_cache_bytes`
-
-* Type: int64
-* Description: Used to limit the total thread cache size in tcmalloc. This limit is not a hard limit, so the actual thread cache usage may exceed this limit. For details, please refer to [TCMALLOC\_MAX\_TOTAL\_THREAD\_CACHE\_BYTES](https://gperftools.github.io/gperftools/tcmalloc.html)
-* Default: 1073741824
-
-If the system is found to be in a high-stress scenario and a large number of threads are found in the tcmalloc lock competition phase through the BE thread stack, such as a large number of `SpinLock` related stacks, you can try increasing this parameter to improve system performance. [Reference](https://github.com/gperftools/gperftools/issues/1111)
-
-### `tc_use_memory_min`
-
-Default: 10737418240
-
-The minimum memory of TCmalloc, when the memory used is less than this, it is not returned to the operating system
-
-### `thrift_client_retry_interval_ms`
-
-* Type: int64
-* Description: Used to set retry interval for thrift client in be to avoid avalanche disaster in fe thrift server, the unit is ms.
-* Default: 1000
-
-### `thrift_connect_timeout_seconds`
-
-Default: 3
-
-The default thrift client connection timeout time (unit: seconds)
-
-### `thrift_rpc_timeout_ms`
-
-Default: 5000
-
-thrift default timeout time, default: 5 seconds
-
-### `thrift_server_type_of_fe`
-
-This configuration indicates the service model used by FE's Thrift service. The type is string and is case-insensitive. This parameter needs to be consistent with the setting of fe's thrift_server_type parameter. Currently there are two values for this parameter, `THREADED` and `THREAD_POOL`.
-
-If the parameter is `THREADED`, the model is a non-blocking I/O model,
-
-If the parameter is `THREAD_POOL`, the model is a blocking I/O model.
-
-### `total_permits_for_compaction_score`
-
-* Type: int64
-* Description: The upper limit of "permits" held by all compaction tasks. This config can be set to limit memory consumption for compaction.
-* Default: 10000
-* Dynamically modify: true
-
-### `trash_file_expire_time_sec`
-
-Default: 259200
-
-The interval for cleaning the recycle bin is 72 hours. When the disk space is insufficient, the file retention period under trash may not comply with this parameter
-
-### `txn_commit_rpc_timeout_ms`
-
-Default: 10000
-
-txn submit rpc timeout, the default is 10 seconds
-
-### `txn_map_shard_size`
-
-Default: 128
-
-txn_map_lock fragment size, the value is 2^n, n=0,1,2,3,4. This is an enhancement to improve the performance of managing txn
-
-### `txn_shard_size`
-
-Default: 1024
-
-txn_lock shard size, the value is 2^n, n=0,1,2,3,4, this is an enhancement function that can improve the performance of submitting and publishing txn
-
-### `unused_rowset_monitor_interval`
-
-Default: 30
-
-Time interval for clearing expired Rowset, unit: second
-
-### `upload_worker_count`
-
-Default: 1
-
-Maximum number of threads for uploading files
-
-### `use_mmap_allocate_chunk`
-
-Default: false
-
-Whether to use mmap to allocate blocks. If you enable this feature, it is best to increase the value of vm.max_map_count, its default value is 65530. You can use "sysctl -w vm.max_map_count=262144" or "echo 262144> /proc/sys/vm/" to operate max_map_count as root. When this setting is true, you must set chunk_reserved_bytes_limit to a relatively low Big number, otherwise the performance is very very bad
-
-### `user_function_dir`
-
-${DORIS_HOME}/lib/udf
-
-udf function directory
-
-### `webserver_num_workers`
-
-Default: 48
-
-Webserver default number of worker threads
-
-### `webserver_port`
-
-* Type: int32
-* Description: Service port of http server on BE
-* Default: 8040
-
-### `write_buffer_size`
-
-Default: 104857600
-
-The size of the buffer before flashing
-
-### `zone_map_row_num_threshold`
-
-* Type: int32
-* Description: If the number of rows in a page is less than this value, no zonemap will be created to reduce data expansion
-* Default: 20
-
-### `aws_log_level`
-
-* Type: int32
-
-* Description: log level of AWS SDK,
- ```
- Off = 0,
- Fatal = 1,
- Error = 2,
- Warn = 3,
- Info = 4,
- Debug = 5,
- Trace = 6
- ```
-
-* Default: 3
-
-### `track_new_delete`
-
-* Type: bool
-* Description: Whether Hook TCmalloc new/delete, currently consume/release tls mem tracker in Hook.
-* Default: true
-
-### `mem_tracker_level`
-
-* Type: int16
-* Description: The level at which MemTracker is displayed on the Web page equal or lower than this level will be displayed on the Web page
- ```
- OVERVIEW = 0
- TASK = 1
- INSTANCE = 2
- VERBOSE = 3
- ```
-* Default: 0
-
-### `mem_tracker_consume_min_size_bytes`
-
-* Type: int32
-* Description: The minimum length of TCMalloc Hook when consume/release MemTracker. Consume size smaller than this value will continue to accumulate to avoid frequent calls to consume/release of MemTracker. Decreasing this value will increase the frequency of consume/release. Increasing this value will cause MemTracker statistics to be inaccurate. Theoretically, the statistical value of a MemTracker differs from the true value = ( mem_tracker_consume_min_size_bytes * the number of BE thr [...]
-* Default: 1048576
-
-### `memory_leak_detection`
-
-* Type: bool
-* Description: Whether to start memory leak detection, when MemTracker is a negative value, it is considered that a memory leak has occurred, but the actual MemTracker records inaccurately will also cause a negative value, so this feature is in the experimental stage.
-* Default: false
-
-### `max_segment_num_per_rowset`
-
-* Type: int32
-* Description: Used to limit the number of segments in the newly generated rowset when importing. If the threshold is exceeded, the import will fail with error -238. Too many segments will cause compaction to take up a lot of memory and cause OOM errors.
-* Default value: 200
-
-### `remote_storage_read_buffer_mb`
-
-* Type: int32
-* Description: The cache size used when reading files on hdfs or object storage.
-* Default value: 16MB
-
-Increasing this value can reduce the number of calls to read remote data, but it will increase memory overhead.
-
-### `external_table_connect_timeout_sec`
-
-* Type: int32
-* Description: The timeout when establishing connection with external table such as ODBC table.
-* Default value: 5 seconds
-
-### `segment_cache_capacity`
-
-* Type: int32
-* Description: The maximum number of Segments cached by Segment Cache.
-* Default value: 1000000
-
-The default value is currently only an empirical value, and may need to be modified according to actual scenarios. Increasing this value can cache more segments and avoid some IO. Decreasing this value will reduce memory usage.
-
-### `auto_refresh_brpc_channel`
-
-* Type: bool
-* Description: When obtaining a brpc connection, judge the availability of the connection through hand_shake rpc, and re-establish the connection if it is not available .
-* Default value: false
-
-### `high_priority_flush_thread_num_per_store`
-
-* Type: int32
-* Description: The number of flush threads per store path allocated for the high priority import task.
-* Default value: 1
-
-### `routine_load_consumer_pool_size`
-
-* Type: int32
-* Description: The number of caches for the data consumer used by the routine load.
-* Default: 10
-
-### `load_task_high_priority_threshold_second`
-
-* Type: int32
-* Description: When the timeout of an import task is less than this threshold, Doris will consider it to be a high priority task. High priority tasks use a separate pool of flush threads.
-* Default: 120
-
-### `min_load_rpc_timeout_ms`
-
-* Type: int32
-* Description: The minimum timeout for each rpc in the load job.
-* Default: 20
-
-Translated with www.DeepL.com/Translator (free version)
-
-### `doris_scan_range_max_mb`
-* Type: int32
-* Description: The maximum amount of data read by each OlapScanner.
-* Default: 1024
-
-### `string_type_length_soft_limit_bytes`
-* Type: int32
-* Description: A soft limit of string type length.
-* Description: 1048576
diff --git a/docs/en/administrator-guide/config/fe_config.md b/docs/en/administrator-guide/config/fe_config.md
deleted file mode 100644
index f34658653c..0000000000
--- a/docs/en/administrator-guide/config/fe_config.md
+++ /dev/null
@@ -1,2210 +0,0 @@
----
-{
- "title": "FE Configuration",
- "language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-<!-- Please sort the configuration alphabetically -->
-
-# FE Configuration
-
-This document mainly introduces the relevant configuration items of FE.
-
-The FE configuration file `fe.conf` is usually stored in the `conf/` directory of the FE deployment path. In version 0.14, another configuration file `fe_custom.conf` will be introduced. The configuration file is used to record the configuration items that are dynamically configured and persisted by the user during operation.
-
-After the FE process is started, it will read the configuration items in `fe.conf` first, and then read the configuration items in `fe_custom.conf`. The configuration items in `fe_custom.conf` will overwrite the same configuration items in `fe.conf`.
-
-The location of the `fe_custom.conf` file can be configured in `fe.conf` through the `custom_config_dir` configuration item.
-
-## View configuration items
-
-There are two ways to view the configuration items of FE:
-
-1. FE web page
-
- Open the FE web page `http://fe_host:fe_http_port/variable` in the browser. You can see the currently effective FE configuration items in `Configure Info`.
-
-2. View by command
-
- After the FE is started, you can view the configuration items of the FE in the MySQL client with the following command:
-
- `ADMIN SHOW FRONTEND CONFIG;`
-
- The meanings of the columns in the results are as follows:
-
- * Key: the name of the configuration item.
- * Value: The value of the current configuration item.
- * Type: The configuration item value type, such as integer or string.
- * IsMutable: whether it can be dynamically configured. If true, the configuration item can be dynamically configured at runtime. If false, it means that the configuration item can only be configured in `fe.conf` and takes effect after restarting FE.
- * MasterOnly: Whether it is a unique configuration item of Master FE node. If it is true, it means that the configuration item is meaningful only at the Master FE node, and is meaningless to other types of FE nodes. If false, it means that the configuration item is meaningful in all types of FE nodes.
- * Comment: The description of the configuration item.
-
-## Set configuration items
-
-There are two ways to configure FE configuration items:
-
-1. Static configuration
-
- Add and set configuration items in the `conf/fe.conf` file. The configuration items in `fe.conf` will be read when the FE process starts. Configuration items not in `fe.conf` will use default values.
-
-2. Dynamic configuration via MySQL protocol
-
- After the FE starts, you can set the configuration items dynamically through the following commands. This command requires administrator privilege.
-
- `ADMIN SET FRONTEND CONFIG (" fe_config_name "=" fe_config_value ");`
-
- Not all configuration items support dynamic configuration. You can check whether the dynamic configuration is supported by the `IsMutable` column in the` ADMIN SHOW FRONTEND CONFIG; `command result.
-
- If the configuration item of `MasterOnly` is modified, the command will be directly forwarded to the Master FE and only the corresponding configuration item in the Master FE will be modified.
-
- **Configuration items modified in this way will become invalid after the FE process restarts.**
-
- For more help on this command, you can view it through the `HELP ADMIN SET CONFIG;` command.
-
-3. Dynamic configuration via HTTP protocol
-
- For details, please refer to [Set Config Action](../http-actions/fe/set-config-action.md)
-
- This method can also persist the modified configuration items. The configuration items will be persisted in the `fe_custom.conf` file and will still take effect after FE is restarted.
-
-## Examples
-
-1. Modify `async_pending_load_task_pool_size`
-
- Through `ADMIN SHOW FRONTEND CONFIG;` you can see that this configuration item cannot be dynamically configured (`IsMutable` is false). You need to add in `fe.conf`:
-
- `async_pending_load_task_pool_size = 20`
-
- Then restart the FE process to take effect the configuration.
-
-2. Modify `dynamic_partition_enable`
-
- Through `ADMIN SHOW FRONTEND CONFIG;` you can see that the configuration item can be dynamically configured (`IsMutable` is true). And it is the unique configuration of Master FE. Then first we can connect to any FE and execute the following command to modify the configuration:
-
- ```
- ADMIN SET FRONTEND CONFIG ("dynamic_partition_enable" = "true"); `
- ```
-
- Afterwards, you can view the modified value with the following command:
-
- ```
- set forward_to_master = true;
- ADMIN SHOW FRONTEND CONFIG;
- ```
-
- After modification in the above manner, if the Master FE restarts or a Master election is performed, the configuration will be invalid. You can add the configuration item directly in `fe.conf` and restart the FE to make the configuration item permanent.
-
-3. Modify `max_distribution_pruner_recursion_depth`
-
- Through `ADMIN SHOW FRONTEND CONFIG;` you can see that the configuration item can be dynamically configured (`IsMutable` is true). It is not unique to Master FE.
-
- Similarly, we can modify the configuration by dynamically modifying the configuration command. Because this configuration is not unique to the Master FE, user need to connect to different FEs separately to modify the configuration dynamically, so that all FEs use the modified configuration values.
-
-## Configurations
-
-### max_dynamic_partition_num
-
-Default: 500
-
-IsMutable: true
-
-MasterOnly: true
-
-Used to limit the maximum number of partitions that can be created when creating a dynamic partition table, to avoid creating too many partitions at one time. The number is determined by "start" and "end" in the dynamic partition parameters..
-
-### grpc_max_message_size_bytes
-
-Default: 1G
-
-Used to set the initial flow window size of the GRPC client channel, and also used to max message size. When the result set is large, you may need to increase this value.
-
-### min_replication_num_per_tablet
-
-Default: 1
-
-Used to set minimal number of replication per tablet.
-
-### max_replication_num_per_tablet
-
-Default: 32767
-
-Used to set maximal number of replication per tablet.
-
-### enable_outfile_to_local
-
-Default: false
-
-Whether to allow the outfile function to export the results to the local disk.
-
-### enable_access_file_without_broker
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-This config is used to try skip broker when access bos or other cloud storage via broker
-
-### enable_bdbje_debug_mode
-
-Default: false
-
-If set to true, FE will be started in BDBJE debug mode
-
-### enable_alpha_rowset
-
-Default: false
-
-Whether to support the creation of alpha rowset tables. The default is false and should only be used in emergency situations, this config should be remove in some future version
-
-### enable_http_server_v2
-
-Default: The default is true after the official 0.14.0 version is released, and the default is false before
-
-HTTP Server V2 is implemented by SpringBoot. It uses an architecture that separates the front and back ends. Only when httpv2 is enabled can users use the new front-end UI interface.
-
-### jetty_server_acceptors
-
-Default: 2
-
-### jetty_server_selectors
-
-Default: 4
-
-### jetty_server_workers
-
-Default: 0
-
-With the above three parameters, Jetty's thread architecture model is very simple, divided into acceptors, selectors and workers three thread pools. Acceptors are responsible for accepting new connections, and then hand them over to selectors to process the unpacking of the HTTP message protocol, and finally workers process the request. The first two thread pools adopt a non-blocking model, and one thread can handle the read and write of many sockets, so the number of thread pools is small.
-
-For most projects, only 4 acceptors threads are required, and 2 to 4 selectors threads are sufficient. Workers are obstructive business logic, often have more database operations, and require a large number of threads. The specific number depends on the proportion of QPS and IO events of the application. The higher the QPS, the more threads are required, the higher the proportion of IO, the more threads waiting, and the more total threads required.
-
-Worker thread pool is not set by default, set according to your needs
-
-### jetty_threadPool_minThreads
-
-The minimum number of threads in the Jetty thread pool, the default is 20
-
-### jetty_threadPool_maxThreads
-
-The maximum number of threads in the Jetty thread pool, the default is 400
-
-### jetty_server_max_http_post_size
-
-Default: 100 * 1024 * 1024 （100MB）
-
-This is the maximum number of bytes of the file uploaded by the put or post method, the default value: 100MB
-
-### **`disable_mini_load`**
-
-Whether to disable the mini load data import method, the default: true (Disabled)
-
-### frontend_address
-
-Status: Deprecated, not recommended use. This parameter may be deleted later Type: string Description: Explicitly set the IP address of FE instead of using *InetAddress.getByName* to get the IP address. Usually in *InetAddress.getByName* When the expected results cannot be obtained. Only IP address is supported, not hostname. Default value: 0.0.0.0
-
-### default_max_filter_ratio
-
-Default: 0
-
-IsMutable: true
-
-MasterOnly: true
-
-Maximum percentage of data that can be filtered (due to reasons such as data is irregularly) , The default value is 0.
-
-### default_db_data_quota_bytes
-
-Default: 1PB
-
-IsMutable: true
-
-MasterOnly: true
-
-Used to set the default database data quota size. To set the quota size of a single database, you can use:
-
-```
-Set the database data quota, the unit is:B/K/KB/M/MB/G/GB/T/TB/P/PB
-ALTER DATABASE db_name SET DATA QUOTA quota;
-View configuration
-show data （Detail: HELP SHOW DATA）
-```
-
-### default_db_replica_quota_size
-
-Default: 1073741824
-
-IsMutable: true
-
-MasterOnly: true
-
-Used to set the default database replica quota. To set the quota size of a single database, you can use:
-
-```
-Set the database replica quota
-ALTER DATABASE db_name SET REPLICA QUOTA quota;
-View configuration
-show data （Detail: HELP SHOW DATA）
-```
-
-### enable_batch_delete_by_default
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-Whether to add a delete sign column when create unique table
-
-### recover_with_empty_tablet
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
- In some very special circumstances, such as code bugs, or human misoperation, etc., all replicas of some tablets may be lost. In this case, the data has been substantially lost. However, in some scenarios, the business still hopes to ensure that the query will not report errors even if there is data loss, and reduce the perception of the user layer. At this point, we can use the blank Tablet to fill the missing replica to ensure that the query can be executed normally.
-
-Set to true so that Doris will automatically use blank replicas to fill tablets which all replicas have been damaged or missing
-
-### max_allowed_in_element_num_of_delete
-
-Default: 1024
-
-IsMutable: true
-
-MasterOnly: true
-
-This configuration is used to limit element num of InPredicate in delete statement.
-
-### cache_result_max_row_count
-
-Default: 3000
-
-IsMutable: true
-
-MasterOnly: false
-
-In order to avoid occupying too much memory, the maximum number of rows that can be cached is 2000 by default. If this threshold is exceeded, the cache cannot be set
-
-### cache_last_version_interval_second
-
-Default: 900
-
-IsMutable: true
-
-MasterOnly: false
-
-The time interval of the latest partitioned version of the table refers to the time interval between the data update and the current version. It is generally set to 900 seconds, which distinguishes offline and real-time import
-
-### cache_enable_partition_mode
-
-Default: true
-
-IsMutable: true
-
-MasterOnly: false
-
-When this switch is turned on, the query result set will be cached according to the partition. If the interval between the query table partition time and the query time is less than cache_last_version_interval_second, the result set will be cached according to the partition.
-
-Part of the data will be obtained from the cache and some data from the disk when querying, and the data will be merged and returned to the client.
-
-### cache_enable_sql_mode
-
-Default: true
-
-IsMutable: true
-
-MasterOnly: false
-
-If this switch is turned on, the SQL query result set will be cached. If the interval between the last visit version time in all partitions of all tables in the query is greater than cache_last_version_interval_second, and the result set is less than cache_result_max_row_count, the result set will be cached, and the next same SQL will hit the cache
-
-If set to true, fe will enable sql result caching. This option is suitable for offline data update scenarios
-
-| | case1 | case2 | case3 | case4 |
-| ---------------------- | ----- | ----- | ----- | ----- |
-| enable_sql_cache | false | true | true | false |
-| enable_partition_cache | false | false | true | true |
-
-### min_clone_task_timeout_sec 和 max_clone_task_timeout_sec
-
-Default: Minimum 3 minutes, maximum two hours
-
-IsMutable: true
-
-MasterOnly: true
-
-Type: long Description: Used to control the maximum timeout of a clone task. The unit is second. Default value: 7200 Dynamic modification: yes
-
-Can cooperate with `mix_clone_task_timeout_sec` to control the maximum and minimum timeout of a clone task. Under normal circumstances, the timeout of a clone task is estimated by the amount of data and the minimum transfer rate (5MB/s). In some special cases, these two configurations can be used to set the upper and lower bounds of the clone task timeout to ensure that the clone task can be completed successfully.
-
-### agent_task_resend_wait_time_ms
-
-Default: 5000
-
-IsMutable: true
-
-MasterOnly: true
-
-This configuration will decide whether to resend agent task when create_time for agent_task is set, only when current_time - create_time > agent_task_resend_wait_time_ms can ReportHandler do resend agent task.
-
-This configuration is currently mainly used to solve the problem of repeated sending of `PUBLISH_VERSION` agent tasks. The current default value of this configuration is 5000, which is an experimental value.
-
-Because there is a certain time delay between submitting agent tasks to AgentTaskQueue and submitting to be, Increasing the value of this configuration can effectively solve the problem of repeated sending of agent tasks,
-
-But at the same time, it will cause the submission of failed or failed execution of the agent task to be executed again for an extended period of time
-
-### enable_odbc_table
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-Whether to enable the ODBC table, it is not enabled by default. You need to manually configure it when you use it. This parameter can be set by: ADMIN SET FRONTEND CONFIG("key"="value")
-
-### enable_spark_load
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-Whether to enable spark load temporarily, it is not enabled by default
-
-### disable_storage_medium_check
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-If disable_storage_medium_check is true, ReportHandler would not check tablet's storage medium and disable storage cool down function, the default value is false. You can set the value true when you don't care what the storage medium of the tablet is.
-
-### drop_backend_after_decommission
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-1. This configuration is used to control whether the system drops the BE after successfully decommissioning the BE. If true, the BE node will be deleted after the BE is successfully offline. If false, after the BE successfully goes offline, the BE will remain in the DECOMMISSION state, but will not be dropped.
-
- This configuration can play a role in certain scenarios. Assume that the initial state of a Doris cluster is one disk per BE node. After running for a period of time, the system has been vertically expanded, that is, each BE node adds 2 new disks. Because Doris currently does not support data balancing among the disks within the BE, the data volume of the initial disk may always be much higher than the data volume of the newly added disk. At this time, we can perform manual inter-disk [...]
-
- 1. Set the configuration item to false.
- 2. Perform a decommission operation on a certain BE node. This operation will migrate all data on the BE to other nodes.
- 3. After the decommission operation is completed, the BE will not be dropped. At this time, cancel the decommission status of the BE. Then the data will start to balance from other BE nodes back to this node. At this time, the data will be evenly distributed to all disks of the BE.
- 4. Perform steps 2 and 3 for all BE nodes in sequence, and finally achieve the purpose of disk balancing for all nodes
-
-### period_of_auto_resume_min
-
-Default: 5 （s）
-
-IsMutable: true
-
-MasterOnly: true
-
-Automatically restore the cycle of Routine load
-
-### max_tolerable_backend_down_num
-
-Default: 0
-
-IsMutable: true
-
-MasterOnly: true
-
-As long as one BE is down, Routine Load cannot be automatically restored
-
-### enable_materialized_view
-
-Default: true
-
-IsMutable: true
-
-MasterOnly: true
-
-This configuration is used to turn on and off the creation of materialized views. If set to true, the function to create a materialized view is enabled. The user can create a materialized view through the `CREATE MATERIALIZED VIEW` command. If set to false, materialized views cannot be created.
-
-If you get an error `The materialized view is coming soon` or `The materialized view is disabled` when creating the materialized view, it means that the configuration is set to false and the function of creating the materialized view is turned off. You can start to create a materialized view by modifying the configuration to true.
-
-This variable is a dynamic configuration, and users can modify the configuration through commands after the FE process starts. You can also modify the FE configuration file and restart the FE to take effect
-
-### check_java_version
-
-Default: true
-
-Doris will check whether the compiled and run Java versions are compatible, if not, it will throw a Java version mismatch exception message and terminate the startup
-
-### max_running_rollup_job_num_per_table
-
-Default: 1
-
-IsMutable: true
-
-MasterOnly: true
-
-Control the concurrency limit of Rollup jobs
-
-### dynamic_partition_enable
-
-Default: true
-
-IsMutable: true
-
-MasterOnly: true
-
-Whether to enable dynamic partition, enabled by default
-
-### dynamic_partition_check_interval_seconds
-
-Default: 600 （s）
-
-IsMutable: true
-
-MasterOnly: true
-
-Decide how often to check dynamic partition
-
-### disable_cluster_feature
-
-Default: true
-
-IsMutable: true
-
-The multi cluster feature will be deprecated in version 0.12 ,set this config to true will disable all operations related to cluster feature, include:
- create/drop cluster
- add free backend/add backend to cluster/decommission cluster balance
- change the backends num of cluster
- link/migration db
-
-### force_do_metadata_checkpoint
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-If set to true, the checkpoint thread will make the checkpoint regardless of the jvm memory used percent
-
-### metadata_checkpoint_memory_threshold
-
-Default: 60 （60%）
-
-IsMutable: true
-
-MasterOnly: true
-
- If the jvm memory used percent(heap or old mem pool) exceed this threshold, checkpoint thread will not work to avoid OOM.
-
-### max_distribution_pruner_recursion_depth
-
-Default: 100
-
-IsMutable: true
-
-MasterOnly: false
-
-This will limit the max recursion depth of hash distribution pruner.
- eg: where a in (5 elements) and b in (4 elements) and c in (3 elements) and d in (2 elements).
- a/b/c/d are distribution columns, so the recursion depth will be 5 * 4 * 3 * 2 = 120, larger than 100,
- So that distribution pruner will no work and just return all buckets.
- Increase the depth can support distribution pruning for more elements, but may cost more CPU.
-
-### max_backup_restore_job_num_per_db
-
-Default: 10
-
-This configuration is mainly used to control the number of backup/restore tasks recorded in each database.
-
-### using_old_load_usage_pattern
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-If set to true, the insert stmt with processing error will still return a label to user. And user can use this label to check the load job's status. The default value is false, which means if insert operation encounter errors, exception will be thrown to user client directly without load label.
-
-### small_file_dir
-
-Default: DORIS_HOME_DIR/small_files
-
-Save small files
-
-### max_small_file_size_bytes
-
-Default: 1M
-
-IsMutable: true
-
-MasterOnly: true
-
-The max size of a single file store in SmallFileMgr
-
-### max_small_file_number
-
-Default: 100
-
-IsMutable: true
-
-MasterOnly: true
-
-The max number of files store in SmallFileMgr
-
-### max_routine_load_task_num_per_be
-
-Default: 5
-
-IsMutable: true
-
-MasterOnly: true
-
-the max concurrent routine load task num per BE. This is to limit the num of routine load tasks sending to a BE, and it should also less than BE config 'routine_load_thread_pool_size'(default 10), which is the routine load task thread pool size on BE.
-
-### max_routine_load_task_concurrent_num
-
-Default: 5
-
-IsMutable: true
-
-MasterOnly: true
-
-the max concurrent routine load task num of a single routine load job
-
-### max_routine_load_job_num
-
-Default: 100
-
-the max routine load job num, including NEED_SCHEDULED, RUNNING, PAUSE
-
-### max_running_txn_num_per_db
-
-Default: 100
-
-IsMutable: true
-
-MasterOnly: true
-
-This configuration is mainly used to control the number of concurrent load jobs of the same database.
-
-When there are too many load jobs running in the cluster, the newly submitted load jobs may report errors:
-
-```text
-current running txns on db xxx is xx, larger than limit xx
-```
-
-When this error is encountered, it means that the load jobs currently running in the cluster exceeds the configuration value. At this time, it is recommended to wait on the business side and retry the load jobs.
-
-Generally it is not recommended to increase this configuration value. An excessively high number of concurrency may cause excessive system load
-
-### enable_metric_calculator
-
-Default: true
-
-If set to true, metric collector will be run as a daemon timer to collect metrics at fix interval
-
-### report_queue_size
-
-Default: 100
-
-IsMutable: true
-
-MasterOnly: true
-
- This threshold is to avoid piling up too many report task in FE, which may cause OOM exception. In some large Doris cluster, eg: 100 Backends with ten million replicas, a tablet report may cost several seconds after some modification of metadata(drop partition, etc..). And one Backend will report tablets info every 1 min, so unlimited receiving reports is unacceptable. we will optimize the processing speed of tablet report in future, but now, just discard the report if queue size exce [...]
- Some online time cost:
- 1. disk report: 0-1 msta
- 2. sk report: 0-1 ms
- 3. tablet report
- 4. 10000 replicas: 200ms
-
-### partition_rebalance_max_moves_num_per_selection
-
-Default: 10
-
-IsMutable: true
-
-MasterOnly: true
-
-Valid only if use PartitionRebalancer,
-
-### partition_rebalance_move_expire_after_access
-
-Default: 600 (s)
-
-IsMutable: true
-
-MasterOnly: true
-
-Valid only if use PartitionRebalancer. If this changed, cached moves will be cleared
-
-### tablet_rebalancer_type
-
-Default: BeLoad
-
-MasterOnly: true
-
-Rebalancer type(ignore case): BeLoad, Partition. If type parse failed, use BeLoad as default
-
-### max_balancing_tablets
-
-Default: 100
-
-IsMutable: true
-
-MasterOnly: true
-
-if the number of balancing tablets in TabletScheduler exceed max_balancing_tablets, no more balance check
-
-### max_scheduling_tablets
-
-Default: 2000
-
-IsMutable: true
-
-MasterOnly: true
-
-if the number of scheduled tablets in TabletScheduler exceed max_scheduling_tablets skip checking.
-
-### disable_balance
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-if set to true, TabletScheduler will not do balance.
-
-### balance_load_score_threshold
-
-Default: 0.1 (10%)
-
-IsMutable: true
-
-MasterOnly: true
-
-the threshold of cluster balance score, if a backend's load score is 10% lower than average score, this backend will be marked as LOW load, if load score is 10% higher than average score, HIGH load will be marked
-
-### schedule_slot_num_per_path
-
-Default: 2
-
-the default slot number per path in tablet scheduler , remove this config and dynamically adjust it by clone task statistic
-
-### tablet_repair_delay_factor_second
-
-Default: 60 （s）
-
-IsMutable: true
-
-MasterOnly: true
-
-the factor of delay time before deciding to repair tablet. if priority is VERY_HIGH, repair it immediately.
-
-- HIGH, delay tablet_repair_delay_factor_second * 1;
-- NORMAL: delay tablet_repair_delay_factor_second * 2;
-- LOW: delay tablet_repair_delay_factor_second * 3;
-
-### es_state_sync_interval_second
-
-Default: 10
-
-fe will call es api to get es index shard info every es_state_sync_interval_secs
-
-### disable_hadoop_load
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-Load using hadoop cluster will be deprecated in future. Set to true to disable this kind of load.
-
-### db_used_data_quota_update_interval_secs
-
-Default: 300 (s)
-
-IsMutable: true
-
-MasterOnly: true
-
-For better data load performance, in the check of whether the amount of data used by the database before data load exceeds the quota, we do not calculate the amount of data already used by the database in real time, but obtain the periodically updated value of the daemon thread.
-
-This configuration is used to set the time interval for updating the value of the amount of data used by the database
-
-### disable_load_job
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-if this is set to true
-
-- all pending load job will failed when call begin txn api
-- all prepare load job will failed when call commit txn api
-- all committed load job will waiting to be published
-
-### catalog_try_lock_timeout_ms
-
-Default: 5000 （ms）
-
-IsMutable: true
-
-The tryLock timeout configuration of catalog lock. Normally it does not need to change, unless you need to test something.
-
-### max_query_retry_time
-
-Default: 1
-
-IsMutable: true
-
-The number of query retries. A query may retry if we encounter RPC exception and no result has been sent to user. You may reduce this number to avoid Avalanche disaster
-
-### remote_fragment_exec_timeout_ms
-
-Default: 5000 （ms）
-
-IsMutable: true
-
-The timeout of executing async remote fragment. In normal case, the async remote fragment will be executed in a short time. If system are under high load condition,try to set this timeout longer.
-
-### enable_local_replica_selection
-
-Default: false
-
-IsMutable: true
-
-If set to true, Planner will try to select replica of tablet on same host as this Frontend. This may reduce network transmission in following case:
-
-- N hosts with N Backends and N Frontends deployed.
-- The data has N replicas.
-- High concurrency queries are syyuyuient to all Frontends evenly
-- In this case, all Frontends can only use local replicas to do the query. If you want to allow fallback to nonlocal replicas when no local replicas available, set enable_local_replica_selection_fallback to true.
-
-### enable_local_replica_selection_fallback
-
-Default: false
-
-IsMutable: true
-
-Used with enable_local_replica_selection. If the local replicas is not available, fallback to the nonlocal replicas.
-
-### max_unfinished_load_job
-
-Default: 1000
-
-IsMutable: true
-
-MasterOnly: true
-
- Max number of load jobs, include PENDING、ETL、LOADING、QUORUM_FINISHED. If exceed this number, load job is not allowed to be submitted
-
-### max_bytes_per_broker_scanner
-
-Default: 3 * 1024 * 1024 * 1024L （3G）
-
-IsMutable: true
-
-MasterOnly: true
-
-Max bytes a broker scanner can process in one broker load job. Commonly, each Backends has one broker scanner.
-
-### enable_auth_check
-
-Default: true
-
-if set to false, auth check will be disable, in case some goes wrong with the new privilege system.
-
-### tablet_stat_update_interval_second
-
-Default: 300,（5min）
-
-update interval of tablet stat , All frontends will get tablet stat from all backends at each interval
-
-### storage_flood_stage_usage_percent
-
-Default: 95 （95%）
-
-IsMutable: true
-
-MasterOnly: true
-
-### storage_flood_stage_left_capacity_bytes
-
-Default:
-
- storage_flood_stage_usage_percent : 95 (95%)
-
- storage_flood_stage_left_capacity_bytes : 1 * 1024 * 1024 * 1024 (1GB)
-
-IsMutable: true
-
-MasterOnly: true
-
-If capacity of disk reach the 'storage_flood_stage_usage_percent' and 'storage_flood_stage_left_capacity_bytes', the following operation will be rejected:
-
-1. load job
-2. restore job
-
-### storage_high_watermark_usage_percent
-
-Default: 85 (85%)
-
-IsMutable: true
-
-MasterOnly: true
-
-### storage_min_left_capacity_bytes
-
-Default: 2 * 1024 * 1024 * 1024 (2GB)
-
-IsMutable: true
-
-MasterOnly: true
-
- 'storage_high_watermark_usage_percent' limit the max capacity usage percent of a Backend storage path. 'storage_min_left_capacity_bytes' limit the minimum left capacity of a Backend storage path. If both limitations are reached, this storage path can not be chose as tablet balance destination. But for tablet recovery, we may exceed these limit for keeping data integrity as much as possible.
-
-### backup_job_default_timeout_ms
-
-Default: 86400 * 1000 (1day)
-
-IsMutable: true
-
-MasterOnly: true
-
-default timeout of backup job
-
-### with_k8s_certs
-
-Default: false
-
-If use k8s deploy manager locally, set this to true and prepare the certs files
-
-### dpp_hadoop_client_path
-
-Default: /lib/hadoop-client/hadoop/bin/hadoop
-
-### dpp_bytes_per_reduce
-
-Default: 100 * 1024 * 1024L; // 100M
-
-### dpp_default_cluster
-
-Default: palo-dpp
-
-### dpp_default_config_str
-
-Default: {
- hadoop_configs : 'mapred.job.priority=NORMAL;mapred.job.map.capacity=50;mapred.job.reduce.capacity=50;mapred.hce.replace.streaming=false;abaci.long.stored.job=true;dce.shuffle.enable=false;dfs.client.authserver.force_stop=true;dfs.client.auth.method=0'
- }
-
-### dpp_config_str
-
-Default: {
- palo-dpp : {
- hadoop_palo_path : '/dir',
- hadoop_configs : 'fs.default.name=hdfs://host:port;mapred.job.tracker=host:port;hadoop.job.ugi=user,password'
- }
- }
-
-### enable_deploy_manager
-
-Default: disable
-
- Set to true if you deploy Palo using thirdparty deploy manager Valid options are:
-
-- disable: no deploy manager
-- k8s: Kubernetes
-- ambari: Ambari
-- local: Local File (for test or Boxer2 BCC version)
-
-### enable_token_check
-
-Default: true
-
-For forward compatibility, will be removed later. check token when download image file.
-
-### expr_depth_limit
-
-Default: 3000
-
-IsMutable: true
-
-Limit on the depth of an expr tree. Exceed this limit may cause long analysis time while holding db read lock. Do not set this if you know what you are doing
-
-### expr_children_limit
-
-Default: 10000
-
-IsMutable: true
-
-Limit on the number of expr children of an expr tree. Exceed this limit may cause long analysis time while holding database read lock.
-
-### proxy_auth_magic_prefix
-
-Default: x@8
-
-### proxy_auth_enable
-
-Default: false
-
-### meta_publish_timeout_ms
-
-Default: 1000 （ms）
-
-The default user resource publishing timeout
-
-### disable_colocate_balance
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-This configs can set to true to disable the automatic colocate tables's relocate and balance. If 'disable_colocate_balance' is set to true, ColocateTableBalancer will not relocate and balance colocate tables.
- **Attention**:
-
-- Under normal circumstances, there is no need to turn off balance at all.
-- Because once the balance is turned off, the unstable colocate table may not be restored
-- Eventually the colocate plan cannot be used when querying.
-
-### query_colocate_join_memory_limit_penalty_factor
-
-Default: 1
-
-IsMutable: true
-
-colocote join PlanFragment instance的memory_limit = exec_mem_limit / min (query_colocate_join_memory_limit_penalty_factor, instance_num)
-
-### max_connection_scheduler_threads_num
-
-Default: 4096
-
-Maximal number of thread in connection-scheduler-pool.
-
-### qe_max_connection
-
-Default: 1024
-
-Maximal number of connections per FE.
-
-### check_consistency_default_timeout_second
-
-Default: 600 （10分钟）
-
-IsMutable: true
-
-MasterOnly: true
-
-Default timeout of a single consistency check task. Set long enough to fit your tablet size
-
-### consistency_check_start_time
-
-Default: 23
-
-IsMutable: true
-
-MasterOnly: true
-
-Consistency checker will run from *consistency_check_start_time* to *consistency_check_end_time*. Default is from 23:00 to 04:00
-
-### consistency_check_end_time
-
-Default: 04
-
-IsMutable: true
-
-MasterOnly: true
-
-Consistency checker will run from *consistency_check_start_time* to *consistency_check_end_time*. Default is from 23:00 to 04:00
-
-### export_tablet_num_per_task
-
-Default: 5
-
-IsMutable: true
-
-MasterOnly: true
-
-Number of tablets per export query plan
-
-### export_task_default_timeout_second
-
-Default: 2 * 3600 （2 hour）
-
-IsMutable: true
-
-MasterOnly: true
-
-Default timeout of export jobs.
-
-### export_running_job_num_limit
-
-Default: 5
-
-IsMutable: true
-
-MasterOnly: true
-
-Limitation of the concurrency of running export jobs. Default is 5. 0 is unlimited
-
-### export_checker_interval_second
-
-Default: 5
-
-Export checker's running interval.
-
-### default_load_parallelism
-
-Default: 1
-
-IsMutable: true
-
-MasterOnly: true
-
-Default parallelism of the broker load execution plan on a single node.
-If the user to set the parallelism when the broker load is submitted, this parameter will be ignored.
-
-### max_broker_concurrency
-
-Default: 10
-
-IsMutable: true
-
-MasterOnly: true
-
-Maximal concurrency of broker scanners.
-
-### min_bytes_per_broker_scanner
-
-Default: 67108864L (64M)
-
-IsMutable: true
-
-MasterOnly: true
-
-Minimum bytes that a single broker scanner will read.
-
-### catalog_trash_expire_second
-
-Default: 86400L (1day)
-
-IsMutable: true
-
-MasterOnly: true
-
-After dropping database(table/partition), you can recover it by using RECOVER stmt. And this specifies the maximal data retention time. After time, the data will be deleted permanently.
-
-### storage_cooldown_second
-
-Default: 30 * 24 * 3600L （30day）
-
-When create a table(or partition), you can specify its storage medium(HDD or SSD). If set to SSD, this specifies the default duration that tablets will stay on SSD. After that, tablets will be moved to HDD automatically. You can set storage cooldown time in CREATE TABLE stmt.
-
-### default_storage_medium
-
-Default: HDD
-
-When create a table(or partition), you can specify its storage medium(HDD or SSD). If not set, this specifies the default medium when creat.
-
-### max_backend_down_time_second
-
-Default: 3600 （1hour）
-
-IsMutable: true
-
-MasterOnly: true
-
-If a backend is down for *max_backend_down_time_second*, a BACKEND_DOWN event will be triggered.
-
-### alter_table_timeout_second
-
-Default: 86400 （1day）
-
-IsMutable: true
-
-MasterOnly: true
-
-Maximal timeout of ALTER TABLE request. Set long enough to fit your table data size.
-
-### capacity_used_percent_high_water
-
-Default: 0.75 （75%）
-
-IsMutable: true
-
-MasterOnly: true
-
-The high water of disk capacity used percent. This is used for calculating load score of a backend
-
-### clone_distribution_balance_threshold
-
-Default: 0.2
-
-IsMutable: true
-
-MasterOnly: true
-
-Balance threshold of num of replicas in Backends.
-
-### clone_capacity_balance_threshold
-
-Default: 0.2
-
-IsMutable: true
-
-MasterOnly: true
-
-Balance threshold of data size in BE.
- The balance algorithm is:
-
-1. Calculate the average used capacity(AUC) of the entire cluster. (total data size / total backends num)
-2. The high water level is (AUC * (1 + clone_capacity_balance_threshold))
-3. The low water level is (AUC * (1 - clone_capacity_balance_threshold))
-4. The Clone checker will try to move replica from high water level BE to low water level BE.
-
-### replica_delay_recovery_second
-
-Default: 0
-
-IsMutable: true
-
-MasterOnly: true
-
-the minimal delay seconds between a replica is failed and fe try to recovery it using clone.
-
-### clone_high_priority_delay_second
-
-Default: 0
-
-IsMutable: true
-
-MasterOnly: true
-
-HIGH priority clone job's delay trigger time.
-
-### clone_normal_priority_delay_second
-
-Default: 300 （5min）
-
-IsMutable: true
-
-MasterOnly: true
-
-NORMAL priority clone job's delay trigger time
-
-### clone_low_priority_delay_second
-
-Default: 600 （10min）
-
-IsMutable: true
-
-MasterOnly: true
-
-LOW priority clone job's delay trigger time. A clone job contains a tablet which need to be cloned(recovery or migration). If the priority is LOW, it will be delayed *clone_low_priority_delay_second* after the job creation and then be executed. This is to avoid a large number of clone jobs running at same time only because a host is down for a short time.
- **NOTICE** that this config(and *clone_normal_priority_delay_second* as well) will not work if it's smaller then *clone_checker_interval_second*
-
-### clone_max_job_num
-
-Default: 100
-
-IsMutable: true
-
-MasterOnly: true
-
-Concurrency of LOW priority clone jobs. Concurrency of High priority clone jobs is currently unlimited.
-
-### clone_job_timeout_second
-
-Default: 7200 (2小时)
-
-IsMutable: true
-
-MasterOnly: true
-
-Default timeout of a single clone job. Set long enough to fit your replica size. The larger the replica data size is, the more time is will cost to finish clone
-
-### clone_checker_interval_second
-
-Default: 300 （5min）
-
-Clone checker's running interval
-
-### tablet_delete_timeout_second
-
-Default: 2
-
-IsMutable: true
-
-MasterOnly: true
-
-Same meaning as *tablet_create_timeout_second*, but used when delete a tablet.
-
-### async_loading_load_task_pool_size
-
-Default: 10
-
-IsMutable: false
-
-MasterOnly: true
-
-The loading_load task executor pool size. This pool size limits the max running loading_load tasks.
-
-Currently, it only limits the loading_load task of broker load
-
-### async_pending_load_task_pool_size
-
-Default: 10
-
-IsMutable: false
-
-MasterOnly: true
-
-The pending_load task executor pool size. This pool size limits the max running pending_load tasks.
-
-Currently, it only limits the pending_load task of broker load and spark load.
-
-It should be less than 'max_running_txn_num_per_db'
-
-### async_load_task_pool_size
-
-Default: 10
-
-IsMutable: false
-
-MasterOnly: true
-
-This configuration is just for compatible with old version, this config has been replaced by async_loading_load_task_pool_size, it will be removed in the future.
-
-### disable_show_stream_load
-
-Default: false
-
-IsMutable: true
-
-MasterOnly: true
-
-Whether to disable show stream load and clear stream load records in memory.
-
-### max_stream_load_record_size
-
-Default: 5000
-
-IsMutable: true
-
-MasterOnly: true
-
-Default max number of recent stream load record that can be stored in memory.
-
-### fetch_stream_load_record_interval_second
-
-Default: 120
-
-IsMutable: true
-
-MasterOnly: true
-
-fetch stream load record interval.
-
-### desired_max_waiting_jobs
-
-Default: 100
-
-IsMutable: true
-
-MasterOnly: true
-
-Default number of waiting jobs for routine load and version 2 of load , This is a desired number. In some situation, such as switch the master, the current number is maybe more than desired_max_waiting_jobs.
-
-### yarn_config_dir
-
-Default: PaloFe.DORIS_HOME_DIR + "/lib/yarn-config"
-
-Default yarn config file directory ,Each time before running the yarn command, we need to check that the config file exists under this path, and if not, create them.
-
-
-### yarn_client_path
-
-Default: DORIS_HOME_DIR + "/lib/yarn-client/hadoop/bin/yarn"
-
-Default yarn client path
-
-### spark_launcher_log_dir
-
-Default: sys_log_dir + "/spark_launcher_log"
-
-The specified spark launcher log dir
-
-### spark_resource_path
-
-Default: none
-
-Default spark dependencies path
-
-### spark_home_default_dir
-
-Default: DORIS_HOME_DIR + "/lib/spark2x"
-
-Default spark home dir
-
-### spark_load_default_timeout_second
-
-Default: 86400 (1天)
-
-IsMutable: true
-
-MasterOnly: true
-
-Default spark load timeout
-
-### spark_dpp_version
-
-Default: 1.0.0
-
-Default spark dpp version
-
-### hadoop_load_default_timeout_second
-
-Default: 86400 * 3 (3天)
-
-IsMutable: true
-
-MasterOnly: true
-
-Default hadoop load timeout
-
-### min_load_timeout_second
-
-Default: 1 （1s）
-
-IsMutable: true
-
-MasterOnly: true
-
-Min stream load timeout applicable to all type of load
-
-### max_stream_load_timeout_second
-
-Default: 259200 （3天）
-
-IsMutable: true
-
-MasterOnly: true
-
-This configuration is specifically used to limit timeout setting for stream load. It is to prevent that failed stream load transactions cannot be canceled within a short time because of the user's large timeout setting
-
-### max_load_timeout_second
-
-Default: 259200 （3天）
-
-IsMutable: true
-
-MasterOnly: true
-
-Max load timeout applicable to all type of load except for stream load
-
-### stream_load_default_timeout_second
-
-Default: 600 （s）
-
-IsMutable: true
-
-MasterOnly: true
-
-Default stream load and streaming mini load timeout
-
-### insert_load_default_timeout_second
-
-Default: 3600 （1 hour）
-
-IsMutable: true
-
-MasterOnly: true
-
-Default insert load timeout
-
-### mini_load_default_timeout_second
-
-Default: 3600 （1 hour）
-
-IsMutable: true
-
-MasterOnly: true
-
-Default non-streaming mini load timeout
-
-### broker_load_default_timeout_second
-
-Default: 14400 （4 hour）
-
-IsMutable: true
-
-MasterOnly: true
-
-Default broker load timeout
-
-### load_running_job_num_limit
-
-Default: 0
-
-IsMutable: true
-
-MasterOnly: true
-
-The number of loading tasks is limited, the default is 0, no limit
-
-### load_input_size_limit_gb
-
-Default: 0
-
-IsMutable: true
-
-MasterOnly: true
-
-The size of the data entered by the Load job, the default is 0, unlimited
-
-### delete_thread_num
-
-Default: 10
-
-Concurrency of delete jobs.
-
-### load_etl_thread_num_normal_priority
-
-Default: 10
-
-Concurrency of NORMAL priority etl load jobs. Do not change this if you know what you are doing.
-
-### load_etl_thread_num_high_priority
-
-Default: 3
-
-Concurrency of HIGH priority etl load jobs. Do not change this if you know what you are doing
-
-### load_pending_thread_num_normal_priority
-
-Default: 10
-
-Concurrency of NORMAL priority pending load jobs. Do not change this if you know what you are doing.
-
-### load_pending_thread_num_high_priority
-
-Default: 3
-
- Concurrency of HIGH priority pending load jobs. Load job priority is defined as HIGH or NORMAL. All mini batch load jobs are HIGH priority, other types of load jobs are NORMAL priority. Priority is set to avoid that a slow load job occupies a thread for a long time. This is just a internal optimized scheduling policy. Currently, you can not specified the job priority manually, and do not change this if you know what you are doing.
-
-### load_checker_interval_second
-
-Default: 5 （s）
-
-The load scheduler running interval. A load job will transfer its state from PENDING to LOADING to FINISHED. The load scheduler will transfer load job from PENDING to LOADING while the txn callback will transfer load job from LOADING to FINISHED. So a load job will cost at most one interval to finish when the concurrency has not reached the upper limit.
-
-### max_layout_length_per_row
-
-Default: 100000
-
-IsMutable: true
-
-MasterOnly: true
-
-Maximal memory layout length of a row. default is 100 KB. In BE, the maximal size of a RowBlock is 100MB(Configure as max_unpacked_row_block_size in be.conf). And each RowBlock contains 1024 rows. So the maximal size of a row is approximately 100 KB.
- eg.
- schema: k1(int), v1(decimal), v2(varchar(2000))
- then the memory layout length of a row is: 4(int) + 16(decimal) + 2000(varchar) = 2020 (Bytes)
- See memory layout length of all types, run 'help create table' in mysql-client.
- If you want to increase this number to support more columns in a row, you also need to increase the
- max_unpacked_row_block_size in be.conf. But the performance impact is unknown.
-
-### load_straggler_wait_second
-
-Default: 300
-
-IsMutable: true
-
-MasterOnly: true
-
-Maximal wait seconds for straggler node in load
- eg.
- there are 3 replicas A, B, C
- load is already quorum finished(A,B) at t1 and C is not finished
- if (current_time - t1) > 300s, then palo will treat C as a failure node
- will call transaction manager to commit the transaction and tell transaction manager
- that C is failed
-
- This is also used when waiting for publish tasks
- this parameter is the default value for all job and the DBA could specify it for separate job
-
-### thrift_server_max_worker_threads
-
-Default: 4096
-
-The thrift server max worker threads
-
-### publish_version_interval_ms
-
-Default: 10 （ms）
-
-minimal intervals between two publish version action
-
-### publish_version_timeout_second
-
-Default: 30 （s）
-
-IsMutable: true
-
-MasterOnly: true
-
-Maximal waiting time for all publish version tasks of one transaction to be finished
-
-### max_create_table_timeout_second
-
-Default: 60 （s）
-
-IsMutable: true
-
-MasterOnly: true
-
-In order not to wait too long for create table(index), set a max timeout.
-
-### tablet_create_timeout_second
-
-Default: 1（s）
-
-IsMutable: true
-
-MasterOnly: true
-
-Maximal waiting time for creating a single replica.
- eg.
- if you create a table with #m tablets and #n replicas for each tablet,
- the create table request will run at most (m * n * tablet_create_timeout_second) before timeout.
-
... 156916 lines suppressed ...
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org