diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index f7f1b675c..727d27369 100644 --- a/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -55,7 +55,7 @@ To ensure the AINode installation package you obtained is complete and correct, **Preparation:** -- Obtain the official SHA512 checksum: Please contact Timecho staff. +- Obtain the official SHA512 checksum: Please contact commercial support. **Verification Steps (using Linux as an example):** @@ -77,7 +77,7 @@ To ensure the AINode installation package you obtained is complete and correct, **Notes:** -- If the verification results do not match, please contact Timecho staff to obtain a new installation package. +- If the verification results do not match, please contact commercial support to obtain a new installation package. - If you encounter a "file not found" prompt during verification, check if the file path is correct or if the installation package was downloaded completely. ### 2.3 Environment Requirements @@ -116,7 +116,7 @@ AINode supports modifying some necessary parameters. You can find the following ### 3.3 Importing Built-in Weight Files *If the deployment environment has network connectivity and can access HuggingFace, the system will automatically pull the built-in model weight files. This step can be skipped.* -*For offline environments, contact Timecho staff to obtain the model weight folder and place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.* +*For offline environments, contact commercial support to obtain the model weight folder and place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.* **NOTE:** Pay attention to the directory hierarchy. The parent directory for all built-in model weights should be `builtin`. ### 3.4 Starting AINode @@ -228,7 +228,7 @@ If you need to upgrade the version of the current AINode, you can refer to the f 3. Update built-in model weights (optional) - * If the new version involves updates to built-in models, relevant information will be updated in the [Release History](../IoTDB-Introduction/Release-history_apache.md). You may contact Timecho staff to obtain the latest weight package and replace it in the `data/ainode/models/builtin` directory. + * If the new version involves updates to built-in models, relevant information will be updated in the [Release History](../IoTDB-Introduction/Release-history_apache.md). You may contact commercial support to obtain the latest weight package and replace it in the `data/ainode/models/builtin` directory. 4. After the upgrade is completed, you can start the AINode service and check the node status. For specific commands, refer to Sections 3.4 and 3.5. diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md index 6299219da..785acb2d3 100644 --- a/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -69,7 +69,7 @@ To ensure the AINode installation package you obtained is complete and valid, we ``` 2. Execute the following command to calculate the hash value: ```Bash - sha512sum timechodb-{version}-ainode-bin.zip + sha512sum apache-iotdb-{version}-ainode-bin.zip ``` 3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name): @@ -129,7 +129,7 @@ AINode supports modifying some necessary parameters. You can find the following > Offline environment only (Online environments can skip this step) > -Contact Timecho team to obtain the model weight files, then place them in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory. +Contact commercial support to obtain the model weight files, then place them in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory. ### 3.4 Start AINode diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md index 8977215fc..998d4e6bf 100644 --- a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md +++ b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md @@ -72,11 +72,11 @@ 48core 1 2 - Please contact Timecho Business for consultation + Please contact commercial support for consultation Over 10000000 - Please contact Timecho Business for consultation + Please contact commercial support for consultation @@ -136,11 +136,11 @@ 128G 1 2 - Please contact Timecho Business for consultation + Please contact commercial support for consultation Over 10000000 - Please contact Timecho Business for consultation + Please contact commercial support for consultation diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Environment-Requirements.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Environment-Requirements.md index 85555c59d..833e7b9dc 100644 --- a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Environment-Requirements.md +++ b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Environment-Requirements.md @@ -80,7 +80,7 @@ IoTDB does not have strict operational requirements for disk array configuration ### 2.1 Version Requirements -IoTDB supports operating systems such as Linux, Windows, and MacOS. TimechoDB also supports Chinese CPUs like Loongson, Phytium, and Kunpeng, as well as Chinese operating systems like Kylin, UOS, and NingSi. +IoTDB supports operating systems such as Linux, Windows, and MacOS. IoTDB also supports Chinese CPUs like Loongson, Phytium, and Kunpeng, as well as Chinese operating systems like Kylin, UOS, and NingSi. ### 2.2 Hard Disk Partitioning diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md index e897012e0..0191a6a15 100644 --- a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md +++ b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md @@ -20,19 +20,19 @@ --> # Monitoring Panel Deployment -The monitoring panel is one of the supporting tools for TimechoDB. It aims to solve the monitoring problems of TimechoDB and its operating system, mainly including operating system resource monitoring, TimechoDB performance monitoring, and hundreds of kernel monitoring metrics, in order to help users monitor cluster health, optimize performance, and perform maintenance. This guide demonstrates how to enable the system monitoring module in a TimechoDB instance and visualize monitoring metrics using Prometheus + Grafana, using a typical 3C3D cluster (3 ConfigNodes and 3 DataNodes) as an example. +The monitoring panel is one of the supporting tools for IoTDB. It aims to solve the monitoring problems of IoTDB and its operating system, mainly including operating system resource monitoring, IoTDB performance monitoring, and hundreds of kernel monitoring metrics, in order to help users monitor cluster health, optimize performance, and perform maintenance. This guide demonstrates how to enable the system monitoring module in a IoTDB instance and visualize monitoring metrics using Prometheus + Grafana, using a typical 3C3D cluster (3 ConfigNodes and 3 DataNodes) as an example. ## 1. Installation Preparation -1. Installing TimechoDB: Install TimechoDB V1.0 or above. Contact sales or technical support to obtain the installation package. +1. Installing IoTDB: Install IoTDB V1.0 or above. Contact sales or technical support to obtain the installation package. -2. Obtain the monitoring panel installation package: The monitoring panel is exclusive to the enterprise-grade TimechoDB. Contact sales or technical support to obtain it. +2. Obtain the monitoring panel installation package: The monitoring panel is exclusive to the enterprise-grade IoTDB. Contact sales or technical support to obtain it. ## 2. Installation Steps -### 2.1 Enable Monitoring Metrics Collection in TimechoDB +### 2.1 Enable Monitoring Metrics Collection in IoTDB -1. Enable related configuration options. The configuration options related to monitoring in TimechoDB are disabled by default. Before deploying the monitoring panel, you need to enable certain configuration options (note that the service needs to be restarted after enabling monitoring configuration). +1. Enable related configuration options. The configuration options related to monitoring in IoTDB are disabled by default. Before deploying the monitoring panel, you need to enable certain configuration options (note that the service needs to be restarted after enabling monitoring configuration). | **Configuration** | **Configuration File** | **Description** | | :--------------------------------- | :------------------------------- | :----------------------------------------------------------- | diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md index 08d42beba..9228cbb3e 100644 --- a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md +++ b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md @@ -20,7 +20,7 @@ --> # Stand-Alone Deployment -This guide introduces how to set up a standalone TimechoDB instance, which includes one ConfigNode and one DataNode (commonly referred to as 1C1D). +This guide introduces how to set up a standalone IoTDB instance, which includes one ConfigNode and one DataNode (commonly referred to as 1C1D). ## 1. Prerequisites diff --git a/src/UserGuide/Master/Table/Ecosystem-Integration/DataGrip.md b/src/UserGuide/Master/Table/Ecosystem-Integration/DataGrip.md index 5e8b37104..ad816b304 100644 --- a/src/UserGuide/Master/Table/Ecosystem-Integration/DataGrip.md +++ b/src/UserGuide/Master/Table/Ecosystem-Integration/DataGrip.md @@ -43,9 +43,9 @@ Ensure DataGrip and IoTDB are installed: Select the appropriate version of the JAR package (choose the `jar-with-dependencies.jar` variant): -- Option 1: https://repo1.maven.org/maven2/com/timecho/iotdb/iotdb-jdbc/2.0.3.3/iotdb-jdbc-2.0.3.3-jar-with-dependencies.jar +- Option 1: https://repo1.maven.org/maven2/org/apache/iotdb/iotdb-jdbc/2.0.3/iotdb-jdbc-2.0.3-jar-with-dependencies.jar -- Option 2: https://repo1.maven.org/maven2/com/timecho/iotdb/iotdb-jdbc/2.0.3.3/ +- Option 2: https://repo1.maven.org/maven2/org/apache/iotdb/iotdb-jdbc/2.0.3/ ![](/img/datagrip-2.png) diff --git a/src/UserGuide/Master/Table/QuickStart/QuickStart_apache.md b/src/UserGuide/Master/Table/QuickStart/QuickStart_apache.md index 1fbf7213c..84ad616f5 100644 --- a/src/UserGuide/Master/Table/QuickStart/QuickStart_apache.md +++ b/src/UserGuide/Master/Table/QuickStart/QuickStart_apache.md @@ -31,7 +31,7 @@ This guide will assist you in quickly installing and deploying IoTDB. You can qu 2. Complete system configuration preparations: IoTDB's system configuration involves multiple aspects. For an introduction to key system configurations, please see [System Requirements](../Deployment-and-Maintenance/Environment-Requirements.md) -3. Obtain the installation package: You can obtain the IoTDB installation package on the [Apache IoTDB official website](https://iotdb.apache.org/zh/Download/).For the specific structure of the installation package, please refer to[Obtain TimechoDB](../Deployment-and-Maintenance/IoTDB-Package_apache.md) +3. Obtain the installation package: You can obtain the IoTDB installation package on the [Apache IoTDB official website](https://iotdb.apache.org/zh/Download/).For the specific structure of the installation package, please refer to[Obtain IoTDB](../Deployment-and-Maintenance/IoTDB-Package_apache.md) 4. Install the database and activate it: Depending on your actual deployment architecture, you can choose from the following tutorials for installation and deployment: diff --git a/src/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md b/src/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md index 00d5b5f17..6ca1d6a06 100644 --- a/src/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md +++ b/src/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md @@ -99,7 +99,7 @@ For more details, refer to the following documents: ## 4. Apache IoTDB Dashboard -The `Apache IoTDB Dashboard` is a companion product of TimechoDB, supporting unified centralized operation and maintenance management. It allows monitoring multiple clusters through a single monitoring panel. You can contact the business team to obtain the Dashboard's JSON file. +The `Apache IoTDB Dashboard` is a companion product of IoTDB, supporting unified centralized operation and maintenance management. It allows monitoring multiple clusters through a single monitoring panel. You can contact the business team to obtain the Dashboard's JSON file. ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png) diff --git a/src/UserGuide/Master/Table/User-Manual/Load-Balance.md b/src/UserGuide/Master/Table/User-Manual/Load-Balance.md index 8514dcf55..05ea8d075 100644 --- a/src/UserGuide/Master/Table/User-Manual/Load-Balance.md +++ b/src/UserGuide/Master/Table/User-Manual/Load-Balance.md @@ -137,18 +137,18 @@ echo "192.168.1.3 iotdb-1" >> /etc/hosts #### 1.3.2 Scaling Operation -1. To ensure the TimechoDB installation package you obtained is complete and correct, it is recommended to perform an SHA512 checksum before installation and deployment. +1. To ensure the IoTDB installation package you obtained is complete and correct, it is recommended to perform an SHA512 checksum before installation and deployment. 2. Unzip the installation package and enter the installation directory. ``` -unzip timechodb-{version}-bin.zip -cd timechodb-{version}-bin +unzip apache-iotdb-{version}-bin.zip +cd apache-iotdb-{version}-bin ``` 3. Modify the relevant configuration. ``` -cd timechodb-{version}-bin/conf +cd apache-iotdb-{version}-bin/conf vim iotdb-system.properties ``` @@ -175,10 +175,10 @@ Navigate to the `sbin`directory under IoTDB and start the datanode: ``` # Linux or macOS - ./timechodb-{version}-bin/sbin/start-cli.sh + ./apache-iotdb-{version}-bin/sbin/start-cli.sh # Windows - .\timechodb-{version}-bin\sbin\start-cli.bat + .\apache-iotdb-{version}-bin\sbin\start-cli.bat ``` 6. Execute commands for verification. diff --git a/src/UserGuide/Master/Table/User-Manual/Maintenance-commands_apache.md b/src/UserGuide/Master/Table/User-Manual/Maintenance-commands_apache.md index b6094310f..2c4bd4f20 100644 --- a/src/UserGuide/Master/Table/User-Manual/Maintenance-commands_apache.md +++ b/src/UserGuide/Master/Table/User-Manual/Maintenance-commands_apache.md @@ -7,9 +7,9 @@ to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at - + http://www.apache.org/licenses/LICENSE-2.0 - + Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY @@ -625,7 +625,7 @@ setConfigurationStatement propertyAssignments : property (',' property)* ; - + property : identifier EQ propertyValue ; @@ -662,7 +662,7 @@ IoTDB> SET CONFIGURATION disk_space_warning_threshold='0.05',heartbeat_interval_ loadConfigurationStatement : LOAD CONFIGURATION localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -692,8 +692,8 @@ IoTDB> LOAD CONFIGURATION ON LOCAL; ```SQL setSystemStatusStatement : SET SYSTEM TO (READONLY | RUNNING) localOrClusterMode? - ; - + ; + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -771,7 +771,7 @@ IoTDB> FLUSH test_db TRUE ON LOCAL; startRepairDataStatement : START REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -800,7 +800,7 @@ IoTDB> START REPAIR DATA ON CLUSTER; stopRepairDataStatement : STOP REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -881,18 +881,18 @@ DEBUG SELECT * FROM table3; 2. Check the log content in `log_datanode_query_debug.log` to view the file scan information involved in the query. ```bash -2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2864/1769139940009-1-0-0.tsfile is not satisfied because of no device! -2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2865/1769139940010-1-0-0.tsfile is not satisfied because of no device! -2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: table3.d1. in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile -2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: table3.d1, all sensors: [, temperature] -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1. metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=-128, chunkMetaDataListDataSize=8, measurementId='', dataType=VECTOR, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2, modified=false, isSeq=true, chunkMetadataList=[measurementId: , datatype: VECTOR, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2, deleteIntervalList: null]}. -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1.temperature metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=64, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=FLOAT, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: FLOAT, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], deleteIntervalList: null]}. -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:110 - Modifications size is 1 for file Path: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:114 - [] -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:125 - After modification Chunk meta data list is: -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:126 - org.apache.tsfile.file.metadata.TableDeviceChunkMetadata@2e11291f -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=19} -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=46} +2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2864/1769139940009-1-0-0.tsfile is not satisfied because of no device! +2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2865/1769139940010-1-0-0.tsfile is not satisfied because of no device! +2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: table3.d1. in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile +2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: table3.d1, all sensors: [, temperature] +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1. metadata in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=-128, chunkMetaDataListDataSize=8, measurementId='', dataType=VECTOR, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2, modified=false, isSeq=true, chunkMetadataList=[measurementId: , datatype: VECTOR, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2, deleteIntervalList: null]}. +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1.temperature metadata in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=64, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=FLOAT, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: FLOAT, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], deleteIntervalList: null]}. +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:110 - Modifications size is 1 for file Path: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:114 - [] +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:125 - After modification Chunk meta data list is: +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:126 - org.apache.tsfile.file.metadata.TableDeviceChunkMetadata@2e11291f +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=19} +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=46} 2026-03-24 10:10:41,519 [pool-69-IoTDB-ClientRPC-Processor-1$20260324_021041_00068_1] INFO o.a.i.d.q.p.Coordinator:902 - debug select * from table3 ``` diff --git a/src/UserGuide/Master/Table/User-Manual/Query-Performance-Analysis.md b/src/UserGuide/Master/Table/User-Manual/Query-Performance-Analysis.md index 4a693599a..17c0259f0 100644 --- a/src/UserGuide/Master/Table/User-Manual/Query-Performance-Analysis.md +++ b/src/UserGuide/Master/Table/User-Manual/Query-Performance-Analysis.md @@ -30,7 +30,7 @@ Query analysis helps users understand query execution mechanisms and identify pe | **Method** | **Installation Difficulty** | **Business Impact** | **Functional Scope** | | :----------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- | | **EXPLAIN ANALYZE** | **Low.** No additional components required; built-in SQL statement in IoTDB. | **Low.** Impacts only the analyzed query, with no effect on other workloads. | **Supports cluster systems.** Enables tracing for a single SQL query. | -| **Monitoring Dashboard** | **Medium.** Requires installation of IoTDB monitoring dashboard tool (TimechoDB) and enabling monitoring services. | **Medium.** Metrics collection introduces additional overhead. | **Supports cluster systems.** Analyzes overall database query load and latency. | +| **Monitoring Dashboard** | **Medium.** Requires installation of IoTDB monitoring dashboard tool (IoTDB) and enabling monitoring services. | **Medium.** Metrics collection introduces additional overhead. | **Supports cluster systems.** Analyzes overall database query load and latency. | | **Arthas Sampling** | **Medium.** Requires Java Arthas installation (may be restricted in internal networks; sometimes requires application restart). | **High.** May degrade response speed of online services due to CPU sampling. | **Does n****ot supports cluster systems.** Analyzes overall database query load and latency. | diff --git a/src/UserGuide/Master/Tree/Background-knowledge/Data-Type.md b/src/UserGuide/Master/Tree/Background-knowledge/Data-Type.md index 0be198c62..965dfe525 100644 --- a/src/UserGuide/Master/Tree/Background-knowledge/Data-Type.md +++ b/src/UserGuide/Master/Tree/Background-knowledge/Data-Type.md @@ -40,7 +40,7 @@ The difference between STRING and TEXT types is that STRING type has more statis ### 1.1 Float Precision -The time series of **FLOAT** and **DOUBLE** type can specify (MAX\_POINT\_NUMBER, see [this page](../SQL-Manual/SQL-Manual_timecho) for more information on how to specify), which is the number of digits after the decimal point of the floating point number, if the encoding method is [RLE](../Technical-Insider/Encoding-and-Compression.md) or [TS\_2DIFF](../Technical-Insider/Encoding-and-Compression.md). If MAX\_POINT\_NUMBER is not specified, the system will use [float\_precision](../Reference/DataNode-Config-Manual.md) in the configuration file `iotdb-system.properties`. +The time series of **FLOAT** and **DOUBLE** type can specify (MAX\_POINT\_NUMBER, see [this page](../SQL-Manual/SQL-Manual_apache) for more information on how to specify), which is the number of digits after the decimal point of the floating point number, if the encoding method is [RLE](../Technical-Insider/Encoding-and-Compression.md) or [TS\_2DIFF](../Technical-Insider/Encoding-and-Compression.md). If MAX\_POINT\_NUMBER is not specified, the system will use [float\_precision](../Reference/DataNode-Config-Manual.md) in the configuration file `iotdb-system.properties`. ```sql CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 'MAX_POINT_NUMBER'='2'; diff --git a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index aa8d48de8..6d27f895e 100644 --- a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -55,7 +55,7 @@ To ensure the AINode installation package you obtained is complete and correct, **Preparation:** -- Obtain the official SHA512 checksum: Please contact Timecho staff. +- Obtain the official SHA512 checksum: Please contact commercial support. **Verification Steps (using Linux as an example):** @@ -77,7 +77,7 @@ To ensure the AINode installation package you obtained is complete and correct, **Notes:** -- If the verification results do not match, please contact Timecho staff to obtain a new installation package. +- If the verification results do not match, please contact commercial support to obtain a new installation package. - If you encounter a "file not found" prompt during verification, check if the file path is correct or if the installation package was downloaded completely. ### 2.3 Environment Requirements @@ -116,7 +116,7 @@ AINode supports modifying some necessary parameters. You can find the following ### 3.3 Importing Built-in Weight Files *If the deployment environment has network connectivity and can access HuggingFace, the system will automatically pull the built-in model weight files. This step can be skipped.* -*For offline environments, contact Timecho staff to obtain the model weight folder and place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.* +*For offline environments, contact commercial support to obtain the model weight folder and place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.* **NOTE:** Pay attention to the directory hierarchy. The parent directory for all built-in model weights should be `builtin`. ### 3.4 Starting AINode @@ -228,7 +228,7 @@ If you need to upgrade the version of the current AINode, you can refer to the f 3. Update built-in model weights (optional) - * If the new version involves updates to built-in models, relevant information will be updated in the [Release History](../IoTDB-Introduction/Release-history_apache.md). You may contact Timecho staff to obtain the latest weight package and replace it in the `data/ainode/models/builtin` directory. + * If the new version involves updates to built-in models, relevant information will be updated in the [Release History](../IoTDB-Introduction/Release-history_apache.md). You may contact commercial support to obtain the latest weight package and replace it in the `data/ainode/models/builtin` directory. 4. After the upgrade is completed, you can start the AINode service and check the node status. For specific commands, refer to Sections 3.4 and 3.5. diff --git a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md index 6d38c04dc..e9fdac335 100644 --- a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -69,7 +69,7 @@ To ensure the AINode installation package you obtained is complete and valid, we ``` 2. Execute the following command to calculate the hash value: ```Bash - sha512sum timechodb-{version}-ainode-bin.zip + sha512sum apache-iotdb-{version}-ainode-bin.zip ``` 3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name): @@ -129,7 +129,7 @@ AINode supports modifying some necessary parameters. You can find the following > Offline environment only (Online environments can skip this step) > - Contact Timecho team to obtain the model weight files, then place them in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory. + Contact commercial support to obtain the model weight files, then place them in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory. ### 3.4 Start AINode diff --git a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md index be7631998..5752268ff 100644 --- a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -205,7 +205,7 @@ You can use the `show cluster` command to view cluster information: ![](/img/%E5%BC%80%E6%BA%90%E7%89%88%20show%20cluter.png) -> The appearance of `ACTIVATED (W)` indicates passive activation, which means that this Configurable Node does not have a license file (or has not issued the latest license file with a timestamp), and its activation depends on other Activated Configurable Nodes in the cluster. At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply. +> The appearance of `ACTIVATED (W)` indicates passive activation, which means that this Configurable Node does not have a license file (or has not issued the latest license file with a timestamp), and its activation depends on other Activated Configurable Nodes in the cluster. At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact commercial support to reapply. ### 3.6 One-click Cluster Start and Stop @@ -476,7 +476,7 @@ For more details on cluster maintenance, please refer to: [Cluster Maintenance]( Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified. - Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions. + Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact commercial support for consultation on solutions. Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart. diff --git a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources.md b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources.md index 4344a1b08..3a0a5b74e 100644 --- a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources.md +++ b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources.md @@ -72,11 +72,11 @@ 48core 1 2 - Please contact Timecho Business for consultation + Please contact commercial support for consultation Over 10000000 - Please contact Timecho Business for consultation + Please contact commercial support for consultation @@ -137,11 +137,11 @@ 128G 1 2 - Please contact Timecho Business for consultation + Please contact commercial support for consultation Over 10000000 - Please contact Timecho Business for consultation + Please contact commercial support for consultation diff --git a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md index ea940bc34..e2bb1d519 100644 --- a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md +++ b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md @@ -173,7 +173,7 @@ When the status is all running, it indicates that the service has started succes ![](/img/%E5%BC%80%E6%BA%90-%E5%8D%95%E6%9C%BAshow.jpeg) -> The appearance of 'Activated (W)' indicates passive activation, indicating that this Config Node does not have a license file (or has not issued the latest license file with a timestamp). At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply. +> The appearance of 'Activated (W)' indicates passive activation, indicating that this Config Node does not have a license file (or has not issued the latest license file with a timestamp). At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact commercial support to reapply. ## 3. Common Questions @@ -181,7 +181,7 @@ When the status is all running, it indicates that the service has started succes Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified. - Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions. + Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact commercial support for consultation on solutions. Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart. diff --git a/src/UserGuide/Master/Tree/Ecosystem-Integration/DataEase.md b/src/UserGuide/Master/Tree/Ecosystem-Integration/DataEase.md index ddfbb62ce..9a22a1bf4 100644 --- a/src/UserGuide/Master/Tree/Ecosystem-Integration/DataEase.md +++ b/src/UserGuide/Master/Tree/Ecosystem-Integration/DataEase.md @@ -41,14 +41,14 @@ | **Preparation Content** | **Version Requirements** | | :-------------------- | :----------------------------------------------------------- | -| IoTDB | Version not required, please refer to [Deployment Guidance](https://www.timecho-global.com/docs/UserGuide/latest/Deployment-and-Maintenance/IoTDB-Package_timecho.html) | +| IoTDB | Version not required, please refer to [Deployment Guidance](../QuickStart/QuickStart_apache.md) | | JDK | Requires JDK 11 or higher (JDK 17 or above is recommended for optimal performance) | -| DataEase | Requires v1 series v1.18 version, please refer to the official [DataEase Installation Guide](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)(V2.x is currently not supported. For integration with other versions, please contact Timecho) | -| DataEase-IoTDB Connector | Please contact Timecho for assistance | +| DataEase | Requires v1 series v1.18 version, please refer to the official [DataEase Installation Guide](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)(V2.x is currently not supported. For integration with other versions, please contact staff) | +| DataEase-IoTDB Connector | Please contact staff for assistance | ## 3. Installation Steps -Step 1: Please contact Timecho to obtain the file and unzip the installation package `iotdb-api-source-1.0.0.zip` +Step 1: Please contact staff to obtain the file and unzip the installation package `iotdb-api-source-1.0.0.zip` Step 2: After extracting the files, modify the `application.properties` configuration file in the `config` folder diff --git a/src/UserGuide/Master/Tree/Ecosystem-Integration/Thingsboard.md b/src/UserGuide/Master/Tree/Ecosystem-Integration/Thingsboard.md index f304c277f..adb1f172e 100644 --- a/src/UserGuide/Master/Tree/Ecosystem-Integration/Thingsboard.md +++ b/src/UserGuide/Master/Tree/Ecosystem-Integration/Thingsboard.md @@ -42,13 +42,13 @@ | :---------------------------------------- | :----------------------------------------------------------- | | JDK | JDK17 or above. Please refer to the downloads on [Oracle Official Website](https://www.oracle.com/java/technologies/downloads/) | | IoTDB |IoTDB v1.3.0 or above. Please refer to the [Deployment guidance](../Deployment-and-Maintenance/IoTDB-Package.md) | -| ThingsBoard
(IoTDB adapted version) | Please contact Timecho staff to obtain the installation package. Detailed installation steps are provided below. | +| ThingsBoard
(IoTDB adapted version) | Please contact commercial support to obtain the installation package. Detailed installation steps are provided below. | ## 3. Installation Steps Please refer to the installation steps on [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/),wherein: -- [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/)【 Step 2: ThingsBoard Service Installation 】 Use the installation package provided by your Timecho contact to install the software. Please note that the official ThingsBoard installation package does not support IoTDB. +- [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/)【 Step 2: ThingsBoard Service Installation 】 Use the installation package provided by your contact to install the software. Please note that the official ThingsBoard installation package does not support IoTDB. - [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/) 【Step 3: Configure ThingsBoard Database - ThingsBoard Configuration】 In this step, you need to add environment variables according to the following content ```Shell diff --git a/src/UserGuide/Master/Tree/QuickStart/QuickStart_apache.md b/src/UserGuide/Master/Tree/QuickStart/QuickStart_apache.md index ec7bee5ff..8489bfb84 100644 --- a/src/UserGuide/Master/Tree/QuickStart/QuickStart_apache.md +++ b/src/UserGuide/Master/Tree/QuickStart/QuickStart_apache.md @@ -32,7 +32,7 @@ This guide will assist you in quickly installing and deploying IoTDB. You can qu 2. Complete system configuration preparations: IoTDB's system configuration involves multiple aspects. For an introduction to key system configurations, please see [System Requirements](../Deployment-and-Maintenance/Environment-Requirements.md) -3. Obtain the installation package: You can obtain the IoTDB installation package on the [Apache IoTDB official website](https://iotdb.apache.org/zh/Download/).For the specific structure of the installation package, please refer to[Obtain TimechoDB](../Deployment-and-Maintenance/IoTDB-Package_apache.md) +3. Obtain the installation package: You can obtain the IoTDB installation package on the [Apache IoTDB official website](https://iotdb.apache.org/zh/Download/).For the specific structure of the installation package, please refer to[Obtain IoTDB](../Deployment-and-Maintenance/IoTDB-Package_apache.md) 4. Install the database and activate it: Depending on your actual deployment architecture, you can choose from the following tutorials for installation and deployment: diff --git a/src/UserGuide/Master/Tree/SQL-Manual/UDF-Libraries_apache.md b/src/UserGuide/Master/Tree/SQL-Manual/UDF-Libraries_apache.md index 617026aa3..c22a1cf9b 100644 --- a/src/UserGuide/Master/Tree/SQL-Manual/UDF-Libraries_apache.md +++ b/src/UserGuide/Master/Tree/SQL-Manual/UDF-Libraries_apache.md @@ -31,8 +31,8 @@ Based on the ability of user-defined functions, IoTDB provides a series of funct | UDF installation package | Supported IoTDB versions | Download link | | --------------- | ----------------- | ------------------------------------------------------------ | - | apache-UDF-1.3.3.zip | V1.3.3 and above |Please contact Timecho for assistance | - | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | Please contact Timecho for assistance| + | apache-UDF-1.3.3.zip | V1.3.3 and above |Please contact staff for assistance | + | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | Please contact staff for assistance| 2. Place the library-udf.jar file in the compressed file obtained in the directory `/ext/udf ` of all nodes in the IoTDB cluster 3. In the SQL operation interface of IoTDB's SQL command line terminal (CLI), execute the corresponding function registration statement as follows. diff --git a/src/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md b/src/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md index afcb22c0f..d4ed0675b 100644 --- a/src/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md +++ b/src/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md @@ -109,7 +109,7 @@ The following documents may help you have a good journey with Prometheus and Gra ## 2. Apache IoTDB Dashboard -`Apache IoTDB Dashboard` is available as a supplement to TimechoDB, designed for unified centralized operations and management. With it, multiple clusters can be monitored through a single panel. You can access the Dashboard's Json file by contacting Commerce. +`Apache IoTDB Dashboard` is available as a supplement to IoTDB, designed for unified centralized operations and management. With it, multiple clusters can be monitored through a single panel. You can access the Dashboard's Json file by contacting Commerce. ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png) diff --git a/src/UserGuide/Master/Tree/User-Manual/Load-Balance.md b/src/UserGuide/Master/Tree/User-Manual/Load-Balance.md index e34001346..5af690a8c 100644 --- a/src/UserGuide/Master/Tree/User-Manual/Load-Balance.md +++ b/src/UserGuide/Master/Tree/User-Manual/Load-Balance.md @@ -137,18 +137,18 @@ echo "192.168.1.3 iotdb-1" >> /etc/hosts #### 1.3.2 Scaling Operation -1. To ensure the TimechoDB installation package you obtained is complete and correct, it is recommended to perform an SHA512 checksum before installation and deployment. +1. To ensure the IoTDB installation package you obtained is complete and correct, it is recommended to perform an SHA512 checksum before installation and deployment. 2. Unzip the installation package and enter the installation directory. ``` -unzip timechodb-{version}-bin.zip -cd timechodb-{version}-bin +unzip apache-iotdb-{version}-bin.zip +cd apache-iotdb-{version}-bin ``` 3. Modify the relevant configuration. ``` -cd timechodb-{version}-bin/conf +cd apache-iotdb-{version}-bin/conf vim iotdb-system.properties ``` @@ -175,10 +175,10 @@ Navigate to the `sbin`directory under IoTDB and start the datanode: ``` # Linux or macOS - ./timechodb-{version}-bin/sbin/start-cli.sh + ./apache-iotdb-{version}-bin/sbin/start-cli.sh # Windows - .\timechodb-{version}-bin\sbin\start-cli.bat + .\apache-iotdb-{version}-bin\sbin\start-cli.bat ``` 6. Execute commands for verification. diff --git a/src/UserGuide/Master/Tree/User-Manual/Maintenance-commands_apache.md b/src/UserGuide/Master/Tree/User-Manual/Maintenance-commands_apache.md index c3ba550bc..dc4a4764e 100644 --- a/src/UserGuide/Master/Tree/User-Manual/Maintenance-commands_apache.md +++ b/src/UserGuide/Master/Tree/User-Manual/Maintenance-commands_apache.md @@ -7,9 +7,9 @@ to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at - + http://www.apache.org/licenses/LICENSE-2.0 - + Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY @@ -199,7 +199,7 @@ showQueriesStatement **Example**: ```SQL -IoTDB> SHOW QUERIES WHERE elapsedtime > 0.003 +IoTDB> SHOW QUERIES WHERE elapsedtime > 0.003 ``` **Result**: @@ -312,7 +312,7 @@ Execution result: #### Syntax: ```sql showDiskUsageStatement - : SHOW DISK_USAGE FROM pathPattern + : SHOW DISK_USAGE FROM pathPattern whereClause? orderByClause? rowPaginationClause? @@ -391,7 +391,7 @@ setConfigurationStatement propertyAssignments : property (',' property)* ; - + property : identifier EQ propertyValue ; @@ -428,7 +428,7 @@ IoTDB> SET CONFIGURATION ‘disk_space_warning_threshold’='0.05',‘heartbeat_ loadConfigurationStatement : LOAD CONFIGURATION localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -458,8 +458,8 @@ IoTDB> LOAD CONFIGURATION ON LOCAL; ```SQL setSystemStatusStatement : SET SYSTEM TO (READONLY | RUNNING) localOrClusterMode? - ; - + ; + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -537,7 +537,7 @@ IoTDB> FLUSH root.ln TRUE ON LOCAL; startRepairDataStatement : START REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -566,7 +566,7 @@ IoTDB> START REPAIR DATA ON CLUSTER; stopRepairDataStatement : STOP REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -648,13 +648,13 @@ DEBUG SELECT * FROM root.ln.**; 2. Check the log content in `log_datanode_query_debug.log` to view the file scan information involved in the query. ```bash -2026-03-24 10:06:18,755 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: root.ln.wf01.wt01.temperature in file: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile -2026-03-24 10:06:18,757 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: root.ln.wf01.wt01, all sensors: [temperature] -2026-03-24 10:06:18,758 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: root.ln.wf01.wt01.temperature metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=0, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=DOUBLE, statistics=startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null]}. -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:97 - Modifications size is 0 for file Path: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:109 - After modification Chunk meta data list is: -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:110 - measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null -2026-03-24 10:06:18,760 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile', regionId=13, timePartitionId=2932, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=27} +2026-03-24 10:06:18,755 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: root.ln.wf01.wt01.temperature in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile +2026-03-24 10:06:18,757 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: root.ln.wf01.wt01, all sensors: [temperature] +2026-03-24 10:06:18,758 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: root.ln.wf01.wt01.temperature metadata in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=0, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=DOUBLE, statistics=startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null]}. +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:97 - Modifications size is 0 for file Path: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:109 - After modification Chunk meta data list is: +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:110 - measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null +2026-03-24 10:06:18,760 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile', regionId=13, timePartitionId=2932, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=27} 2026-03-24 10:06:18,761 [pool-69-IoTDB-ClientRPC-Processor-1$20260324_020618_00052_1] INFO o.a.i.d.q.p.Coordinator:902 - debug select * from root.ln.** ``` diff --git a/src/UserGuide/Master/Tree/User-Manual/Streaming_apache.md b/src/UserGuide/Master/Tree/User-Manual/Streaming_apache.md index b5a8e2419..586dcbb62 100644 --- a/src/UserGuide/Master/Tree/User-Manual/Streaming_apache.md +++ b/src/UserGuide/Master/Tree/User-Manual/Streaming_apache.md @@ -561,7 +561,7 @@ WITH SOURCE ( -- Default IoTDB Data Extraction Plugin 'source' = 'iotdb-source', -- Path prefix, only data that can match the path prefix will be extracted for subsequent processing and delivery - 'source.pattern' = 'root.timecho', + 'source.pattern' = 'root.iotdb', -- Whether to extract historical data 'source.history.enable' = 'true', -- Describes the time range of the historical data being extracted, indicating the earliest possible time diff --git a/src/UserGuide/V1.2.x/Deployment-and-Maintenance/Monitoring-Board-Install-and-Deploy.md b/src/UserGuide/V1.2.x/Deployment-and-Maintenance/Monitoring-Board-Install-and-Deploy.md index 3a78193e8..4f0ff68bd 100644 --- a/src/UserGuide/V1.2.x/Deployment-and-Maintenance/Monitoring-Board-Install-and-Deploy.md +++ b/src/UserGuide/V1.2.x/Deployment-and-Maintenance/Monitoring-Board-Install-and-Deploy.md @@ -29,7 +29,7 @@ From the Apache IoTDB 1.0 version, we introduced the system monitoring module, y 1. Apache IoTDB: version 1.0 and above, download from the official website: https://iotdb.apache.org/Download/ 2. Prometheus: version 2.30.3 and above, download from the official website: https://prometheus.io/download/ 3. Grafana: version 8.4.2 and above, download from the official website: https://grafana.com/grafana/download -4. IoTDB-Grafana installer: Grafana Dashboards is an TimechoDB(Enterprise Edition based on IoTDB) tool, and you may contact your sales for the relevant installer. +4. IoTDB-Grafana installer: Grafana Dashboards is an IoTDB(Enterprise Edition based on IoTDB) tool, and you may contact your sales for the relevant installer. ### cluster requirement diff --git a/src/UserGuide/V1.2.x/Reference/UDF-Libraries.md b/src/UserGuide/V1.2.x/Reference/UDF-Libraries.md index d30fb4548..a634210f9 100644 --- a/src/UserGuide/V1.2.x/Reference/UDF-Libraries.md +++ b/src/UserGuide/V1.2.x/Reference/UDF-Libraries.md @@ -31,7 +31,7 @@ Based on the ability of user-defined functions, IoTDB provides a series of funct | UDF libraries version | Supported IoTDB versions | Download link | | --------------- | ----------------- | ------------------------------------------------------------ | - | TimechoDB-UDF-1.2.x.zip | V1.0.0～V1.2.x |Please contact Timecho for assistance| + | IoTDB-UDF-1.2.x.zip | V1.0.0～V1.2.x |Please contact staff for assistance| 2. Place the library-udf.jar file in the compressed file obtained in the directory `/ext/udf ` of all nodes in the IoTDB cluster 3. In the SQL command line terminal (CLI) or visualization console (Workbench) SQL operation interface of IoTDB, execute the corresponding function registration statement as follows. diff --git a/src/UserGuide/V1.2.x/User-Manual/Data-Sync.md b/src/UserGuide/V1.2.x/User-Manual/Data-Sync.md index 380459c39..52630b752 100644 --- a/src/UserGuide/V1.2.x/User-Manual/Data-Sync.md +++ b/src/UserGuide/V1.2.x/User-Manual/Data-Sync.md @@ -89,7 +89,7 @@ WITH EXTRACTOR ( -- Default IoTDB Data Extraction Plugin 'extractor' = 'iotdb-extractor', -- Path prefix, only data that can match the path prefix will be extracted for subsequent processing and delivery - 'extractor.pattern' = 'root.timecho', + 'extractor.pattern' = 'root.iotdb', -- Whether to extract historical data 'extractor.history.enable' = 'true', -- Describes the time range of the historical data being extracted, indicating the earliest possible time diff --git a/src/UserGuide/V1.2.x/User-Manual/Streaming.md b/src/UserGuide/V1.2.x/User-Manual/Streaming.md index 4ac8ec837..0653052bb 100644 --- a/src/UserGuide/V1.2.x/User-Manual/Streaming.md +++ b/src/UserGuide/V1.2.x/User-Manual/Streaming.md @@ -563,7 +563,7 @@ WITH EXTRACTOR ( -- Default IoTDB Data Extraction Plugin 'extractor' = 'iotdb-extractor', -- Path prefix, only data that can match the path prefix will be extracted for subsequent processing and delivery - 'extractor.pattern' = 'root.timecho', + 'extractor.pattern' = 'root.iotdb', -- Whether to extract historical data 'extractor.history.enable' = 'true', -- Describes the time range of the historical data being extracted, indicating the earliest possible time diff --git a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/AINode_Deployment_apache.md index 73574db6b..f876e49de 100644 --- a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -69,7 +69,7 @@ To ensure the AINode installation package you obtained is complete and valid, we ``` 2. Execute the following command to calculate the hash value: ```Bash - sha512sum timechodb-{version}-ainode-bin.zip + sha512sum apache-iotdb-{version}-ainode-bin.zip ``` 3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name): diff --git a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md index 043d4fb45..6f2e00c3c 100644 --- a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -415,7 +415,7 @@ sbin/remove-datanode.bat [datanode_id] Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified. - Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions. + Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact commercial support for consultation on solutions. Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart. diff --git a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Database-Resources.md b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Database-Resources.md index 38871d38e..b94af1936 100644 --- a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Database-Resources.md +++ b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Database-Resources.md @@ -72,11 +72,11 @@ 48core 1 2 - Please contact Timecho Business for consultation + Please contact commercial support for consultation Over 10000000 - Please contact Timecho Business for consultation + Please contact commercial support for consultation @@ -134,11 +134,11 @@ 128G 1 2 - Please contact Timecho Business for consultation + Please contact commercial support for consultation Over 10000000 - Please contact Timecho Business for consultation + Please contact commercial support for consultation diff --git a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md index eadc227f7..51d54fe15 100644 --- a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md +++ b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md @@ -179,7 +179,7 @@ When the status is all running, it indicates that the service has started succes Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified. - Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions. + Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact commercial support for consultation on solutions. Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart. diff --git a/src/UserGuide/V1.3.x/Ecosystem-Integration/DataEase.md b/src/UserGuide/V1.3.x/Ecosystem-Integration/DataEase.md index 021ed7d68..13bb431f3 100644 --- a/src/UserGuide/V1.3.x/Ecosystem-Integration/DataEase.md +++ b/src/UserGuide/V1.3.x/Ecosystem-Integration/DataEase.md @@ -41,14 +41,14 @@ | **Preparation Content** | **Version Requirements** | | :-------------------- | :----------------------------------------------------------- | -| IoTDB | Version not required, please refer to [Deployment Guidance](https://www.timecho-global.com/docs/UserGuide/latest/Deployment-and-Maintenance/IoTDB-Package_timecho.html) | +| IoTDB | Version not required, please refer to [Deployment Guidance](../QuickStart/QuickStart_apache.md) | | JDK | Requires JDK 11 or higher (JDK 17 or above is recommended for optimal performance) | -| DataEase | Requires v1 series v1.18 version, please refer to the official [DataEase Installation Guide](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)(V2.x is currently not supported. For integration with other versions, please contact Timecho) | -| DataEase-IoTDB Connector | Please contact Timecho for assistance | +| DataEase | Requires v1 series v1.18 version, please refer to the official [DataEase Installation Guide](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)(V2.x is currently not supported. For integration with other versions, please contact staff) | +| DataEase-IoTDB Connector | Please contact staff for assistance | ## Installation Steps -Step 1: Please contact Timecho to obtain the file and unzip the installation package `iotdb-api-source-1.0.0.zip` +Step 1: Please contact staff to obtain the file and unzip the installation package `iotdb-api-source-1.0.0.zip` Step 2: After extracting the files, modify the `application.properties` configuration file in the `config` folder diff --git a/src/UserGuide/V1.3.x/Ecosystem-Integration/Thingsboard.md b/src/UserGuide/V1.3.x/Ecosystem-Integration/Thingsboard.md index 024d3ed46..b5e580d9d 100644 --- a/src/UserGuide/V1.3.x/Ecosystem-Integration/Thingsboard.md +++ b/src/UserGuide/V1.3.x/Ecosystem-Integration/Thingsboard.md @@ -42,13 +42,13 @@ | :---------------------------------------- | :----------------------------------------------------------- | | JDK | JDK17 or above. Please refer to the downloads on [Oracle Official Website](https://www.oracle.com/java/technologies/downloads/) | | IoTDB |IoTDB v1.3.0 or above. Please refer to the [Deployment guidance](../Deployment-and-Maintenance/IoTDB-Package.md) | -| ThingsBoard
(IoTDB adapted version) | Please contact Timecho staff to obtain the installation package. Detailed installation steps are provided below. | +| ThingsBoard
(IoTDB adapted version) | Please contact commercial support to obtain the installation package. Detailed installation steps are provided below. | ## Installation Steps Please refer to the installation steps on [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/),wherein: -- [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/)【 Step 2: ThingsBoard Service Installation 】 Use the installation package provided by your Timecho contact to install the software. Please note that the official ThingsBoard installation package does not support IoTDB. +- [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/)【 Step 2: ThingsBoard Service Installation 】 Use the installation package provided by your contact to install the software. Please note that the official ThingsBoard installation package does not support IoTDB. - [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/) 【Step 3: Configure ThingsBoard Database - ThingsBoard Configuration】 In this step, you need to add environment variables according to the following content ```Shell diff --git a/src/UserGuide/V1.3.x/IoTDB-Introduction/IoTDB-Introduction_apache.md b/src/UserGuide/V1.3.x/IoTDB-Introduction/IoTDB-Introduction_apache.md index 4c782c02a..8f8ebdf84 100644 --- a/src/UserGuide/V1.3.x/IoTDB-Introduction/IoTDB-Introduction_apache.md +++ b/src/UserGuide/V1.3.x/IoTDB-Introduction/IoTDB-Introduction_apache.md @@ -35,7 +35,7 @@ Apache IoTDB is a low-cost, high-performance native temporal database for the In IoTDB products consist of several components that help users efficiently manage and analyze the massive amount of time-series data generated by the IoT.
- Introduction-en-timecho.png + Introduction-en-apache.png
diff --git a/src/UserGuide/V1.3.x/SQL-Manual/UDF-Libraries_apache.md b/src/UserGuide/V1.3.x/SQL-Manual/UDF-Libraries_apache.md index 7c93cbdb6..34775eb04 100644 --- a/src/UserGuide/V1.3.x/SQL-Manual/UDF-Libraries_apache.md +++ b/src/UserGuide/V1.3.x/SQL-Manual/UDF-Libraries_apache.md @@ -33,8 +33,8 @@ Based on the ability of user-defined functions, IoTDB provides a series of funct | UDF installation package | Supported IoTDB versions | Download link | | --------------- | ----------------- | ------------------------------------------------------------ | - | apache-UDF-1.3.3.zip | V1.3.3 and above |Please contact Timecho for assistance | - | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | Please contact Timecho for assistance| + | apache-UDF-1.3.3.zip | V1.3.3 and above |Please contact staff for assistance | + | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | Please contact staff for assistance| 2. Place the library-udf.jar file in the compressed file obtained in the directory `/ext/udf ` of all nodes in the IoTDB cluster 3. In the SQL operation interface of IoTDB's SQL command line terminal (CLI), execute the corresponding function registration statement as follows. diff --git a/src/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md b/src/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md index 956ec134e..aa38f1952 100644 --- a/src/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md +++ b/src/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md @@ -109,7 +109,7 @@ The following documents may help you have a good journey with Prometheus and Gra ## Apache IoTDB Dashboard -`Apache IoTDB Dashboard` is available as a supplement to TimechoDB, designed for unified centralized operations and management. With it, multiple clusters can be monitored through a single panel. You can access the Dashboard's Json file by contacting Commerce. +`Apache IoTDB Dashboard` is available as a supplement to IoTDB, designed for unified centralized operations and management. With it, multiple clusters can be monitored through a single panel. You can access the Dashboard's Json file by contacting Commerce. ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png) diff --git a/src/UserGuide/V1.3.x/User-Manual/Streaming_apache.md b/src/UserGuide/V1.3.x/User-Manual/Streaming_apache.md index 7f9b9716a..bfb49b91d 100644 --- a/src/UserGuide/V1.3.x/User-Manual/Streaming_apache.md +++ b/src/UserGuide/V1.3.x/User-Manual/Streaming_apache.md @@ -561,7 +561,7 @@ WITH SOURCE ( -- Default IoTDB Data Extraction Plugin 'source' = 'iotdb-source', -- Path prefix, only data that can match the path prefix will be extracted for subsequent processing and delivery - 'source.pattern' = 'root.timecho', + 'source.pattern' = 'root.iotdb', -- Whether to extract historical data 'source.history.enable' = 'true', -- Describes the time range of the historical data being extracted, indicating the earliest possible time diff --git a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/AINode_Deployment_apache.md index 57967f345..5ff6a9dd7 100644 --- a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -69,7 +69,7 @@ To ensure the AINode installation package you obtained is complete and valid, we ``` 2. Execute the following command to calculate the hash value: ```Bash - sha512sum timechodb-{version}-ainode-bin.zip + sha512sum apache-iotdb-{version}-ainode-bin.zip ``` 3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name): diff --git a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md index 1a9bcace9..23590ad6f 100644 --- a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -409,7 +409,7 @@ remove datanode [datanode_id] Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified. - Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions. + Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact commercial support for consultation on solutions. Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart. diff --git a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Database-Resources.md b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Database-Resources.md index 38871d38e..b94af1936 100644 --- a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Database-Resources.md +++ b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Database-Resources.md @@ -72,11 +72,11 @@ 48core 1 2 - Please contact Timecho Business for consultation + Please contact commercial support for consultation Over 10000000 - Please contact Timecho Business for consultation + Please contact commercial support for consultation @@ -134,11 +134,11 @@ 128G 1 2 - Please contact Timecho Business for consultation + Please contact commercial support for consultation Over 10000000 - Please contact Timecho Business for consultation + Please contact commercial support for consultation diff --git a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md index a939b12a4..527875f38 100644 --- a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md +++ b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md @@ -183,7 +183,7 @@ When the status is all running, it indicates that the service has started succes Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified. - Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions. + Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact commercial support for consultation on solutions. Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart. diff --git a/src/UserGuide/dev-1.3/Ecosystem-Integration/DataEase.md b/src/UserGuide/dev-1.3/Ecosystem-Integration/DataEase.md index 021ed7d68..13bb431f3 100644 --- a/src/UserGuide/dev-1.3/Ecosystem-Integration/DataEase.md +++ b/src/UserGuide/dev-1.3/Ecosystem-Integration/DataEase.md @@ -41,14 +41,14 @@ | **Preparation Content** | **Version Requirements** | | :-------------------- | :----------------------------------------------------------- | -| IoTDB | Version not required, please refer to [Deployment Guidance](https://www.timecho-global.com/docs/UserGuide/latest/Deployment-and-Maintenance/IoTDB-Package_timecho.html) | +| IoTDB | Version not required, please refer to [Deployment Guidance](../QuickStart/QuickStart_apache.md) | | JDK | Requires JDK 11 or higher (JDK 17 or above is recommended for optimal performance) | -| DataEase | Requires v1 series v1.18 version, please refer to the official [DataEase Installation Guide](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)(V2.x is currently not supported. For integration with other versions, please contact Timecho) | -| DataEase-IoTDB Connector | Please contact Timecho for assistance | +| DataEase | Requires v1 series v1.18 version, please refer to the official [DataEase Installation Guide](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)(V2.x is currently not supported. For integration with other versions, please contact staff) | +| DataEase-IoTDB Connector | Please contact staff for assistance | ## Installation Steps -Step 1: Please contact Timecho to obtain the file and unzip the installation package `iotdb-api-source-1.0.0.zip` +Step 1: Please contact staff to obtain the file and unzip the installation package `iotdb-api-source-1.0.0.zip` Step 2: After extracting the files, modify the `application.properties` configuration file in the `config` folder diff --git a/src/UserGuide/dev-1.3/Ecosystem-Integration/Thingsboard.md b/src/UserGuide/dev-1.3/Ecosystem-Integration/Thingsboard.md index 024d3ed46..b5e580d9d 100644 --- a/src/UserGuide/dev-1.3/Ecosystem-Integration/Thingsboard.md +++ b/src/UserGuide/dev-1.3/Ecosystem-Integration/Thingsboard.md @@ -42,13 +42,13 @@ | :---------------------------------------- | :----------------------------------------------------------- | | JDK | JDK17 or above. Please refer to the downloads on [Oracle Official Website](https://www.oracle.com/java/technologies/downloads/) | | IoTDB |IoTDB v1.3.0 or above. Please refer to the [Deployment guidance](../Deployment-and-Maintenance/IoTDB-Package.md) | -| ThingsBoard
(IoTDB adapted version) | Please contact Timecho staff to obtain the installation package. Detailed installation steps are provided below. | +| ThingsBoard
(IoTDB adapted version) | Please contact commercial support to obtain the installation package. Detailed installation steps are provided below. | ## Installation Steps Please refer to the installation steps on [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/),wherein: -- [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/)【 Step 2: ThingsBoard Service Installation 】 Use the installation package provided by your Timecho contact to install the software. Please note that the official ThingsBoard installation package does not support IoTDB. +- [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/)【 Step 2: ThingsBoard Service Installation 】 Use the installation package provided by your contact to install the software. Please note that the official ThingsBoard installation package does not support IoTDB. - [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/) 【Step 3: Configure ThingsBoard Database - ThingsBoard Configuration】 In this step, you need to add environment variables according to the following content ```Shell diff --git a/src/UserGuide/dev-1.3/IoTDB-Introduction/IoTDB-Introduction_apache.md b/src/UserGuide/dev-1.3/IoTDB-Introduction/IoTDB-Introduction_apache.md index 4c782c02a..8f8ebdf84 100644 --- a/src/UserGuide/dev-1.3/IoTDB-Introduction/IoTDB-Introduction_apache.md +++ b/src/UserGuide/dev-1.3/IoTDB-Introduction/IoTDB-Introduction_apache.md @@ -35,7 +35,7 @@ Apache IoTDB is a low-cost, high-performance native temporal database for the In IoTDB products consist of several components that help users efficiently manage and analyze the massive amount of time-series data generated by the IoT.
- Introduction-en-timecho.png + Introduction-en-apache.png
diff --git a/src/UserGuide/dev-1.3/SQL-Manual/UDF-Libraries_apache.md b/src/UserGuide/dev-1.3/SQL-Manual/UDF-Libraries_apache.md index 5beb7791e..830b77c53 100644 --- a/src/UserGuide/dev-1.3/SQL-Manual/UDF-Libraries_apache.md +++ b/src/UserGuide/dev-1.3/SQL-Manual/UDF-Libraries_apache.md @@ -33,8 +33,8 @@ Based on the ability of user-defined functions, IoTDB provides a series of funct | UDF installation package | Supported IoTDB versions | Download link | | --------------- | ----------------- | ------------------------------------------------------------ | - | apache-UDF-1.3.3.zip | V1.3.3 and above |Please contact Timecho for assistance | - | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | Please contact Timecho for assistance| + | apache-UDF-1.3.3.zip | V1.3.3 and above |Please contact staff for assistance | + | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | Please contact staff for assistance| 2. Place the library-udf.jar file in the compressed file obtained in the directory `/ext/udf ` of all nodes in the IoTDB cluster 3. In the SQL operation interface of IoTDB's SQL command line terminal (CLI), execute the corresponding function registration statement as follows. diff --git a/src/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md b/src/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md index 956ec134e..aa38f1952 100644 --- a/src/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md +++ b/src/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md @@ -109,7 +109,7 @@ The following documents may help you have a good journey with Prometheus and Gra ## Apache IoTDB Dashboard -`Apache IoTDB Dashboard` is available as a supplement to TimechoDB, designed for unified centralized operations and management. With it, multiple clusters can be monitored through a single panel. You can access the Dashboard's Json file by contacting Commerce. +`Apache IoTDB Dashboard` is available as a supplement to IoTDB, designed for unified centralized operations and management. With it, multiple clusters can be monitored through a single panel. You can access the Dashboard's Json file by contacting Commerce. ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png) diff --git a/src/UserGuide/dev-1.3/User-Manual/Streaming_apache.md b/src/UserGuide/dev-1.3/User-Manual/Streaming_apache.md index 7f9b9716a..bfb49b91d 100644 --- a/src/UserGuide/dev-1.3/User-Manual/Streaming_apache.md +++ b/src/UserGuide/dev-1.3/User-Manual/Streaming_apache.md @@ -561,7 +561,7 @@ WITH SOURCE ( -- Default IoTDB Data Extraction Plugin 'source' = 'iotdb-source', -- Path prefix, only data that can match the path prefix will be extracted for subsequent processing and delivery - 'source.pattern' = 'root.timecho', + 'source.pattern' = 'root.iotdb', -- Whether to extract historical data 'source.history.enable' = 'true', -- Describes the time range of the historical data being extracted, indicating the earliest possible time diff --git a/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index b6059dded..ff02d4c38 100644 --- a/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -55,7 +55,7 @@ To ensure the AINode installation package you obtained is complete and correct, **Preparation:** -- Obtain the official SHA512 checksum: Please contact Timecho staff. +- Obtain the official SHA512 checksum: Please contact commercial support. **Verification Steps (using Linux as an example):** @@ -77,7 +77,7 @@ To ensure the AINode installation package you obtained is complete and correct, **Notes:** -- If the verification results do not match, please contact Timecho staff to obtain a new installation package. +- If the verification results do not match, please contact commercial support to obtain a new installation package. - If you encounter a "file not found" prompt during verification, check if the file path is correct or if the installation package was downloaded completely. ### 2.3 Environment Requirements @@ -116,7 +116,7 @@ AINode supports modifying some necessary parameters. You can find the following ### 3.3 Importing Built-in Weight Files *If the deployment environment has network connectivity and can access HuggingFace, the system will automatically pull the built-in model weight files. This step can be skipped.* -*For offline environments, contact Timecho staff to obtain the model weight folder and place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.* +*For offline environments, contact commercial support to obtain the model weight folder and place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.* **NOTE:** Pay attention to the directory hierarchy. The parent directory for all built-in model weights should be `builtin`. ### 3.4 Starting AINode @@ -228,7 +228,7 @@ If you need to upgrade the version of the current AINode, you can refer to the f 3. Update built-in model weights (optional) - * If the new version involves updates to built-in models, relevant information will be updated in the [Release History](../IoTDB-Introduction/Release-history_apache.md). You may contact Timecho staff to obtain the latest weight package and replace it in the `data/ainode/models/builtin` directory. + * If the new version involves updates to built-in models, relevant information will be updated in the [Release History](../IoTDB-Introduction/Release-history_apache.md). You may contact commercial support to obtain the latest weight package and replace it in the `data/ainode/models/builtin` directory. 4. After the upgrade is completed, you can start the AINode service and check the node status. For specific commands, refer to Sections 3.4 and 3.5. diff --git a/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md index 6299219da..785acb2d3 100644 --- a/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -69,7 +69,7 @@ To ensure the AINode installation package you obtained is complete and valid, we ``` 2. Execute the following command to calculate the hash value: ```Bash - sha512sum timechodb-{version}-ainode-bin.zip + sha512sum apache-iotdb-{version}-ainode-bin.zip ``` 3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name): @@ -129,7 +129,7 @@ AINode supports modifying some necessary parameters. You can find the following > Offline environment only (Online environments can skip this step) > -Contact Timecho team to obtain the model weight files, then place them in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory. +Contact commercial support to obtain the model weight files, then place them in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory. ### 3.4 Start AINode diff --git a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md index 8977215fc..998d4e6bf 100644 --- a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md +++ b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md @@ -72,11 +72,11 @@ 48core 1 2 - Please contact Timecho Business for consultation + Please contact commercial support for consultation Over 10000000 - Please contact Timecho Business for consultation + Please contact commercial support for consultation @@ -136,11 +136,11 @@ 128G 1 2 - Please contact Timecho Business for consultation + Please contact commercial support for consultation Over 10000000 - Please contact Timecho Business for consultation + Please contact commercial support for consultation diff --git a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Environment-Requirements.md b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Environment-Requirements.md index 85555c59d..833e7b9dc 100644 --- a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Environment-Requirements.md +++ b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Environment-Requirements.md @@ -80,7 +80,7 @@ IoTDB does not have strict operational requirements for disk array configuration ### 2.1 Version Requirements -IoTDB supports operating systems such as Linux, Windows, and MacOS. TimechoDB also supports Chinese CPUs like Loongson, Phytium, and Kunpeng, as well as Chinese operating systems like Kylin, UOS, and NingSi. +IoTDB supports operating systems such as Linux, Windows, and MacOS. IoTDB also supports Chinese CPUs like Loongson, Phytium, and Kunpeng, as well as Chinese operating systems like Kylin, UOS, and NingSi. ### 2.2 Hard Disk Partitioning diff --git a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md index e897012e0..0191a6a15 100644 --- a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md +++ b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md @@ -20,19 +20,19 @@ --> # Monitoring Panel Deployment -The monitoring panel is one of the supporting tools for TimechoDB. It aims to solve the monitoring problems of TimechoDB and its operating system, mainly including operating system resource monitoring, TimechoDB performance monitoring, and hundreds of kernel monitoring metrics, in order to help users monitor cluster health, optimize performance, and perform maintenance. This guide demonstrates how to enable the system monitoring module in a TimechoDB instance and visualize monitoring metrics using Prometheus + Grafana, using a typical 3C3D cluster (3 ConfigNodes and 3 DataNodes) as an example. +The monitoring panel is one of the supporting tools for IoTDB. It aims to solve the monitoring problems of IoTDB and its operating system, mainly including operating system resource monitoring, IoTDB performance monitoring, and hundreds of kernel monitoring metrics, in order to help users monitor cluster health, optimize performance, and perform maintenance. This guide demonstrates how to enable the system monitoring module in a IoTDB instance and visualize monitoring metrics using Prometheus + Grafana, using a typical 3C3D cluster (3 ConfigNodes and 3 DataNodes) as an example. ## 1. Installation Preparation -1. Installing TimechoDB: Install TimechoDB V1.0 or above. Contact sales or technical support to obtain the installation package. +1. Installing IoTDB: Install IoTDB V1.0 or above. Contact sales or technical support to obtain the installation package. -2. Obtain the monitoring panel installation package: The monitoring panel is exclusive to the enterprise-grade TimechoDB. Contact sales or technical support to obtain it. +2. Obtain the monitoring panel installation package: The monitoring panel is exclusive to the enterprise-grade IoTDB. Contact sales or technical support to obtain it. ## 2. Installation Steps -### 2.1 Enable Monitoring Metrics Collection in TimechoDB +### 2.1 Enable Monitoring Metrics Collection in IoTDB -1. Enable related configuration options. The configuration options related to monitoring in TimechoDB are disabled by default. Before deploying the monitoring panel, you need to enable certain configuration options (note that the service needs to be restarted after enabling monitoring configuration). +1. Enable related configuration options. The configuration options related to monitoring in IoTDB are disabled by default. Before deploying the monitoring panel, you need to enable certain configuration options (note that the service needs to be restarted after enabling monitoring configuration). | **Configuration** | **Configuration File** | **Description** | | :--------------------------------- | :------------------------------- | :----------------------------------------------------------- | diff --git a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md index 08d42beba..9228cbb3e 100644 --- a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md +++ b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md @@ -20,7 +20,7 @@ --> # Stand-Alone Deployment -This guide introduces how to set up a standalone TimechoDB instance, which includes one ConfigNode and one DataNode (commonly referred to as 1C1D). +This guide introduces how to set up a standalone IoTDB instance, which includes one ConfigNode and one DataNode (commonly referred to as 1C1D). ## 1. Prerequisites diff --git a/src/UserGuide/latest-Table/Ecosystem-Integration/DataGrip.md b/src/UserGuide/latest-Table/Ecosystem-Integration/DataGrip.md index 5e8b37104..ad816b304 100644 --- a/src/UserGuide/latest-Table/Ecosystem-Integration/DataGrip.md +++ b/src/UserGuide/latest-Table/Ecosystem-Integration/DataGrip.md @@ -43,9 +43,9 @@ Ensure DataGrip and IoTDB are installed: Select the appropriate version of the JAR package (choose the `jar-with-dependencies.jar` variant): -- Option 1: https://repo1.maven.org/maven2/com/timecho/iotdb/iotdb-jdbc/2.0.3.3/iotdb-jdbc-2.0.3.3-jar-with-dependencies.jar +- Option 1: https://repo1.maven.org/maven2/org/apache/iotdb/iotdb-jdbc/2.0.3/iotdb-jdbc-2.0.3-jar-with-dependencies.jar -- Option 2: https://repo1.maven.org/maven2/com/timecho/iotdb/iotdb-jdbc/2.0.3.3/ +- Option 2: https://repo1.maven.org/maven2/org/apache/iotdb/iotdb-jdbc/2.0.3/ ![](/img/datagrip-2.png) diff --git a/src/UserGuide/latest-Table/QuickStart/QuickStart_apache.md b/src/UserGuide/latest-Table/QuickStart/QuickStart_apache.md index 1fbf7213c..84ad616f5 100644 --- a/src/UserGuide/latest-Table/QuickStart/QuickStart_apache.md +++ b/src/UserGuide/latest-Table/QuickStart/QuickStart_apache.md @@ -31,7 +31,7 @@ This guide will assist you in quickly installing and deploying IoTDB. You can qu 2. Complete system configuration preparations: IoTDB's system configuration involves multiple aspects. For an introduction to key system configurations, please see [System Requirements](../Deployment-and-Maintenance/Environment-Requirements.md) -3. Obtain the installation package: You can obtain the IoTDB installation package on the [Apache IoTDB official website](https://iotdb.apache.org/zh/Download/).For the specific structure of the installation package, please refer to[Obtain TimechoDB](../Deployment-and-Maintenance/IoTDB-Package_apache.md) +3. Obtain the installation package: You can obtain the IoTDB installation package on the [Apache IoTDB official website](https://iotdb.apache.org/zh/Download/).For the specific structure of the installation package, please refer to[Obtain IoTDB](../Deployment-and-Maintenance/IoTDB-Package_apache.md) 4. Install the database and activate it: Depending on your actual deployment architecture, you can choose from the following tutorials for installation and deployment: diff --git a/src/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md b/src/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md index 5b710f5ef..71126139a 100644 --- a/src/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md +++ b/src/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md @@ -98,7 +98,7 @@ For more details, refer to the following documents: ## 4. Apache IoTDB Dashboard -The `Apache IoTDB Dashboard` is a companion product of TimechoDB, supporting unified centralized operation and maintenance management. It allows monitoring multiple clusters through a single monitoring panel. You can contact the business team to obtain the Dashboard's JSON file. +The `Apache IoTDB Dashboard` is a companion product of IoTDB, supporting unified centralized operation and maintenance management. It allows monitoring multiple clusters through a single monitoring panel. You can contact the business team to obtain the Dashboard's JSON file. ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png) diff --git a/src/UserGuide/latest-Table/User-Manual/Load-Balance.md b/src/UserGuide/latest-Table/User-Manual/Load-Balance.md index 8514dcf55..05ea8d075 100644 --- a/src/UserGuide/latest-Table/User-Manual/Load-Balance.md +++ b/src/UserGuide/latest-Table/User-Manual/Load-Balance.md @@ -137,18 +137,18 @@ echo "192.168.1.3 iotdb-1" >> /etc/hosts #### 1.3.2 Scaling Operation -1. To ensure the TimechoDB installation package you obtained is complete and correct, it is recommended to perform an SHA512 checksum before installation and deployment. +1. To ensure the IoTDB installation package you obtained is complete and correct, it is recommended to perform an SHA512 checksum before installation and deployment. 2. Unzip the installation package and enter the installation directory. ``` -unzip timechodb-{version}-bin.zip -cd timechodb-{version}-bin +unzip apache-iotdb-{version}-bin.zip +cd apache-iotdb-{version}-bin ``` 3. Modify the relevant configuration. ``` -cd timechodb-{version}-bin/conf +cd apache-iotdb-{version}-bin/conf vim iotdb-system.properties ``` @@ -175,10 +175,10 @@ Navigate to the `sbin`directory under IoTDB and start the datanode: ``` # Linux or macOS - ./timechodb-{version}-bin/sbin/start-cli.sh + ./apache-iotdb-{version}-bin/sbin/start-cli.sh # Windows - .\timechodb-{version}-bin\sbin\start-cli.bat + .\apache-iotdb-{version}-bin\sbin\start-cli.bat ``` 6. Execute commands for verification. diff --git a/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_apache.md b/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_apache.md index b6094310f..2c4bd4f20 100644 --- a/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_apache.md +++ b/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_apache.md @@ -7,9 +7,9 @@ to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at - + http://www.apache.org/licenses/LICENSE-2.0 - + Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY @@ -625,7 +625,7 @@ setConfigurationStatement propertyAssignments : property (',' property)* ; - + property : identifier EQ propertyValue ; @@ -662,7 +662,7 @@ IoTDB> SET CONFIGURATION disk_space_warning_threshold='0.05',heartbeat_interval_ loadConfigurationStatement : LOAD CONFIGURATION localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -692,8 +692,8 @@ IoTDB> LOAD CONFIGURATION ON LOCAL; ```SQL setSystemStatusStatement : SET SYSTEM TO (READONLY | RUNNING) localOrClusterMode? - ; - + ; + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -771,7 +771,7 @@ IoTDB> FLUSH test_db TRUE ON LOCAL; startRepairDataStatement : START REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -800,7 +800,7 @@ IoTDB> START REPAIR DATA ON CLUSTER; stopRepairDataStatement : STOP REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -881,18 +881,18 @@ DEBUG SELECT * FROM table3; 2. Check the log content in `log_datanode_query_debug.log` to view the file scan information involved in the query. ```bash -2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2864/1769139940009-1-0-0.tsfile is not satisfied because of no device! -2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2865/1769139940010-1-0-0.tsfile is not satisfied because of no device! -2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: table3.d1. in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile -2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: table3.d1, all sensors: [, temperature] -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1. metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=-128, chunkMetaDataListDataSize=8, measurementId='', dataType=VECTOR, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2, modified=false, isSeq=true, chunkMetadataList=[measurementId: , datatype: VECTOR, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2, deleteIntervalList: null]}. -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1.temperature metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=64, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=FLOAT, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: FLOAT, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], deleteIntervalList: null]}. -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:110 - Modifications size is 1 for file Path: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:114 - [] -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:125 - After modification Chunk meta data list is: -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:126 - org.apache.tsfile.file.metadata.TableDeviceChunkMetadata@2e11291f -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=19} -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=46} +2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2864/1769139940009-1-0-0.tsfile is not satisfied because of no device! +2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2865/1769139940010-1-0-0.tsfile is not satisfied because of no device! +2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: table3.d1. in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile +2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: table3.d1, all sensors: [, temperature] +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1. metadata in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=-128, chunkMetaDataListDataSize=8, measurementId='', dataType=VECTOR, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2, modified=false, isSeq=true, chunkMetadataList=[measurementId: , datatype: VECTOR, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2, deleteIntervalList: null]}. +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1.temperature metadata in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=64, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=FLOAT, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: FLOAT, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], deleteIntervalList: null]}. +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:110 - Modifications size is 1 for file Path: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:114 - [] +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:125 - After modification Chunk meta data list is: +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:126 - org.apache.tsfile.file.metadata.TableDeviceChunkMetadata@2e11291f +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=19} +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=46} 2026-03-24 10:10:41,519 [pool-69-IoTDB-ClientRPC-Processor-1$20260324_021041_00068_1] INFO o.a.i.d.q.p.Coordinator:902 - debug select * from table3 ``` diff --git a/src/UserGuide/latest-Table/User-Manual/Query-Performance-Analysis.md b/src/UserGuide/latest-Table/User-Manual/Query-Performance-Analysis.md index 4a693599a..17c0259f0 100644 --- a/src/UserGuide/latest-Table/User-Manual/Query-Performance-Analysis.md +++ b/src/UserGuide/latest-Table/User-Manual/Query-Performance-Analysis.md @@ -30,7 +30,7 @@ Query analysis helps users understand query execution mechanisms and identify pe | **Method** | **Installation Difficulty** | **Business Impact** | **Functional Scope** | | :----------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- | | **EXPLAIN ANALYZE** | **Low.** No additional components required; built-in SQL statement in IoTDB. | **Low.** Impacts only the analyzed query, with no effect on other workloads. | **Supports cluster systems.** Enables tracing for a single SQL query. | -| **Monitoring Dashboard** | **Medium.** Requires installation of IoTDB monitoring dashboard tool (TimechoDB) and enabling monitoring services. | **Medium.** Metrics collection introduces additional overhead. | **Supports cluster systems.** Analyzes overall database query load and latency. | +| **Monitoring Dashboard** | **Medium.** Requires installation of IoTDB monitoring dashboard tool (IoTDB) and enabling monitoring services. | **Medium.** Metrics collection introduces additional overhead. | **Supports cluster systems.** Analyzes overall database query load and latency. | | **Arthas Sampling** | **Medium.** Requires Java Arthas installation (may be restricted in internal networks; sometimes requires application restart). | **High.** May degrade response speed of online services due to CPU sampling. | **Does n****ot supports cluster systems.** Analyzes overall database query load and latency. | diff --git a/src/UserGuide/latest/Background-knowledge/Data-Type.md b/src/UserGuide/latest/Background-knowledge/Data-Type.md index 0be198c62..965dfe525 100644 --- a/src/UserGuide/latest/Background-knowledge/Data-Type.md +++ b/src/UserGuide/latest/Background-knowledge/Data-Type.md @@ -40,7 +40,7 @@ The difference between STRING and TEXT types is that STRING type has more statis ### 1.1 Float Precision -The time series of **FLOAT** and **DOUBLE** type can specify (MAX\_POINT\_NUMBER, see [this page](../SQL-Manual/SQL-Manual_timecho) for more information on how to specify), which is the number of digits after the decimal point of the floating point number, if the encoding method is [RLE](../Technical-Insider/Encoding-and-Compression.md) or [TS\_2DIFF](../Technical-Insider/Encoding-and-Compression.md). If MAX\_POINT\_NUMBER is not specified, the system will use [float\_precision](../Reference/DataNode-Config-Manual.md) in the configuration file `iotdb-system.properties`. +The time series of **FLOAT** and **DOUBLE** type can specify (MAX\_POINT\_NUMBER, see [this page](../SQL-Manual/SQL-Manual_apache) for more information on how to specify), which is the number of digits after the decimal point of the floating point number, if the encoding method is [RLE](../Technical-Insider/Encoding-and-Compression.md) or [TS\_2DIFF](../Technical-Insider/Encoding-and-Compression.md). If MAX\_POINT\_NUMBER is not specified, the system will use [float\_precision](../Reference/DataNode-Config-Manual.md) in the configuration file `iotdb-system.properties`. ```sql CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=FLOAT, ENCODING=RLE, 'MAX_POINT_NUMBER'='2'; diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index 104323a6a..5041947c3 100644 --- a/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -55,7 +55,7 @@ To ensure the AINode installation package you obtained is complete and correct, **Preparation:** -- Obtain the official SHA512 checksum: Please contact Timecho staff. +- Obtain the official SHA512 checksum: Please contact commercial support. **Verification Steps (using Linux as an example):** @@ -77,7 +77,7 @@ To ensure the AINode installation package you obtained is complete and correct, **Notes:** -- If the verification results do not match, please contact Timecho staff to obtain a new installation package. +- If the verification results do not match, please contact commercial support to obtain a new installation package. - If you encounter a "file not found" prompt during verification, check if the file path is correct or if the installation package was downloaded completely. ### 2.3 Environment Requirements @@ -116,7 +116,7 @@ AINode supports modifying some necessary parameters. You can find the following ### 3.3 Importing Built-in Weight Files *If the deployment environment has network connectivity and can access HuggingFace, the system will automatically pull the built-in model weight files. This step can be skipped.* -*For offline environments, contact Timecho staff to obtain the model weight folder and place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.* +*For offline environments, contact commercial support to obtain the model weight folder and place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.* **NOTE:** Pay attention to the directory hierarchy. The parent directory for all built-in model weights should be `builtin`. ### 3.4 Starting AINode @@ -228,7 +228,7 @@ If you need to upgrade the version of the current AINode, you can refer to the f 3. Update built-in model weights (optional) - * If the new version involves updates to built-in models, relevant information will be updated in the [Release History](../IoTDB-Introduction/Release-history_apache.md). You may contact Timecho staff to obtain the latest weight package and replace it in the `data/ainode/models/builtin` directory. + * If the new version involves updates to built-in models, relevant information will be updated in the [Release History](../IoTDB-Introduction/Release-history_apache.md). You may contact commercial support to obtain the latest weight package and replace it in the `data/ainode/models/builtin` directory. 4. After the upgrade is completed, you can start the AINode service and check the node status. For specific commands, refer to Sections 3.4 and 3.5. diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md index 6d38c04dc..e9fdac335 100644 --- a/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -69,7 +69,7 @@ To ensure the AINode installation package you obtained is complete and valid, we ``` 2. Execute the following command to calculate the hash value: ```Bash - sha512sum timechodb-{version}-ainode-bin.zip + sha512sum apache-iotdb-{version}-ainode-bin.zip ``` 3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name): @@ -129,7 +129,7 @@ AINode supports modifying some necessary parameters. You can find the following > Offline environment only (Online environments can skip this step) > - Contact Timecho team to obtain the model weight files, then place them in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory. + Contact commercial support to obtain the model weight files, then place them in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory. ### 3.4 Start AINode diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md index be7631998..5752268ff 100644 --- a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -205,7 +205,7 @@ You can use the `show cluster` command to view cluster information: ![](/img/%E5%BC%80%E6%BA%90%E7%89%88%20show%20cluter.png) -> The appearance of `ACTIVATED (W)` indicates passive activation, which means that this Configurable Node does not have a license file (or has not issued the latest license file with a timestamp), and its activation depends on other Activated Configurable Nodes in the cluster. At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply. +> The appearance of `ACTIVATED (W)` indicates passive activation, which means that this Configurable Node does not have a license file (or has not issued the latest license file with a timestamp), and its activation depends on other Activated Configurable Nodes in the cluster. At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact commercial support to reapply. ### 3.6 One-click Cluster Start and Stop @@ -476,7 +476,7 @@ For more details on cluster maintenance, please refer to: [Cluster Maintenance]( Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified. - Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions. + Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact commercial support for consultation on solutions. Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart. diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/Database-Resources.md b/src/UserGuide/latest/Deployment-and-Maintenance/Database-Resources.md index 706343fda..4f6ebf7dc 100644 --- a/src/UserGuide/latest/Deployment-and-Maintenance/Database-Resources.md +++ b/src/UserGuide/latest/Deployment-and-Maintenance/Database-Resources.md @@ -72,11 +72,11 @@ 48core 1 2 - Please contact Timecho Business for consultation + Please contact commercial support for consultation Over 10000000 - Please contact Timecho Business for consultation + Please contact commercial support for consultation @@ -136,11 +136,11 @@ 128G 1 2 - Please contact Timecho Business for consultation + Please contact commercial support for consultation Over 10000000 - Please contact Timecho Business for consultation + Please contact commercial support for consultation diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md index ea940bc34..e2bb1d519 100644 --- a/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md +++ b/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md @@ -173,7 +173,7 @@ When the status is all running, it indicates that the service has started succes ![](/img/%E5%BC%80%E6%BA%90-%E5%8D%95%E6%9C%BAshow.jpeg) -> The appearance of 'Activated (W)' indicates passive activation, indicating that this Config Node does not have a license file (or has not issued the latest license file with a timestamp). At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply. +> The appearance of 'Activated (W)' indicates passive activation, indicating that this Config Node does not have a license file (or has not issued the latest license file with a timestamp). At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact commercial support to reapply. ## 3. Common Questions @@ -181,7 +181,7 @@ When the status is all running, it indicates that the service has started succes Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified. - Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions. + Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact commercial support for consultation on solutions. Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart. diff --git a/src/UserGuide/latest/Ecosystem-Integration/DataEase.md b/src/UserGuide/latest/Ecosystem-Integration/DataEase.md index ddfbb62ce..9a22a1bf4 100644 --- a/src/UserGuide/latest/Ecosystem-Integration/DataEase.md +++ b/src/UserGuide/latest/Ecosystem-Integration/DataEase.md @@ -41,14 +41,14 @@ | **Preparation Content** | **Version Requirements** | | :-------------------- | :----------------------------------------------------------- | -| IoTDB | Version not required, please refer to [Deployment Guidance](https://www.timecho-global.com/docs/UserGuide/latest/Deployment-and-Maintenance/IoTDB-Package_timecho.html) | +| IoTDB | Version not required, please refer to [Deployment Guidance](../QuickStart/QuickStart_apache.md) | | JDK | Requires JDK 11 or higher (JDK 17 or above is recommended for optimal performance) | -| DataEase | Requires v1 series v1.18 version, please refer to the official [DataEase Installation Guide](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)(V2.x is currently not supported. For integration with other versions, please contact Timecho) | -| DataEase-IoTDB Connector | Please contact Timecho for assistance | +| DataEase | Requires v1 series v1.18 version, please refer to the official [DataEase Installation Guide](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)(V2.x is currently not supported. For integration with other versions, please contact staff) | +| DataEase-IoTDB Connector | Please contact staff for assistance | ## 3. Installation Steps -Step 1: Please contact Timecho to obtain the file and unzip the installation package `iotdb-api-source-1.0.0.zip` +Step 1: Please contact staff to obtain the file and unzip the installation package `iotdb-api-source-1.0.0.zip` Step 2: After extracting the files, modify the `application.properties` configuration file in the `config` folder diff --git a/src/UserGuide/latest/Ecosystem-Integration/Thingsboard.md b/src/UserGuide/latest/Ecosystem-Integration/Thingsboard.md index f304c277f..adb1f172e 100644 --- a/src/UserGuide/latest/Ecosystem-Integration/Thingsboard.md +++ b/src/UserGuide/latest/Ecosystem-Integration/Thingsboard.md @@ -42,13 +42,13 @@ | :---------------------------------------- | :----------------------------------------------------------- | | JDK | JDK17 or above. Please refer to the downloads on [Oracle Official Website](https://www.oracle.com/java/technologies/downloads/) | | IoTDB |IoTDB v1.3.0 or above. Please refer to the [Deployment guidance](../Deployment-and-Maintenance/IoTDB-Package.md) | -| ThingsBoard
(IoTDB adapted version) | Please contact Timecho staff to obtain the installation package. Detailed installation steps are provided below. | +| ThingsBoard
(IoTDB adapted version) | Please contact commercial support to obtain the installation package. Detailed installation steps are provided below. | ## 3. Installation Steps Please refer to the installation steps on [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/),wherein: -- [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/)【 Step 2: ThingsBoard Service Installation 】 Use the installation package provided by your Timecho contact to install the software. Please note that the official ThingsBoard installation package does not support IoTDB. +- [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/)【 Step 2: ThingsBoard Service Installation 】 Use the installation package provided by your contact to install the software. Please note that the official ThingsBoard installation package does not support IoTDB. - [ThingsBoard Official Website](https://thingsboard.io/docs/user-guide/install/ubuntu/) 【Step 3: Configure ThingsBoard Database - ThingsBoard Configuration】 In this step, you need to add environment variables according to the following content ```Shell diff --git a/src/UserGuide/latest/QuickStart/QuickStart_apache.md b/src/UserGuide/latest/QuickStart/QuickStart_apache.md index ec7bee5ff..8489bfb84 100644 --- a/src/UserGuide/latest/QuickStart/QuickStart_apache.md +++ b/src/UserGuide/latest/QuickStart/QuickStart_apache.md @@ -32,7 +32,7 @@ This guide will assist you in quickly installing and deploying IoTDB. You can qu 2. Complete system configuration preparations: IoTDB's system configuration involves multiple aspects. For an introduction to key system configurations, please see [System Requirements](../Deployment-and-Maintenance/Environment-Requirements.md) -3. Obtain the installation package: You can obtain the IoTDB installation package on the [Apache IoTDB official website](https://iotdb.apache.org/zh/Download/).For the specific structure of the installation package, please refer to[Obtain TimechoDB](../Deployment-and-Maintenance/IoTDB-Package_apache.md) +3. Obtain the installation package: You can obtain the IoTDB installation package on the [Apache IoTDB official website](https://iotdb.apache.org/zh/Download/).For the specific structure of the installation package, please refer to[Obtain IoTDB](../Deployment-and-Maintenance/IoTDB-Package_apache.md) 4. Install the database and activate it: Depending on your actual deployment architecture, you can choose from the following tutorials for installation and deployment: diff --git a/src/UserGuide/latest/SQL-Manual/UDF-Libraries_apache.md b/src/UserGuide/latest/SQL-Manual/UDF-Libraries_apache.md index 806a1375f..cca59fca3 100644 --- a/src/UserGuide/latest/SQL-Manual/UDF-Libraries_apache.md +++ b/src/UserGuide/latest/SQL-Manual/UDF-Libraries_apache.md @@ -31,8 +31,8 @@ Based on the ability of user-defined functions, IoTDB provides a series of funct | UDF installation package | Supported IoTDB versions | Download link | | --------------- | ----------------- | ------------------------------------------------------------ | - | apache-UDF-1.3.3.zip | V1.3.3 and above |Please contact Timecho for assistance | - | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | Please contact Timecho for assistance| + | apache-UDF-1.3.3.zip | V1.3.3 and above |Please contact staff for assistance | + | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | Please contact staff for assistance| 2. Place the library-udf.jar file in the compressed file obtained in the directory `/ext/udf ` of all nodes in the IoTDB cluster 3. In the SQL operation interface of IoTDB's SQL command line terminal (CLI), execute the corresponding function registration statement as follows. diff --git a/src/UserGuide/latest/Tools-System/Monitor-Tool_apache.md b/src/UserGuide/latest/Tools-System/Monitor-Tool_apache.md index afcb22c0f..d4ed0675b 100644 --- a/src/UserGuide/latest/Tools-System/Monitor-Tool_apache.md +++ b/src/UserGuide/latest/Tools-System/Monitor-Tool_apache.md @@ -109,7 +109,7 @@ The following documents may help you have a good journey with Prometheus and Gra ## 2. Apache IoTDB Dashboard -`Apache IoTDB Dashboard` is available as a supplement to TimechoDB, designed for unified centralized operations and management. With it, multiple clusters can be monitored through a single panel. You can access the Dashboard's Json file by contacting Commerce. +`Apache IoTDB Dashboard` is available as a supplement to IoTDB, designed for unified centralized operations and management. With it, multiple clusters can be monitored through a single panel. You can access the Dashboard's Json file by contacting Commerce. ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png) diff --git a/src/UserGuide/latest/User-Manual/Load-Balance.md b/src/UserGuide/latest/User-Manual/Load-Balance.md index e34001346..5af690a8c 100644 --- a/src/UserGuide/latest/User-Manual/Load-Balance.md +++ b/src/UserGuide/latest/User-Manual/Load-Balance.md @@ -137,18 +137,18 @@ echo "192.168.1.3 iotdb-1" >> /etc/hosts #### 1.3.2 Scaling Operation -1. To ensure the TimechoDB installation package you obtained is complete and correct, it is recommended to perform an SHA512 checksum before installation and deployment. +1. To ensure the IoTDB installation package you obtained is complete and correct, it is recommended to perform an SHA512 checksum before installation and deployment. 2. Unzip the installation package and enter the installation directory. ``` -unzip timechodb-{version}-bin.zip -cd timechodb-{version}-bin +unzip apache-iotdb-{version}-bin.zip +cd apache-iotdb-{version}-bin ``` 3. Modify the relevant configuration. ``` -cd timechodb-{version}-bin/conf +cd apache-iotdb-{version}-bin/conf vim iotdb-system.properties ``` @@ -175,10 +175,10 @@ Navigate to the `sbin`directory under IoTDB and start the datanode: ``` # Linux or macOS - ./timechodb-{version}-bin/sbin/start-cli.sh + ./apache-iotdb-{version}-bin/sbin/start-cli.sh # Windows - .\timechodb-{version}-bin\sbin\start-cli.bat + .\apache-iotdb-{version}-bin\sbin\start-cli.bat ``` 6. Execute commands for verification. diff --git a/src/UserGuide/latest/User-Manual/Maintenance-commands_apache.md b/src/UserGuide/latest/User-Manual/Maintenance-commands_apache.md index c3ba550bc..dc4a4764e 100644 --- a/src/UserGuide/latest/User-Manual/Maintenance-commands_apache.md +++ b/src/UserGuide/latest/User-Manual/Maintenance-commands_apache.md @@ -7,9 +7,9 @@ to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at - + http://www.apache.org/licenses/LICENSE-2.0 - + Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY @@ -199,7 +199,7 @@ showQueriesStatement **Example**: ```SQL -IoTDB> SHOW QUERIES WHERE elapsedtime > 0.003 +IoTDB> SHOW QUERIES WHERE elapsedtime > 0.003 ``` **Result**: @@ -312,7 +312,7 @@ Execution result: #### Syntax: ```sql showDiskUsageStatement - : SHOW DISK_USAGE FROM pathPattern + : SHOW DISK_USAGE FROM pathPattern whereClause? orderByClause? rowPaginationClause? @@ -391,7 +391,7 @@ setConfigurationStatement propertyAssignments : property (',' property)* ; - + property : identifier EQ propertyValue ; @@ -428,7 +428,7 @@ IoTDB> SET CONFIGURATION ‘disk_space_warning_threshold’='0.05',‘heartbeat_ loadConfigurationStatement : LOAD CONFIGURATION localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -458,8 +458,8 @@ IoTDB> LOAD CONFIGURATION ON LOCAL; ```SQL setSystemStatusStatement : SET SYSTEM TO (READONLY | RUNNING) localOrClusterMode? - ; - + ; + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -537,7 +537,7 @@ IoTDB> FLUSH root.ln TRUE ON LOCAL; startRepairDataStatement : START REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -566,7 +566,7 @@ IoTDB> START REPAIR DATA ON CLUSTER; stopRepairDataStatement : STOP REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -648,13 +648,13 @@ DEBUG SELECT * FROM root.ln.**; 2. Check the log content in `log_datanode_query_debug.log` to view the file scan information involved in the query. ```bash -2026-03-24 10:06:18,755 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: root.ln.wf01.wt01.temperature in file: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile -2026-03-24 10:06:18,757 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: root.ln.wf01.wt01, all sensors: [temperature] -2026-03-24 10:06:18,758 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: root.ln.wf01.wt01.temperature metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=0, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=DOUBLE, statistics=startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null]}. -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:97 - Modifications size is 0 for file Path: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:109 - After modification Chunk meta data list is: -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:110 - measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null -2026-03-24 10:06:18,760 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile', regionId=13, timePartitionId=2932, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=27} +2026-03-24 10:06:18,755 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: root.ln.wf01.wt01.temperature in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile +2026-03-24 10:06:18,757 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: root.ln.wf01.wt01, all sensors: [temperature] +2026-03-24 10:06:18,758 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: root.ln.wf01.wt01.temperature metadata in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=0, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=DOUBLE, statistics=startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null]}. +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:97 - Modifications size is 0 for file Path: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:109 - After modification Chunk meta data list is: +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:110 - measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null +2026-03-24 10:06:18,760 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile', regionId=13, timePartitionId=2932, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=27} 2026-03-24 10:06:18,761 [pool-69-IoTDB-ClientRPC-Processor-1$20260324_020618_00052_1] INFO o.a.i.d.q.p.Coordinator:902 - debug select * from root.ln.** ``` diff --git a/src/UserGuide/latest/User-Manual/Streaming_apache.md b/src/UserGuide/latest/User-Manual/Streaming_apache.md index b5a8e2419..586dcbb62 100644 --- a/src/UserGuide/latest/User-Manual/Streaming_apache.md +++ b/src/UserGuide/latest/User-Manual/Streaming_apache.md @@ -561,7 +561,7 @@ WITH SOURCE ( -- Default IoTDB Data Extraction Plugin 'source' = 'iotdb-source', -- Path prefix, only data that can match the path prefix will be extracted for subsequent processing and delivery - 'source.pattern' = 'root.timecho', + 'source.pattern' = 'root.iotdb', -- Whether to extract historical data 'source.history.enable' = 'true', -- Describes the time range of the historical data being extracted, indicating the earliest possible time diff --git a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index 5c3990aa5..b09ef486d 100644 --- a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -55,7 +55,7 @@ AINode 安装包（`apache-iotdb--ainode-bin.zip`）解压后关键目 **准备工作：** -* 获取官方发布的 SHA512 校验码：请联系天谋工作人员获取 +* 获取官方发布的 SHA512 校验码：请联系商业支持获取 **校验步骤（以 linux 为例）：** @@ -79,7 +79,7 @@ b39039a1235a86bc3ce3df0a102efa215e281b5839683ccaf47883b390af4e686f99e6980a24a9d4 **注意事项：** -* 若校验结果不一致，请联系天谋工作人员重新获取安装包 +* 若校验结果不一致，请联系商业支持重新获取安装包 * 校验过程中若出现"文件不存在"提示，需检查文件路径是否正确或安装包是否完整下载 ### 2.3 环境要求 @@ -119,7 +119,7 @@ AINode 支持修改一些必要的参数。可以在 `/IOTDB_AINODE_HOME/conf/io 若部署环境可联网且能连通 HuggingFace 环境，系统会自动拉取内置模型权重文件，可忽略本步骤。 -若为离线环境，联系天谋工作人员获取模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。 +若为离线环境，联系商业支持获取模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。 **​NOTE：​**注意目录层级，最终所有内置模型权重的父目录都是 `builtin `。 @@ -231,7 +231,7 @@ IoTDB> show cluster * 备份 conf 目录下已修改的配置文件，然后替换 conf 文件夹，并将修改的配置同步到对应位置 3. 更新内置模型权重（可选） - * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。可联系天谋工作人员获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 + * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。可联系商业支持获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 4. 升级完毕后，可启动 AINode 服务，并查看节点状态，具体命令可参考【3.4】和【3.5】小节。 diff --git a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md index 7bf8a380f..5badae7a5 100644 --- a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -67,7 +67,7 @@ AINode 安装包（`apache-iotdb--ainode-bin.zip`），安装包解压 ``` 2. 执行以下命令计算哈希值： ```Bash - sha512sum timechodb-{version}-ainode-bin.zip + sha512sum apache-iotdb-{version}-ainode-bin.zip ``` 3. 终端输出结果（左侧为SHA512 校验码，右侧为文件名）： @@ -127,7 +127,7 @@ AINode 支持修改一些必要的参数。可以在 `conf/iotdb-ainode.properti > 仅离线环境，在线环境可忽略本步骤 > -联系天谋工作人员获取模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。 +联系商业支持获取模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。 ### 3.4 启动 AINode diff --git a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md index ff0b4d6b6..e5f0a1142 100644 --- a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -418,7 +418,7 @@ remove datanode [datanode_id] 1. Confignode节点启动失败 - 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。 - - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。 + - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。 - 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。 - 清理环境： diff --git a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md index 2766e74a6..c1b64662a 100644 --- a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md +++ b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md @@ -73,11 +73,11 @@ 48核 1 2 - 请联系天谋商务咨询 + 请联系商业支持咨询 1000w以上 - 请联系天谋商务咨询 + 请联系商业支持咨询 @@ -137,11 +137,11 @@ 128G 1 2 - 请联系天谋商务咨询 + 请联系商业支持咨询 1000w以上 - 请联系天谋商务咨询 + 请联系商业支持咨询 diff --git a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md index 786ba6216..05bde1d94 100644 --- a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md +++ b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md @@ -163,7 +163,7 @@ DataNode 配置 1. Confignode节点启动失败 - 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。 - - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。 + - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。 - 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。 - 清理环境： 1. 结束所有 ConfigNode 和 DataNode 进程。 diff --git a/src/zh/UserGuide/Master/Table/Ecosystem-Integration/DataGrip.md b/src/zh/UserGuide/Master/Table/Ecosystem-Integration/DataGrip.md index 7909ceb2f..1dd89e97d 100644 --- a/src/zh/UserGuide/Master/Table/Ecosystem-Integration/DataGrip.md +++ b/src/zh/UserGuide/Master/Table/Ecosystem-Integration/DataGrip.md @@ -43,9 +43,9 @@ IoTDB 通过 JDBC 接口与 DataGrip 集成，支持像管理文件夹一样通 选择对应版本的 jar 包，下载后缀 `jar-with-dependencies.jar` 的包： -- 链接 1：https://repo1.maven.org/maven2/com/timecho/iotdb/iotdb-jdbc/2.0.3.3/iotdb-jdbc-2.0.3.3-jar-with-dependencies.jar +- 链接 1：https://repo1.maven.org/maven2/org/apache/iotdb/iotdb-jdbc/2.0.3/iotdb-jdbc-2.0.3-jar-with-dependencies.jar -- 链接 2：https://repo1.maven.org/maven2/com/timecho/iotdb/iotdb-jdbc/2.0.3.3/ +- 链接 2：https://repo1.maven.org/maven2/org/apache/iotdb/iotdb-jdbc/2.0.3/ ![](/img/datagrip-2.png) diff --git a/src/zh/UserGuide/Master/Table/SQL-Manual/Nested-Queries.md b/src/zh/UserGuide/Master/Table/SQL-Manual/Nested-Queries.md index 093a6f8d7..2422c5d75 100644 --- a/src/zh/UserGuide/Master/Table/SQL-Manual/Nested-Queries.md +++ b/src/zh/UserGuide/Master/Table/SQL-Manual/Nested-Queries.md @@ -970,7 +970,7 @@ IoTDB> SELECT s1 <= **示例：** -* 多设备降采样对齐查询，详细示例可见：[示例](../Basic-Concept/Query-Data_timecho.md#_3-6-多设备降采样对齐查询) +* 多设备降采样对齐查询，详细示例可见：[示例](../Basic-Concept/Query-Data_apache.md#_3-6-多设备降采样对齐查询) ### 4.5 关联标量子查询 diff --git a/src/zh/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md b/src/zh/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md index 262849879..652690200 100644 --- a/src/zh/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md +++ b/src/zh/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md @@ -104,7 +104,7 @@ static_configs: ## 4. Apache IoTDB Dashboard -`Apache IoTDB Dashboard`是 TimechoDB 的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。 +`Apache IoTDB Dashboard`是 IoTDB 的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。 ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png) diff --git a/src/zh/UserGuide/Master/Table/User-Manual/Load-Balance.md b/src/zh/UserGuide/Master/Table/User-Manual/Load-Balance.md index 7fe0a8e6c..f54905e0e 100644 --- a/src/zh/UserGuide/Master/Table/User-Manual/Load-Balance.md +++ b/src/zh/UserGuide/Master/Table/User-Manual/Load-Balance.md @@ -133,18 +133,18 @@ echo "192.168.1.3 iotdb-1" >> /etc/hosts ``` #### 1.3.2 扩容操作 -1. 为确保您获取的 TimechoDB 安装包完整且正确，在执行安装部署前建议您进行 SHA512 校验。 +1. 为确保您获取的 IoTDB 安装包完整且正确，在执行安装部署前建议您进行 SHA512 校验。 2. 解压安装包并进入安装目录 ```Shell -unzip timechodb-{version}-bin.zip -cd timechodb-{version}-bin +unzip apache-iotdb-{version}-bin.zip +cd apache-iotdb-{version}-bin ``` 3. 修改相应配置 ```Shell -cd timechodb-{version}-bin/conf +cd apache-iotdb-{version}-bin/conf vim iotdb-system.properies ``` @@ -171,10 +171,10 @@ vim iotdb-system.properies ```Shell # Linux或MACOS系统 - ./timechodb-{version}-bin/sbin/start-cli.sh + ./apache-iotdb-{version}-bin/sbin/start-cli.sh # windows系统 - ./timechodb-{version}-bin/sbin/start-cli.bat + ./apache-iotdb-{version}-bin/sbin/start-cli.bat ``` 6. 执行命令进行验证 diff --git a/src/zh/UserGuide/Master/Table/User-Manual/Maintenance-statement_apache.md b/src/zh/UserGuide/Master/Table/User-Manual/Maintenance-statement_apache.md index 3ac95b3a5..6f4005271 100644 --- a/src/zh/UserGuide/Master/Table/User-Manual/Maintenance-statement_apache.md +++ b/src/zh/UserGuide/Master/Table/User-Manual/Maintenance-statement_apache.md @@ -7,9 +7,9 @@ to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at - + http://www.apache.org/licenses/LICENSE-2.0 - + Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY @@ -293,7 +293,7 @@ showQueriesStatement #### 示例： ```SQL -IoTDB> SHOW QUERIES WHERE elapsed_time > 30 +IoTDB> SHOW QUERIES WHERE elapsed_time > 30 ``` 执行结果如下： @@ -636,7 +636,7 @@ setConfigurationStatement propertyAssignments : property (',' property)* ; - + property : identifier EQ propertyValue ; @@ -675,7 +675,7 @@ IoTDB> SET CONFIGURATION disk_space_warning_threshold='0.05',heartbeat_interval_ loadConfigurationStatement : LOAD CONFIGURATION localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -705,8 +705,8 @@ IoTDB> LOAD CONFIGURATION ON LOCAL; ```SQL setSystemStatusStatement : SET SYSTEM TO (READONLY | RUNNING) localOrClusterMode? - ; - + ; + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -792,7 +792,7 @@ IoTDB> FLUSH test_db TRUE ON LOCAL; startRepairDataStatement : START REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -823,7 +823,7 @@ IoTDB> START REPAIR DATA ON CLUSTER; stopRepairDataStatement : STOP REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -907,18 +907,18 @@ debug select * from table3; 2. 观察`log_datanode_query_debug.log` 的日志内容，查看查询涉及到的文件 scan 信息。 ```Bash -2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2864/1769139940009-1-0-0.tsfile is not satisfied because of no device! -2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2865/1769139940010-1-0-0.tsfile is not satisfied because of no device! -2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: table3.d1. in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile -2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: table3.d1, all sensors: [, temperature] -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1. metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=-128, chunkMetaDataListDataSize=8, measurementId='', dataType=VECTOR, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2, modified=false, isSeq=true, chunkMetadataList=[measurementId: , datatype: VECTOR, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2, deleteIntervalList: null]}. -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1.temperature metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=64, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=FLOAT, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: FLOAT, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], deleteIntervalList: null]}. -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:110 - Modifications size is 1 for file Path: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:114 - [] -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:125 - After modification Chunk meta data list is: -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:126 - org.apache.tsfile.file.metadata.TableDeviceChunkMetadata@2e11291f -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=19} -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=46} -2026-03-24 10:10:41,519 [pool-69-IoTDB-ClientRPC-Processor-1$20260324_021041_00068_1] INFO o.a.i.d.q.p.Coordinator:902 - debug select * from table3 +2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2864/1769139940009-1-0-0.tsfile is not satisfied because of no device! +2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2865/1769139940010-1-0-0.tsfile is not satisfied because of no device! +2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: table3.d1. in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile +2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: table3.d1, all sensors: [, temperature] +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1. metadata in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=-128, chunkMetaDataListDataSize=8, measurementId='', dataType=VECTOR, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2, modified=false, isSeq=true, chunkMetadataList=[measurementId: , datatype: VECTOR, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2, deleteIntervalList: null]}. +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1.temperature metadata in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=64, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=FLOAT, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: FLOAT, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], deleteIntervalList: null]}. +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:110 - Modifications size is 1 for file Path: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:114 - [] +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:125 - After modification Chunk meta data list is: +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:126 - org.apache.tsfile.file.metadata.TableDeviceChunkMetadata@2e11291f +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=19} +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=46} +2026-03-24 10:10:41,519 [pool-69-IoTDB-ClientRPC-Processor-1$20260324_021041_00068_1] INFO o.a.i.d.q.p.Coordinator:902 - debug select * from table3 ``` diff --git a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index 5c3990aa5..b09ef486d 100644 --- a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -55,7 +55,7 @@ AINode 安装包（`apache-iotdb--ainode-bin.zip`）解压后关键目 **准备工作：** -* 获取官方发布的 SHA512 校验码：请联系天谋工作人员获取 +* 获取官方发布的 SHA512 校验码：请联系商业支持获取 **校验步骤（以 linux 为例）：** @@ -79,7 +79,7 @@ b39039a1235a86bc3ce3df0a102efa215e281b5839683ccaf47883b390af4e686f99e6980a24a9d4 **注意事项：** -* 若校验结果不一致，请联系天谋工作人员重新获取安装包 +* 若校验结果不一致，请联系商业支持重新获取安装包 * 校验过程中若出现"文件不存在"提示，需检查文件路径是否正确或安装包是否完整下载 ### 2.3 环境要求 @@ -119,7 +119,7 @@ AINode 支持修改一些必要的参数。可以在 `/IOTDB_AINODE_HOME/conf/io 若部署环境可联网且能连通 HuggingFace 环境，系统会自动拉取内置模型权重文件，可忽略本步骤。 -若为离线环境，联系天谋工作人员获取模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。 +若为离线环境，联系商业支持获取模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。 **​NOTE：​**注意目录层级，最终所有内置模型权重的父目录都是 `builtin `。 @@ -231,7 +231,7 @@ IoTDB> show cluster * 备份 conf 目录下已修改的配置文件，然后替换 conf 文件夹，并将修改的配置同步到对应位置 3. 更新内置模型权重（可选） - * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。可联系天谋工作人员获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 + * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。可联系商业支持获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 4. 升级完毕后，可启动 AINode 服务，并查看节点状态，具体命令可参考【3.4】和【3.5】小节。 diff --git a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md index ee1bc4c5a..69f409db1 100644 --- a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -67,7 +67,7 @@ AINode 安装包（`apache-iotdb--ainode-bin.zip`），安装包解压 ``` 2. 执行以下命令计算哈希值： ```Bash - sha512sum timechodb-{version}-ainode-bin.zip + sha512sum apache-iotdb-{version}-ainode-bin.zip ``` 3. 终端输出结果（左侧为SHA512 校验码，右侧为文件名）： @@ -127,7 +127,7 @@ AINode 支持修改一些必要的参数。可以在 `conf/iotdb-ainode.properti > 仅离线环境，在线环境可忽略本步骤 > -联系天谋工作人员获取模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。 +联系商业支持获取模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。 ### 3.4 启动 AINode diff --git a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md index da1d6fdfe..993db7cf7 100644 --- a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -452,7 +452,7 @@ remove datanode [datanode_id] 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。 - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。 + 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。 diff --git a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources_apache.md b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources_apache.md index 3baed4e31..685af9b52 100644 --- a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources_apache.md +++ b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources_apache.md @@ -72,11 +72,11 @@ 48核 1 2 - 请联系天谋商务咨询 + 请联系商业支持咨询 1000w以上 - 请联系天谋商务咨询 + 请联系商业支持咨询 @@ -136,11 +136,11 @@ 128G 1 2 - 请联系天谋商务咨询 + 请联系商业支持咨询 1000w以上 - 请联系天谋商务咨询 + 请联系商业支持咨询 diff --git a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md index 4b51009ff..2ac6d67a0 100644 --- a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md +++ b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md @@ -176,7 +176,7 @@ cd sbin 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。 - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。 + 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。 diff --git a/src/zh/UserGuide/Master/Tree/Ecosystem-Integration/DataEase.md b/src/zh/UserGuide/Master/Tree/Ecosystem-Integration/DataEase.md index 6534fcb78..c23599b95 100644 --- a/src/zh/UserGuide/Master/Tree/Ecosystem-Integration/DataEase.md +++ b/src/zh/UserGuide/Master/Tree/Ecosystem-Integration/DataEase.md @@ -42,10 +42,10 @@ | **准备内容** | **版本要求** | | :-------------------- | :----------------------------------------------------------- | -| IoTDB | 版本无要求，安装请参考 IoTDB [部署指导](https://www.timecho.com/docs/zh/UserGuide/latest/Deployment-and-Maintenance/IoTDB-Package_timecho.html) | +| IoTDB | 版本无要求，安装请参考 IoTDB [部署指导](../QuickStart/QuickStart_apache.md) | | JDK | 建议 JDK11 及以上版本（推荐部署 JDK17 及以上版本） | -| DataEase | 要求 v1 系列 v1.18 版本，安装请参考 DataEase 官网[安装指导](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)（暂不支持 v2.x，其他版本适配请联系天谋商务） | -| DataEase-IoTDB 连接器 | 请联系天谋商务获取 | +| DataEase | 要求 v1 系列 v1.18 版本，安装请参考 DataEase 官网[安装指导](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)（暂不支持 v2.x，其他版本适配请联系工作人员） | +| DataEase-IoTDB 连接器 | 请联系工作人员获取 | ## 3. 安装步骤 diff --git a/src/zh/UserGuide/Master/Tree/Ecosystem-Integration/Thingsboard.md b/src/zh/UserGuide/Master/Tree/Ecosystem-Integration/Thingsboard.md index 404e1f368..d3bdd017a 100644 --- a/src/zh/UserGuide/Master/Tree/Ecosystem-Integration/Thingsboard.md +++ b/src/zh/UserGuide/Master/Tree/Ecosystem-Integration/Thingsboard.md @@ -41,7 +41,7 @@ | 准备内容 | 版本要求 | | :-------------------------- | :----------------------------------------------------------- | | JDK | 要求已安装 17 及以上版本，具体下载请查看 [Oracle 官网](https://www.oracle.com/java/technologies/downloads/) | -| IoTDB | 要求已安装 V1.3.0 及以上版本，具体安装过程请参考[ 部署指导](https://www.timecho.com/docs/zh/UserGuide/latest/Deployment-and-Maintenance/IoTDB-Package_timecho.html) | +| IoTDB | 要求已安装 V1.3.0 及以上版本，具体安装过程请参考[ 部署指导](../QuickStart/QuickStart_apache.md) | | ThingsBoard（IoTDB 适配版） | 安装包请联系商务获取，具体安装步骤参见下文 | ## 3. 安装步骤 diff --git a/src/zh/UserGuide/Master/Tree/Reference/UDF-Libraries_apache.md b/src/zh/UserGuide/Master/Tree/Reference/UDF-Libraries_apache.md index 072b82921..dd0ccbbd5 100644 --- a/src/zh/UserGuide/Master/Tree/Reference/UDF-Libraries_apache.md +++ b/src/zh/UserGuide/Master/Tree/Reference/UDF-Libraries_apache.md @@ -29,8 +29,8 @@ | UDF 安装包 | 支持的 IoTDB 版本 | 下载链接 | | --------------- | ----------------- | ------------------------------------------------------------ | - | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系天谋商务获取 | - | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系天谋商务获取| + | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系商业支持获取 | + | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系商业支持获取| 2. 将获取的压缩包中的 library-udf.jar 文件放置在 IoTDB 集群所有节点的 `/ext/udf` 的目录下 3. 在 IoTDB 的 SQL 命令行终端（CLI）的 SQL 操作界面中，执行下述相应的函数注册语句。 diff --git a/src/zh/UserGuide/Master/Tree/SQL-Manual/UDF-Libraries_apache.md b/src/zh/UserGuide/Master/Tree/SQL-Manual/UDF-Libraries_apache.md index 1bd7addc0..cf49274bd 100644 --- a/src/zh/UserGuide/Master/Tree/SQL-Manual/UDF-Libraries_apache.md +++ b/src/zh/UserGuide/Master/Tree/SQL-Manual/UDF-Libraries_apache.md @@ -30,8 +30,8 @@ 1. 请获取与 IoTDB 版本兼容的 UDF 函数库 JAR 包的压缩包。 | UDF 安装包 | 支持的 IoTDB 版本 | 下载链接 | | -------------------- | ------------- | --------- | - | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系天谋商务获取 | - | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系天谋商务获取 | + | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系商业支持获取 | + | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系商业支持获取 | 2. 将获取的压缩包中的 library-udf.jar 文件放置在 IoTDB 集群所有节点的 `/ext/udf` 的目录下 3. 在 IoTDB 的 SQL 命令行终端（CLI）的 SQL 操作界面中，执行下述相应的函数注册语句。 4. 批量注册：两种注册方式：注册脚本 或 SQL汇总语句 diff --git a/src/zh/UserGuide/Master/Tree/Tools-System/CLI_apache.md b/src/zh/UserGuide/Master/Tree/Tools-System/CLI_apache.md index 9e81896d7..606db20a2 100644 --- a/src/zh/UserGuide/Master/Tree/Tools-System/CLI_apache.md +++ b/src/zh/UserGuide/Master/Tree/Tools-System/CLI_apache.md @@ -76,7 +76,7 @@ Successfully login at 127.0.0.1:6667 | -h `` | string 类型 | 否 | IoTDB 客户端连接 IoTDB 服务器的 IP 地址， 默认使用：127.0.0.1。 | -h 127.0.0.1 | | -p `` | int 类型 | 否 | IoTDB 客户端连接服务器的端口号，IoTDB 默认使用 6667。 | -p 6667 | | -u `` | string 类型 | 否 | IoTDB 客户端连接服务器所使用的用户名，默认使用 root。 | -u root | -| -pw `` | string 类型 | 否 | IoTDB 客户端连接服务器所使用的密码，默认使用 TimechoDB@2021（V2.0.6版本之前为root）。 | -pw root | +| -pw `` | string 类型 | 否 | IoTDB 客户端连接服务器所使用的密码，默认使用 IoTDB@2021（V2.0.6版本之前为root）。 | -pw root | | -sql_dialect `` | string 类型 | 否 | 目前可选 tree（树模型） 、table（表模型），默认 tree | -sql_dialect table | | -e `` | string 类型 | 否 | 在不进入客户端输入模式的情况下，批量操作 IoTDB。 | -e "show databases" | | -c | 空 | 否 | 如果服务器设置了 rpc_thrift_compression_enable=true， 则 CLI 必须使用 -c | -c | diff --git a/src/zh/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md b/src/zh/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md index 7959e40ee..abdd526d3 100644 --- a/src/zh/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md +++ b/src/zh/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md @@ -104,7 +104,7 @@ static_configs: ## 4. Apache IoTDB Dashboard -`Apache IoTDB Dashboard`是 TimechoDB 的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。 +`Apache IoTDB Dashboard`是 IoTDB 的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。 ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png) diff --git a/src/zh/UserGuide/Master/Tree/User-Manual/Load-Balance.md b/src/zh/UserGuide/Master/Tree/User-Manual/Load-Balance.md index 3793290a3..756488b8a 100644 --- a/src/zh/UserGuide/Master/Tree/User-Manual/Load-Balance.md +++ b/src/zh/UserGuide/Master/Tree/User-Manual/Load-Balance.md @@ -133,18 +133,18 @@ echo "192.168.1.3 iotdb-1" >> /etc/hosts ``` #### 1.3.2 扩容操作 -1. 为确保您获取的 TimechoDB 安装包完整且正确，在执行安装部署前建议您进行 SHA512 校验。 +1. 为确保您获取的 IoTDB 安装包完整且正确，在执行安装部署前建议您进行 SHA512 校验。 2. 解压安装包并进入安装目录 ```Shell -unzip timechodb-{version}-bin.zip -cd timechodb-{version}-bin +unzip apache-iotdb-{version}-bin.zip +cd apache-iotdb-{version}-bin ``` 3. 修改相应配置 ```Shell -cd timechodb-{version}-bin/conf +cd apache-iotdb-{version}-bin/conf vim iotdb-system.properies ``` @@ -171,10 +171,10 @@ vim iotdb-system.properies ```Shell # Linux或MACOS系统 - ./timechodb-{version}-bin/sbin/start-cli.sh + ./apache-iotdb-{version}-bin/sbin/start-cli.sh # windows系统 - ./timechodb-{version}-bin/sbin/start-cli.bat + ./apache-iotdb-{version}-bin/sbin/start-cli.bat ``` 6. 执行命令进行验证 diff --git a/src/zh/UserGuide/Master/Tree/User-Manual/Maintenance-statement_apache.md b/src/zh/UserGuide/Master/Tree/User-Manual/Maintenance-statement_apache.md index b73a3691f..ac80d3f31 100644 --- a/src/zh/UserGuide/Master/Tree/User-Manual/Maintenance-statement_apache.md +++ b/src/zh/UserGuide/Master/Tree/User-Manual/Maintenance-statement_apache.md @@ -7,9 +7,9 @@ to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at - + http://www.apache.org/licenses/LICENSE-2.0 - + Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY @@ -194,12 +194,12 @@ showQueriesStatement - **datanodeid**：发起查询语句的 DataNode 的ID - **elapsedtime**：查询的执行耗时，单位是秒 - **statement**：查询的 SQL 语句 - + #### 示例： ```SQL -IoTDB> SHOW QUERIES WHERE elapsedtime > 0.003 +IoTDB> SHOW QUERIES WHERE elapsedtime > 0.003 ``` 执行结果如下： @@ -318,7 +318,7 @@ IoTDB> SHOW SERVICES ON 1 ```SQL showDiskUsageStatement - : SHOW DISK_USAGE FROM pathPattern + : SHOW DISK_USAGE FROM pathPattern whereClause? orderByClause? rowPaginationClause? @@ -400,7 +400,7 @@ setConfigurationStatement propertyAssignments : property (',' property)* ; - + property : identifier EQ propertyValue ; @@ -439,7 +439,7 @@ IoTDB> SET CONFIGURATION 'disk_space_warning_threshold'='0.05','heartbeat_interv loadConfigurationStatement : LOAD CONFIGURATION localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -469,8 +469,8 @@ IoTDB> LOAD CONFIGURATION ON LOCAL; ```SQL setSystemStatusStatement : SET SYSTEM TO (READONLY | RUNNING) localOrClusterMode? - ; - + ; + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -556,7 +556,7 @@ IoTDB> FLUSH root.ln TRUE ON LOCAL; startRepairDataStatement : START REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -587,7 +587,7 @@ IoTDB> START REPAIR DATA ON CLUSTER; stopRepairDataStatement : STOP REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -672,13 +672,13 @@ debug select * from root.ln.**; 2. 观察`log_datanode_query_debug.log` 的日志内容，查看查询涉及到的文件 scan 信息。 ```Bash -2026-03-24 10:06:18,755 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: root.ln.wf01.wt01.temperature in file: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile -2026-03-24 10:06:18,757 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: root.ln.wf01.wt01, all sensors: [temperature] -2026-03-24 10:06:18,758 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: root.ln.wf01.wt01.temperature metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=0, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=DOUBLE, statistics=startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null]}. -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:97 - Modifications size is 0 for file Path: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:109 - After modification Chunk meta data list is: -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:110 - measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null -2026-03-24 10:06:18,760 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile', regionId=13, timePartitionId=2932, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=27} +2026-03-24 10:06:18,755 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: root.ln.wf01.wt01.temperature in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile +2026-03-24 10:06:18,757 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: root.ln.wf01.wt01, all sensors: [temperature] +2026-03-24 10:06:18,758 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: root.ln.wf01.wt01.temperature metadata in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=0, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=DOUBLE, statistics=startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null]}. +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:97 - Modifications size is 0 for file Path: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:109 - After modification Chunk meta data list is: +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:110 - measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null +2026-03-24 10:06:18,760 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile', regionId=13, timePartitionId=2932, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=27} 2026-03-24 10:06:18,761 [pool-69-IoTDB-ClientRPC-Processor-1$20260324_020618_00052_1] INFO o.a.i.d.q.p.Coordinator:902 - debug select * from root.ln.** ``` diff --git a/src/zh/UserGuide/Master/Tree/User-Manual/Streaming_apache.md b/src/zh/UserGuide/Master/Tree/User-Manual/Streaming_apache.md index ef5c0f4d7..0a9ce0a34 100644 --- a/src/zh/UserGuide/Master/Tree/User-Manual/Streaming_apache.md +++ b/src/zh/UserGuide/Master/Tree/User-Manual/Streaming_apache.md @@ -567,7 +567,7 @@ WITH SOURCE ( -- 默认的 IoTDB 数据抽取插件 'source' = 'iotdb-source', -- 路径前缀，只有能够匹配该路径前缀的数据才会被抽取，用作后续的处理和发送 - 'source.pattern' = 'root.timecho', + 'source.pattern' = 'root.iotdb', -- 描述被抽取的历史数据的时间范围，表示最早时间 'source.history.start-time' = '2011.12.03T10:15:30+01:00', -- 描述被抽取的历史数据的时间范围，表示最晚时间 diff --git a/src/zh/UserGuide/V1.2.x/Deployment-and-Maintenance/Monitoring-Board-Install-and-Deploy.md b/src/zh/UserGuide/V1.2.x/Deployment-and-Maintenance/Monitoring-Board-Install-and-Deploy.md index b25214a71..67d324b64 100644 --- a/src/zh/UserGuide/V1.2.x/Deployment-and-Maintenance/Monitoring-Board-Install-and-Deploy.md +++ b/src/zh/UserGuide/V1.2.x/Deployment-and-Maintenance/Monitoring-Board-Install-and-Deploy.md @@ -29,7 +29,7 @@ 1. Apache IoTDB：1.0 版本及以上，可以前往官网下载：https://iotdb.apache.org/Download/ 2. Prometheus：2.30.3 版本及以上，可以前往官网下载：https://prometheus.io/download/ 3. Grafana：8.4.2 版本及以上，可以前往官网下载：https://grafana.com/grafana/download -4. IoTDB-Grafana安装包：Grafana看板为TimechoDB（基于IoTDB的企业版数据库）工具，您可联系您的销售获取相关安装包 +4. IoTDB-Grafana安装包：Grafana看板为 IoTDB的企业版工具，您可联系您的销售获取相关安装包 ### 集群要求 diff --git a/src/zh/UserGuide/V1.2.x/Reference/UDF-Libraries.md b/src/zh/UserGuide/V1.2.x/Reference/UDF-Libraries.md index 15a477f6e..45a72931f 100644 --- a/src/zh/UserGuide/V1.2.x/Reference/UDF-Libraries.md +++ b/src/zh/UserGuide/V1.2.x/Reference/UDF-Libraries.md @@ -29,7 +29,7 @@ | UDF 函数库版本 | 支持的 IoTDB 版本 | 下载链接 | | --------------- | ----------------- | ------------------------------------------------------------ | - | UDF-1.2.x.zip | V1.0.0～V1.2.x | 请联系天谋商务获取| + | UDF-1.2.x.zip | V1.0.0～V1.2.x | 请联系工作人员获取| 2. 将获取的压缩包中的 `library-udf.jar` 文件放置在 IoTDB 集群所有节点的 `/ext/udf` 的目录下 3. 在 IoTDB 的 SQL 命令行终端（CLI）或可视化控制台（Workbench）的 SQL 操作界面中，执行下述相应的函数注册语句。 diff --git a/src/zh/UserGuide/V1.2.x/User-Manual/Data-Sync.md b/src/zh/UserGuide/V1.2.x/User-Manual/Data-Sync.md index 775264e2b..fb72fea4f 100644 --- a/src/zh/UserGuide/V1.2.x/User-Manual/Data-Sync.md +++ b/src/zh/UserGuide/V1.2.x/User-Manual/Data-Sync.md @@ -91,7 +91,7 @@ WITH EXTRACTOR ( -- 默认的 IoTDB 数据抽取插件 'extractor' = 'iotdb-extractor', -- 路径前缀，只有能够匹配该路径前缀的数据才会被抽取，用作后续的处理和发送 - 'extractor.pattern' = 'root.timecho', + 'extractor.pattern' = 'root.iotdb', -- 是否抽取历史数据 'extractor.history.enable' = 'true', -- 描述被抽取的历史数据的时间范围，表示最早时间 diff --git a/src/zh/UserGuide/V1.2.x/User-Manual/Streaming.md b/src/zh/UserGuide/V1.2.x/User-Manual/Streaming.md index 7d8c36b98..82af6bcfd 100644 --- a/src/zh/UserGuide/V1.2.x/User-Manual/Streaming.md +++ b/src/zh/UserGuide/V1.2.x/User-Manual/Streaming.md @@ -575,7 +575,7 @@ WITH EXTRACTOR ( -- 默认的 IoTDB 数据抽取插件 'extractor' = 'iotdb-extractor', -- 路径前缀，只有能够匹配该路径前缀的数据才会被抽取，用作后续的处理和发送 - 'extractor.pattern' = 'root.timecho', + 'extractor.pattern' = 'root.iotdb', -- 是否抽取历史数据 'extractor.history.enable' = 'true', -- 描述被抽取的历史数据的时间范围，表示最早时间 diff --git a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/AINode_Deployment_apache.md index 548b7e5eb..b874c2ede 100644 --- a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -68,7 +68,7 @@ AINode 是 IoTDB 在 ConfigNode、DataNode 后提供的第三种内生节点， ``` 2. 执行以下命令计算哈希值： ```Bash - sha512sum timechodb-{version}-ainode-bin.zip + sha512sum apache-iotdb-{version}-ainode-bin.zip ``` 3. 终端输出结果（左侧为SHA512 校验码，右侧为文件名）： diff --git a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md index 57413c8bf..36bd73ac0 100644 --- a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -414,7 +414,7 @@ sbin/remove-datanode.bat [datanode_id] 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。 - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。 + 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。 diff --git a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Database-Resources.md b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Database-Resources.md index 67c629ffd..6395e1c05 100644 --- a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Database-Resources.md +++ b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Database-Resources.md @@ -72,11 +72,11 @@ 48核 1 2 - 请联系天谋商务咨询 + 请联系工作人员咨询 1000w以上 - 请联系天谋商务咨询 + 请联系工作人员咨询 @@ -134,11 +134,11 @@ 128G 1 2 - 请联系天谋商务咨询 + 请联系工作人员咨询 1000w以上 - 请联系天谋商务咨询 + 请联系工作人员咨询 diff --git a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md index 32e7db962..7a2ed7a73 100644 --- a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md +++ b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md @@ -176,7 +176,7 @@ cd sbin 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。 - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。 + 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。 diff --git a/src/zh/UserGuide/V1.3.x/Ecosystem-Integration/DataEase.md b/src/zh/UserGuide/V1.3.x/Ecosystem-Integration/DataEase.md index d3be92a31..9caa2bad2 100644 --- a/src/zh/UserGuide/V1.3.x/Ecosystem-Integration/DataEase.md +++ b/src/zh/UserGuide/V1.3.x/Ecosystem-Integration/DataEase.md @@ -42,10 +42,10 @@ | **准备内容** | **版本要求** | | :-------------------- | :----------------------------------------------------------- | -| IoTDB | 版本无要求，安装请参考 IoTDB [部署指导](https://www.timecho.com/docs/zh/UserGuide/latest/Deployment-and-Maintenance/IoTDB-Package_timecho.html) | +| IoTDB | 版本无要求，安装请参考 IoTDB [部署指导](../QuickStart/QuickStart_apache.md) | | JDK | 建议 JDK11 及以上版本（推荐部署 JDK17 及以上版本） | -| DataEase | 要求 v1 系列 v1.18 版本，安装请参考 DataEase 官网[安装指导](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)（暂不支持 v2.x，其他版本适配请联系天谋商务） | -| DataEase-IoTDB 连接器 | 请联系天谋商务获取 | +| DataEase | 要求 v1 系列 v1.18 版本，安装请参考 DataEase 官网[安装指导](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)（暂不支持 v2.x，其他版本适配请联系工作人员） | +| DataEase-IoTDB 连接器 | 请联系工作人员获取 | ## 安装步骤 diff --git a/src/zh/UserGuide/V1.3.x/Ecosystem-Integration/Thingsboard.md b/src/zh/UserGuide/V1.3.x/Ecosystem-Integration/Thingsboard.md index 2b92a4dd3..67bd9f7e3 100644 --- a/src/zh/UserGuide/V1.3.x/Ecosystem-Integration/Thingsboard.md +++ b/src/zh/UserGuide/V1.3.x/Ecosystem-Integration/Thingsboard.md @@ -41,7 +41,7 @@ | 准备内容 | 版本要求 | | :-------------------------- | :----------------------------------------------------------- | | JDK | 要求已安装 17 及以上版本，具体下载请查看 [Oracle 官网](https://www.oracle.com/java/technologies/downloads/) | -| IoTDB | 要求已安装 V1.3.0 及以上版本，具体安装过程请参考[ 部署指导](https://www.timecho.com/docs/zh/UserGuide/latest/Deployment-and-Maintenance/IoTDB-Package_timecho.html) | +| IoTDB | 要求已安装 V1.3.0 及以上版本，具体安装过程请参考[ 部署指导](../QuickStart/QuickStart_apache.md) | | ThingsBoard（IoTDB 适配版） | 安装包请联系商务获取，具体安装步骤参见下文 | ## 安装步骤 diff --git a/src/zh/UserGuide/V1.3.x/Reference/UDF-Libraries_apache.md b/src/zh/UserGuide/V1.3.x/Reference/UDF-Libraries_apache.md index b35e35e1a..927478823 100644 --- a/src/zh/UserGuide/V1.3.x/Reference/UDF-Libraries_apache.md +++ b/src/zh/UserGuide/V1.3.x/Reference/UDF-Libraries_apache.md @@ -29,8 +29,8 @@ | UDF 安装包 | 支持的 IoTDB 版本 | 下载链接 | | --------------- | ----------------- | ------------------------------------------------------------ | - | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系天谋商务获取 | - | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系天谋商务获取| + | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系商业支持获取 | + | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系商业支持获取| 2. 将获取的压缩包中的 library-udf.jar 文件放置在 IoTDB 集群所有节点的 `/ext/udf` 的目录下 3. 在 IoTDB 的 SQL 命令行终端（CLI）的 SQL 操作界面中，执行下述相应的函数注册语句。 diff --git a/src/zh/UserGuide/V1.3.x/SQL-Manual/UDF-Libraries_apache.md b/src/zh/UserGuide/V1.3.x/SQL-Manual/UDF-Libraries_apache.md index a207b74f7..c95babc1a 100644 --- a/src/zh/UserGuide/V1.3.x/SQL-Manual/UDF-Libraries_apache.md +++ b/src/zh/UserGuide/V1.3.x/SQL-Manual/UDF-Libraries_apache.md @@ -29,8 +29,8 @@ | UDF 安装包 | 支持的 IoTDB 版本 | 下载链接 | | --------------- | ----------------- | ------------------------------------------------------------ | - | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系天谋商务获取 | - | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系天谋商务获取| + | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系商业支持获取 | + | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系商业支持获取| 2. 将获取的压缩包中的 library-udf.jar 文件放置在 IoTDB 集群所有节点的 `/ext/udf` 的目录下 3. 在 IoTDB 的 SQL 命令行终端（CLI）的 SQL 操作界面中，执行下述相应的函数注册语句。 diff --git a/src/zh/UserGuide/V1.3.x/Tools-System/CLI_apache.md b/src/zh/UserGuide/V1.3.x/Tools-System/CLI_apache.md index 42d6952c1..a8ad997e5 100644 --- a/src/zh/UserGuide/V1.3.x/Tools-System/CLI_apache.md +++ b/src/zh/UserGuide/V1.3.x/Tools-System/CLI_apache.md @@ -72,7 +72,7 @@ Successfully login at 127.0.0.1:6667 | -h `` | string 类型 | 否 | IoTDB 客户端连接 IoTDB 服务器的 IP 地址， 默认使用：127.0.0.1。 | -h 127.0.0.1 | | -p `` | int 类型 | 否 | IoTDB 客户端连接服务器的端口号，IoTDB 默认使用 6667。 | -p 6667 | | -u `` | string 类型 | 否 | IoTDB 客户端连接服务器所使用的用户名，默认使用 root。 | -u root | -| -pw `` | string 类型 | 否 | IoTDB 客户端连接服务器所使用的密码，默认使用 TimechoDB@2021（V2.0.6版本之前为root）。 | -pw root | +| -pw `` | string 类型 | 否 | IoTDB 客户端连接服务器所使用的密码，默认使用 root。 | -pw root | | -e `` | string 类型 | 否 | 在不进入客户端输入模式的情况下，批量操作 IoTDB。 | -e "show databases" | | -c | 空 | 否 | 如果服务器设置了 rpc_thrift_compression_enable=true， 则 CLI 必须使用 -c | -c | | -disableISO8601 | 空 | 否 | 如果设置了这个参数，IoTDB 将以数字的形式打印时间戳 （timestamp）。 | -disableISO8601 | diff --git a/src/zh/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md b/src/zh/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md index 16023f4e8..3ef0730da 100644 --- a/src/zh/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md +++ b/src/zh/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md @@ -104,7 +104,7 @@ static_configs: ## Apache IoTDB Dashboard -`Apache IoTDB Dashboard`是 TimechoDB 的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。 +`Apache IoTDB Dashboard`是 IoTDB 企业版的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。 ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png) diff --git a/src/zh/UserGuide/V1.3.x/User-Manual/Streaming_apache.md b/src/zh/UserGuide/V1.3.x/User-Manual/Streaming_apache.md index 14393c9f1..38811fa30 100644 --- a/src/zh/UserGuide/V1.3.x/User-Manual/Streaming_apache.md +++ b/src/zh/UserGuide/V1.3.x/User-Manual/Streaming_apache.md @@ -573,7 +573,7 @@ WITH SOURCE ( -- 默认的 IoTDB 数据抽取插件 'source' = 'iotdb-source', -- 路径前缀，只有能够匹配该路径前缀的数据才会被抽取，用作后续的处理和发送 - 'source.pattern' = 'root.timecho', + 'source.pattern' = 'root.iotdb', -- 描述被抽取的历史数据的时间范围，表示最早时间 'source.history.start-time' = '2011.12.03T10:15:30+01:00', -- 描述被抽取的历史数据的时间范围，表示最晚时间 diff --git a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/AINode_Deployment_apache.md index 548b7e5eb..b874c2ede 100644 --- a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -68,7 +68,7 @@ AINode 是 IoTDB 在 ConfigNode、DataNode 后提供的第三种内生节点， ``` 2. 执行以下命令计算哈希值： ```Bash - sha512sum timechodb-{version}-ainode-bin.zip + sha512sum apache-iotdb-{version}-ainode-bin.zip ``` 3. 终端输出结果（左侧为SHA512 校验码，右侧为文件名）： diff --git a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md index facc311b4..21e48c4b0 100644 --- a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -201,7 +201,7 @@ cd sbin ![](/img/%E5%BC%80%E6%BA%90%E7%89%88%20show%20cluter.png) -> 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. +> 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系商业支持重新申请. ### 一键启停集群 @@ -406,7 +406,7 @@ remove datanode [datanode_id] 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。 - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。 + 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。 diff --git a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Database-Resources.md b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Database-Resources.md index 67c629ffd..6395e1c05 100644 --- a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Database-Resources.md +++ b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Database-Resources.md @@ -72,11 +72,11 @@ 48核 1 2 - 请联系天谋商务咨询 + 请联系工作人员咨询 1000w以上 - 请联系天谋商务咨询 + 请联系工作人员咨询 @@ -134,11 +134,11 @@ 128G 1 2 - 请联系天谋商务咨询 + 请联系工作人员咨询 1000w以上 - 请联系天谋商务咨询 + 请联系工作人员咨询 diff --git a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md index 4d4985856..cae44bfc9 100644 --- a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md +++ b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md @@ -172,7 +172,7 @@ cd sbin ![](/img/%E5%BC%80%E6%BA%90-%E5%8D%95%E6%9C%BAshow.jpeg) -> 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件）。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. +> 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件）。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系商业支持重新申请. ## 常见问题 @@ -180,7 +180,7 @@ cd sbin 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。 - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。 + 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。 diff --git a/src/zh/UserGuide/dev-1.3/Ecosystem-Integration/DataEase.md b/src/zh/UserGuide/dev-1.3/Ecosystem-Integration/DataEase.md index d3be92a31..9caa2bad2 100644 --- a/src/zh/UserGuide/dev-1.3/Ecosystem-Integration/DataEase.md +++ b/src/zh/UserGuide/dev-1.3/Ecosystem-Integration/DataEase.md @@ -42,10 +42,10 @@ | **准备内容** | **版本要求** | | :-------------------- | :----------------------------------------------------------- | -| IoTDB | 版本无要求，安装请参考 IoTDB [部署指导](https://www.timecho.com/docs/zh/UserGuide/latest/Deployment-and-Maintenance/IoTDB-Package_timecho.html) | +| IoTDB | 版本无要求，安装请参考 IoTDB [部署指导](../QuickStart/QuickStart_apache.md) | | JDK | 建议 JDK11 及以上版本（推荐部署 JDK17 及以上版本） | -| DataEase | 要求 v1 系列 v1.18 版本，安装请参考 DataEase 官网[安装指导](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)（暂不支持 v2.x，其他版本适配请联系天谋商务） | -| DataEase-IoTDB 连接器 | 请联系天谋商务获取 | +| DataEase | 要求 v1 系列 v1.18 版本，安装请参考 DataEase 官网[安装指导](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)（暂不支持 v2.x，其他版本适配请联系工作人员） | +| DataEase-IoTDB 连接器 | 请联系工作人员获取 | ## 安装步骤 diff --git a/src/zh/UserGuide/dev-1.3/Ecosystem-Integration/Thingsboard.md b/src/zh/UserGuide/dev-1.3/Ecosystem-Integration/Thingsboard.md index 2b92a4dd3..67bd9f7e3 100644 --- a/src/zh/UserGuide/dev-1.3/Ecosystem-Integration/Thingsboard.md +++ b/src/zh/UserGuide/dev-1.3/Ecosystem-Integration/Thingsboard.md @@ -41,7 +41,7 @@ | 准备内容 | 版本要求 | | :-------------------------- | :----------------------------------------------------------- | | JDK | 要求已安装 17 及以上版本，具体下载请查看 [Oracle 官网](https://www.oracle.com/java/technologies/downloads/) | -| IoTDB | 要求已安装 V1.3.0 及以上版本，具体安装过程请参考[ 部署指导](https://www.timecho.com/docs/zh/UserGuide/latest/Deployment-and-Maintenance/IoTDB-Package_timecho.html) | +| IoTDB | 要求已安装 V1.3.0 及以上版本，具体安装过程请参考[ 部署指导](../QuickStart/QuickStart_apache.md) | | ThingsBoard（IoTDB 适配版） | 安装包请联系商务获取，具体安装步骤参见下文 | ## 安装步骤 diff --git a/src/zh/UserGuide/dev-1.3/Reference/UDF-Libraries_apache.md b/src/zh/UserGuide/dev-1.3/Reference/UDF-Libraries_apache.md index b35e35e1a..927478823 100644 --- a/src/zh/UserGuide/dev-1.3/Reference/UDF-Libraries_apache.md +++ b/src/zh/UserGuide/dev-1.3/Reference/UDF-Libraries_apache.md @@ -29,8 +29,8 @@ | UDF 安装包 | 支持的 IoTDB 版本 | 下载链接 | | --------------- | ----------------- | ------------------------------------------------------------ | - | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系天谋商务获取 | - | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系天谋商务获取| + | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系商业支持获取 | + | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系商业支持获取| 2. 将获取的压缩包中的 library-udf.jar 文件放置在 IoTDB 集群所有节点的 `/ext/udf` 的目录下 3. 在 IoTDB 的 SQL 命令行终端（CLI）的 SQL 操作界面中，执行下述相应的函数注册语句。 diff --git a/src/zh/UserGuide/dev-1.3/SQL-Manual/UDF-Libraries_apache.md b/src/zh/UserGuide/dev-1.3/SQL-Manual/UDF-Libraries_apache.md index 80cc6be4d..6708ac887 100644 --- a/src/zh/UserGuide/dev-1.3/SQL-Manual/UDF-Libraries_apache.md +++ b/src/zh/UserGuide/dev-1.3/SQL-Manual/UDF-Libraries_apache.md @@ -29,8 +29,8 @@ | UDF 安装包 | 支持的 IoTDB 版本 | 下载链接 | | --------------- | ----------------- | ------------------------------------------------------------ | - | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系天谋商务获取 | - | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系天谋商务获取| + | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系商业支持获取 | + | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系商业支持获取| 2. 将获取的压缩包中的 library-udf.jar 文件放置在 IoTDB 集群所有节点的 `/ext/udf` 的目录下 3. 在 IoTDB 的 SQL 命令行终端（CLI）的 SQL 操作界面中，执行下述相应的函数注册语句。 diff --git a/src/zh/UserGuide/dev-1.3/Tools-System/CLI_apache.md b/src/zh/UserGuide/dev-1.3/Tools-System/CLI_apache.md index 42d6952c1..f1cd5ad74 100644 --- a/src/zh/UserGuide/dev-1.3/Tools-System/CLI_apache.md +++ b/src/zh/UserGuide/dev-1.3/Tools-System/CLI_apache.md @@ -72,7 +72,7 @@ Successfully login at 127.0.0.1:6667 | -h `` | string 类型 | 否 | IoTDB 客户端连接 IoTDB 服务器的 IP 地址， 默认使用：127.0.0.1。 | -h 127.0.0.1 | | -p `` | int 类型 | 否 | IoTDB 客户端连接服务器的端口号，IoTDB 默认使用 6667。 | -p 6667 | | -u `` | string 类型 | 否 | IoTDB 客户端连接服务器所使用的用户名，默认使用 root。 | -u root | -| -pw `` | string 类型 | 否 | IoTDB 客户端连接服务器所使用的密码，默认使用 TimechoDB@2021（V2.0.6版本之前为root）。 | -pw root | +| -pw `` | string 类型 | 否 | IoTDB 客户端连接服务器所使用的密码，默认使用 IoTDB@2021（V2.0.6版本之前为root）。 | -pw root | | -e `` | string 类型 | 否 | 在不进入客户端输入模式的情况下，批量操作 IoTDB。 | -e "show databases" | | -c | 空 | 否 | 如果服务器设置了 rpc_thrift_compression_enable=true， 则 CLI 必须使用 -c | -c | | -disableISO8601 | 空 | 否 | 如果设置了这个参数，IoTDB 将以数字的形式打印时间戳 （timestamp）。 | -disableISO8601 | diff --git a/src/zh/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md b/src/zh/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md index 16023f4e8..871b61cbf 100644 --- a/src/zh/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md +++ b/src/zh/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md @@ -104,7 +104,7 @@ static_configs: ## Apache IoTDB Dashboard -`Apache IoTDB Dashboard`是 TimechoDB 的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。 +`Apache IoTDB Dashboard`是 IoTDB 的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。 ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png) diff --git a/src/zh/UserGuide/dev-1.3/User-Manual/Streaming_apache.md b/src/zh/UserGuide/dev-1.3/User-Manual/Streaming_apache.md index 14393c9f1..38811fa30 100644 --- a/src/zh/UserGuide/dev-1.3/User-Manual/Streaming_apache.md +++ b/src/zh/UserGuide/dev-1.3/User-Manual/Streaming_apache.md @@ -573,7 +573,7 @@ WITH SOURCE ( -- 默认的 IoTDB 数据抽取插件 'source' = 'iotdb-source', -- 路径前缀，只有能够匹配该路径前缀的数据才会被抽取，用作后续的处理和发送 - 'source.pattern' = 'root.timecho', + 'source.pattern' = 'root.iotdb', -- 描述被抽取的历史数据的时间范围，表示最早时间 'source.history.start-time' = '2011.12.03T10:15:30+01:00', -- 描述被抽取的历史数据的时间范围，表示最晚时间 diff --git a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index 8fa71017a..adb5f6979 100644 --- a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -55,7 +55,7 @@ AINode 安装包（`apache-iotdb--ainode-bin.zip`）解压后关键目 **准备工作：** -* 获取官方发布的 SHA512 校验码：请联系天谋工作人员获取 +* 获取官方发布的 SHA512 校验码：请联系商业支持获取 **校验步骤（以 linux 为例）：** @@ -79,7 +79,7 @@ b39039a1235a86bc3ce3df0a102efa215e281b5839683ccaf47883b390af4e686f99e6980a24a9d4 **注意事项：** -* 若校验结果不一致，请联系天谋工作人员重新获取安装包 +* 若校验结果不一致，请联系商业支持重新获取安装包 * 校验过程中若出现"文件不存在"提示，需检查文件路径是否正确或安装包是否完整下载 ### 2.3 环境要求 @@ -119,7 +119,7 @@ AINode 支持修改一些必要的参数。可以在 `/IOTDB_AINODE_HOME/conf/io 若部署环境可联网且能连通 HuggingFace 环境，系统会自动拉取内置模型权重文件，可忽略本步骤。 -若为离线环境，联系天谋工作人员获取模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。 +若为离线环境，联系商业支持获取模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。 **​NOTE：​**注意目录层级，最终所有内置模型权重的父目录都是 `builtin `。 @@ -231,7 +231,7 @@ IoTDB> show cluster * 备份 conf 目录下已修改的配置文件，然后替换 conf 文件夹，并将修改的配置同步到对应位置 3. 更新内置模型权重（可选） - * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。可联系天谋工作人员获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 + * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。可联系商业支持获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 4. 升级完毕后，可启动 AINode 服务，并查看节点状态，具体命令可参考【3.4】和【3.5】小节。 diff --git a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md index 7bf8a380f..5badae7a5 100644 --- a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -67,7 +67,7 @@ AINode 安装包（`apache-iotdb--ainode-bin.zip`），安装包解压 ``` 2. 执行以下命令计算哈希值： ```Bash - sha512sum timechodb-{version}-ainode-bin.zip + sha512sum apache-iotdb-{version}-ainode-bin.zip ``` 3. 终端输出结果（左侧为SHA512 校验码，右侧为文件名）： @@ -127,7 +127,7 @@ AINode 支持修改一些必要的参数。可以在 `conf/iotdb-ainode.properti > 仅离线环境，在线环境可忽略本步骤 > -联系天谋工作人员获取模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。 +联系商业支持获取模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。 ### 3.4 启动 AINode diff --git a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md index ff0b4d6b6..e5f0a1142 100644 --- a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -418,7 +418,7 @@ remove datanode [datanode_id] 1. Confignode节点启动失败 - 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。 - - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。 + - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。 - 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。 - 清理环境： diff --git a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md index 2766e74a6..c1b64662a 100644 --- a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md +++ b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md @@ -73,11 +73,11 @@ 48核 1 2 - 请联系天谋商务咨询 + 请联系商业支持咨询 1000w以上 - 请联系天谋商务咨询 + 请联系商业支持咨询 @@ -137,11 +137,11 @@ 128G 1 2 - 请联系天谋商务咨询 + 请联系商业支持咨询 1000w以上 - 请联系天谋商务咨询 + 请联系商业支持咨询 diff --git a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md index e8c7e1baf..739d5d864 100644 --- a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md +++ b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md @@ -163,7 +163,7 @@ DataNode 配置 1. Confignode节点启动失败 - 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。 - - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。 + - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。 - 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。 - 清理环境： 1. 结束所有 ConfigNode 和 DataNode 进程。 diff --git a/src/zh/UserGuide/latest-Table/Ecosystem-Integration/DataGrip.md b/src/zh/UserGuide/latest-Table/Ecosystem-Integration/DataGrip.md index 7909ceb2f..1dd89e97d 100644 --- a/src/zh/UserGuide/latest-Table/Ecosystem-Integration/DataGrip.md +++ b/src/zh/UserGuide/latest-Table/Ecosystem-Integration/DataGrip.md @@ -43,9 +43,9 @@ IoTDB 通过 JDBC 接口与 DataGrip 集成，支持像管理文件夹一样通 选择对应版本的 jar 包，下载后缀 `jar-with-dependencies.jar` 的包： -- 链接 1：https://repo1.maven.org/maven2/com/timecho/iotdb/iotdb-jdbc/2.0.3.3/iotdb-jdbc-2.0.3.3-jar-with-dependencies.jar +- 链接 1：https://repo1.maven.org/maven2/org/apache/iotdb/iotdb-jdbc/2.0.3/iotdb-jdbc-2.0.3-jar-with-dependencies.jar -- 链接 2：https://repo1.maven.org/maven2/com/timecho/iotdb/iotdb-jdbc/2.0.3.3/ +- 链接 2：https://repo1.maven.org/maven2/org/apache/iotdb/iotdb-jdbc/2.0.3/ ![](/img/datagrip-2.png) diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md b/src/zh/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md index 7959e40ee..2b5cc4683 100644 --- a/src/zh/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md +++ b/src/zh/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md @@ -104,7 +104,7 @@ static_configs: ## 4. Apache IoTDB Dashboard -`Apache IoTDB Dashboard`是 TimechoDB 的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。 +`Apache IoTDB Dashboard`是 IoTDB 企业版的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。 ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png) diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Load-Balance.md b/src/zh/UserGuide/latest-Table/User-Manual/Load-Balance.md index 7fe0a8e6c..f54905e0e 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Load-Balance.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Load-Balance.md @@ -133,18 +133,18 @@ echo "192.168.1.3 iotdb-1" >> /etc/hosts ``` #### 1.3.2 扩容操作 -1. 为确保您获取的 TimechoDB 安装包完整且正确，在执行安装部署前建议您进行 SHA512 校验。 +1. 为确保您获取的 IoTDB 安装包完整且正确，在执行安装部署前建议您进行 SHA512 校验。 2. 解压安装包并进入安装目录 ```Shell -unzip timechodb-{version}-bin.zip -cd timechodb-{version}-bin +unzip apache-iotdb-{version}-bin.zip +cd apache-iotdb-{version}-bin ``` 3. 修改相应配置 ```Shell -cd timechodb-{version}-bin/conf +cd apache-iotdb-{version}-bin/conf vim iotdb-system.properies ``` @@ -171,10 +171,10 @@ vim iotdb-system.properies ```Shell # Linux或MACOS系统 - ./timechodb-{version}-bin/sbin/start-cli.sh + ./apache-iotdb-{version}-bin/sbin/start-cli.sh # windows系统 - ./timechodb-{version}-bin/sbin/start-cli.bat + ./apache-iotdb-{version}-bin/sbin/start-cli.bat ``` 6. 执行命令进行验证 diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_apache.md b/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_apache.md index 3ac95b3a5..6f4005271 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_apache.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_apache.md @@ -7,9 +7,9 @@ to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at - + http://www.apache.org/licenses/LICENSE-2.0 - + Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY @@ -293,7 +293,7 @@ showQueriesStatement #### 示例： ```SQL -IoTDB> SHOW QUERIES WHERE elapsed_time > 30 +IoTDB> SHOW QUERIES WHERE elapsed_time > 30 ``` 执行结果如下： @@ -636,7 +636,7 @@ setConfigurationStatement propertyAssignments : property (',' property)* ; - + property : identifier EQ propertyValue ; @@ -675,7 +675,7 @@ IoTDB> SET CONFIGURATION disk_space_warning_threshold='0.05',heartbeat_interval_ loadConfigurationStatement : LOAD CONFIGURATION localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -705,8 +705,8 @@ IoTDB> LOAD CONFIGURATION ON LOCAL; ```SQL setSystemStatusStatement : SET SYSTEM TO (READONLY | RUNNING) localOrClusterMode? - ; - + ; + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -792,7 +792,7 @@ IoTDB> FLUSH test_db TRUE ON LOCAL; startRepairDataStatement : START REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -823,7 +823,7 @@ IoTDB> START REPAIR DATA ON CLUSTER; stopRepairDataStatement : STOP REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -907,18 +907,18 @@ debug select * from table3; 2. 观察`log_datanode_query_debug.log` 的日志内容，查看查询涉及到的文件 scan 信息。 ```Bash -2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2864/1769139940009-1-0-0.tsfile is not satisfied because of no device! -2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2865/1769139940010-1-0-0.tsfile is not satisfied because of no device! -2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: table3.d1. in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile -2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: table3.d1, all sensors: [, temperature] -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1. metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=-128, chunkMetaDataListDataSize=8, measurementId='', dataType=VECTOR, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2, modified=false, isSeq=true, chunkMetadataList=[measurementId: , datatype: VECTOR, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2, deleteIntervalList: null]}. -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1.temperature metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=64, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=FLOAT, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: FLOAT, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], deleteIntervalList: null]}. -2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:110 - Modifications size is 1 for file Path: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:114 - [] -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:125 - After modification Chunk meta data list is: -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:126 - org.apache.tsfile.file.metadata.TableDeviceChunkMetadata@2e11291f -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=19} -2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=46} -2026-03-24 10:10:41,519 [pool-69-IoTDB-ClientRPC-Processor-1$20260324_021041_00068_1] INFO o.a.i.d.q.p.Coordinator:902 - debug select * from table3 +2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2864/1769139940009-1-0-0.tsfile is not satisfied because of no device! +2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2865/1769139940010-1-0-0.tsfile is not satisfied because of no device! +2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: table3.d1. in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile +2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: table3.d1, all sensors: [, temperature] +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1. metadata in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=-128, chunkMetaDataListDataSize=8, measurementId='', dataType=VECTOR, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2, modified=false, isSeq=true, chunkMetadataList=[measurementId: , datatype: VECTOR, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2, deleteIntervalList: null]}. +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1.temperature metadata in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=64, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=FLOAT, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: FLOAT, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], deleteIntervalList: null]}. +2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:110 - Modifications size is 1 for file Path: /home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:114 - [] +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:125 - After modification Chunk meta data list is: +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:126 - org.apache.tsfile.file.metadata.TableDeviceChunkMetadata@2e11291f +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=19} +2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/apache-iotdb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=46} +2026-03-24 10:10:41,519 [pool-69-IoTDB-ClientRPC-Processor-1$20260324_021041_00068_1] INFO o.a.i.d.q.p.Coordinator:902 - debug select * from table3 ``` diff --git a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index 8fa71017a..adb5f6979 100644 --- a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -55,7 +55,7 @@ AINode 安装包（`apache-iotdb--ainode-bin.zip`）解压后关键目 **准备工作：** -* 获取官方发布的 SHA512 校验码：请联系天谋工作人员获取 +* 获取官方发布的 SHA512 校验码：请联系商业支持获取 **校验步骤（以 linux 为例）：** @@ -79,7 +79,7 @@ b39039a1235a86bc3ce3df0a102efa215e281b5839683ccaf47883b390af4e686f99e6980a24a9d4 **注意事项：** -* 若校验结果不一致，请联系天谋工作人员重新获取安装包 +* 若校验结果不一致，请联系商业支持重新获取安装包 * 校验过程中若出现"文件不存在"提示，需检查文件路径是否正确或安装包是否完整下载 ### 2.3 环境要求 @@ -119,7 +119,7 @@ AINode 支持修改一些必要的参数。可以在 `/IOTDB_AINODE_HOME/conf/io 若部署环境可联网且能连通 HuggingFace 环境，系统会自动拉取内置模型权重文件，可忽略本步骤。 -若为离线环境，联系天谋工作人员获取模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。 +若为离线环境，联系商业支持获取模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。 **​NOTE：​**注意目录层级，最终所有内置模型权重的父目录都是 `builtin `。 @@ -231,7 +231,7 @@ IoTDB> show cluster * 备份 conf 目录下已修改的配置文件，然后替换 conf 文件夹，并将修改的配置同步到对应位置 3. 更新内置模型权重（可选） - * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。可联系天谋工作人员获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 + * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。可联系商业支持获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 4. 升级完毕后，可启动 AINode 服务，并查看节点状态，具体命令可参考【3.4】和【3.5】小节。 diff --git a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md index 06952af0e..6e816560e 100644 --- a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -67,7 +67,7 @@ AINode 安装包（`apache-iotdb--ainode-bin.zip`），安装包解压 ``` 2. 执行以下命令计算哈希值： ```Bash - sha512sum timechodb-{version}-ainode-bin.zip + sha512sum apache-iotdb-{version}-ainode-bin.zip ``` 3. 终端输出结果（左侧为SHA512 校验码，右侧为文件名）： @@ -126,7 +126,7 @@ AINode 支持修改一些必要的参数。可以在 `conf/iotdb-ainode.properti > 仅离线环境，在线环境可忽略本步骤 > -联系天谋工作人员获取模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。 +联系商业支持获取模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。 ### 3.4 启动 AINode diff --git a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md index da1d6fdfe..993db7cf7 100644 --- a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -452,7 +452,7 @@ remove datanode [datanode_id] 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。 - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。 + 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。 diff --git a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Database-Resources_apache.md b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Database-Resources_apache.md index 3baed4e31..685af9b52 100644 --- a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Database-Resources_apache.md +++ b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Database-Resources_apache.md @@ -72,11 +72,11 @@ 48核 1 2 - 请联系天谋商务咨询 + 请联系商业支持咨询 1000w以上 - 请联系天谋商务咨询 + 请联系商业支持咨询 @@ -136,11 +136,11 @@ 128G 1 2 - 请联系天谋商务咨询 + 请联系商业支持咨询 1000w以上 - 请联系天谋商务咨询 + 请联系商业支持咨询 diff --git a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md index 4b51009ff..2ac6d67a0 100644 --- a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md +++ b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md @@ -176,7 +176,7 @@ cd sbin 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。 - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。 + 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。 diff --git a/src/zh/UserGuide/latest/Ecosystem-Integration/DataEase.md b/src/zh/UserGuide/latest/Ecosystem-Integration/DataEase.md index 6534fcb78..c23599b95 100644 --- a/src/zh/UserGuide/latest/Ecosystem-Integration/DataEase.md +++ b/src/zh/UserGuide/latest/Ecosystem-Integration/DataEase.md @@ -42,10 +42,10 @@ | **准备内容** | **版本要求** | | :-------------------- | :----------------------------------------------------------- | -| IoTDB | 版本无要求，安装请参考 IoTDB [部署指导](https://www.timecho.com/docs/zh/UserGuide/latest/Deployment-and-Maintenance/IoTDB-Package_timecho.html) | +| IoTDB | 版本无要求，安装请参考 IoTDB [部署指导](../QuickStart/QuickStart_apache.md) | | JDK | 建议 JDK11 及以上版本（推荐部署 JDK17 及以上版本） | -| DataEase | 要求 v1 系列 v1.18 版本，安装请参考 DataEase 官网[安装指导](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)（暂不支持 v2.x，其他版本适配请联系天谋商务） | -| DataEase-IoTDB 连接器 | 请联系天谋商务获取 | +| DataEase | 要求 v1 系列 v1.18 版本，安装请参考 DataEase 官网[安装指导](https://dataease.io/docs/v2/installation/offline_INSTL_and_UPG/)（暂不支持 v2.x，其他版本适配请联系工作人员） | +| DataEase-IoTDB 连接器 | 请联系工作人员获取 | ## 3. 安装步骤 diff --git a/src/zh/UserGuide/latest/Ecosystem-Integration/Thingsboard.md b/src/zh/UserGuide/latest/Ecosystem-Integration/Thingsboard.md index 404e1f368..d3bdd017a 100644 --- a/src/zh/UserGuide/latest/Ecosystem-Integration/Thingsboard.md +++ b/src/zh/UserGuide/latest/Ecosystem-Integration/Thingsboard.md @@ -41,7 +41,7 @@ | 准备内容 | 版本要求 | | :-------------------------- | :----------------------------------------------------------- | | JDK | 要求已安装 17 及以上版本，具体下载请查看 [Oracle 官网](https://www.oracle.com/java/technologies/downloads/) | -| IoTDB | 要求已安装 V1.3.0 及以上版本，具体安装过程请参考[ 部署指导](https://www.timecho.com/docs/zh/UserGuide/latest/Deployment-and-Maintenance/IoTDB-Package_timecho.html) | +| IoTDB | 要求已安装 V1.3.0 及以上版本，具体安装过程请参考[ 部署指导](../QuickStart/QuickStart_apache.md) | | ThingsBoard（IoTDB 适配版） | 安装包请联系商务获取，具体安装步骤参见下文 | ## 3. 安装步骤 diff --git a/src/zh/UserGuide/latest/SQL-Manual/UDF-Libraries_apache.md b/src/zh/UserGuide/latest/SQL-Manual/UDF-Libraries_apache.md index 834a767ae..bea5273a0 100644 --- a/src/zh/UserGuide/latest/SQL-Manual/UDF-Libraries_apache.md +++ b/src/zh/UserGuide/latest/SQL-Manual/UDF-Libraries_apache.md @@ -30,8 +30,8 @@ 1. 请获取与 IoTDB 版本兼容的 UDF 函数库 JAR 包的压缩包。 | UDF 安装包 | 支持的 IoTDB 版本 | 下载链接 | | -------------------- | ------------- | --------- | - | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系天谋商务获取 | - | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系天谋商务获取 | + | apache-UDF-1.3.3.zip | V1.3.3及以上 | 请联系商业支持获取 | + | apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | 请联系商业支持获取 | 2. 将获取的压缩包中的 library-udf.jar 文件放置在 IoTDB 集群所有节点的 `/ext/udf` 的目录下 3. 在 IoTDB 的 SQL 命令行终端（CLI）的 SQL 操作界面中，执行下述相应的函数注册语句。 4. 批量注册：两种注册方式：注册脚本 或 SQL汇总语句 diff --git a/src/zh/UserGuide/latest/Tools-System/CLI_apache.md b/src/zh/UserGuide/latest/Tools-System/CLI_apache.md index 9e81896d7..7f85819a8 100644 --- a/src/zh/UserGuide/latest/Tools-System/CLI_apache.md +++ b/src/zh/UserGuide/latest/Tools-System/CLI_apache.md @@ -76,7 +76,7 @@ Successfully login at 127.0.0.1:6667 | -h `` | string 类型 | 否 | IoTDB 客户端连接 IoTDB 服务器的 IP 地址， 默认使用：127.0.0.1。 | -h 127.0.0.1 | | -p `` | int 类型 | 否 | IoTDB 客户端连接服务器的端口号，IoTDB 默认使用 6667。 | -p 6667 | | -u `` | string 类型 | 否 | IoTDB 客户端连接服务器所使用的用户名，默认使用 root。 | -u root | -| -pw `` | string 类型 | 否 | IoTDB 客户端连接服务器所使用的密码，默认使用 TimechoDB@2021（V2.0.6版本之前为root）。 | -pw root | +| -pw `` | string 类型 | 否 | IoTDB 客户端连接服务器所使用的密码，默认使用 root。 | -pw root | | -sql_dialect `` | string 类型 | 否 | 目前可选 tree（树模型） 、table（表模型），默认 tree | -sql_dialect table | | -e `` | string 类型 | 否 | 在不进入客户端输入模式的情况下，批量操作 IoTDB。 | -e "show databases" | | -c | 空 | 否 | 如果服务器设置了 rpc_thrift_compression_enable=true， 则 CLI 必须使用 -c | -c | diff --git a/src/zh/UserGuide/latest/Tools-System/Monitor-Tool_apache.md b/src/zh/UserGuide/latest/Tools-System/Monitor-Tool_apache.md index b9b591923..065bd3cf5 100644 --- a/src/zh/UserGuide/latest/Tools-System/Monitor-Tool_apache.md +++ b/src/zh/UserGuide/latest/Tools-System/Monitor-Tool_apache.md @@ -104,7 +104,7 @@ static_configs: ## 4. Apache IoTDB Dashboard -`Apache IoTDB Dashboard`是 TimechoDB 的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。 +`Apache IoTDB Dashboard`是 IoTDB 企业版的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。 ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png) diff --git a/src/zh/UserGuide/latest/User-Manual/Load-Balance.md b/src/zh/UserGuide/latest/User-Manual/Load-Balance.md index 3793290a3..756488b8a 100644 --- a/src/zh/UserGuide/latest/User-Manual/Load-Balance.md +++ b/src/zh/UserGuide/latest/User-Manual/Load-Balance.md @@ -133,18 +133,18 @@ echo "192.168.1.3 iotdb-1" >> /etc/hosts ``` #### 1.3.2 扩容操作 -1. 为确保您获取的 TimechoDB 安装包完整且正确，在执行安装部署前建议您进行 SHA512 校验。 +1. 为确保您获取的 IoTDB 安装包完整且正确，在执行安装部署前建议您进行 SHA512 校验。 2. 解压安装包并进入安装目录 ```Shell -unzip timechodb-{version}-bin.zip -cd timechodb-{version}-bin +unzip apache-iotdb-{version}-bin.zip +cd apache-iotdb-{version}-bin ``` 3. 修改相应配置 ```Shell -cd timechodb-{version}-bin/conf +cd apache-iotdb-{version}-bin/conf vim iotdb-system.properies ``` @@ -171,10 +171,10 @@ vim iotdb-system.properies ```Shell # Linux或MACOS系统 - ./timechodb-{version}-bin/sbin/start-cli.sh + ./apache-iotdb-{version}-bin/sbin/start-cli.sh # windows系统 - ./timechodb-{version}-bin/sbin/start-cli.bat + ./apache-iotdb-{version}-bin/sbin/start-cli.bat ``` 6. 执行命令进行验证 diff --git a/src/zh/UserGuide/latest/User-Manual/Maintenance-statement_apache.md b/src/zh/UserGuide/latest/User-Manual/Maintenance-statement_apache.md index b73a3691f..ac80d3f31 100644 --- a/src/zh/UserGuide/latest/User-Manual/Maintenance-statement_apache.md +++ b/src/zh/UserGuide/latest/User-Manual/Maintenance-statement_apache.md @@ -7,9 +7,9 @@ to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at - + http://www.apache.org/licenses/LICENSE-2.0 - + Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY @@ -194,12 +194,12 @@ showQueriesStatement - **datanodeid**：发起查询语句的 DataNode 的ID - **elapsedtime**：查询的执行耗时，单位是秒 - **statement**：查询的 SQL 语句 - + #### 示例： ```SQL -IoTDB> SHOW QUERIES WHERE elapsedtime > 0.003 +IoTDB> SHOW QUERIES WHERE elapsedtime > 0.003 ``` 执行结果如下： @@ -318,7 +318,7 @@ IoTDB> SHOW SERVICES ON 1 ```SQL showDiskUsageStatement - : SHOW DISK_USAGE FROM pathPattern + : SHOW DISK_USAGE FROM pathPattern whereClause? orderByClause? rowPaginationClause? @@ -400,7 +400,7 @@ setConfigurationStatement propertyAssignments : property (',' property)* ; - + property : identifier EQ propertyValue ; @@ -439,7 +439,7 @@ IoTDB> SET CONFIGURATION 'disk_space_warning_threshold'='0.05','heartbeat_interv loadConfigurationStatement : LOAD CONFIGURATION localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -469,8 +469,8 @@ IoTDB> LOAD CONFIGURATION ON LOCAL; ```SQL setSystemStatusStatement : SET SYSTEM TO (READONLY | RUNNING) localOrClusterMode? - ; - + ; + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -556,7 +556,7 @@ IoTDB> FLUSH root.ln TRUE ON LOCAL; startRepairDataStatement : START REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -587,7 +587,7 @@ IoTDB> START REPAIR DATA ON CLUSTER; stopRepairDataStatement : STOP REPAIR DATA localOrClusterMode? ; - + localOrClusterMode : (ON (LOCAL | CLUSTER)) ; @@ -672,13 +672,13 @@ debug select * from root.ln.**; 2. 观察`log_datanode_query_debug.log` 的日志内容，查看查询涉及到的文件 scan 信息。 ```Bash -2026-03-24 10:06:18,755 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: root.ln.wf01.wt01.temperature in file: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile -2026-03-24 10:06:18,757 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: root.ln.wf01.wt01, all sensors: [temperature] -2026-03-24 10:06:18,758 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: root.ln.wf01.wt01.temperature metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=0, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=DOUBLE, statistics=startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null]}. -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:97 - Modifications size is 0 for file Path: /home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:109 - After modification Chunk meta data list is: -2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:110 - measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null -2026-03-24 10:06:18,760 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile', regionId=13, timePartitionId=2932, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=27} +2026-03-24 10:06:18,755 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: root.ln.wf01.wt01.temperature in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile +2026-03-24 10:06:18,757 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: root.ln.wf01.wt01, all sensors: [temperature] +2026-03-24 10:06:18,758 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: root.ln.wf01.wt01.temperature metadata in file: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile from cache: TimeseriesMetadata{timeSeriesMetadataType=0, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=DOUBLE, statistics=startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null]}. +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:97 - Modifications size is 0 for file Path: /home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:109 - After modification Chunk meta data list is: +2026-03-24 10:06:18,759 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.d.r.r.c.m.DiskChunkMetadataLoader:110 - measurementId: temperature, datatype: DOUBLE, version: 0, Statistics: startTime: 1773824951259 endTime: 1773824951259 count: 1 [minValue:12.9,maxValue:12.9,firstValue:12.9,lastValue:12.9,sumValue:12.9], deleteIntervalList: null +2026-03-24 10:06:18,760 [Query-Worker-Thread-3$20260324_020618_00052_1.1.0.0] INFO o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/apache-iotdb/data/datanode/data/sequence/root.ln/13/2932/1773824951611-1-0-0.tsfile', regionId=13, timePartitionId=2932, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=27} 2026-03-24 10:06:18,761 [pool-69-IoTDB-ClientRPC-Processor-1$20260324_020618_00052_1] INFO o.a.i.d.q.p.Coordinator:902 - debug select * from root.ln.** ``` diff --git a/src/zh/UserGuide/latest/User-Manual/Streaming_apache.md b/src/zh/UserGuide/latest/User-Manual/Streaming_apache.md index ef5c0f4d7..0a9ce0a34 100644 --- a/src/zh/UserGuide/latest/User-Manual/Streaming_apache.md +++ b/src/zh/UserGuide/latest/User-Manual/Streaming_apache.md @@ -567,7 +567,7 @@ WITH SOURCE ( -- 默认的 IoTDB 数据抽取插件 'source' = 'iotdb-source', -- 路径前缀，只有能够匹配该路径前缀的数据才会被抽取，用作后续的处理和发送 - 'source.pattern' = 'root.timecho', + 'source.pattern' = 'root.iotdb', -- 描述被抽取的历史数据的时间范围，表示最早时间 'source.history.start-time' = '2011.12.03T10:15:30+01:00', -- 描述被抽取的历史数据的时间范围，表示最晚时间