From 1fe63855e577dde5918daf37132542cef9aa6b82 Mon Sep 17 00:00:00 2001 From: Yiran Date: Sun, 29 Sep 2024 14:06:03 +0800 Subject: [PATCH 1/4] rename operations to administration --- .../frontend/table-sharding.md | 2 +- docs/faq-and-others/faq.md | 4 +- docs/reference/command-lines.md | 2 +- docs/reference/sql/admin.md | 4 +- .../{operations => administration}/admin.md | 6 +-- .../capacity-plan.md | 2 +- .../data-management/basic-table-operations.md | 0 .../data-management/compaction.md | 0 .../data-management/overview.md | 2 +- .../data-management/region-failover.md | 2 +- .../data-management/region-migration.md | 0 .../data-management/table-sharding.md | 0 .../back-up-&-restore-data.md | 0 ...olution-based-on-active-active-failover.md | 0 ...oss-region-deployment-in-single-cluster.md | 0 .../dr-solution-for-standalone.md | 0 .../disaster-recovery/overview.md | 0 .../monitoring/export-metrics.md | 0 .../monitoring/overview.md | 0 .../monitoring/tracing.md | 0 .../overview.md | 0 .../performance-tuning-tips.md | 0 .../remote-wal/cluster-deployment.md | 0 .../remote-wal/quick-start.md | 0 .../{operations => administration}/upgrade.md | 0 docs/user-guide/concepts/data-model.md | 4 +- .../concepts/features-that-you-concern.md | 2 +- docs/user-guide/concepts/storage-location.md | 2 +- docs/user-guide/deployments/configuration.md | 6 +-- docs/user-guide/deployments/overview.md | 2 +- docs/user-guide/ingest-data/for-iot/sql.md | 2 +- docs/user-guide/manage-data/overview.md | 2 +- docs/user-guide/overview.md | 2 +- docs/user-guide/protocols/mysql.md | 2 +- docs/user-guide/protocols/postgresql.md | 2 +- docs/user-guide/query-data/sql.md | 4 +- .../current.json | 4 +- .../frontend/table-sharding.md | 2 +- .../current/faq-and-others/faq.md | 4 +- .../current/reference/command-lines.md | 2 +- .../current/reference/sql/admin.md | 4 +- .../{operations => administration}/admin.md | 6 +-- .../capacity-plan.md | 2 +- .../data-management/basic-table-operations.md | 0 .../data-management/compaction.md | 0 .../data-management/overview.md | 2 +- .../data-management/region-failover.md | 2 +- .../data-management/region-migration.md | 0 .../data-management/table-sharding.md | 0 .../back-up-&-restore-data.md | 0 ...olution-based-on-active-active-failover.md | 0 ...oss-region-deployment-in-single-cluster.md | 0 .../dr-solution-for-standalone.md | 0 .../disaster-recovery/overview.md | 0 .../monitoring/export-metrics.md | 0 .../monitoring/overview.md | 0 .../monitoring/tracing.md | 0 .../overview.md | 0 .../performance-tuning-tips.md | 0 .../remote-wal/cluster-deployment.md | 0 .../remote-wal/quick-start.md | 0 .../{operations => administration}/upgrade.md | 2 +- .../current/user-guide/concepts/data-model.md | 4 +- .../concepts/features-that-you-concern.md | 2 +- .../user-guide/concepts/storage-location.md | 2 +- .../user-guide/deployments/configuration.md | 6 +-- .../user-guide/deployments/overview.md | 2 +- .../user-guide/ingest-data/for-iot/sql.md | 4 +- .../user-guide/manage-data/overview.md | 2 +- .../current/user-guide/overview.md | 2 +- .../current/user-guide/protocols/mysql.md | 2 +- .../user-guide/protocols/postgresql.md | 2 +- .../current/user-guide/query-data/sql.md | 4 +- sidebars.ts | 40 +++++++++---------- 74 files changed, 78 insertions(+), 78 deletions(-) rename docs/user-guide/{operations => administration}/admin.md (82%) rename docs/user-guide/{operations => administration}/capacity-plan.md (97%) rename docs/user-guide/{operations => administration}/data-management/basic-table-operations.md (100%) rename docs/user-guide/{operations => administration}/data-management/compaction.md (100%) rename docs/user-guide/{operations => administration}/data-management/overview.md (86%) rename docs/user-guide/{operations => administration}/data-management/region-failover.md (98%) rename docs/user-guide/{operations => administration}/data-management/region-migration.md (100%) rename docs/user-guide/{operations => administration}/data-management/table-sharding.md (100%) rename docs/user-guide/{operations => administration}/disaster-recovery/back-up-&-restore-data.md (100%) rename docs/user-guide/{operations => administration}/disaster-recovery/dr-solution-based-on-active-active-failover.md (100%) rename docs/user-guide/{operations => administration}/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster.md (100%) rename docs/user-guide/{operations => administration}/disaster-recovery/dr-solution-for-standalone.md (100%) rename docs/user-guide/{operations => administration}/disaster-recovery/overview.md (100%) rename docs/user-guide/{operations => administration}/monitoring/export-metrics.md (100%) rename docs/user-guide/{operations => administration}/monitoring/overview.md (100%) rename docs/user-guide/{operations => administration}/monitoring/tracing.md (100%) rename docs/user-guide/{operations => administration}/overview.md (100%) rename docs/user-guide/{operations => administration}/performance-tuning-tips.md (100%) rename docs/user-guide/{operations => administration}/remote-wal/cluster-deployment.md (100%) rename docs/user-guide/{operations => administration}/remote-wal/quick-start.md (100%) rename docs/user-guide/{operations => administration}/upgrade.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/admin.md (80%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/capacity-plan.md (97%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/data-management/basic-table-operations.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/data-management/compaction.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/data-management/overview.md (85%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/data-management/region-failover.md (98%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/data-management/region-migration.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/data-management/table-sharding.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/disaster-recovery/back-up-&-restore-data.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/disaster-recovery/dr-solution-based-on-active-active-failover.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/disaster-recovery/dr-solution-for-standalone.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/disaster-recovery/overview.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/monitoring/export-metrics.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/monitoring/overview.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/monitoring/tracing.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/overview.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/performance-tuning-tips.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/remote-wal/cluster-deployment.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/remote-wal/quick-start.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/{operations => administration}/upgrade.md (99%) diff --git a/docs/contributor-guide/frontend/table-sharding.md b/docs/contributor-guide/frontend/table-sharding.md index 3f427007b..53d17a0cb 100644 --- a/docs/contributor-guide/frontend/table-sharding.md +++ b/docs/contributor-guide/frontend/table-sharding.md @@ -4,7 +4,7 @@ The sharding of stored data is essential to any distributed database. This docum ## Partition -For the syntax of creating a partitioned table, please refer to the [Table Sharding](/user-guide/operations/data-management/table-sharding.md) section in the User Guide. +For the syntax of creating a partitioned table, please refer to the [Table Sharding](/user-guide/administration/data-management/table-sharding.md) section in the User Guide. ## Region diff --git a/docs/faq-and-others/faq.md b/docs/faq-and-others/faq.md index 9a4ea03dd..be2ed8f6d 100644 --- a/docs/faq-and-others/faq.md +++ b/docs/faq-and-others/faq.md @@ -57,7 +57,7 @@ Please check out our initial version on [GitHub Repo](https://github.com/Greptim Yes, GreptimeDB is a schemaless database without need for creating tables in advance. The table and columns will be created automatically when writing data with protocol gRPC, InfluxDB, OpentsDB, Prometheus remote write. -For more information, refer to [this document](/user-guide/operations/data-management/basic-table-operations.md#create-table). +For more information, refer to [this document](/user-guide/administration/data-management/basic-table-operations.md#create-table). ### How do you measure the passing rate of PromQL compatibility tests? Is there any testing framework？ @@ -183,7 +183,7 @@ A minimum of 3 nodes is required, with each node running the 3 services: metasrv It is not necessary to deploy all three services on each node. A small-sized cluster can be set up with 3 nodes dedicated to metasrv. Frontend and datanode can be deployed on equal nodes, with one container running two processes. -For more general advice for deployment, please read [Capacity Plan](/user-guide/operations/capacity-plan.md). +For more general advice for deployment, please read [Capacity Plan](/user-guide/administration/capacity-plan.md). ### Does GreptimeDB support inverted indexes, and does it use Tantivy? diff --git a/docs/reference/command-lines.md b/docs/reference/command-lines.md index 06ac915d1..496566ce7 100644 --- a/docs/reference/command-lines.md +++ b/docs/reference/command-lines.md @@ -197,5 +197,5 @@ greptime flownode start --node-id=0 --rpc-addr=127.0.0.1:6800 --metasrv-addrs=12 ### Upgrade GreptimeDB version -Please refer to [the upgrade steps](/user-guide/operations/upgrade.md) +Please refer to [the upgrade steps](/user-guide/administration/upgrade.md) diff --git a/docs/reference/sql/admin.md b/docs/reference/sql/admin.md index ef2106517..36f800659 100644 --- a/docs/reference/sql/admin.md +++ b/docs/reference/sql/admin.md @@ -13,9 +13,9 @@ GreptimeDB provides some administration functions to manage the database and dat * `flush_table(table_name)` to flush a table's memtables into SST file by table name. * `flush_region(region_id)` to flush a region's memtables into SST file by region id. Find the region id through [PARTITIONS](./information-schema/partitions.md) table. -* `compact_table(table_name, [type], [options])` to schedule a compaction task for a table by table name, read [compaction](/user-guide/operations/data-management/compaction.md#strict-window-compaction-strategy-swcs-and-manual-compaction) for more details. +* `compact_table(table_name, [type], [options])` to schedule a compaction task for a table by table name, read [compaction](/user-guide/administration/data-management/compaction.md#strict-window-compaction-strategy-swcs-and-manual-compaction) for more details. * `compact_region(region_id)` to schedule a compaction task for a region by region id. -* `migrate_region(region_id, from_peer, to_peer, [timeout])` to migrate regions between datanodes, please read the [Region Migration](/user-guide/operations/data-management/region-migration.md). +* `migrate_region(region_id, from_peer, to_peer, [timeout])` to migrate regions between datanodes, please read the [Region Migration](/user-guide/administration/data-management/region-migration.md). * `procedure_state(procedure_id)` to query a procedure state by its id. * `flush_flow(flow_name)` to flush a flow's output into the sink table. diff --git a/docs/user-guide/operations/admin.md b/docs/user-guide/administration/admin.md similarity index 82% rename from docs/user-guide/operations/admin.md rename to docs/user-guide/administration/admin.md index 6db323273..f1306d9c6 100644 --- a/docs/user-guide/operations/admin.md +++ b/docs/user-guide/administration/admin.md @@ -6,8 +6,8 @@ This document addresses strategies and practices used in the operation of Grepti * [Installation](/getting-started/installation/overview.md) for GreptimeDB and the [g-t-control](/reference/gtctl.md) command line tool. * Database Configuration, please read the [Configuration](/user-guide/deployments/configuration.md) reference. -* [Monitoring metrics](/user-guide/operations/monitoring/export-metrics.md) and [Tracing](/user-guide/operations/monitoring/tracing.md) for GreptimeDB. -* GreptimeDB [Disaster Recovery](/user-guide/operations/disaster-recovery/overview.md). +* [Monitoring metrics](/user-guide/administration/monitoring/export-metrics.md) and [Tracing](/user-guide/administration/monitoring/tracing.md) for GreptimeDB. +* GreptimeDB [Disaster Recovery](/user-guide/administration/disaster-recovery/overview.md). * Cluster Failover for GreptimeDB by [Setting Remote WAL](./remote-wal/quick-start.md). ### Runtime information @@ -36,4 +36,4 @@ The `INFORMATION_SCHEMA` database provides access to system metadata, such as th ## Best Practices -* [Performance Tuning Tips](/user-guide/operations/performance-tuning-tips.md) \ No newline at end of file +* [Performance Tuning Tips](/user-guide/administration/performance-tuning-tips.md) \ No newline at end of file diff --git a/docs/user-guide/operations/capacity-plan.md b/docs/user-guide/administration/capacity-plan.md similarity index 97% rename from docs/user-guide/operations/capacity-plan.md rename to docs/user-guide/administration/capacity-plan.md index b457d93b8..afe1a7d24 100644 --- a/docs/user-guide/operations/capacity-plan.md +++ b/docs/user-guide/administration/capacity-plan.md @@ -13,7 +13,7 @@ there are several key considerations: - Data retention policy - Hardware costs -To monitor the various metrics of GreptimeDB, please refer to [Monitoring](/user-guide/operations/monitoring/export-metrics.md). +To monitor the various metrics of GreptimeDB, please refer to [Monitoring](/user-guide/administration/monitoring/export-metrics.md). ## CPU diff --git a/docs/user-guide/operations/data-management/basic-table-operations.md b/docs/user-guide/administration/data-management/basic-table-operations.md similarity index 100% rename from docs/user-guide/operations/data-management/basic-table-operations.md rename to docs/user-guide/administration/data-management/basic-table-operations.md diff --git a/docs/user-guide/operations/data-management/compaction.md b/docs/user-guide/administration/data-management/compaction.md similarity index 100% rename from docs/user-guide/operations/data-management/compaction.md rename to docs/user-guide/administration/data-management/compaction.md diff --git a/docs/user-guide/operations/data-management/overview.md b/docs/user-guide/administration/data-management/overview.md similarity index 86% rename from docs/user-guide/operations/data-management/overview.md rename to docs/user-guide/administration/data-management/overview.md index 7080a75c1..f735bbede 100644 --- a/docs/user-guide/operations/data-management/overview.md +++ b/docs/user-guide/administration/data-management/overview.md @@ -6,5 +6,5 @@ * [Expire Data by Setting TTL](/user-guide/manage-data/overview.md#manage-data-retention-with-ttl-policies) * [Table Sharding](table-sharding.md): Partition tables by regions * [Region Migration](region-migration.md): Migrate regions for load balancing -* [Region Failover](/user-guide/operations/data-management/region-failover.md) +* [Region Failover](/user-guide/administration/data-management/region-failover.md) * [Compaction](compaction.md) diff --git a/docs/user-guide/operations/data-management/region-failover.md b/docs/user-guide/administration/data-management/region-failover.md similarity index 98% rename from docs/user-guide/operations/data-management/region-failover.md rename to docs/user-guide/administration/data-management/region-failover.md index 3da11fc80..9bd2abe7a 100644 --- a/docs/user-guide/operations/data-management/region-failover.md +++ b/docs/user-guide/administration/data-management/region-failover.md @@ -1,6 +1,6 @@ # Region Failover -Region Failover provides the ability to recover regions from region failures without losing data. This is implemented via [Region Migration](/user-guide/operations/data-management/region-migration.md). +Region Failover provides the ability to recover regions from region failures without losing data. This is implemented via [Region Migration](/user-guide/administration/data-management/region-migration.md). ## Enable the Region Failover diff --git a/docs/user-guide/operations/data-management/region-migration.md b/docs/user-guide/administration/data-management/region-migration.md similarity index 100% rename from docs/user-guide/operations/data-management/region-migration.md rename to docs/user-guide/administration/data-management/region-migration.md diff --git a/docs/user-guide/operations/data-management/table-sharding.md b/docs/user-guide/administration/data-management/table-sharding.md similarity index 100% rename from docs/user-guide/operations/data-management/table-sharding.md rename to docs/user-guide/administration/data-management/table-sharding.md diff --git a/docs/user-guide/operations/disaster-recovery/back-up-&-restore-data.md b/docs/user-guide/administration/disaster-recovery/back-up-&-restore-data.md similarity index 100% rename from docs/user-guide/operations/disaster-recovery/back-up-&-restore-data.md rename to docs/user-guide/administration/disaster-recovery/back-up-&-restore-data.md diff --git a/docs/user-guide/operations/disaster-recovery/dr-solution-based-on-active-active-failover.md b/docs/user-guide/administration/disaster-recovery/dr-solution-based-on-active-active-failover.md similarity index 100% rename from docs/user-guide/operations/disaster-recovery/dr-solution-based-on-active-active-failover.md rename to docs/user-guide/administration/disaster-recovery/dr-solution-based-on-active-active-failover.md diff --git a/docs/user-guide/operations/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster.md b/docs/user-guide/administration/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster.md similarity index 100% rename from docs/user-guide/operations/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster.md rename to docs/user-guide/administration/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster.md diff --git a/docs/user-guide/operations/disaster-recovery/dr-solution-for-standalone.md b/docs/user-guide/administration/disaster-recovery/dr-solution-for-standalone.md similarity index 100% rename from docs/user-guide/operations/disaster-recovery/dr-solution-for-standalone.md rename to docs/user-guide/administration/disaster-recovery/dr-solution-for-standalone.md diff --git a/docs/user-guide/operations/disaster-recovery/overview.md b/docs/user-guide/administration/disaster-recovery/overview.md similarity index 100% rename from docs/user-guide/operations/disaster-recovery/overview.md rename to docs/user-guide/administration/disaster-recovery/overview.md diff --git a/docs/user-guide/operations/monitoring/export-metrics.md b/docs/user-guide/administration/monitoring/export-metrics.md similarity index 100% rename from docs/user-guide/operations/monitoring/export-metrics.md rename to docs/user-guide/administration/monitoring/export-metrics.md diff --git a/docs/user-guide/operations/monitoring/overview.md b/docs/user-guide/administration/monitoring/overview.md similarity index 100% rename from docs/user-guide/operations/monitoring/overview.md rename to docs/user-guide/administration/monitoring/overview.md diff --git a/docs/user-guide/operations/monitoring/tracing.md b/docs/user-guide/administration/monitoring/tracing.md similarity index 100% rename from docs/user-guide/operations/monitoring/tracing.md rename to docs/user-guide/administration/monitoring/tracing.md diff --git a/docs/user-guide/operations/overview.md b/docs/user-guide/administration/overview.md similarity index 100% rename from docs/user-guide/operations/overview.md rename to docs/user-guide/administration/overview.md diff --git a/docs/user-guide/operations/performance-tuning-tips.md b/docs/user-guide/administration/performance-tuning-tips.md similarity index 100% rename from docs/user-guide/operations/performance-tuning-tips.md rename to docs/user-guide/administration/performance-tuning-tips.md diff --git a/docs/user-guide/operations/remote-wal/cluster-deployment.md b/docs/user-guide/administration/remote-wal/cluster-deployment.md similarity index 100% rename from docs/user-guide/operations/remote-wal/cluster-deployment.md rename to docs/user-guide/administration/remote-wal/cluster-deployment.md diff --git a/docs/user-guide/operations/remote-wal/quick-start.md b/docs/user-guide/administration/remote-wal/quick-start.md similarity index 100% rename from docs/user-guide/operations/remote-wal/quick-start.md rename to docs/user-guide/administration/remote-wal/quick-start.md diff --git a/docs/user-guide/operations/upgrade.md b/docs/user-guide/administration/upgrade.md similarity index 100% rename from docs/user-guide/operations/upgrade.md rename to docs/user-guide/administration/upgrade.md diff --git a/docs/user-guide/concepts/data-model.md b/docs/user-guide/concepts/data-model.md index d26df5ceb..e47c14315 100644 --- a/docs/user-guide/concepts/data-model.md +++ b/docs/user-guide/concepts/data-model.md @@ -78,7 +78,7 @@ CREATE TABLE access_logs ( - `remote_addr`, `http_status`, `http_method`, `http_refer` and `user_agent` are tags. - `request` is a field that enables full-text index by the [`FULLTEXT` column option](/reference/sql/create.md#fulltext-column-option). -To learn how to indicate `Tag`, `Timestamp`, and `Field` columns, Please refer to [table management](/user-guide/operations/data-management/basic-table-operations.md#create-a-table) and [CREATE statement](/reference/sql/create.md). +To learn how to indicate `Tag`, `Timestamp`, and `Field` columns, Please refer to [table management](/user-guide/administration/data-management/basic-table-operations.md#create-a-table) and [CREATE statement](/reference/sql/create.md). Of course, you can place metrics and logs in a single table at any time, which is also a key capability provided by GreptimeDB. @@ -95,4 +95,4 @@ GreptimeDB is designed on top of Table for the following reasons: The multi-value model is used to model data sources, where a metric can have multiple values represented by fields. The advantage of the multi-value model is that it can write or read multiple values to the database at once, reducing transfer traffic and simplifying queries. In contrast, the single-value model requires splitting the data into multiple records. Read the [blog](https://greptime.com/blogs/2024-05-09-prometheus) for more detailed benefits of multi-value mode. -GreptimeDB uses SQL to manage table schema. Please refer to [table management](/user-guide/operations/data-management/basic-table-operations.md) for more information. However, our definition of schema is not mandatory and leans towards a **schemaless** approach, similar to MongoDB. For more details, see [Automatic Schema Generation](/user-guide/ingest-data/overview.md#automatic-schema-generation). +GreptimeDB uses SQL to manage table schema. Please refer to [table management](/user-guide/administration/data-management/basic-table-operations.md) for more information. However, our definition of schema is not mandatory and leans towards a **schemaless** approach, similar to MongoDB. For more details, see [Automatic Schema Generation](/user-guide/ingest-data/overview.md#automatic-schema-generation). diff --git a/docs/user-guide/concepts/features-that-you-concern.md b/docs/user-guide/concepts/features-that-you-concern.md index c715be7ca..f7b302957 100644 --- a/docs/user-guide/concepts/features-that-you-concern.md +++ b/docs/user-guide/concepts/features-that-you-concern.md @@ -58,4 +58,4 @@ Please read the performance benchmark reports: ## Does GreptimeDB have disaster recovery solutions? -Yes. Please refer to [disaster recovery](/user-guide/operations/disaster-recovery/overview.md). \ No newline at end of file +Yes. Please refer to [disaster recovery](/user-guide/administration/disaster-recovery/overview.md). \ No newline at end of file diff --git a/docs/user-guide/concepts/storage-location.md b/docs/user-guide/concepts/storage-location.md index 090ad18f7..eb23c63ea 100644 --- a/docs/user-guide/concepts/storage-location.md +++ b/docs/user-guide/concepts/storage-location.md @@ -33,7 +33,7 @@ The storage file structure of GreptimeDB includes of the following: The `data` directory in the file structure can be stored in cloud storage. Please refer to [Storage option](../deployments/configuration.md#storage-options) for more details. -Please note that only storing the data directory in object storage is not sufficient to ensure data reliability and disaster recovery. The `wal` and `metadata` also need to be considered for disaster recovery. Please refer to the [disaster recovery documentation](/user-guide/operations/disaster-recovery/overview.md). +Please note that only storing the data directory in object storage is not sufficient to ensure data reliability and disaster recovery. The `wal` and `metadata` also need to be considered for disaster recovery. Please refer to the [disaster recovery documentation](/user-guide/administration/disaster-recovery/overview.md). ## Multiple storage engines diff --git a/docs/user-guide/deployments/configuration.md b/docs/user-guide/deployments/configuration.md index a1a242634..25cea25f5 100644 --- a/docs/user-guide/deployments/configuration.md +++ b/docs/user-guide/deployments/configuration.md @@ -386,9 +386,9 @@ default_ratio = 1.0 - `enable_otlp_tracing`: whether to turn on tracing, not turned on by default. - `otlp_endpoint`: Export the target endpoint of tracing using gRPC-based OTLP protocol, the default value is `localhost:4317`. - `append_stdout`: Whether to append logs to stdout. Defaults to `true`. -- `tracing_sample_ratio`: This field can configure the sampling rate of tracing. How to use `tracing_sample_ratio`, please refer to [How to configure tracing sampling rate](/user-guide/operations/monitoring/tracing.md#guide-how-to-configure-tracing-sampling-rate). +- `tracing_sample_ratio`: This field can configure the sampling rate of tracing. How to use `tracing_sample_ratio`, please refer to [How to configure tracing sampling rate](/user-guide/administration/monitoring/tracing.md#guide-how-to-configure-tracing-sampling-rate). -How to use distributed tracing, please reference [Tracing](/user-guide/operations/monitoring/tracing.md#tutorial-use-jaeger-to-trace-greptimedb) +How to use distributed tracing, please reference [Tracing](/user-guide/administration/monitoring/tracing.md#tutorial-use-jaeger-to-trace-greptimedb) ### Region engine options @@ -482,7 +482,7 @@ The `meta_client` configures the Metasrv client, including: ### Monitor metrics options These options are used to save system metrics to GreptimeDB itself. -For instructions on how to use this feature, please refer to the [Monitoring](/user-guide/operations/monitoring/export-metrics.md) guide. +For instructions on how to use this feature, please refer to the [Monitoring](/user-guide/administration/monitoring/export-metrics.md) guide. ```toml [export_metrics] diff --git a/docs/user-guide/deployments/overview.md b/docs/user-guide/deployments/overview.md index d54438c09..cb4c1bc2f 100644 --- a/docs/user-guide/deployments/overview.md +++ b/docs/user-guide/deployments/overview.md @@ -18,7 +18,7 @@ Learn how to [run GreptimeDB on Android devices](run-on-android.md). ## Capacity plan -Understand how to [plan for capacity](/user-guide/operations/capacity-plan.md) to ensure your GreptimeDB deployment can handle your workload. +Understand how to [plan for capacity](/user-guide/administration/capacity-plan.md) to ensure your GreptimeDB deployment can handle your workload. ## GreptimeCloud diff --git a/docs/user-guide/ingest-data/for-iot/sql.md b/docs/user-guide/ingest-data/for-iot/sql.md index 251cf3587..8cd5f7106 100644 --- a/docs/user-guide/ingest-data/for-iot/sql.md +++ b/docs/user-guide/ingest-data/for-iot/sql.md @@ -32,7 +32,7 @@ The above statement will create a table with the following schema: ``` For more information about the `CREATE TABLE` statement, -please refer to [table management](/user-guide/operations/data-management/basic-table-operations.md#create-a-table). +please refer to [table management](/user-guide/administration/data-management/basic-table-operations.md#create-a-table). ## Insert data diff --git a/docs/user-guide/manage-data/overview.md b/docs/user-guide/manage-data/overview.md index 0cc180a26..d2adf251d 100644 --- a/docs/user-guide/manage-data/overview.md +++ b/docs/user-guide/manage-data/overview.md @@ -317,5 +317,5 @@ For more information about TTL policies, please refer to the [CREATE](/reference ## More data management operations -For more advanced data management operations, such as basic table operations, table sharding and region migration, please refer to the [Data Management](/user-guide/operations/data-management/overview.md) in the administration section. +For more advanced data management operations, such as basic table operations, table sharding and region migration, please refer to the [Data Management](/user-guide/administration/data-management/overview.md) in the administration section. diff --git a/docs/user-guide/overview.md b/docs/user-guide/overview.md index a3b5fa45e..172e8ce51 100644 --- a/docs/user-guide/overview.md +++ b/docs/user-guide/overview.md @@ -66,5 +66,5 @@ Having understood these features, you can now go directly to exploring the featu * [Integrations](./integrations/overview.md) * [Protocols](./protocols/overview.md) * [Continuous Aggregation](./continuous-aggregation/overview.md) -* [Operations](./operations/overview.md) +* [Operations](./administration/overview.md) diff --git a/docs/user-guide/protocols/mysql.md b/docs/user-guide/protocols/mysql.md index 2bdac13b7..3f076a6e9 100644 --- a/docs/user-guide/protocols/mysql.md +++ b/docs/user-guide/protocols/mysql.md @@ -14,7 +14,7 @@ mysql -h -P 4002 -u -p ## Table management -Please refer to [Table Management](/user-guide/operations/data-management/basic-table-operations.md). +Please refer to [Table Management](/user-guide/administration/data-management/basic-table-operations.md). ## Ingest data diff --git a/docs/user-guide/protocols/postgresql.md b/docs/user-guide/protocols/postgresql.md index af551d0e0..1b431a4a5 100644 --- a/docs/user-guide/protocols/postgresql.md +++ b/docs/user-guide/protocols/postgresql.md @@ -15,7 +15,7 @@ psql -h -p 4003 -U -d public ## Table management -Please refer to [Table Management](/user-guide/operations/data-management/basic-table-operations.md). +Please refer to [Table Management](/user-guide/administration/data-management/basic-table-operations.md). ## Ingest data diff --git a/docs/user-guide/query-data/sql.md b/docs/user-guide/query-data/sql.md index e551fc3da..6fabec7bf 100644 --- a/docs/user-guide/query-data/sql.md +++ b/docs/user-guide/query-data/sql.md @@ -4,7 +4,7 @@ GreptimeDB supports full SQL for querying data from a database. In this document, we will use the `monitor` table to demonstrate how to query data. For instructions on creating the `monitor` table and inserting data into it, -Please refer to [table management](/user-guide/operations/data-management/basic-table-operations.md#create-a-table) and [Ingest Data](/user-guide/ingest-data/for-iot/sql.md). +Please refer to [table management](/user-guide/administration/data-management/basic-table-operations.md#create-a-table) and [Ingest Data](/user-guide/ingest-data/for-iot/sql.md). ## Basic query @@ -265,7 +265,7 @@ SELECT DISTINCT ON (host) * FROM monitor ORDER BY host, ts DESC; GreptimeDB supports [Range Query](/reference/sql/range.md) to aggregate data by time window. -Suppose we have the following data in the [`monitor` table](/user-guide/operations/data-management/basic-table-operations.md#create-a-table): +Suppose we have the following data in the [`monitor` table](/user-guide/administration/data-management/basic-table-operations.md#create-a-table): ```sql +-----------+---------------------+------+--------+ diff --git a/i18n/zh/docusaurus-plugin-content-docs/current.json b/i18n/zh/docusaurus-plugin-content-docs/current.json index 18e6f2a6e..8fb0d7aa1 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current.json +++ b/i18n/zh/docusaurus-plugin-content-docs/current.json @@ -43,8 +43,8 @@ "message": "客户端库", "description": "The label for category Client Libraries in sidebar docs" }, - "sidebar.docs.category.Operations": { - "message": "运维操作", + "sidebar.docs.category.Administration": { + "message": "管理数据库", "description": "The label for category Operations in sidebar docs" }, "sidebar.docs.category.Deployments": { diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/contributor-guide/frontend/table-sharding.md b/i18n/zh/docusaurus-plugin-content-docs/current/contributor-guide/frontend/table-sharding.md index d30591059..1128df2a4 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/contributor-guide/frontend/table-sharding.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/contributor-guide/frontend/table-sharding.md @@ -4,7 +4,7 @@ ## 分区 -有关创建分区表的语法，请参阅用户指南中的[表分片](/user-guide/operations/data-management/table-sharding.md)部分。 +有关创建分区表的语法，请参阅用户指南中的[表分片](/user-guide/administration/data-management/table-sharding.md)部分。 ## Region diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/faq-and-others/faq.md b/i18n/zh/docusaurus-plugin-content-docs/current/faq-and-others/faq.md index 3f89da632..05bfa98e6 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/faq-and-others/faq.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/faq-and-others/faq.md @@ -58,7 +58,7 @@ Please check out our initial version on [GitHub Repo](https://github.com/Greptim Yes, GreptimeDB is a schemaless database without need for creating tables in advance. The table and columns will be created automatically when writing data with protocol gRPC, InfluxDB, OpentsDB, Prometheus remote write. -For more information, refer to [this document](/user-guide/operations/data-management/basic-table-operations.md#create-table). +For more information, refer to [this document](/user-guide/administration/data-management/basic-table-operations.md#create-table). ### How do you measure the passing rate of PromQL compatibility tests? Is there any testing framework？ @@ -184,7 +184,7 @@ A minimum of 3 nodes is required, with each node running the 3 services: metasrv It is not necessary to deploy all three services on each node. A small-sized cluster can be set up with 3 nodes dedicated to metasrv. Frontend and datanode can be deployed on equal nodes, with one container running two processes. -For more general advice for deployment, please read [Capacity Plan](/user-guide/operations/capacity-plan.md). +For more general advice for deployment, please read [Capacity Plan](/user-guide/administration/capacity-plan.md). ### Does GreptimeDB support inverted indexes, and does it use Tantivy? diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/reference/command-lines.md b/i18n/zh/docusaurus-plugin-content-docs/current/reference/command-lines.md index f57ade7c8..b4274ac7e 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/reference/command-lines.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/reference/command-lines.md @@ -197,4 +197,4 @@ greptime flownode start --node-id=0 --rpc-addr=127.0.0.1:6800 --metasrv-addrs=12 ### 升级 GreptimeDB 版本 -请参考具体的[升级步骤](/user-guide/operations/upgrade.md) +请参考具体的[升级步骤](/user-guide/administration/upgrade.md) diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/reference/sql/admin.md b/i18n/zh/docusaurus-plugin-content-docs/current/reference/sql/admin.md index dc28aea6f..2c71154d7 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/reference/sql/admin.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/reference/sql/admin.md @@ -12,9 +12,9 @@ GreptimeDB 提供了一些管理函数来管理数据库和数据： * `flush_table(table_name)` 根据表名将表的 Memtable 刷新到 SST 文件中。 * `flush_region(region_id)` 根据 Region ID 将 Region 的 Memtable 刷新到 SST 文件中。通过 [PARTITIONS](./information-schema/partitions.md) 表查找 Region ID。 -* `compact_table(table_name, [type], [options])` 为表启动一个 compaction 任务，详细信息请阅读 [compaction](/user-guide/operations/data-management/compaction.md#严格窗口压缩策略swcs和手动压缩)。 +* `compact_table(table_name, [type], [options])` 为表启动一个 compaction 任务，详细信息请阅读 [compaction](/user-guide/administration/data-management/compaction.md#严格窗口压缩策略swcs和手动压缩)。 * `compact_region(region_id)` 为 Region 启动一个 compaction 任务。 -* `migrate_region(region_id, from_peer, to_peer, [timeout])` 在 Datanode 之间迁移 Region，请阅读 [Region Migration](/user-guide/operations/data-management/region-migration.md)。 +* `migrate_region(region_id, from_peer, to_peer, [timeout])` 在 Datanode 之间迁移 Region，请阅读 [Region Migration](/user-guide/administration/data-management/region-migration.md)。 * `procedure_state(procedure_id)` 根据 ID 查询 Procedure 状态。 * `flush_flow(flow_name)` 将 Flow 的输出刷新到目标接收表。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/admin.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/admin.md similarity index 80% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/admin.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/admin.md index 9dc24e317..e82752966 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/admin.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/admin.md @@ -6,8 +6,8 @@ * GreptimeDB 的 [安装](/getting-started/installation/overview.md) 和 [g-t-control](/reference/gtctl.md) 命令行工具。 * 数据库配置，请阅读 [配置](/user-guide/deployments/configuration.md) 参考。 -* GreptimeDB 的 [指标监控](/user-guide/operations/monitoring/export-metrics.md) 和 [链路追踪](/user-guide/operations/monitoring/tracing.md)。 -* GreptimeDB 的 [灾难恢复方案](/user-guide/operations/disaster-recovery/overview.md)。 +* GreptimeDB 的 [指标监控](/user-guide/administration/monitoring/export-metrics.md) 和 [链路追踪](/user-guide/administration/monitoring/tracing.md)。 +* GreptimeDB 的 [灾难恢复方案](/user-guide/administration/disaster-recovery/overview.md)。 * 通过[设置 Remote WAL](./remote-wal/quick-start.md) 实现 GreptimeDB 的集群容灾。 ### 运行时信息 @@ -36,4 +36,4 @@ ORDER BY datanode_id ASC ## 最佳实践 -* [性能调优技巧](/user-guide/operations/performance-tuning-tips.md) \ No newline at end of file +* [性能调优技巧](/user-guide/administration/performance-tuning-tips.md) \ No newline at end of file diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/capacity-plan.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/capacity-plan.md similarity index 97% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/capacity-plan.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/capacity-plan.md index d6f89380a..dc4f92455 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/capacity-plan.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/capacity-plan.md @@ -13,7 +13,7 @@ GreptimeDB 具备超轻量级的启动基准， - 数据保留策略 - 硬件成本 -要监控 GreptimeDB 的各种指标，请参阅[监控](/user-guide/operations/monitoring/export-metrics.md)。 +要监控 GreptimeDB 的各种指标，请参阅[监控](/user-guide/administration/monitoring/export-metrics.md)。 ## CPU diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/basic-table-operations.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/basic-table-operations.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/basic-table-operations.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/basic-table-operations.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/compaction.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/compaction.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/compaction.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/compaction.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/overview.md similarity index 85% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/overview.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/overview.md index 86810f7cc..5a3316971 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/overview.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/overview.md @@ -6,5 +6,5 @@ * [通过设置 TTL 过期数据](/user-guide/manage-data/overview.md#使用-ttl-策略保留数据) * [表分片](table-sharding.md): 按 Region 对表进行分区 * [Region Migration](region-migration.md): 为负载均衡迁移 Region -* [Region Failover](/user-guide/operations/data-management/region-failover.md) +* [Region Failover](/user-guide/administration/data-management/region-failover.md) * [Compaction](compaction.md) diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/region-failover.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/region-failover.md similarity index 98% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/region-failover.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/region-failover.md index 2b7d5a6cf..7484834a4 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/region-failover.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/region-failover.md @@ -1,6 +1,6 @@ # Region Failover -Region Failover 提供了在不丢失数据的情况下从 Region 故障中恢复的能力。这是通过 [Region 迁移](/user-guide/operations/data-management/region-migration.md) 实现的。 +Region Failover 提供了在不丢失数据的情况下从 Region 故障中恢复的能力。这是通过 [Region 迁移](/user-guide/administration/data-management/region-migration.md) 实现的。 ## 开启 Region Failover diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/region-migration.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/region-migration.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/region-migration.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/region-migration.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/table-sharding.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/table-sharding.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/data-management/table-sharding.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/table-sharding.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/disaster-recovery/back-up-&-restore-data.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/disaster-recovery/back-up-&-restore-data.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/disaster-recovery/back-up-&-restore-data.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/disaster-recovery/back-up-&-restore-data.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/disaster-recovery/dr-solution-based-on-active-active-failover.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/disaster-recovery/dr-solution-based-on-active-active-failover.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/disaster-recovery/dr-solution-based-on-active-active-failover.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/disaster-recovery/dr-solution-based-on-active-active-failover.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/disaster-recovery/dr-solution-for-standalone.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/disaster-recovery/dr-solution-for-standalone.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/disaster-recovery/dr-solution-for-standalone.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/disaster-recovery/dr-solution-for-standalone.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/disaster-recovery/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/disaster-recovery/overview.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/disaster-recovery/overview.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/disaster-recovery/overview.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/monitoring/export-metrics.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/monitoring/export-metrics.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/monitoring/export-metrics.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/monitoring/export-metrics.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/monitoring/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/monitoring/overview.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/monitoring/overview.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/monitoring/overview.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/monitoring/tracing.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/monitoring/tracing.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/monitoring/tracing.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/monitoring/tracing.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/overview.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/performance-tuning-tips.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/performance-tuning-tips.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/performance-tuning-tips.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/performance-tuning-tips.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/remote-wal/cluster-deployment.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/remote-wal/cluster-deployment.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/remote-wal/cluster-deployment.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/remote-wal/cluster-deployment.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/remote-wal/quick-start.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/remote-wal/quick-start.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/remote-wal/quick-start.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/remote-wal/quick-start.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/upgrade.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/upgrade.md similarity index 99% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/upgrade.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/upgrade.md index dbfb59c09..34e0a53f5 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/operations/upgrade.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/upgrade.md @@ -1,4 +1,4 @@ -# Upgrade +# 版本升级 从 `v0.4` 开始，我们提供了一个内置的工具来帮助您将以前的 GreptimeDB 部署升级到最新版本。 如果不同版本之间有 Breaking Change，我们都建议使用此方法在不同版本的 GreptimeDB 之间进行迁移升级。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/data-model.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/data-model.md index f9914239e..23e9eafa7 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/data-model.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/data-model.md @@ -63,7 +63,7 @@ CREATE TABLE access_logs ( - `remote_addr`、`http_status`、`http_method`、`http_refer`、`user_agent` 为 Tag。 - `request` 是通过 [`FULLTEXT` 列选项](/reference/sql/create.md#fulltext-列选项)启用全文索引的字段。 -要了解如何指定 `Tag`、`Timestamp` 和 `Field` 列，请参见[表管理](/user-guide/operations/data-management/basic-table-operations.md#创建表)和 [CREATE 语句](/reference/sql/create.md)。 +要了解如何指定 `Tag`、`Timestamp` 和 `Field` 列，请参见[表管理](/user-guide/administration/data-management/basic-table-operations.md#创建表)和 [CREATE 语句](/reference/sql/create.md)。 当然，无论何时，你都可以将指标和日志放在一张表里，这也是 GreptimeDB 提供的关键能力。 @@ -77,4 +77,4 @@ GreptimeDB 基于表进行设计，原因如下： - 当我们有了表格 Schema 后，自然而然地引入了 SQL，并用它来处理各种表之间的关联分析和聚合查询，为用户抵消了学习和使用成本。 - 比起 OpenTSDB 和 Prometheus 采用的单值模型，GreptimeDB 使用多值模型使其中一行数据可以具有多列数据。多值模型面向数据源建模，一个 metric 可以有用 field 表示的值。多值模型的优势在于它可以一次性向数据库写入或读取多个值，从而减少传输流量并简化查询。相比之下，单值模型则需要将数据拆分成多个记录。阅读[博客](https://greptime.com/blogs/2024-05-09-prometheus)以获取更多详情。 -GreptimeDB 使用 SQL 管理表 Schema。有关更多信息，请参见[表管理](/user-guide/operations/data-management/basic-table-operations.md)。但是，我们对 Schema 的定义并不是强制性的，而是倾向于 **Schemaless** 的方式，类似于 MongoDB。有关更多详细信息，请参见[自动生成表结构](../ingest-data/overview.md#自动生成表结构)。 +GreptimeDB 使用 SQL 管理表 Schema。有关更多信息，请参见[表管理](/user-guide/administration/data-management/basic-table-operations.md)。但是，我们对 Schema 的定义并不是强制性的，而是倾向于 **Schemaless** 的方式，类似于 MongoDB。有关更多详细信息，请参见[自动生成表结构](../ingest-data/overview.md#自动生成表结构)。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/features-that-you-concern.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/features-that-you-concern.md index 601c20c31..be1132bf5 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/features-that-you-concern.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/features-that-you-concern.md @@ -56,4 +56,4 @@ GreptimeDB 还提供一个完全托管的云服务 [GreptimeCloud](https://grept ## GreptimeDB 有灾难恢复解决方案吗？ -有的，请参阅[灾难恢复文档](/user-guide/operations/disaster-recovery/overview.md)。 +有的，请参阅[灾难恢复文档](/user-guide/administration/disaster-recovery/overview.md)。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/storage-location.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/storage-location.md index 6425ef9cd..220e33206 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/storage-location.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/storage-location.md @@ -33,7 +33,7 @@ GreptimeDB 的存储文件结构包括以下内容： 文件结构中的 `cluster` 和 `data` 目录可以存储在云存储中。请参考[存储选项](../deployments/configuration.md#存储选项)了解更多细节。 -请注意，仅将 `data` 目录存储在对象存储中不足以确保数据可靠性和灾难恢复，`wal` 和 `metadata` 也需要考虑灾难恢复，更详细地请参阅[灾难恢复文档](/user-guide/operations/disaster-recovery/overview.md)。 +请注意，仅将 `data` 目录存储在对象存储中不足以确保数据可靠性和灾难恢复，`wal` 和 `metadata` 也需要考虑灾难恢复，更详细地请参阅[灾难恢复文档](/user-guide/administration/disaster-recovery/overview.md)。 ## 多存储引擎支持 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments/configuration.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments/configuration.md index 4e28d1ab0..efbd204c3 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments/configuration.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments/configuration.md @@ -375,9 +375,9 @@ default_ratio = 1.0 - `enable_otlp_tracing`：是否打开分布式追踪，默认不开启。 - `otlp_endpoint`：使用基于 gRPC 的 OTLP 协议导出 tracing 的目标端点，默认值为 `localhost:4317`。 - `append_stdout`：是否将日志打印到 stdout。默认是`true`。 -- `tracing_sample_ratio`：该字段可以配置 tracing 的采样率，如何使用 `tracing_sample_ratio`，请参考 [如何配置 tracing 采样率](/user-guide/operations/monitoring/tracing.md#指南如何配置-tracing-采样率)。 +- `tracing_sample_ratio`：该字段可以配置 tracing 的采样率，如何使用 `tracing_sample_ratio`，请参考 [如何配置 tracing 采样率](/user-guide/administration/monitoring/tracing.md#指南如何配置-tracing-采样率)。 -如何使用分布式追踪，请参考 [Tracing](/user-guide/operations/monitoring/tracing.md#教程使用-jaeger-追踪-greptimedb-调用链路) +如何使用分布式追踪，请参考 [Tracing](/user-guide/administration/monitoring/tracing.md#教程使用-jaeger-追踪-greptimedb-调用链路) ### Region 引擎选项 @@ -471,7 +471,7 @@ tcp_nodelay = true ### 指标监控选项 这些选项用于将系统监控指标保存到 GreptimeDB 本身。 -有关如何使用此功能的说明，请参见 [监控](/user-guide/operations/monitoring/export-metrics.md) 指南。 +有关如何使用此功能的说明，请参见 [监控](/user-guide/administration/monitoring/export-metrics.md) 指南。 ```toml [export_metrics] diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments/overview.md index c6311ab5d..c92382554 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments/overview.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments/overview.md @@ -20,7 +20,7 @@ GreptimeDB 默认不启用鉴权认证。 ## 容量规划 -了解如何[规划容量](/user-guide/operations/capacity-plan.md)以确保你的 GreptimeDB 部署能够处理你的工作负载。 +了解如何[规划容量](/user-guide/administration/capacity-plan.md)以确保你的 GreptimeDB 部署能够处理你的工作负载。 ## GreptimeCloud diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/ingest-data/for-iot/sql.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/ingest-data/for-iot/sql.md index 3d6fc8fb4..bc3f5eee7 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/ingest-data/for-iot/sql.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/ingest-data/for-iot/sql.md @@ -3,7 +3,7 @@ 你可以使用 [MySQL](/user-guide/protocols/mysql.md) 或 [PostgreSQL](/user-guide/protocols/postgresql.md) 客户端执行 SQL 语句， 使用任何你喜欢的编程语言（如Java JDBC）通过 MySQL 或 PostgreSQL 协议访问 GreptimeDB。 -我们将使用 `monitor` 表作为示例来展示如何写入数据。有关如何创建 `monitor` 表的 SQL 示例，请参见[表管理](/user-guide/operations/data-management/basic-table-operations.md#创建表)。 +我们将使用 `monitor` 表作为示例来展示如何写入数据。有关如何创建 `monitor` 表的 SQL 示例，请参见[表管理](/user-guide/administration/data-management/basic-table-operations.md#创建表)。 ## 创建表 @@ -32,7 +32,7 @@ CREATE TABLE monitor ( 4 rows in set (0.01 sec) ``` -有关 `CREATE TABLE` 语句的更多信息，请参阅[表管理](/user-guide/operations/data-management/basic-table-operations.md#create-a-table)。 +有关 `CREATE TABLE` 语句的更多信息，请参阅[表管理](/user-guide/administration/data-management/basic-table-operations.md#create-a-table)。 ## 插入数据 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/manage-data/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/manage-data/overview.md index 69dab0448..99198e5bc 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/manage-data/overview.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/manage-data/overview.md @@ -314,4 +314,4 @@ CREATE DATABASE test WITH ('ttl'='7d'); ## 更多数据管理操作 -有关更高级的数据管理操作，例如基本表操作、表分片和 Region 迁移，请参阅 Administration 部分的[数据管理](/user-guide/operations/data-management/overview.md)。 +有关更高级的数据管理操作，例如基本表操作、表分片和 Region 迁移，请参阅 Administration 部分的[数据管理](/user-guide/administration/data-management/overview.md)。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/overview.md index 59daaa29e..fc6893f33 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/overview.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/overview.md @@ -66,4 +66,4 @@ ALIGN '5s' BY (host) FILL PREV * [集成](./integrations/overview.md) * [协议](./protocols/overview.md) * [持续聚合](./continuous-aggregation/overview.md) -* [运维操作](./operations/overview.md) +* [运维操作](./administration/overview.md) diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/mysql.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/mysql.md index 264dadfec..d0d3e3b6e 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/mysql.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/mysql.md @@ -14,7 +14,7 @@ mysql -h -P 4002 -u -p ## 管理表 -请参考[表管理](/user-guide/operations/data-management/basic-table-operations.md)。 +请参考[表管理](/user-guide/administration/data-management/basic-table-operations.md)。 ## 写入数据 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/postgresql.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/postgresql.md index b83191ab6..845d624e5 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/postgresql.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/postgresql.md @@ -14,7 +14,7 @@ psql -h -p 4003 -U -d public ## 管理表 -请参考[管理表](/user-guide/operations/data-management/basic-table-operations.md)。 +请参考[管理表](/user-guide/administration/data-management/basic-table-operations.md)。 ## 写入数据 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/query-data/sql.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/query-data/sql.md index 39e2b2e4e..f5c7acd58 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/query-data/sql.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/query-data/sql.md @@ -2,7 +2,7 @@ GreptimeDB 在查询数据时支持完整的 `SQL` 语法。 -在这篇文档中，我们将使用 `monitor` 表中的数据作为示例来演示如何查询数据。关于如何创建 `monitor` 表格并向其中插入数据，请参考[表管理](/user-guide/operations/data-management/basic-table-operations.md#创建表)和[写入数据](/user-guide/ingest-data/for-iot/sql.md)。 +在这篇文档中，我们将使用 `monitor` 表中的数据作为示例来演示如何查询数据。关于如何创建 `monitor` 表格并向其中插入数据，请参考[表管理](/user-guide/administration/data-management/basic-table-operations.md#创建表)和[写入数据](/user-guide/ingest-data/for-iot/sql.md)。 ## 基础查询 @@ -253,7 +253,7 @@ SELECT DISTINCT ON (host) * FROM monitor ORDER BY host, ts DESC; GreptimeDB 支持 [Range Query](/reference/sql/range.md) 来按时间窗口聚合数据。 -假设我们有以下数据在 [`monitor` 表](/user-guide/operations/data-management/basic-table-operations.md#创建表) 中： +假设我们有以下数据在 [`monitor` 表](/user-guide/administration/data-management/basic-table-operations.md#创建表) 中： ```sql +-----------+---------------------+------+--------+ diff --git a/sidebars.ts b/sidebars.ts index 2003133d9..5260dd8d5 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -174,49 +174,49 @@ const sidebars: SidebarsConfig = { }, { type: 'category', - label: 'Operations', + label: 'Administration', items: [ - 'user-guide/operations/overview', - 'user-guide/operations/admin', - 'user-guide/operations/capacity-plan', + 'user-guide/administration/overview', + 'user-guide/administration/admin', + 'user-guide/administration/capacity-plan', { type: 'category', label: 'Data Management', items: [ - 'user-guide/operations/data-management/overview', - 'user-guide/operations/data-management/basic-table-operations', - 'user-guide/operations/data-management/table-sharding', - 'user-guide/operations/data-management/region-migration', - 'user-guide/operations/data-management/region-failover', - 'user-guide/operations/data-management/compaction', + 'user-guide/administration/data-management/overview', + 'user-guide/administration/data-management/basic-table-operations', + 'user-guide/administration/data-management/table-sharding', + 'user-guide/administration/data-management/region-migration', + 'user-guide/administration/data-management/region-failover', + 'user-guide/administration/data-management/compaction', ], }, { type: 'category', label: 'Disaster Recovery', items: [ - 'user-guide/operations/disaster-recovery/overview', - 'user-guide/operations/disaster-recovery/back-up-&-restore-data', - 'user-guide/operations/disaster-recovery/dr-solution-based-on-active-active-failover', - 'user-guide/operations/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster', + 'user-guide/administration/disaster-recovery/overview', + 'user-guide/administration/disaster-recovery/back-up-&-restore-data', + 'user-guide/administration/disaster-recovery/dr-solution-based-on-active-active-failover', + 'user-guide/administration/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster', ], }, { type: 'category', label: 'Remote WAL', - items: ['user-guide/operations/remote-wal/quick-start', 'user-guide/operations/remote-wal/cluster-deployment'], + items: ['user-guide/administration/remote-wal/quick-start', 'user-guide/administration/remote-wal/cluster-deployment'], }, { type: 'category', label: 'Monitoring', items: [ - 'user-guide/operations/monitoring/overview', - 'user-guide/operations/monitoring/export-metrics', - 'user-guide/operations/monitoring/tracing', + 'user-guide/administration/monitoring/overview', + 'user-guide/administration/monitoring/export-metrics', + 'user-guide/administration/monitoring/tracing', ], }, - 'user-guide/operations/performance-tuning-tips', - 'user-guide/operations/upgrade', + 'user-guide/administration/performance-tuning-tips', + 'user-guide/administration/upgrade', ], }, ], From 79d8c273df42f07e66539e59cfb62d10fd7756f1 Mon Sep 17 00:00:00 2001 From: Yiran Date: Sun, 29 Sep 2024 15:01:58 +0800 Subject: [PATCH 2/4] move admin.md to overview --- docs/user-guide/administration/admin.md | 39 ---------------- docs/user-guide/administration/overview.md | 46 ++++++++++++++++--- .../user-guide/administration/admin.md | 39 ---------------- .../user-guide/administration/overview.md | 46 ++++++++++++++++--- sidebars.ts | 1 - 5 files changed, 78 insertions(+), 93 deletions(-) delete mode 100644 docs/user-guide/administration/admin.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/admin.md diff --git a/docs/user-guide/administration/admin.md b/docs/user-guide/administration/admin.md deleted file mode 100644 index f1306d9c6..000000000 --- a/docs/user-guide/administration/admin.md +++ /dev/null @@ -1,39 +0,0 @@ -# Administration - -This document addresses strategies and practices used in the operation of GreptimeDB systems and deployments. - -## Database/Cluster management - -* [Installation](/getting-started/installation/overview.md) for GreptimeDB and the [g-t-control](/reference/gtctl.md) command line tool. -* Database Configuration, please read the [Configuration](/user-guide/deployments/configuration.md) reference. -* [Monitoring metrics](/user-guide/administration/monitoring/export-metrics.md) and [Tracing](/user-guide/administration/monitoring/tracing.md) for GreptimeDB. -* GreptimeDB [Disaster Recovery](/user-guide/administration/disaster-recovery/overview.md). -* Cluster Failover for GreptimeDB by [Setting Remote WAL](./remote-wal/quick-start.md). - -### Runtime information - -* Find the topology information of the cluster though [CLUSTER_INFO](/reference/sql/information-schema/cluster-info.md) table. -* Find the table regions distribution though [PARTITIONS](/reference/sql/information-schema/partitions.md) and [REGION_PEERS](/reference/sql/information-schema/region-peers.md) tables. - -For example, find all the region id of a table: - -```sql -SELECT greptime_partition_id FROM PARTITIONS WHERE table_name = 'monitor' -``` - -Find the distribution of all regions in a table: - -```sql -SELECT b.peer_id as datanode_id, - a.greptime_partition_id as region_id -FROM information_schema.partitions a LEFT JOIN information_schema.region_peers b -ON a.greptime_partition_id = b.region_id -WHERE a.table_name='monitor' -ORDER BY datanode_id ASC -``` - -The `INFORMATION_SCHEMA` database provides access to system metadata, such as the name of a database or table, the data type of a column, etc. Please read the [reference](/reference/sql/information-schema/overview.md). - -## Best Practices - -* [Performance Tuning Tips](/user-guide/administration/performance-tuning-tips.md) \ No newline at end of file diff --git a/docs/user-guide/administration/overview.md b/docs/user-guide/administration/overview.md index 631f783a5..0c64ce502 100644 --- a/docs/user-guide/administration/overview.md +++ b/docs/user-guide/administration/overview.md @@ -1,9 +1,41 @@ # Overview -* [Administration](./admin.md) -* [Capacity Plan](./capacity-plan.md) -* [Data Management](./data-management/overview.md) -* [Disaster Recovery](./disaster-recovery/overview.md) -* [Monitoring](./monitoring/overview.md) -* [Remote WAL](./remote-wal/quick-start.md) -* [Upgrade](./upgrade.md) +This document addresses strategies and practices used in the administration of GreptimeDB. + +* [Installation](/getting-started/installation/overview.md) for GreptimeDB and the [g-t-control](/reference/gtctl.md) command line tool. +* [Capacity Plan](/user-guide/administration/capacity-plan.md) for GreptimeDB based on your workload. +* [Manage Data](/user-guide/administration/manage-data.md) for avoiding data loss, lower cost and better performance. +* Database Configuration, please read the [Configuration](/user-guide/deployments/configuration.md) reference. +* GreptimeDB [Disaster Recovery](/user-guide/administration/disaster-recovery/overview.md). +* Cluster Failover for GreptimeDB by [Setting Remote WAL](./remote-wal/quick-start.md). +* [Monitoring metrics](/user-guide/administration/monitoring/export-metrics.md) and [Tracing](/user-guide/administration/monitoring/tracing.md) for GreptimeDB. +* [Upgrade](/user-guide/administration/upgrade.md) GreptimeDB to a new version. + + +### Runtime information + +* Find the topology information of the cluster though [CLUSTER_INFO](/reference/sql/information-schema/cluster-info.md) table. +* Find the table regions distribution though [PARTITIONS](/reference/sql/information-schema/partitions.md) and [REGION_PEERS](/reference/sql/information-schema/region-peers.md) tables. + +For example, find all the region id of a table: + +```sql +SELECT greptime_partition_id FROM PARTITIONS WHERE table_name = 'monitor' +``` + +Find the distribution of all regions in a table: + +```sql +SELECT b.peer_id as datanode_id, + a.greptime_partition_id as region_id +FROM information_schema.partitions a LEFT JOIN information_schema.region_peers b +ON a.greptime_partition_id = b.region_id +WHERE a.table_name='monitor' +ORDER BY datanode_id ASC +``` + +The `INFORMATION_SCHEMA` database provides access to system metadata, such as the name of a database or table, the data type of a column, etc. Please read the [reference](/reference/sql/information-schema/overview.md). + +## Best Practices + +* [Performance Tuning Tips](/user-guide/administration/performance-tuning-tips.md) \ No newline at end of file diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/admin.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/admin.md deleted file mode 100644 index e82752966..000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/admin.md +++ /dev/null @@ -1,39 +0,0 @@ -# 管理 - -本文件介绍了在 GreptimeDB 系统运维和部署中使用的策略和实践。 - -## 数据库/集群管理 - -* GreptimeDB 的 [安装](/getting-started/installation/overview.md) 和 [g-t-control](/reference/gtctl.md) 命令行工具。 -* 数据库配置，请阅读 [配置](/user-guide/deployments/configuration.md) 参考。 -* GreptimeDB 的 [指标监控](/user-guide/administration/monitoring/export-metrics.md) 和 [链路追踪](/user-guide/administration/monitoring/tracing.md)。 -* GreptimeDB 的 [灾难恢复方案](/user-guide/administration/disaster-recovery/overview.md)。 -* 通过[设置 Remote WAL](./remote-wal/quick-start.md) 实现 GreptimeDB 的集群容灾。 - -### 运行时信息 - -* 通过 [CLUSTER_INFO](/reference/sql/information-schema/cluster-info.md) 表查找集群的拓扑信息。 -* 通过 [PARTITIONS](/reference/sql/information-schema/partitions.md) 表和[REGION_PEERS](/reference/sql/information-schema/region-peers.md) 表查找表的 Region 分布。 - -例如查询一张表的所有 Region Id: - -```sql -SELECT greptime_partition_id FROM PARTITIONS WHERE table_name = 'monitor' -``` - -查询一张表的 region 分布在哪些 datanode 上： - -```sql -SELECT b.peer_id as datanode_id, - a.greptime_partition_id as region_id -FROM information_schema.partitions a LEFT JOIN information_schema.region_peers b -ON a.greptime_partition_id = b.region_id -WHERE a.table_name='monitor' -ORDER BY datanode_id ASC -``` - -`INFORMATION_SCHEMA` 数据库提供了对系统元数据的访问，如数据库或表的名称、列的数据类型等。请阅读 [参考文档](/reference/sql/information-schema/overview.md)。 - -## 最佳实践 - -* [性能调优技巧](/user-guide/administration/performance-tuning-tips.md) \ No newline at end of file diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md index f8baa3be8..3d5b0e68a 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md @@ -1,9 +1,41 @@ # 概述 -* [管理](./admin.md) -* [容量规划](./capacity-plan.md) -* [数据管理](./data-management/overview.md) -* [灾难恢复](./disaster-recovery/overview.md) -* [监控](./monitoring/overview.md) -* [Remote WAL](./remote-wal/quick-start.md) -* [Upgrade](upgrade.md) +本文档介绍了在 GreptimeDB 管理中使用的策略和实践。 + +* [安装](/getting-started/installation/overview.md) GreptimeDB 和 [g-t-control](/reference/gtctl.md) 命令行工具。 +* 根据工作负载进行 GreptimeDB 的[容量规划](/user-guide/administration/capacity-plan.md)。 +* [管理数据](/user-guide/administration/manage-data.md) 以避免数据丢失、降低成本和提高性能。 +* 数据库配置，请阅读[配置](/user-guide/deployments/configuration.md)参考文档。 +* GreptimeDB 的[灾难恢复方案](/user-guide/administration/disaster-recovery/overview.md)。 +* 通过[设置 Remote WAL](./remote-wal/quick-start.md) 实现 GreptimeDB 的集群容灾。 +* GreptimeDB 的[监控指标](/user-guide/administration/monitoring/export-metrics.md)和[链路追踪](/user-guide/administration/monitoring/tracing.md)。 +* [升级](/user-guide/administration/upgrade.md) GreptimeDB 到新版本。 + + +### 运行时信息 + +* 通过 [CLUSTER_INFO](/reference/sql/information-schema/cluster-info.md) 表查找集群的拓扑信息。 +* 通过 [PARTITIONS](/reference/sql/information-schema/partitions.md) 表和[REGION_PEERS](/reference/sql/information-schema/region-peers.md) 表查找表的 Region 分布。 + +例如查询一张表的所有 Region Id: + +```sql +SELECT greptime_partition_id FROM PARTITIONS WHERE table_name = 'monitor' +``` + +查询一张表的 region 分布在哪些 datanode 上： + +```sql +SELECT b.peer_id as datanode_id, + a.greptime_partition_id as region_id +FROM information_schema.partitions a LEFT JOIN information_schema.region_peers b +ON a.greptime_partition_id = b.region_id +WHERE a.table_name='monitor' +ORDER BY datanode_id ASC +``` + +`INFORMATION_SCHEMA` 数据库提供了对系统元数据的访问，如数据库或表的名称、列的数据类型等。请阅读 [参考文档](/reference/sql/information-schema/overview.md)。 + +## 最佳实践 + +* [性能调优技巧](/user-guide/administration/performance-tuning-tips.md) \ No newline at end of file diff --git a/sidebars.ts b/sidebars.ts index 5260dd8d5..5a1a4a00e 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -177,7 +177,6 @@ const sidebars: SidebarsConfig = { label: 'Administration', items: [ 'user-guide/administration/overview', - 'user-guide/administration/admin', 'user-guide/administration/capacity-plan', { type: 'category', From c27a737792d8a627085332cd875f4e1c742658f4 Mon Sep 17 00:00:00 2001 From: Yiran Date: Sun, 29 Sep 2024 15:25:19 +0800 Subject: [PATCH 3/4] add runtime info doc --- docs/user-guide/administration/overview.md | 31 ++----------------- .../user-guide/administration/runtime-info.md | 26 ++++++++++++++++ .../user-guide/administration/overview.md | 29 +---------------- .../user-guide/administration/runtime-info.md | 25 +++++++++++++++ sidebars.ts | 1 + 5 files changed, 55 insertions(+), 57 deletions(-) create mode 100644 docs/user-guide/administration/runtime-info.md create mode 100644 i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/runtime-info.md diff --git a/docs/user-guide/administration/overview.md b/docs/user-guide/administration/overview.md index 0c64ce502..29f930c7c 100644 --- a/docs/user-guide/administration/overview.md +++ b/docs/user-guide/administration/overview.md @@ -10,32 +10,5 @@ This document addresses strategies and practices used in the administration of G * Cluster Failover for GreptimeDB by [Setting Remote WAL](./remote-wal/quick-start.md). * [Monitoring metrics](/user-guide/administration/monitoring/export-metrics.md) and [Tracing](/user-guide/administration/monitoring/tracing.md) for GreptimeDB. * [Upgrade](/user-guide/administration/upgrade.md) GreptimeDB to a new version. - - -### Runtime information - -* Find the topology information of the cluster though [CLUSTER_INFO](/reference/sql/information-schema/cluster-info.md) table. -* Find the table regions distribution though [PARTITIONS](/reference/sql/information-schema/partitions.md) and [REGION_PEERS](/reference/sql/information-schema/region-peers.md) tables. - -For example, find all the region id of a table: - -```sql -SELECT greptime_partition_id FROM PARTITIONS WHERE table_name = 'monitor' -``` - -Find the distribution of all regions in a table: - -```sql -SELECT b.peer_id as datanode_id, - a.greptime_partition_id as region_id -FROM information_schema.partitions a LEFT JOIN information_schema.region_peers b -ON a.greptime_partition_id = b.region_id -WHERE a.table_name='monitor' -ORDER BY datanode_id ASC -``` - -The `INFORMATION_SCHEMA` database provides access to system metadata, such as the name of a database or table, the data type of a column, etc. Please read the [reference](/reference/sql/information-schema/overview.md). - -## Best Practices - -* [Performance Tuning Tips](/user-guide/administration/performance-tuning-tips.md) \ No newline at end of file +* Get the [Runtime Information](/user-guide/administration/runtime-info.md) of the cluster. +* [Performance Tuning Tips](/user-guide/administration/performance-tuning-tips.md). diff --git a/docs/user-guide/administration/runtime-info.md b/docs/user-guide/administration/runtime-info.md new file mode 100644 index 000000000..27049eab3 --- /dev/null +++ b/docs/user-guide/administration/runtime-info.md @@ -0,0 +1,26 @@ +# Runtime Information + +The `INFORMATION_SCHEMA` database provides access to system metadata, such as the name of a database or table, the data type of a column, etc. + +* Find the topology information of the cluster though [CLUSTER_INFO](/reference/sql/information-schema/cluster-info.md) table. +* Find the table regions distribution though [PARTITIONS](/reference/sql/information-schema/partitions.md) and [REGION_PEERS](/reference/sql/information-schema/region-peers.md) tables. + +For example, find all the region id of a table: + +```sql +SELECT greptime_partition_id FROM PARTITIONS WHERE table_name = 'monitor' +``` + +Find the distribution of all regions in a table: + +```sql +SELECT b.peer_id as datanode_id, + a.greptime_partition_id as region_id +FROM information_schema.partitions a LEFT JOIN information_schema.region_peers b +ON a.greptime_partition_id = b.region_id +WHERE a.table_name='monitor' +ORDER BY datanode_id ASC +``` + +For more information about the `INFORMATION_SCHEMA` database, +Please read the [reference](/reference/sql/information-schema/overview.md). diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md index 3d5b0e68a..257df0ce1 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md @@ -10,32 +10,5 @@ * 通过[设置 Remote WAL](./remote-wal/quick-start.md) 实现 GreptimeDB 的集群容灾。 * GreptimeDB 的[监控指标](/user-guide/administration/monitoring/export-metrics.md)和[链路追踪](/user-guide/administration/monitoring/tracing.md)。 * [升级](/user-guide/administration/upgrade.md) GreptimeDB 到新版本。 - - -### 运行时信息 - -* 通过 [CLUSTER_INFO](/reference/sql/information-schema/cluster-info.md) 表查找集群的拓扑信息。 -* 通过 [PARTITIONS](/reference/sql/information-schema/partitions.md) 表和[REGION_PEERS](/reference/sql/information-schema/region-peers.md) 表查找表的 Region 分布。 - -例如查询一张表的所有 Region Id: - -```sql -SELECT greptime_partition_id FROM PARTITIONS WHERE table_name = 'monitor' -``` - -查询一张表的 region 分布在哪些 datanode 上： - -```sql -SELECT b.peer_id as datanode_id, - a.greptime_partition_id as region_id -FROM information_schema.partitions a LEFT JOIN information_schema.region_peers b -ON a.greptime_partition_id = b.region_id -WHERE a.table_name='monitor' -ORDER BY datanode_id ASC -``` - -`INFORMATION_SCHEMA` 数据库提供了对系统元数据的访问，如数据库或表的名称、列的数据类型等。请阅读 [参考文档](/reference/sql/information-schema/overview.md)。 - -## 最佳实践 - +* 获取集群的[运行时信息](/user-guide/administration/runtime-info.md)。 * [性能调优技巧](/user-guide/administration/performance-tuning-tips.md) \ No newline at end of file diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/runtime-info.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/runtime-info.md new file mode 100644 index 000000000..88a09f766 --- /dev/null +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/runtime-info.md @@ -0,0 +1,25 @@ +# 运行时信息 + +`INFORMATION_SCHEMA` 数据库提供了对系统元数据的访问，如数据库或表的名称、列的数据类型等。 + +* 通过 [CLUSTER_INFO](/reference/sql/information-schema/cluster-info.md) 表查找集群的拓扑信息。 +* 通过 [PARTITIONS](/reference/sql/information-schema/partitions.md) 表和[REGION_PEERS](/reference/sql/information-schema/region-peers.md) 表查找表的 Region 分布。 + +例如查询一张表的所有 Region Id: + +```sql +SELECT greptime_partition_id FROM PARTITIONS WHERE table_name = 'monitor' +``` + +查询一张表的 region 分布在哪些 datanode 上： + +```sql +SELECT b.peer_id as datanode_id, + a.greptime_partition_id as region_id +FROM information_schema.partitions a LEFT JOIN information_schema.region_peers b +ON a.greptime_partition_id = b.region_id +WHERE a.table_name='monitor' +ORDER BY datanode_id ASC +``` + +请阅读[参考文档](/reference/sql/information-schema/overview.md)获取更多关于 `INFORMATION_SCHEMA` 数据库的信息。 diff --git a/sidebars.ts b/sidebars.ts index 5a1a4a00e..eb130ccb9 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -214,6 +214,7 @@ const sidebars: SidebarsConfig = { 'user-guide/administration/monitoring/tracing', ], }, + 'user-guide/administration/runtime-info', 'user-guide/administration/performance-tuning-tips', 'user-guide/administration/upgrade', ], From 1d70d03bb20d7df91834d2cec886fe072c22a51d Mon Sep 17 00:00:00 2001 From: Yiran Date: Sun, 29 Sep 2024 15:35:26 +0800 Subject: [PATCH 4/4] rename `data management` to `manage data` --- .../frontend/table-sharding.md | 2 +- docs/faq-and-others/faq.md | 2 +- docs/reference/sql/admin.md | 4 ++-- .../basic-table-operations.md | 0 .../compaction.md | 0 .../overview.md | 2 +- .../region-failover.md | 2 +- .../region-migration.md | 0 .../table-sharding.md | 0 docs/user-guide/administration/overview.md | 20 +++++++++---------- docs/user-guide/concepts/data-model.md | 4 ++-- docs/user-guide/ingest-data/for-iot/sql.md | 2 +- docs/user-guide/manage-data/overview.md | 2 +- docs/user-guide/protocols/mysql.md | 2 +- docs/user-guide/protocols/postgresql.md | 2 +- docs/user-guide/query-data/sql.md | 4 ++-- .../current.json | 6 +----- .../frontend/table-sharding.md | 2 +- .../current/faq-and-others/faq.md | 2 +- .../current/reference/sql/admin.md | 4 ++-- .../basic-table-operations.md | 0 .../compaction.md | 0 .../overview.md | 2 +- .../region-failover.md | 2 +- .../region-migration.md | 0 .../table-sharding.md | 0 .../user-guide/administration/overview.md | 20 +++++++++---------- .../current/user-guide/concepts/data-model.md | 4 ++-- .../user-guide/ingest-data/for-iot/sql.md | 4 ++-- .../user-guide/manage-data/overview.md | 2 +- .../current/user-guide/protocols/mysql.md | 2 +- .../user-guide/protocols/postgresql.md | 2 +- .../current/user-guide/query-data/sql.md | 4 ++-- sidebars.ts | 14 ++++++------- 34 files changed, 57 insertions(+), 61 deletions(-) rename docs/user-guide/administration/{data-management => manage-data}/basic-table-operations.md (100%) rename docs/user-guide/administration/{data-management => manage-data}/compaction.md (100%) rename docs/user-guide/administration/{data-management => manage-data}/overview.md (86%) rename docs/user-guide/administration/{data-management => manage-data}/region-failover.md (98%) rename docs/user-guide/administration/{data-management => manage-data}/region-migration.md (100%) rename docs/user-guide/administration/{data-management => manage-data}/table-sharding.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/{data-management => manage-data}/basic-table-operations.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/{data-management => manage-data}/compaction.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/{data-management => manage-data}/overview.md (85%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/{data-management => manage-data}/region-failover.md (98%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/{data-management => manage-data}/region-migration.md (100%) rename i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/{data-management => manage-data}/table-sharding.md (100%) diff --git a/docs/contributor-guide/frontend/table-sharding.md b/docs/contributor-guide/frontend/table-sharding.md index 53d17a0cb..589510370 100644 --- a/docs/contributor-guide/frontend/table-sharding.md +++ b/docs/contributor-guide/frontend/table-sharding.md @@ -4,7 +4,7 @@ The sharding of stored data is essential to any distributed database. This docum ## Partition -For the syntax of creating a partitioned table, please refer to the [Table Sharding](/user-guide/administration/data-management/table-sharding.md) section in the User Guide. +For the syntax of creating a partitioned table, please refer to the [Table Sharding](/user-guide/administration/manage-data/table-sharding.md) section in the User Guide. ## Region diff --git a/docs/faq-and-others/faq.md b/docs/faq-and-others/faq.md index be2ed8f6d..6f259a81d 100644 --- a/docs/faq-and-others/faq.md +++ b/docs/faq-and-others/faq.md @@ -57,7 +57,7 @@ Please check out our initial version on [GitHub Repo](https://github.com/Greptim Yes, GreptimeDB is a schemaless database without need for creating tables in advance. The table and columns will be created automatically when writing data with protocol gRPC, InfluxDB, OpentsDB, Prometheus remote write. -For more information, refer to [this document](/user-guide/administration/data-management/basic-table-operations.md#create-table). +For more information, refer to [this document](/user-guide/administration/manage-data/basic-table-operations.md#create-table). ### How do you measure the passing rate of PromQL compatibility tests? Is there any testing framework？ diff --git a/docs/reference/sql/admin.md b/docs/reference/sql/admin.md index 36f800659..bf6a56e86 100644 --- a/docs/reference/sql/admin.md +++ b/docs/reference/sql/admin.md @@ -13,9 +13,9 @@ GreptimeDB provides some administration functions to manage the database and dat * `flush_table(table_name)` to flush a table's memtables into SST file by table name. * `flush_region(region_id)` to flush a region's memtables into SST file by region id. Find the region id through [PARTITIONS](./information-schema/partitions.md) table. -* `compact_table(table_name, [type], [options])` to schedule a compaction task for a table by table name, read [compaction](/user-guide/administration/data-management/compaction.md#strict-window-compaction-strategy-swcs-and-manual-compaction) for more details. +* `compact_table(table_name, [type], [options])` to schedule a compaction task for a table by table name, read [compaction](/user-guide/administration/manage-data/compaction.md#strict-window-compaction-strategy-swcs-and-manual-compaction) for more details. * `compact_region(region_id)` to schedule a compaction task for a region by region id. -* `migrate_region(region_id, from_peer, to_peer, [timeout])` to migrate regions between datanodes, please read the [Region Migration](/user-guide/administration/data-management/region-migration.md). +* `migrate_region(region_id, from_peer, to_peer, [timeout])` to migrate regions between datanodes, please read the [Region Migration](/user-guide/administration/manage-data/region-migration.md). * `procedure_state(procedure_id)` to query a procedure state by its id. * `flush_flow(flow_name)` to flush a flow's output into the sink table. diff --git a/docs/user-guide/administration/data-management/basic-table-operations.md b/docs/user-guide/administration/manage-data/basic-table-operations.md similarity index 100% rename from docs/user-guide/administration/data-management/basic-table-operations.md rename to docs/user-guide/administration/manage-data/basic-table-operations.md diff --git a/docs/user-guide/administration/data-management/compaction.md b/docs/user-guide/administration/manage-data/compaction.md similarity index 100% rename from docs/user-guide/administration/data-management/compaction.md rename to docs/user-guide/administration/manage-data/compaction.md diff --git a/docs/user-guide/administration/data-management/overview.md b/docs/user-guide/administration/manage-data/overview.md similarity index 86% rename from docs/user-guide/administration/data-management/overview.md rename to docs/user-guide/administration/manage-data/overview.md index f735bbede..2140f648a 100644 --- a/docs/user-guide/administration/data-management/overview.md +++ b/docs/user-guide/administration/manage-data/overview.md @@ -6,5 +6,5 @@ * [Expire Data by Setting TTL](/user-guide/manage-data/overview.md#manage-data-retention-with-ttl-policies) * [Table Sharding](table-sharding.md): Partition tables by regions * [Region Migration](region-migration.md): Migrate regions for load balancing -* [Region Failover](/user-guide/administration/data-management/region-failover.md) +* [Region Failover](/user-guide/administration/manage-data/region-failover.md) * [Compaction](compaction.md) diff --git a/docs/user-guide/administration/data-management/region-failover.md b/docs/user-guide/administration/manage-data/region-failover.md similarity index 98% rename from docs/user-guide/administration/data-management/region-failover.md rename to docs/user-guide/administration/manage-data/region-failover.md index 9bd2abe7a..f1672e399 100644 --- a/docs/user-guide/administration/data-management/region-failover.md +++ b/docs/user-guide/administration/manage-data/region-failover.md @@ -1,6 +1,6 @@ # Region Failover -Region Failover provides the ability to recover regions from region failures without losing data. This is implemented via [Region Migration](/user-guide/administration/data-management/region-migration.md). +Region Failover provides the ability to recover regions from region failures without losing data. This is implemented via [Region Migration](/user-guide/administration/manage-data/region-migration.md). ## Enable the Region Failover diff --git a/docs/user-guide/administration/data-management/region-migration.md b/docs/user-guide/administration/manage-data/region-migration.md similarity index 100% rename from docs/user-guide/administration/data-management/region-migration.md rename to docs/user-guide/administration/manage-data/region-migration.md diff --git a/docs/user-guide/administration/data-management/table-sharding.md b/docs/user-guide/administration/manage-data/table-sharding.md similarity index 100% rename from docs/user-guide/administration/data-management/table-sharding.md rename to docs/user-guide/administration/manage-data/table-sharding.md diff --git a/docs/user-guide/administration/overview.md b/docs/user-guide/administration/overview.md index 29f930c7c..c7dbccbcc 100644 --- a/docs/user-guide/administration/overview.md +++ b/docs/user-guide/administration/overview.md @@ -2,13 +2,13 @@ This document addresses strategies and practices used in the administration of GreptimeDB. -* [Installation](/getting-started/installation/overview.md) for GreptimeDB and the [g-t-control](/reference/gtctl.md) command line tool. -* [Capacity Plan](/user-guide/administration/capacity-plan.md) for GreptimeDB based on your workload. -* [Manage Data](/user-guide/administration/manage-data.md) for avoiding data loss, lower cost and better performance. -* Database Configuration, please read the [Configuration](/user-guide/deployments/configuration.md) reference. -* GreptimeDB [Disaster Recovery](/user-guide/administration/disaster-recovery/overview.md). -* Cluster Failover for GreptimeDB by [Setting Remote WAL](./remote-wal/quick-start.md). -* [Monitoring metrics](/user-guide/administration/monitoring/export-metrics.md) and [Tracing](/user-guide/administration/monitoring/tracing.md) for GreptimeDB. -* [Upgrade](/user-guide/administration/upgrade.md) GreptimeDB to a new version. -* Get the [Runtime Information](/user-guide/administration/runtime-info.md) of the cluster. -* [Performance Tuning Tips](/user-guide/administration/performance-tuning-tips.md). +* [Installation](/getting-started/installation/overview.md) for GreptimeDB and the [g-t-control](/reference/gtctl.md) command line tool +* [Capacity Plan](/user-guide/administration/capacity-plan.md) for GreptimeDB based on your workload +* [Manage Data](/user-guide/administration/manage-data/overview.md) for avoiding data loss, lower cost and better performance +* Database Configuration, please read the [Configuration](/user-guide/deployments/configuration.md) reference +* GreptimeDB [Disaster Recovery](/user-guide/administration/disaster-recovery/overview.md) +* Cluster Failover for GreptimeDB by [Setting Remote WAL](./remote-wal/quick-start.md) +* [Monitoring metrics](/user-guide/administration/monitoring/export-metrics.md) and [Tracing](/user-guide/administration/monitoring/tracing.md) for GreptimeDB +* [Performance Tuning Tips](/user-guide/administration/performance-tuning-tips.md) +* [Upgrade](/user-guide/administration/upgrade.md) GreptimeDB to a new version +* Get the [runtime information](/user-guide/administration/runtime-info.md) of the cluster diff --git a/docs/user-guide/concepts/data-model.md b/docs/user-guide/concepts/data-model.md index e47c14315..9f5c5863d 100644 --- a/docs/user-guide/concepts/data-model.md +++ b/docs/user-guide/concepts/data-model.md @@ -78,7 +78,7 @@ CREATE TABLE access_logs ( - `remote_addr`, `http_status`, `http_method`, `http_refer` and `user_agent` are tags. - `request` is a field that enables full-text index by the [`FULLTEXT` column option](/reference/sql/create.md#fulltext-column-option). -To learn how to indicate `Tag`, `Timestamp`, and `Field` columns, Please refer to [table management](/user-guide/administration/data-management/basic-table-operations.md#create-a-table) and [CREATE statement](/reference/sql/create.md). +To learn how to indicate `Tag`, `Timestamp`, and `Field` columns, Please refer to [table management](/user-guide/administration/manage-data/basic-table-operations.md#create-a-table) and [CREATE statement](/reference/sql/create.md). Of course, you can place metrics and logs in a single table at any time, which is also a key capability provided by GreptimeDB. @@ -95,4 +95,4 @@ GreptimeDB is designed on top of Table for the following reasons: The multi-value model is used to model data sources, where a metric can have multiple values represented by fields. The advantage of the multi-value model is that it can write or read multiple values to the database at once, reducing transfer traffic and simplifying queries. In contrast, the single-value model requires splitting the data into multiple records. Read the [blog](https://greptime.com/blogs/2024-05-09-prometheus) for more detailed benefits of multi-value mode. -GreptimeDB uses SQL to manage table schema. Please refer to [table management](/user-guide/administration/data-management/basic-table-operations.md) for more information. However, our definition of schema is not mandatory and leans towards a **schemaless** approach, similar to MongoDB. For more details, see [Automatic Schema Generation](/user-guide/ingest-data/overview.md#automatic-schema-generation). +GreptimeDB uses SQL to manage table schema. Please refer to [table management](/user-guide/administration/manage-data/basic-table-operations.md) for more information. However, our definition of schema is not mandatory and leans towards a **schemaless** approach, similar to MongoDB. For more details, see [Automatic Schema Generation](/user-guide/ingest-data/overview.md#automatic-schema-generation). diff --git a/docs/user-guide/ingest-data/for-iot/sql.md b/docs/user-guide/ingest-data/for-iot/sql.md index 8cd5f7106..be585619b 100644 --- a/docs/user-guide/ingest-data/for-iot/sql.md +++ b/docs/user-guide/ingest-data/for-iot/sql.md @@ -32,7 +32,7 @@ The above statement will create a table with the following schema: ``` For more information about the `CREATE TABLE` statement, -please refer to [table management](/user-guide/administration/data-management/basic-table-operations.md#create-a-table). +please refer to [table management](/user-guide/administration/manage-data/basic-table-operations.md#create-a-table). ## Insert data diff --git a/docs/user-guide/manage-data/overview.md b/docs/user-guide/manage-data/overview.md index d2adf251d..5bf2469d6 100644 --- a/docs/user-guide/manage-data/overview.md +++ b/docs/user-guide/manage-data/overview.md @@ -317,5 +317,5 @@ For more information about TTL policies, please refer to the [CREATE](/reference ## More data management operations -For more advanced data management operations, such as basic table operations, table sharding and region migration, please refer to the [Data Management](/user-guide/administration/data-management/overview.md) in the administration section. +For more advanced data management operations, such as basic table operations, table sharding and region migration, please refer to the [Data Management](/user-guide/administration/manage-data/overview.md) in the administration section. diff --git a/docs/user-guide/protocols/mysql.md b/docs/user-guide/protocols/mysql.md index 3f076a6e9..8ae9fc85c 100644 --- a/docs/user-guide/protocols/mysql.md +++ b/docs/user-guide/protocols/mysql.md @@ -14,7 +14,7 @@ mysql -h -P 4002 -u -p ## Table management -Please refer to [Table Management](/user-guide/administration/data-management/basic-table-operations.md). +Please refer to [Table Management](/user-guide/administration/manage-data/basic-table-operations.md). ## Ingest data diff --git a/docs/user-guide/protocols/postgresql.md b/docs/user-guide/protocols/postgresql.md index 1b431a4a5..e21572447 100644 --- a/docs/user-guide/protocols/postgresql.md +++ b/docs/user-guide/protocols/postgresql.md @@ -15,7 +15,7 @@ psql -h -p 4003 -U -d public ## Table management -Please refer to [Table Management](/user-guide/administration/data-management/basic-table-operations.md). +Please refer to [Table Management](/user-guide/administration/manage-data/basic-table-operations.md). ## Ingest data diff --git a/docs/user-guide/query-data/sql.md b/docs/user-guide/query-data/sql.md index 6fabec7bf..9b03643d9 100644 --- a/docs/user-guide/query-data/sql.md +++ b/docs/user-guide/query-data/sql.md @@ -4,7 +4,7 @@ GreptimeDB supports full SQL for querying data from a database. In this document, we will use the `monitor` table to demonstrate how to query data. For instructions on creating the `monitor` table and inserting data into it, -Please refer to [table management](/user-guide/administration/data-management/basic-table-operations.md#create-a-table) and [Ingest Data](/user-guide/ingest-data/for-iot/sql.md). +Please refer to [table management](/user-guide/administration/manage-data/basic-table-operations.md#create-a-table) and [Ingest Data](/user-guide/ingest-data/for-iot/sql.md). ## Basic query @@ -265,7 +265,7 @@ SELECT DISTINCT ON (host) * FROM monitor ORDER BY host, ts DESC; GreptimeDB supports [Range Query](/reference/sql/range.md) to aggregate data by time window. -Suppose we have the following data in the [`monitor` table](/user-guide/administration/data-management/basic-table-operations.md#create-a-table): +Suppose we have the following data in the [`monitor` table](/user-guide/administration/manage-data/basic-table-operations.md#create-a-table): ```sql +-----------+---------------------+------+--------+ diff --git a/i18n/zh/docusaurus-plugin-content-docs/current.json b/i18n/zh/docusaurus-plugin-content-docs/current.json index 8fb0d7aa1..d542ebb65 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current.json +++ b/i18n/zh/docusaurus-plugin-content-docs/current.json @@ -44,7 +44,7 @@ "description": "The label for category Client Libraries in sidebar docs" }, "sidebar.docs.category.Administration": { - "message": "管理数据库", + "message": "管理", "description": "The label for category Operations in sidebar docs" }, "sidebar.docs.category.Deployments": { @@ -171,10 +171,6 @@ "message": "管理数据", "description": "The label for category Manage Data in sidebar docs" }, - "sidebar.docs.category.Data Management": { - "message": "管理数据", - "description": "The label for category Data Management in sidebar docs" - }, "sidebar.docs.category.Protocols": { "message": "协议", "description": "The label for category Manage Data in sidebar docs" diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/contributor-guide/frontend/table-sharding.md b/i18n/zh/docusaurus-plugin-content-docs/current/contributor-guide/frontend/table-sharding.md index 1128df2a4..4347b6333 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/contributor-guide/frontend/table-sharding.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/contributor-guide/frontend/table-sharding.md @@ -4,7 +4,7 @@ ## 分区 -有关创建分区表的语法，请参阅用户指南中的[表分片](/user-guide/administration/data-management/table-sharding.md)部分。 +有关创建分区表的语法，请参阅用户指南中的[表分片](/user-guide/administration/manage-data/table-sharding.md)部分。 ## Region diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/faq-and-others/faq.md b/i18n/zh/docusaurus-plugin-content-docs/current/faq-and-others/faq.md index 05bfa98e6..b91ccff3b 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/faq-and-others/faq.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/faq-and-others/faq.md @@ -58,7 +58,7 @@ Please check out our initial version on [GitHub Repo](https://github.com/Greptim Yes, GreptimeDB is a schemaless database without need for creating tables in advance. The table and columns will be created automatically when writing data with protocol gRPC, InfluxDB, OpentsDB, Prometheus remote write. -For more information, refer to [this document](/user-guide/administration/data-management/basic-table-operations.md#create-table). +For more information, refer to [this document](/user-guide/administration/manage-data/basic-table-operations.md#create-table). ### How do you measure the passing rate of PromQL compatibility tests? Is there any testing framework？ diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/reference/sql/admin.md b/i18n/zh/docusaurus-plugin-content-docs/current/reference/sql/admin.md index 2c71154d7..415f395b1 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/reference/sql/admin.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/reference/sql/admin.md @@ -12,9 +12,9 @@ GreptimeDB 提供了一些管理函数来管理数据库和数据： * `flush_table(table_name)` 根据表名将表的 Memtable 刷新到 SST 文件中。 * `flush_region(region_id)` 根据 Region ID 将 Region 的 Memtable 刷新到 SST 文件中。通过 [PARTITIONS](./information-schema/partitions.md) 表查找 Region ID。 -* `compact_table(table_name, [type], [options])` 为表启动一个 compaction 任务，详细信息请阅读 [compaction](/user-guide/administration/data-management/compaction.md#严格窗口压缩策略swcs和手动压缩)。 +* `compact_table(table_name, [type], [options])` 为表启动一个 compaction 任务，详细信息请阅读 [compaction](/user-guide/administration/manage-data/compaction.md#严格窗口压缩策略swcs和手动压缩)。 * `compact_region(region_id)` 为 Region 启动一个 compaction 任务。 -* `migrate_region(region_id, from_peer, to_peer, [timeout])` 在 Datanode 之间迁移 Region，请阅读 [Region Migration](/user-guide/administration/data-management/region-migration.md)。 +* `migrate_region(region_id, from_peer, to_peer, [timeout])` 在 Datanode 之间迁移 Region，请阅读 [Region Migration](/user-guide/administration/manage-data/region-migration.md)。 * `procedure_state(procedure_id)` 根据 ID 查询 Procedure 状态。 * `flush_flow(flow_name)` 将 Flow 的输出刷新到目标接收表。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/basic-table-operations.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/basic-table-operations.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/basic-table-operations.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/basic-table-operations.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/compaction.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/compaction.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/compaction.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/compaction.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/overview.md similarity index 85% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/overview.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/overview.md index 5a3316971..0ea87d814 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/overview.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/overview.md @@ -6,5 +6,5 @@ * [通过设置 TTL 过期数据](/user-guide/manage-data/overview.md#使用-ttl-策略保留数据) * [表分片](table-sharding.md): 按 Region 对表进行分区 * [Region Migration](region-migration.md): 为负载均衡迁移 Region -* [Region Failover](/user-guide/administration/data-management/region-failover.md) +* [Region Failover](/user-guide/administration/manage-data/region-failover.md) * [Compaction](compaction.md) diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/region-failover.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/region-failover.md similarity index 98% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/region-failover.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/region-failover.md index 7484834a4..0c7d6066b 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/region-failover.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/region-failover.md @@ -1,6 +1,6 @@ # Region Failover -Region Failover 提供了在不丢失数据的情况下从 Region 故障中恢复的能力。这是通过 [Region 迁移](/user-guide/administration/data-management/region-migration.md) 实现的。 +Region Failover 提供了在不丢失数据的情况下从 Region 故障中恢复的能力。这是通过 [Region 迁移](/user-guide/administration/manage-data/region-migration.md) 实现的。 ## 开启 Region Failover diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/region-migration.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/region-migration.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/region-migration.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/region-migration.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/table-sharding.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/table-sharding.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/data-management/table-sharding.md rename to i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/manage-data/table-sharding.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md index 257df0ce1..68c36aa65 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/administration/overview.md @@ -2,13 +2,13 @@ 本文档介绍了在 GreptimeDB 管理中使用的策略和实践。 -* [安装](/getting-started/installation/overview.md) GreptimeDB 和 [g-t-control](/reference/gtctl.md) 命令行工具。 -* 根据工作负载进行 GreptimeDB 的[容量规划](/user-guide/administration/capacity-plan.md)。 -* [管理数据](/user-guide/administration/manage-data.md) 以避免数据丢失、降低成本和提高性能。 -* 数据库配置，请阅读[配置](/user-guide/deployments/configuration.md)参考文档。 -* GreptimeDB 的[灾难恢复方案](/user-guide/administration/disaster-recovery/overview.md)。 -* 通过[设置 Remote WAL](./remote-wal/quick-start.md) 实现 GreptimeDB 的集群容灾。 -* GreptimeDB 的[监控指标](/user-guide/administration/monitoring/export-metrics.md)和[链路追踪](/user-guide/administration/monitoring/tracing.md)。 -* [升级](/user-guide/administration/upgrade.md) GreptimeDB 到新版本。 -* 获取集群的[运行时信息](/user-guide/administration/runtime-info.md)。 -* [性能调优技巧](/user-guide/administration/performance-tuning-tips.md) \ No newline at end of file +* [安装](/getting-started/installation/overview.md) GreptimeDB 和 [g-t-control](/reference/gtctl.md) 命令行工具 +* 根据工作负载进行 GreptimeDB 的[容量规划](/user-guide/administration/capacity-plan.md) +* [管理数据](/user-guide/administration/manage-data/overview.md) 以避免数据丢失、降低成本和提高性能 +* 数据库配置，请阅读[配置](/user-guide/deployments/configuration.md)参考文档 +* GreptimeDB 的[灾难恢复方案](/user-guide/administration/disaster-recovery/overview.md) +* 通过[设置 Remote WAL](./remote-wal/quick-start.md) 实现 GreptimeDB 的集群容灾 +* GreptimeDB 的[监控指标](/user-guide/administration/monitoring/export-metrics.md)和[链路追踪](/user-guide/administration/monitoring/tracing.md) +* [性能调优技巧](/user-guide/administration/performance-tuning-tips.md) +* [升级](/user-guide/administration/upgrade.md) GreptimeDB 到新版本 +* 获取集群的[运行时信息](/user-guide/administration/runtime-info.md) diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/data-model.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/data-model.md index 23e9eafa7..06f6d47ab 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/data-model.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/concepts/data-model.md @@ -63,7 +63,7 @@ CREATE TABLE access_logs ( - `remote_addr`、`http_status`、`http_method`、`http_refer`、`user_agent` 为 Tag。 - `request` 是通过 [`FULLTEXT` 列选项](/reference/sql/create.md#fulltext-列选项)启用全文索引的字段。 -要了解如何指定 `Tag`、`Timestamp` 和 `Field` 列，请参见[表管理](/user-guide/administration/data-management/basic-table-operations.md#创建表)和 [CREATE 语句](/reference/sql/create.md)。 +要了解如何指定 `Tag`、`Timestamp` 和 `Field` 列，请参见[表管理](/user-guide/administration/manage-data/basic-table-operations.md#创建表)和 [CREATE 语句](/reference/sql/create.md)。 当然，无论何时，你都可以将指标和日志放在一张表里，这也是 GreptimeDB 提供的关键能力。 @@ -77,4 +77,4 @@ GreptimeDB 基于表进行设计，原因如下： - 当我们有了表格 Schema 后，自然而然地引入了 SQL，并用它来处理各种表之间的关联分析和聚合查询，为用户抵消了学习和使用成本。 - 比起 OpenTSDB 和 Prometheus 采用的单值模型，GreptimeDB 使用多值模型使其中一行数据可以具有多列数据。多值模型面向数据源建模，一个 metric 可以有用 field 表示的值。多值模型的优势在于它可以一次性向数据库写入或读取多个值，从而减少传输流量并简化查询。相比之下，单值模型则需要将数据拆分成多个记录。阅读[博客](https://greptime.com/blogs/2024-05-09-prometheus)以获取更多详情。 -GreptimeDB 使用 SQL 管理表 Schema。有关更多信息，请参见[表管理](/user-guide/administration/data-management/basic-table-operations.md)。但是，我们对 Schema 的定义并不是强制性的，而是倾向于 **Schemaless** 的方式，类似于 MongoDB。有关更多详细信息，请参见[自动生成表结构](../ingest-data/overview.md#自动生成表结构)。 +GreptimeDB 使用 SQL 管理表 Schema。有关更多信息，请参见[表管理](/user-guide/administration/manage-data/basic-table-operations.md)。但是，我们对 Schema 的定义并不是强制性的，而是倾向于 **Schemaless** 的方式，类似于 MongoDB。有关更多详细信息，请参见[自动生成表结构](../ingest-data/overview.md#自动生成表结构)。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/ingest-data/for-iot/sql.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/ingest-data/for-iot/sql.md index bc3f5eee7..5f1f0d0bb 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/ingest-data/for-iot/sql.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/ingest-data/for-iot/sql.md @@ -3,7 +3,7 @@ 你可以使用 [MySQL](/user-guide/protocols/mysql.md) 或 [PostgreSQL](/user-guide/protocols/postgresql.md) 客户端执行 SQL 语句， 使用任何你喜欢的编程语言（如Java JDBC）通过 MySQL 或 PostgreSQL 协议访问 GreptimeDB。 -我们将使用 `monitor` 表作为示例来展示如何写入数据。有关如何创建 `monitor` 表的 SQL 示例，请参见[表管理](/user-guide/administration/data-management/basic-table-operations.md#创建表)。 +我们将使用 `monitor` 表作为示例来展示如何写入数据。有关如何创建 `monitor` 表的 SQL 示例，请参见[表管理](/user-guide/administration/manage-data/basic-table-operations.md#创建表)。 ## 创建表 @@ -32,7 +32,7 @@ CREATE TABLE monitor ( 4 rows in set (0.01 sec) ``` -有关 `CREATE TABLE` 语句的更多信息，请参阅[表管理](/user-guide/administration/data-management/basic-table-operations.md#create-a-table)。 +有关 `CREATE TABLE` 语句的更多信息，请参阅[表管理](/user-guide/administration/manage-data/basic-table-operations.md#create-a-table)。 ## 插入数据 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/manage-data/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/manage-data/overview.md index 99198e5bc..e74b147f5 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/manage-data/overview.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/manage-data/overview.md @@ -314,4 +314,4 @@ CREATE DATABASE test WITH ('ttl'='7d'); ## 更多数据管理操作 -有关更高级的数据管理操作，例如基本表操作、表分片和 Region 迁移，请参阅 Administration 部分的[数据管理](/user-guide/administration/data-management/overview.md)。 +有关更高级的数据管理操作，例如基本表操作、表分片和 Region 迁移，请参阅 Administration 部分的[数据管理](/user-guide/administration/manage-data/overview.md)。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/mysql.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/mysql.md index d0d3e3b6e..37297929c 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/mysql.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/mysql.md @@ -14,7 +14,7 @@ mysql -h -P 4002 -u -p ## 管理表 -请参考[表管理](/user-guide/administration/data-management/basic-table-operations.md)。 +请参考[表管理](/user-guide/administration/manage-data/basic-table-operations.md)。 ## 写入数据 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/postgresql.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/postgresql.md index 845d624e5..521977508 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/postgresql.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/protocols/postgresql.md @@ -14,7 +14,7 @@ psql -h -p 4003 -U -d public ## 管理表 -请参考[管理表](/user-guide/administration/data-management/basic-table-operations.md)。 +请参考[管理表](/user-guide/administration/manage-data/basic-table-operations.md)。 ## 写入数据 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/query-data/sql.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/query-data/sql.md index f5c7acd58..8bf26527f 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/query-data/sql.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/query-data/sql.md @@ -2,7 +2,7 @@ GreptimeDB 在查询数据时支持完整的 `SQL` 语法。 -在这篇文档中，我们将使用 `monitor` 表中的数据作为示例来演示如何查询数据。关于如何创建 `monitor` 表格并向其中插入数据，请参考[表管理](/user-guide/administration/data-management/basic-table-operations.md#创建表)和[写入数据](/user-guide/ingest-data/for-iot/sql.md)。 +在这篇文档中，我们将使用 `monitor` 表中的数据作为示例来演示如何查询数据。关于如何创建 `monitor` 表格并向其中插入数据，请参考[表管理](/user-guide/administration/manage-data/basic-table-operations.md#创建表)和[写入数据](/user-guide/ingest-data/for-iot/sql.md)。 ## 基础查询 @@ -253,7 +253,7 @@ SELECT DISTINCT ON (host) * FROM monitor ORDER BY host, ts DESC; GreptimeDB 支持 [Range Query](/reference/sql/range.md) 来按时间窗口聚合数据。 -假设我们有以下数据在 [`monitor` 表](/user-guide/administration/data-management/basic-table-operations.md#创建表) 中： +假设我们有以下数据在 [`monitor` 表](/user-guide/administration/manage-data/basic-table-operations.md#创建表) 中： ```sql +-----------+---------------------+------+--------+ diff --git a/sidebars.ts b/sidebars.ts index eb130ccb9..8250862ab 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -180,14 +180,14 @@ const sidebars: SidebarsConfig = { 'user-guide/administration/capacity-plan', { type: 'category', - label: 'Data Management', + label: 'Manage Data', items: [ - 'user-guide/administration/data-management/overview', - 'user-guide/administration/data-management/basic-table-operations', - 'user-guide/administration/data-management/table-sharding', - 'user-guide/administration/data-management/region-migration', - 'user-guide/administration/data-management/region-failover', - 'user-guide/administration/data-management/compaction', + 'user-guide/administration/manage-data/overview', + 'user-guide/administration/manage-data/basic-table-operations', + 'user-guide/administration/manage-data/table-sharding', + 'user-guide/administration/manage-data/region-migration', + 'user-guide/administration/manage-data/region-failover', + 'user-guide/administration/manage-data/compaction', ], }, {