You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
+31-3Lines changed: 31 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,6 +57,35 @@ Use the hostname for `cn_internal_address` and `dn_internal_address` in IoTDB co
57
57
58
58
2. Configure the operating system environment according to [Environment Requirement](../Deployment-and-Maintenance/Environment-Requirements.md)）
59
59
60
+
### 2.1 Pre-installation Check
61
+
62
+
To ensure the IoTDB Enterprise Edition installation package you obtained is complete and authentic, we recommend performing an SHA512 verification before proceeding with the installation and deployment.
63
+
64
+
#### Preparation:
65
+
66
+
- Obtain the officially released SHA512 checksum: Find the "SHA512 Checksum" corresponding to each version in the [Release History](../IoTDB-Introduction/Release-history_timecho.md) document.
67
+
68
+
#### Verification Steps (Linux as an Example):
69
+
70
+
1. Open the terminal and navigate to the directory where the installation package is stored (e.g., /data/iotdb):
71
+
```Bash
72
+
cd /data/iotdb
73
+
```
74
+
2. Execute the following command to calculate the hash value:
75
+
```Bash
76
+
sha512sum timechodb-{version}-bin.zip
77
+
```
78
+
3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):
79
+
80
+
81
+
82
+
4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment operations in accordance with the procedures below.
83
+
84
+
#### Notes:
85
+
86
+
- If the verification results do not match, please contact Timecho Team to re-obtain the installation package.
87
+
- If a "file not found" prompt appears during verification, check whether the file path is correct or if the installation package has been fully downloaded.
88
+
60
89
## 3. Installation Steps
61
90
62
91
Taking a cluster with three Linux servers with the following information as example:
@@ -124,7 +153,7 @@ Set the following parameters in `./conf/iotdb-system.properties`. Refer to `./co
| dn_rpc_address | Address for the client RPC service | 0.0.0.0 | The IPV4 address or host name of the server where it is located, and it is recommended to use the IPV4 address | iotdb-1 | iotdb-2 | iotdb-3 | Effective after restarting the service. |
156
+
| dn_rpc_address | Address for the client RPC service | 0.0.0.0 | The IPV4 address or host name of the server where it is located, and it is recommended to use the IPV4 address | iotdb-1 | iotdb-2 | iotdb-3 | Effective after restarting the service. |
128
157
| dn_rpc_port | Port for the client RPC service | 6667 | 6667 | 6667 | 6667 | 6667 | Effective after restarting the service. |
129
158
| dn_internal_address | Address used for internal communication within the cluster | 127.0.0.1 | Server's IPv4 address or hostname. Use hostname to avoid issues when the IP changes. | iotdb-1 | iotdb-2 | iotdb-3 | This parameter cannot be modified after the first startup. |
130
159
| dn_internal_port | Port used for internal communication within the cluster | 10730 | 10730 | 10730 | 10730 | 10730 | This parameter cannot be modified after the first startup. |
@@ -175,8 +204,7 @@ On each server, navigate to the `sbin` directory and start the DataNode:
175
204
176
205
```Bash
177
206
show system info
178
-
```
179
-
207
+
```
180
208
181
209
3. Copy the returned machine codes of all nodes in the cluster (displayed as a green string) and send it to the Timecho team:
Copy file name to clipboardExpand all lines: src/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+37-10Lines changed: 37 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,36 @@ Use the hostname for `cn_internal_address` and `dn_internal_address` in IoTDB co
48
48
49
49
## 2. Installation Steps
50
50
51
-
### 2.1 Extract Installation Package
51
+
### 2.1 Pre-installation Check
52
+
53
+
To ensure the IoTDB Enterprise Edition installation package you obtained is complete and authentic, we recommend performing an SHA512 verification before proceeding with the installation and deployment.
54
+
55
+
#### Preparation:
56
+
57
+
- Obtain the officially released SHA512 checksum: Find the "SHA512 Checksum" corresponding to each version in the [Release History](../IoTDB-Introduction/Release-history_timecho.md) document.
58
+
59
+
#### Verification Steps (Linux as an Example):
60
+
61
+
1. Open the terminal and navigate to the directory where the installation package is stored (e.g., /data/iotdb):
62
+
```Bash
63
+
cd /data/iotdb
64
+
```
65
+
2. Execute the following command to calculate the hash value:
66
+
```Bash
67
+
sha512sum timechodb-{version}-bin.zip
68
+
```
69
+
3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):
70
+
71
+
72
+
73
+
4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment operations in accordance with the procedures below.
74
+
75
+
#### Notes:
76
+
77
+
- If the verification results do not match, please contact Timecho Team to re-obtain the installation package.
78
+
- If a "file not found" prompt appears during verification, check whether the file path is correct or if the installation package has been fully downloaded.
79
+
80
+
### 2.2 Extract Installation Package
52
81
53
82
Unzip the installation package and navigate to the directory:
| MEMORY_SIZE | Total memory allocated for the node | Empty | As needed | Save changes without immediate execution; modifications take effect after service restart. |
72
101
73
-
#### 2.2.2 General Configuration
102
+
#### 2.3.2 General Configuration
74
103
75
104
Set the following parameters in`conf/iotdb-system.properties`. Refer to `conf/iotdb-system.properties.template`for a complete list.
76
105
@@ -104,7 +133,7 @@ Set the following parameters in `conf/iotdb-system.properties`. Refer to `conf/i
104
133
| dn_schema_region_consensus_port | Port used for metadata replica consensus protocol communication | 10760 | 10760 | This parameter cannot be modified after the first startup. |
105
134
| dn_seed_config_node | Address of the ConfigNode for registering and joining the cluster. (e.g.,`cn_internal_address:cn_internal_port`) | 127.0.0.1:10710 | Use `cn_internal_address:cn_internal_port`| This parameter cannot be modified after the first startup. |
106
135
107
-
### 2.3 Start ConfigNode
136
+
### 2.4 Start ConfigNode
108
137
109
138
Navigate to the `sbin` directory and start ConfigNode:
110
139
@@ -116,15 +145,15 @@ If the startup fails, refer to the [Common Issues](#3-common-issues)。 section
116
145
117
146
118
147
119
-
### 2.4 Start DataNode
148
+
### 2.5 Start DataNode
120
149
121
150
Navigate to the `sbin` directory of IoTDB and start the DataNode:
122
151
123
152
```Bash
124
153
./sbin/start-datanode.sh -d # The "-d" flag starts the process in the background.
- Navigate to the `activation` folder and copy the `system_info` file.
170
198
- Send the `system_info` file to the Timecho team.
171
199
- Place the license file provided by the Timecho team into the corresponding `activation` folder for each node.
172
200
173
-
174
-
### 2.6 Verify Activation
201
+
### 2.7 Verify Activation
175
202
176
203
In the CLI, you can check the activation status by running the `show activation` command. Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated.
Copy file name to clipboardExpand all lines: src/UserGuide/Master/Table/IoTDB-Introduction/Release-history_apache.md
+23-1Lines changed: 23 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,9 +20,25 @@
20
20
-->
21
21
# Release History
22
22
23
+
24
+
## V2.0.5
25
+
26
+
> Release Date: 2025.08.21
27
+
28
+
V2.0.5, as the official release of the Dual-Model Tree-Table system, primarily introduces the tree-to-table view, window functions for the table model, the aggregate function approx_most_frequent, and supports LEFT & RIGHT JOIN as well as ASOF LEFT JOIN. The AINode now includes two new built-in models, Timer-XL and Timer-Sundial, and supports inference capabilities for both tree and table models. Additionally, this version brings comprehensive improvements to database monitoring, performance, and stability. The specific updates are as follows:
29
+
30
+
***Query Module**: Supports manual creation of tree-to-table views
31
+
***Query Module**: Adds window functions for the table model
32
+
***Query Module**: Adds the aggregate function approx_most_frequent for the table model
33
+
***Query Module**: Extends JOIN functionality for the table model, supporting LEFT & RIGHT JOIN and ASOF LEFT JOIN
34
+
***Query Module**: The table model now supports row pattern recognition, enabling the capture of continuous data for analysis and computation
35
+
***Storage Module**: Adds multiple system tables for the table model, such as VIEWS (table view information) and MODELS (model information)
36
+
***AI Module**: AINode adds two new built-in models, Timer-XL and Timer-Sundial
37
+
***AI Module**: AINode supports inference functions for both tree and table models
38
+
23
39
## V2.0.4
24
40
25
-
> Release Time: 2025.07.09
41
+
> Release Date: 2025.07.09
26
42
27
43
V2.0.4 serves as the official release of the dual-model system for tree and table structures. The table model primarily introduces user-defined table functions (UDTF) and multiple built-in table functions, adds the aggregate function approx_count_distinct, and supports ASOF INNER JOIN for time columns. Additionally, script tools have been categorized and reorganized, with Windows-specific scripts separated. The release also includes comprehensive improvements in database monitoring, performance, and stability. The detailed updates are as follows:
28
44
@@ -106,6 +122,12 @@ V2.0.1-beta introduces dual tree-table model configuration, supporting standard
106
122
* **Ecosystem Integration**:
107
123
* Kubernetes Operator support
108
124
125
+
## V1.3.5
126
+
127
+
> Release Date: 2025.09.12
128
+
129
+
V1.3.5, as a bugfix release based on the previous 1.3.x versions, primarily adjusts the user password encryption algorithm to further enhance data access security. It also optimizes kernel stability and addresses issues reported by the community.
0 commit comments