) which you need to install in your project if you want to use the feature.
To start (and stop) an IoTDB Database in a Docker container simply do:
+
```python
class MyTestCase(unittest.TestCase):
@@ -484,13 +503,15 @@ by default it will load the image `apache/iotdb:latest`, if you want a specific
## IoTDB DBAPI
-IoTDB DBAPI implements the Python DB API 2.0 specification (https://peps.python.org/pep-0249/), which defines a common
+IoTDB DBAPI implements the Python DB API 2.0 specification (), which defines a common
interface for accessing databases in Python.
### Examples
-+ Initialization
+
+- Initialization
The initialized parameters are consistent with the session part (except for the sqlalchemy_mode).
+
```python
from iotdb.dbapi import connect
@@ -501,23 +522,27 @@ password_ = "root"
conn = connect(ip, port_, username_, password_,fetch_size=1024,zone_id="UTC+8",sqlalchemy_mode=False)
cursor = conn.cursor()
```
-+ simple SQL statement execution
+
+- simple SQL statement execution
+
```python
cursor.execute("SELECT ** FROM root")
for row in cursor.fetchall():
print(row)
```
-+ execute SQL with parameter
+- execute SQL with parameter
IoTDB DBAPI supports pyformat style parameters
+
```python
cursor.execute("SELECT ** FROM root WHERE time < %(time)s",{"time":"2017-11-01T00:08:00.000"})
for row in cursor.fetchall():
print(row)
```
-+ execute SQL with parameter sequences
+- execute SQL with parameter sequences
+
```python
seq_of_parameters = [
{"timestamp": 1, "temperature": 1},
@@ -530,17 +555,21 @@ sql = "insert into root.cursor(timestamp,temperature) values(%(timestamp)s,%(tem
cursor.executemany(sql,seq_of_parameters)
```
-+ close the connection and cursor
+- close the connection and cursor
+
```python
cursor.close()
conn.close()
```
## IoTDB SQLAlchemy Dialect (Experimental)
+
The SQLAlchemy dialect of IoTDB is written to adapt to Apache Superset.
This part is still being improved.
Please do not use it in the production environment!
+
### Mapping of the metadata
+
The data model used by SQLAlchemy is a relational data model, which describes the relationships between different entities through tables.
While the data model of IoTDB is a hierarchical data model, which organizes the data through a tree structure.
In order to adapt IoTDB to the dialect of SQLAlchemy, the original data model in IoTDB needs to be reorganized.
@@ -554,25 +583,27 @@ The metadata in the IoTDB are：
4. Measurement
The metadata in the SQLAlchemy are：
+
1. Schema
2. Table
3. Column
The mapping relationship between them is：
-| The metadata in the SQLAlchemy | The metadata in the IoTDB |
-| -------------------- | -------------------------------------------- |
-| Schema | Database |
-| Table | Path ( from database to entity ) + Entity |
-| Column | Measurement |
+| The metadata in the SQLAlchemy | The metadata in the IoTDB |
+| ------------------------------ | ----------------------------------------- |
+| Schema | Database |
+| Table | Path ( from database to entity ) + Entity |
+| Column | Measurement |
The following figure shows the relationship between the two more intuitively:
### Data type mapping
+
| data type in IoTDB | data type in SQLAlchemy |
-|--------------------|-------------------------|
+| ------------------ | ----------------------- |
| BOOLEAN | Boolean |
| INT32 | Integer |
| INT64 | BigInteger |
@@ -583,7 +614,7 @@ The following figure shows the relationship between the two more intuitively:
### Example
-+ execute statement
+- execute statement
```python
from sqlalchemy import create_engine
@@ -595,7 +626,7 @@ for row in result.fetchall():
print(row)
```
-+ ORM (now only simple queries are supported)
+- ORM (now only simple queries are supported)
```python
from sqlalchemy import create_engine, Column, Float, BigInteger, MetaData
@@ -626,49 +657,39 @@ for row in res:
print(row)
```
-
## Developers
### Introduction
This is an example of how to connect to IoTDB with python, using the thrift rpc interfaces. Things are almost the same on Windows or Linux, but pay attention to the difference like path separator.
-
-
### Prerequisites
Python3.7 or later is preferred.
You have to install Thrift (0.11.0 or later) to compile our thrift file into python code. Below is the official tutorial of installation, eventually, you should have a thrift executable.
-```
-http://thrift.apache.org/docs/install/
-```
+
Before starting you need to install `requirements_dev.txt` in your python environment, e.g. by calling
+
```shell
pip install -r requirements_dev.txt
```
-
-
### Compile the thrift library and Debug
-In the root of IoTDB's source code folder, run `mvn clean generate-sources -pl iotdb-client/client-py -am`.
+In the root of IoTDB's source code folder, run `mvn clean generate-sources -pl iotdb-client/client-py -am`.
This will automatically delete and repopulate the folder `iotdb/thrift` with the generated thrift files.
This folder is ignored from git and should **never be pushed to git!**
**Notice** Do not upload `iotdb/thrift` to the git repo.
-
-
-
### Session Client & Example
We packed up the Thrift interface in `client-py/src/iotdb/Session.py` (similar with its Java counterpart), also provided an example file `client-py/src/SessionExample.py` of how to use the session module. please read it carefully.
-
Or, another simple example:
```python
@@ -684,8 +705,6 @@ zone = session.get_time_zone()
session.close()
```
-
-
### Tests
Please add your custom tests in `tests` folder.
@@ -694,15 +713,11 @@ To run all defined tests just type `pytest .` in the root folder.
**Notice** Some tests need docker to be started on your system as a test instance is started in a docker container using [testcontainers](https://testcontainers-python.readthedocs.io/en/latest/index.html).
-
-
### Futher Tools
[black](https://pypi.org/project/black/) and [flake8](https://pypi.org/project/flake8/) are installed for autoformatting and linting.
Both can be run by `black .` or `flake8 .` respectively.
-
-
## Releasing
To do a release just ensure that you have the right set of generated thrift files.
@@ -710,23 +725,18 @@ Then run linting and auto-formatting.
Then, ensure that all tests work (via `pytest .`).
Then you are good to go to do a release!
-
-
### Preparing your environment
First, install all necessary dev dependencies via `pip install -r requirements_dev.txt`.
-
-
### Doing the Release
There is a convenient script `release.sh` to do all steps for a release.
Namely, these are
-* Remove all transient directories from last release (if exists)
-* (Re-)generate all generated sources via mvn
-* Run Linting (flake8)
-* Run Tests via pytest
-* Build
-* Release to pypi
-
+- Remove all transient directories from last release (if exists)
+- (Re-)generate all generated sources via mvn
+- Run Linting (flake8)
+- Run Tests via pytest
+- Build
+- Release to pypi
diff --git a/src/UserGuide/V2.0.1/Tree/API/Programming-Rust-Native-API.md b/src/UserGuide/V1.3.3/API/Programming-Rust-Native-API.md
similarity index 63%
rename from src/UserGuide/V2.0.1/Tree/API/Programming-Rust-Native-API.md
rename to src/UserGuide/V1.3.3/API/Programming-Rust-Native-API.md
index f58df68fc..4ec73a52b 100644
--- a/src/UserGuide/V2.0.1/Tree/API/Programming-Rust-Native-API.md
+++ b/src/UserGuide/V1.3.3/API/Programming-Rust-Native-API.md
@@ -1,78 +1,77 @@
# Rust Native API Native API
-IoTDB uses Thrift as a cross language RPC framework, so access to IoTDB can be achieved through the interface provided by Thrift.
+IoTDB uses Thrift as a cross language RPC framework, so access to IoTDB can be achieved through the interface provided by Thrift.
This document will introduce how to generate a native Rust interface that can access IoTDB.
## Dependents
- * JDK >= 1.8
- * Rust >= 1.0.0
- * thrift 0.14.1
- * Linux、Macos or like unix
- * Windows+bash
+- JDK >= 1.8
+- Rust >= 1.0.0
+- thrift 0.14.1
+- Linux、Macos or like unix
+- Windows+bash
Thrift (0.14.1 or higher) must be installed to compile Thrift files into Rust code. The following is the official installation tutorial, and in the end, you should receive a Thrift executable file.
-```
-http://thrift.apache.org/docs/install/
-```
+
## Compile the Thrift library and generate the Rust native interface
1. Find the `pom.xml` file in the root directory of the IoTDB source code folder.
2. Open the `pom.xml` file and find the following content:
+
```xml
-
- generate-thrift-sources-python
- generate-sources
-
- compile
-
-
- py
- ${project.build.directory}/generated-sources-python/
-
-
+
+ generate-thrift-sources-python
+ generate-sources
+
+ compile
+
+
+ py
+ ${project.build.directory}/generated-sources-python/
+
+
```
+
3. Duplicate this block and change the `id`, `generator` and `outputDirectory` to this:
+
```xml
-
- generate-thrift-sources-rust
- generate-sources
-
- compile
-
-
- rs
- ${project.build.directory}/generated-sources-rust/
-
-
+
+ generate-thrift-sources-rust
+ generate-sources
+
+ compile
+
+
+ rs
+ ${project.build.directory}/generated-sources-rust/
+
+
```
+
4. In the root directory of the IoTDB source code folder，run `mvn clean generate-sources`.
-This command will automatically delete the files in `iotdb/iotdb-protocol/thrift/target` and `iotdb/iotdb-protocol/thrift-commons/target`, and repopulate the folder with the newly generated files.
-The newly generated Rust sources will be located in `iotdb/iotdb-protocol/thrift/target/generated-sources-rust` in the various modules of the `iotdb-protocol` module.
+ This command will automatically delete the files in `iotdb/iotdb-protocol/thrift/target` and `iotdb/iotdb-protocol/thrift-commons/target`, and repopulate the folder with the newly generated files.
+ The newly generated Rust sources will be located in `iotdb/iotdb-protocol/thrift/target/generated-sources-rust` in the various modules of the `iotdb-protocol` module.
## Using the Rust native interface
@@ -80,7 +79,7 @@ Copy `iotdb/iotdb-protocol/thrift/target/generated-sources-rust/` and `iotdb/iot
## RPC interface
-```
+```cpp
// open a session
TSOpenSessionResp openSession(1:TSOpenSessionReq req);
@@ -96,7 +95,7 @@ TSStatus executeBatchStatement(1:TSExecuteBatchStatementReq req);
// execute query SQL statement
TSExecuteStatementResp executeQueryStatement(1:TSExecuteStatementReq req);
-// execute insert, delete and update SQL statement
+// execute insert, delete and update SQL statement
TSExecuteStatementResp executeUpdateStatement(1:TSExecuteStatementReq req);
// fetch next query result
@@ -105,7 +104,7 @@ TSFetchResultsResp fetchResults(1:TSFetchResultsReq req)
// fetch meta data
TSFetchMetadataResp fetchMetadata(1:TSFetchMetadataReq req)
-// cancel a query
+// cancel a query
TSStatus cancelOperation(1:TSCancelOperationReq req);
// close a query dataset
diff --git a/src/UserGuide/V2.0.1/Tree/API/RestServiceV1.md b/src/UserGuide/V1.3.3/API/RestServiceV1.md
similarity index 57%
rename from src/UserGuide/V2.0.1/Tree/API/RestServiceV1.md
rename to src/UserGuide/V1.3.3/API/RestServiceV1.md
index 775235fed..9d46c3c65 100644
--- a/src/UserGuide/V2.0.1/Tree/API/RestServiceV1.md
+++ b/src/UserGuide/V1.3.3/API/RestServiceV1.md
@@ -1,25 +1,23 @@
-# RESTful API V1(Not Recommend)
+# RESTful API V1(Not Recommend)
+
IoTDB's RESTful services can be used for query, write, and management operations, using the OpenAPI standard to define interfaces and generate frameworks.
## Enable RESTful Services
@@ -33,6 +31,7 @@ RESTful services are disabled by default.
```
## Authentication
+
Except the liveness probe API `/ping`, RESTful services use the basic authentication. Each URL request needs to carry `'Authorization': 'Basic ' + base64.encode(username + ':' + password)`.
The username used in the following examples is: `root`, and password is: `root`.
@@ -48,24 +47,26 @@ Authorization: Basic cm9vdDpyb290
HTTP Status Code：`401`
HTTP response body:
- ```json
- {
- "code": 600,
- "message": "WRONG_LOGIN_PASSWORD_ERROR"
- }
- ```
+
+ ```json
+ {
+ "code": 600,
+ "message": "WRONG_LOGIN_PASSWORD_ERROR"
+ }
+ ```
- If the `Authorization` header is missing，the following error is returned:
HTTP Status Code：`401`
HTTP response body:
- ```json
- {
- "code": 603,
- "message": "UNINITIALIZED_AUTH_ERROR"
- }
- ```
+
+ ```json
+ {
+ "code": 603,
+ "message": "UNINITIALIZED_AUTH_ERROR"
+ }
+ ```
## Interface
@@ -79,7 +80,7 @@ Request path: `http://ip:port/ping`
The user name used in the example is: root, password: root
-Example request:
+Example request:
```shell
$ curl http://127.0.0.1:18080/ping
@@ -92,10 +93,10 @@ Response status codes:
Response parameters:
-|parameter name |parameter type |parameter describe|
-|:--- | :--- | :---|
-|code | integer | status code |
-| message | string | message |
+| parameter name | parameter type | parameter describe |
+| :------------- | :------------- | :----------------- |
+| code | integer | status code |
+| message | string | message |
Sample response:
@@ -131,18 +132,18 @@ Request path: `http://ip:port/rest/v1/query`
Parameter Description:
-| parameter name | parameter type | required | parameter description |
-|----------------| -------------- | -------- | ------------------------------------------------------------ |
-| sql | string | yes | |
-| rowLimit | integer | no | The maximum number of rows in the result set that can be returned by a query.
If this parameter is not set, the `rest_query_default_row_size_limit` of the configuration file will be used as the default value.
When the number of rows in the returned result set exceeds the limit, the status code `411` will be returned. |
+| parameter name | parameter type | required | parameter description |
+| -------------- | -------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| sql | string | yes | |
+| rowLimit | integer | no | The maximum number of rows in the result set that can be returned by a query.
If this parameter is not set, the `rest_query_default_row_size_limit` of the configuration file will be used as the default value.
When the number of rows in the returned result set exceeds the limit, the status code `411` will be returned. |
Response parameters:
-| parameter name | parameter type | parameter description |
-|----------------| -------------- | ------------------------------------------------------------ |
-| expressions | array | Array of result set column names for data query, `null` for metadata query |
-| columnNames | array | Array of column names for metadata query result set, `null` for data query |
-| timestamps | array | Timestamp column, `null` for metadata query |
+| parameter name | parameter type | parameter description |
+| -------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| expressions | array | Array of result set column names for data query, `null` for metadata query |
+| columnNames | array | Array of column names for metadata query result set, `null` for data query |
+| timestamps | array | Timestamp column, `null` for metadata query |
| values | array | A two-dimensional array, the first dimension has the same length as the result set column name array, and the second dimension array represents a column of the result set |
**Examples:**
@@ -151,38 +152,24 @@ Tip: Statements like `select * from root.xx.**` are not recommended because thos
**Expression query**
- ```shell
- curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X POST --data '{"sql":"select s3, s4, s3 + 1 from root.sg27 limit 2"}' http://127.0.0.1:18080/rest/v1/query
- ````
+```shell
+curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X POST --data '{"sql":"select s3, s4, s3 + 1 from root.sg27 limit 2"}' http://127.0.0.1:18080/rest/v1/query
+```
+
Response instance
- ```json
- {
- "expressions": [
- "root.sg27.s3",
- "root.sg27.s4",
- "root.sg27.s3 + 1"
- ],
- "columnNames": null,
- "timestamps": [
- 1635232143960,
- 1635232153960
- ],
- "values": [
- [
- 11,
- null
- ],
- [
- false,
- true
- ],
- [
- 12.0,
- null
- ]
- ]
- }
- ```
+
+```json
+{
+ "expressions": ["root.sg27.s3", "root.sg27.s4", "root.sg27.s3 + 1"],
+ "columnNames": null,
+ "timestamps": [1635232143960, 1635232153960],
+ "values": [
+ [11, null],
+ [false, true],
+ [12.0, null]
+ ]
+}
+```
**Show child paths**
@@ -193,16 +180,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "columnNames": [
- "child paths"
- ],
+ "columnNames": ["child paths"],
"timestamps": null,
- "values": [
- [
- "root.sg27",
- "root.sg28"
- ]
- ]
+ "values": [["root.sg27", "root.sg28"]]
}
```
@@ -215,16 +195,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "columnNames": [
- "child nodes"
- ],
+ "columnNames": ["child nodes"],
"timestamps": null,
- "values": [
- [
- "sg27",
- "sg28"
- ]
- ]
+ "values": [["sg27", "sg28"]]
}
```
@@ -237,20 +210,11 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "columnNames": [
- "database",
- "ttl"
- ],
+ "columnNames": ["database", "ttl"],
"timestamps": null,
"values": [
- [
- "root.sg27",
- "root.sg28"
- ],
- [
- null,
- null
- ]
+ ["root.sg27", "root.sg28"],
+ [null, null]
]
}
```
@@ -264,19 +228,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "columnNames": [
- "database",
- "ttl"
- ],
+ "columnNames": ["database", "ttl"],
"timestamps": null,
- "values": [
- [
- "root.sg27"
- ],
- [
- null
- ]
- ]
+ "values": [["root.sg27"], [null]]
}
```
@@ -339,54 +293,14 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
],
"timestamps": null,
"values": [
- [
- "root.sg27.s3",
- "root.sg27.s4",
- "root.sg28.s3",
- "root.sg28.s4"
- ],
- [
- null,
- null,
- null,
- null
- ],
- [
- "root.sg27",
- "root.sg27",
- "root.sg28",
- "root.sg28"
- ],
- [
- "INT32",
- "BOOLEAN",
- "INT32",
- "BOOLEAN"
- ],
- [
- "RLE",
- "RLE",
- "RLE",
- "RLE"
- ],
- [
- "SNAPPY",
- "SNAPPY",
- "SNAPPY",
- "SNAPPY"
- ],
- [
- null,
- null,
- null,
- null
- ],
- [
- null,
- null,
- null,
- null
- ]
+ ["root.sg27.s3", "root.sg27.s4", "root.sg28.s3", "root.sg28.s4"],
+ [null, null, null, null],
+ ["root.sg27", "root.sg27", "root.sg28", "root.sg28"],
+ ["INT32", "BOOLEAN", "INT32", "BOOLEAN"],
+ ["RLE", "RLE", "RLE", "RLE"],
+ ["SNAPPY", "SNAPPY", "SNAPPY", "SNAPPY"],
+ [null, null, null, null],
+ [null, null, null, null]
]
}
```
@@ -412,54 +326,14 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
],
"timestamps": null,
"values": [
- [
- "root.sg28.s4",
- "root.sg27.s4",
- "root.sg28.s3",
- "root.sg27.s3"
- ],
- [
- null,
- null,
- null,
- null
- ],
- [
- "root.sg28",
- "root.sg27",
- "root.sg28",
- "root.sg27"
- ],
- [
- "BOOLEAN",
- "BOOLEAN",
- "INT32",
- "INT32"
- ],
- [
- "RLE",
- "RLE",
- "RLE",
- "RLE"
- ],
- [
- "SNAPPY",
- "SNAPPY",
- "SNAPPY",
- "SNAPPY"
- ],
- [
- null,
- null,
- null,
- null
- ],
- [
- null,
- null,
- null,
- null
- ]
+ ["root.sg28.s4", "root.sg27.s4", "root.sg28.s3", "root.sg27.s3"],
+ [null, null, null, null],
+ ["root.sg28", "root.sg27", "root.sg28", "root.sg27"],
+ ["BOOLEAN", "BOOLEAN", "INT32", "INT32"],
+ ["RLE", "RLE", "RLE", "RLE"],
+ ["SNAPPY", "SNAPPY", "SNAPPY", "SNAPPY"],
+ [null, null, null, null],
+ [null, null, null, null]
]
}
```
@@ -473,15 +347,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "columnNames": [
- "count"
- ],
+ "columnNames": ["count"],
"timestamps": null,
- "values": [
- [
- 4
- ]
- ]
+ "values": [[4]]
}
```
@@ -494,15 +362,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "columnNames": [
- "count"
- ],
+ "columnNames": ["count"],
"timestamps": null,
- "values": [
- [
- 4
- ]
- ]
+ "values": [[4]]
}
```
@@ -515,20 +377,11 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "columnNames": [
- "devices",
- "isAligned"
- ],
+ "columnNames": ["devices", "isAligned"],
"timestamps": null,
"values": [
- [
- "root.sg27",
- "root.sg28"
- ],
- [
- "false",
- "false"
- ]
+ ["root.sg27", "root.sg28"],
+ ["false", "false"]
]
}
```
@@ -542,25 +395,12 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "columnNames": [
- "devices",
- "database",
- "isAligned"
- ],
+ "columnNames": ["devices", "database", "isAligned"],
"timestamps": null,
"values": [
- [
- "root.sg27",
- "root.sg28"
- ],
- [
- "root.sg27",
- "root.sg28"
- ],
- [
- "false",
- "false"
- ]
+ ["root.sg27", "root.sg28"],
+ ["root.sg27", "root.sg28"],
+ ["false", "false"]
]
}
```
@@ -574,15 +414,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "columnNames": [
- "user"
- ],
+ "columnNames": ["user"],
"timestamps": null,
- "values": [
- [
- "root"
- ]
- ]
+ "values": [["root"]]
}
```
@@ -594,22 +428,10 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
- "expressions": [
- "count(root.sg27.s3)",
- "count(root.sg27.s4)"
- ],
+ "expressions": ["count(root.sg27.s3)", "count(root.sg27.s4)"],
"columnNames": null,
- "timestamps": [
- 0
- ],
- "values": [
- [
- 1
- ],
- [
- 2
- ]
- ]
+ "timestamps": [0],
+ "values": [[1], [2]]
}
```
@@ -622,19 +444,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "columnNames": [
- "count(root.sg27.*)",
- "count(root.sg28.*)"
- ],
+ "columnNames": ["count(root.sg27.*)", "count(root.sg28.*)"],
"timestamps": null,
- "values": [
- [
- 3
- ],
- [
- 3
- ]
- ]
+ "values": [[3], [3]]
}
```
@@ -646,48 +458,15 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
- "expressions": [
- "count(root.sg27.s3)",
- "count(root.sg27.s4)"
- ],
+ "expressions": ["count(root.sg27.s3)", "count(root.sg27.s4)"],
"columnNames": null,
"timestamps": [
- 1635232143960,
- 1635232144960,
- 1635232145960,
- 1635232146960,
- 1635232147960,
- 1635232148960,
- 1635232149960,
- 1635232150960,
- 1635232151960,
- 1635232152960
+ 1635232143960, 1635232144960, 1635232145960, 1635232146960, 1635232147960,
+ 1635232148960, 1635232149960, 1635232150960, 1635232151960, 1635232152960
],
"values": [
- [
- 1,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0
- ],
- [
- 1,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0
- ]
+ [1, 0, 0, 0, 0, 0, 0, 0, 0, 0],
+ [1, 0, 0, 0, 0, 0, 0, 0, 0, 0]
]
}
```
@@ -701,25 +480,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -
```json
{
"expressions": null,
- "columnNames": [
- "timeseries",
- "value",
- "dataType"
- ],
- "timestamps": [
- 1635232143960
- ],
- "values": [
- [
- "root.sg27.s3"
- ],
- [
- "11"
- ],
- [
- "INT32"
- ]
- ]
+ "columnNames": ["timeseries", "value", "dataType"],
+ "timestamps": [1635232143960],
+ "values": [["root.sg27.s3"], ["11"], ["INT32"]]
}
```
@@ -772,23 +535,25 @@ Request path: `http://ip:port/rest/v1/nonQuery`
Parameter Description:
-|parameter name |parameter type |parameter describe|
-|:--- | :--- | :---|
-| sql | string | query content |
+| parameter name | parameter type | parameter describe |
+| :------------- | :------------- | :----------------- |
+| sql | string | query content |
Example request:
+
```shell
curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X POST --data '{"sql":"CREATE DATABASE root.ln"}' http://127.0.0.1:18080/rest/v1/nonQuery
```
Response parameters:
-|parameter name |parameter type |parameter describe|
-|:--- | :--- | :---|
-| code | integer | status code |
-| message | string | message |
+| parameter name | parameter type | parameter describe |
+| :------------- | :------------- | :----------------- |
+| code | integer | status code |
+| message | string | message |
Sample response:
+
```json
{
"code": 200,
@@ -796,8 +561,6 @@ Sample response:
}
```
-
-
### insertTablet
Request method: `POST`
@@ -808,28 +571,30 @@ Request path: `http://ip:port/rest/v1/insertTablet`
Parameter Description:
-| parameter name |parameter type |is required|parameter describe|
-|:---------------| :--- | :---| :---|
-| timestamps | array | yes | Time column |
-| measurements | array | yes | The name of the measuring point |
-| dataTypes | array | yes | The data type |
-| values | array | yes | Value columns, the values in each column can be `null` |
-| isAligned | boolean | yes | Whether to align the timeseries |
-| deviceId | string | yes | Device name |
+| parameter name | parameter type | is required | parameter describe |
+| :------------- | :------------- | :---------- | :----------------------------------------------------- |
+| timestamps | array | yes | Time column |
+| measurements | array | yes | The name of the measuring point |
+| dataTypes | array | yes | The data type |
+| values | array | yes | Value columns, the values in each column can be `null` |
+| isAligned | boolean | yes | Whether to align the timeseries |
+| deviceId | string | yes | Device name |
Example request:
+
```shell
curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X POST --data '{"timestamps":[1635232143960,1635232153960],"measurements":["s3","s4"],"dataTypes":["INT32","BOOLEAN"],"values":[[11,null],[false,true]],"isAligned":false,"deviceId":"root.sg27"}' http://127.0.0.1:18080/rest/v1/insertTablet
```
Sample response:
-|parameter name |parameter type |parameter describe|
-|:--- | :--- | :---|
-| code | integer | status code |
-| message | string | message |
+| parameter name | parameter type | parameter describe |
+| :------------- | :------------- | :----------------- |
+| code | integer | status code |
+| message | string | message |
Sample response:
+
```json
{
"code": 200,
@@ -841,83 +606,79 @@ Sample response:
The configuration is located in 'iotdb-system.properties'.
-* Set 'enable_rest_service' to 'true' to enable the module, and 'false' to disable the module. By default, this value is' false '.
+- Set 'enable_rest_service' to 'true' to enable the module, and 'false' to disable the module. By default, this value is' false '.
```properties
enable_rest_service=true
```
-* This parameter is valid only when 'enable_REST_service =true'. Set 'rest_service_port' to a number (1025 to 65535) to customize the REST service socket port. By default, the value is 18080.
+- This parameter is valid only when 'enable_REST_service =true'. Set 'rest_service_port' to a number (1025 to 65535) to customize the REST service socket port. By default, the value is 18080.
```properties
rest_service_port=18080
```
-* Set 'enable_swagger' to 'true' to display rest service interface information through swagger, and 'false' to do not display the rest service interface information through the swagger. By default, this value is' false '.
+- Set 'enable_swagger' to 'true' to display rest service interface information through swagger, and 'false' to do not display the rest service interface information through the swagger. By default, this value is' false '.
```properties
enable_swagger=false
```
-* The maximum number of rows in the result set that can be returned by a query. When the number of rows in the returned result set exceeds the limit, the status code `411` is returned.
+- The maximum number of rows in the result set that can be returned by a query. When the number of rows in the returned result set exceeds the limit, the status code `411` is returned.
-````properties
+```properties
rest_query_default_row_size_limit=10000
-````
+```
-* Expiration time for caching customer login information (used to speed up user authentication, in seconds, 8 hours by default)
+- Expiration time for caching customer login information (used to speed up user authentication, in seconds, 8 hours by default)
```properties
cache_expire=28800
```
-
-* Maximum number of users stored in the cache (default: 100)
+- Maximum number of users stored in the cache (default: 100)
```properties
cache_max_num=100
```
-* Initial cache size (default: 10)
+- Initial cache size (default: 10)
```properties
cache_init_num=10
```
-* REST Service whether to enable SSL configuration, set 'enable_https' to' true 'to enable the module, and set' false 'to disable the module. By default, this value is' false '.
+- REST Service whether to enable SSL configuration, set 'enable_https' to' true 'to enable the module, and set' false 'to disable the module. By default, this value is' false '.
```properties
enable_https=false
```
-* keyStore location path (optional)
+- keyStore location path (optional)
```properties
key_store_path=
```
-
-* keyStore password (optional)
+- keyStore password (optional)
```properties
key_store_pwd=
```
-
-* trustStore location path (optional)
+- trustStore location path (optional)
```properties
trust_store_path=
```
-* trustStore password (optional)
+- trustStore password (optional)
```properties
trust_store_pwd=
```
-
-* SSL timeout period, in seconds
+- SSL timeout period, in seconds
```properties
idle_timeout=5000
diff --git a/src/UserGuide/V2.0.1/Tree/API/RestServiceV2.md b/src/UserGuide/V1.3.3/API/RestServiceV2.md
similarity index 60%
rename from src/UserGuide/V2.0.1/Tree/API/RestServiceV2.md
rename to src/UserGuide/V1.3.3/API/RestServiceV2.md
index 6c6011bf5..36dbf72f0 100644
--- a/src/UserGuide/V2.0.1/Tree/API/RestServiceV2.md
+++ b/src/UserGuide/V1.3.3/API/RestServiceV2.md
@@ -1,25 +1,23 @@
-# RESTful API V2
+# RESTful API V2
+
IoTDB's RESTful services can be used for query, write, and management operations, using the OpenAPI standard to define interfaces and generate frameworks.
## Enable RESTful Services
@@ -33,6 +31,7 @@ RESTful services are disabled by default.
```
## Authentication
+
Except the liveness probe API `/ping`, RESTful services use the basic authentication. Each URL request needs to carry `'Authorization': 'Basic ' + base64.encode(username + ':' + password)`.
The username used in the following examples is: `root`, and password is: `root`.
@@ -48,24 +47,26 @@ Authorization: Basic cm9vdDpyb290
HTTP Status Code：`401`
HTTP response body:
- ```json
- {
- "code": 600,
- "message": "WRONG_LOGIN_PASSWORD_ERROR"
- }
- ```
+
+ ```json
+ {
+ "code": 600,
+ "message": "WRONG_LOGIN_PASSWORD_ERROR"
+ }
+ ```
- If the `Authorization` header is missing，the following error is returned:
HTTP Status Code：`401`
HTTP response body:
- ```json
- {
- "code": 603,
- "message": "UNINITIALIZED_AUTH_ERROR"
- }
- ```
+
+ ```json
+ {
+ "code": 603,
+ "message": "UNINITIALIZED_AUTH_ERROR"
+ }
+ ```
## Interface
@@ -79,7 +80,7 @@ Request path: `http://ip:port/ping`
The user name used in the example is: root, password: root
-Example request:
+Example request:
```shell
$ curl http://127.0.0.1:18080/ping
@@ -92,10 +93,10 @@ Response status codes:
Response parameters:
-|parameter name |parameter type |parameter describe|
-|:--- | :--- | :---|
-|code | integer | status code |
-| message | string | message |
+| parameter name | parameter type | parameter describe |
+| :------------- | :------------- | :----------------- |
+| code | integer | status code |
+| message | string | message |
Sample response:
@@ -131,18 +132,18 @@ Request path: `http://ip:port/rest/v2/query`
Parameter Description:
-| parameter name | parameter type | required | parameter description |
-|----------------| -------------- | -------- | ------------------------------------------------------------ |
-| sql | string | yes | |
+| parameter name | parameter type | required | parameter description |
+| -------------- | -------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| sql | string | yes | |
| row_limit | integer | no | The maximum number of rows in the result set that can be returned by a query.
If this parameter is not set, the `rest_query_default_row_size_limit` of the configuration file will be used as the default value.
When the number of rows in the returned result set exceeds the limit, the status code `411` will be returned. |
Response parameters:
-| parameter name | parameter type | parameter description |
-|----------------| -------------- | ------------------------------------------------------------ |
-| expressions | array | Array of result set column names for data query, `null` for metadata query |
-| column_names | array | Array of column names for metadata query result set, `null` for data query |
-| timestamps | array | Timestamp column, `null` for metadata query |
+| parameter name | parameter type | parameter description |
+| -------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| expressions | array | Array of result set column names for data query, `null` for metadata query |
+| column_names | array | Array of column names for metadata query result set, `null` for data query |
+| timestamps | array | Timestamp column, `null` for metadata query |
| values | array | A two-dimensional array, the first dimension has the same length as the result set column name array, and the second dimension array represents a column of the result set |
**Examples:**
@@ -153,33 +154,17 @@ Tip: Statements like `select * from root.xx.**` are not recommended because thos
```shell
curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X POST --data '{"sql":"select s3, s4, s3 + 1 from root.sg27 limit 2"}' http://127.0.0.1:18080/rest/v2/query
-````
+```
```json
{
- "expressions": [
- "root.sg27.s3",
- "root.sg27.s4",
- "root.sg27.s3 + 1"
- ],
+ "expressions": ["root.sg27.s3", "root.sg27.s4", "root.sg27.s3 + 1"],
"column_names": null,
- "timestamps": [
- 1635232143960,
- 1635232153960
- ],
+ "timestamps": [1635232143960, 1635232153960],
"values": [
- [
- 11,
- null
- ],
- [
- false,
- true
- ],
- [
- 12.0,
- null
- ]
+ [11, null],
+ [false, true],
+ [12.0, null]
]
}
```
@@ -193,16 +178,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "column_names": [
- "child paths"
- ],
+ "column_names": ["child paths"],
"timestamps": null,
- "values": [
- [
- "root.sg27",
- "root.sg28"
- ]
- ]
+ "values": [["root.sg27", "root.sg28"]]
}
```
@@ -215,16 +193,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "column_names": [
- "child nodes"
- ],
+ "column_names": ["child nodes"],
"timestamps": null,
- "values": [
- [
- "sg27",
- "sg28"
- ]
- ]
+ "values": [["sg27", "sg28"]]
}
```
@@ -237,20 +208,11 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "column_names": [
- "database",
- "ttl"
- ],
+ "column_names": ["database", "ttl"],
"timestamps": null,
"values": [
- [
- "root.sg27",
- "root.sg28"
- ],
- [
- null,
- null
- ]
+ ["root.sg27", "root.sg28"],
+ [null, null]
]
}
```
@@ -264,19 +226,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "column_names": [
- "database",
- "ttl"
- ],
+ "column_names": ["database", "ttl"],
"timestamps": null,
- "values": [
- [
- "root.sg27"
- ],
- [
- null
- ]
- ]
+ "values": [["root.sg27"], [null]]
}
```
@@ -339,54 +291,14 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
],
"timestamps": null,
"values": [
- [
- "root.sg27.s3",
- "root.sg27.s4",
- "root.sg28.s3",
- "root.sg28.s4"
- ],
- [
- null,
- null,
- null,
- null
- ],
- [
- "root.sg27",
- "root.sg27",
- "root.sg28",
- "root.sg28"
- ],
- [
- "INT32",
- "BOOLEAN",
- "INT32",
- "BOOLEAN"
- ],
- [
- "RLE",
- "RLE",
- "RLE",
- "RLE"
- ],
- [
- "SNAPPY",
- "SNAPPY",
- "SNAPPY",
- "SNAPPY"
- ],
- [
- null,
- null,
- null,
- null
- ],
- [
- null,
- null,
- null,
- null
- ]
+ ["root.sg27.s3", "root.sg27.s4", "root.sg28.s3", "root.sg28.s4"],
+ [null, null, null, null],
+ ["root.sg27", "root.sg27", "root.sg28", "root.sg28"],
+ ["INT32", "BOOLEAN", "INT32", "BOOLEAN"],
+ ["RLE", "RLE", "RLE", "RLE"],
+ ["SNAPPY", "SNAPPY", "SNAPPY", "SNAPPY"],
+ [null, null, null, null],
+ [null, null, null, null]
]
}
```
@@ -412,54 +324,14 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
],
"timestamps": null,
"values": [
- [
- "root.sg28.s4",
- "root.sg27.s4",
- "root.sg28.s3",
- "root.sg27.s3"
- ],
- [
- null,
- null,
- null,
- null
- ],
- [
- "root.sg28",
- "root.sg27",
- "root.sg28",
- "root.sg27"
- ],
- [
- "BOOLEAN",
- "BOOLEAN",
- "INT32",
- "INT32"
- ],
- [
- "RLE",
- "RLE",
- "RLE",
- "RLE"
- ],
- [
- "SNAPPY",
- "SNAPPY",
- "SNAPPY",
- "SNAPPY"
- ],
- [
- null,
- null,
- null,
- null
- ],
- [
- null,
- null,
- null,
- null
- ]
+ ["root.sg28.s4", "root.sg27.s4", "root.sg28.s3", "root.sg27.s3"],
+ [null, null, null, null],
+ ["root.sg28", "root.sg27", "root.sg28", "root.sg27"],
+ ["BOOLEAN", "BOOLEAN", "INT32", "INT32"],
+ ["RLE", "RLE", "RLE", "RLE"],
+ ["SNAPPY", "SNAPPY", "SNAPPY", "SNAPPY"],
+ [null, null, null, null],
+ [null, null, null, null]
]
}
```
@@ -473,15 +345,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "column_names": [
- "count"
- ],
+ "column_names": ["count"],
"timestamps": null,
- "values": [
- [
- 4
- ]
- ]
+ "values": [[4]]
}
```
@@ -494,15 +360,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "column_names": [
- "count"
- ],
+ "column_names": ["count"],
"timestamps": null,
- "values": [
- [
- 4
- ]
- ]
+ "values": [[4]]
}
```
@@ -515,20 +375,11 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "column_names": [
- "devices",
- "isAligned"
- ],
+ "column_names": ["devices", "isAligned"],
"timestamps": null,
"values": [
- [
- "root.sg27",
- "root.sg28"
- ],
- [
- "false",
- "false"
- ]
+ ["root.sg27", "root.sg28"],
+ ["false", "false"]
]
}
```
@@ -542,25 +393,12 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "column_names": [
- "devices",
- "database",
- "isAligned"
- ],
+ "column_names": ["devices", "database", "isAligned"],
"timestamps": null,
"values": [
- [
- "root.sg27",
- "root.sg28"
- ],
- [
- "root.sg27",
- "root.sg28"
- ],
- [
- "false",
- "false"
- ]
+ ["root.sg27", "root.sg28"],
+ ["root.sg27", "root.sg28"],
+ ["false", "false"]
]
}
```
@@ -574,15 +412,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "column_names": [
- "user"
- ],
+ "column_names": ["user"],
"timestamps": null,
- "values": [
- [
- "root"
- ]
- ]
+ "values": [["root"]]
}
```
@@ -594,22 +426,10 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
- "expressions": [
- "count(root.sg27.s3)",
- "count(root.sg27.s4)"
- ],
+ "expressions": ["count(root.sg27.s3)", "count(root.sg27.s4)"],
"column_names": null,
- "timestamps": [
- 0
- ],
- "values": [
- [
- 1
- ],
- [
- 2
- ]
- ]
+ "timestamps": [0],
+ "values": [[1], [2]]
}
```
@@ -622,19 +442,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
"expressions": null,
- "column_names": [
- "count(root.sg27.*)",
- "count(root.sg28.*)"
- ],
+ "column_names": ["count(root.sg27.*)", "count(root.sg28.*)"],
"timestamps": null,
- "values": [
- [
- 3
- ],
- [
- 3
- ]
- ]
+ "values": [[3], [3]]
}
```
@@ -646,48 +456,15 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X
```json
{
- "expressions": [
- "count(root.sg27.s3)",
- "count(root.sg27.s4)"
- ],
+ "expressions": ["count(root.sg27.s3)", "count(root.sg27.s4)"],
"column_names": null,
"timestamps": [
- 1635232143960,
- 1635232144960,
- 1635232145960,
- 1635232146960,
- 1635232147960,
- 1635232148960,
- 1635232149960,
- 1635232150960,
- 1635232151960,
- 1635232152960
+ 1635232143960, 1635232144960, 1635232145960, 1635232146960, 1635232147960,
+ 1635232148960, 1635232149960, 1635232150960, 1635232151960, 1635232152960
],
"values": [
- [
- 1,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0
- ],
- [
- 1,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0,
- 0
- ]
+ [1, 0, 0, 0, 0, 0, 0, 0, 0, 0],
+ [1, 0, 0, 0, 0, 0, 0, 0, 0, 0]
]
}
```
@@ -701,25 +478,9 @@ curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -
```json
{
"expressions": null,
- "column_names": [
- "timeseries",
- "value",
- "dataType"
- ],
- "timestamps": [
- 1635232143960
- ],
- "values": [
- [
- "root.sg27.s3"
- ],
- [
- "11"
- ],
- [
- "INT32"
- ]
- ]
+ "column_names": ["timeseries", "value", "dataType"],
+ "timestamps": [1635232143960],
+ "values": [["root.sg27.s3"], ["11"], ["INT32"]]
}
```
@@ -772,23 +533,25 @@ Request path: `http://ip:port/rest/v2/nonQuery`
Parameter Description:
-|parameter name |parameter type |parameter describe|
-|:--- | :--- | :---|
-| sql | string | query content |
+| parameter name | parameter type | parameter describe |
+| :------------- | :------------- | :----------------- |
+| sql | string | query content |
Example request:
+
```shell
curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X POST --data '{"sql":"CREATE DATABASE root.ln"}' http://127.0.0.1:18080/rest/v2/nonQuery
```
Response parameters:
-|parameter name |parameter type |parameter describe|
-|:--- | :--- | :---|
-| code | integer | status code |
-| message | string | message |
+| parameter name | parameter type | parameter describe |
+| :------------- | :------------- | :----------------- |
+| code | integer | status code |
+| message | string | message |
Sample response:
+
```json
{
"code": 200,
@@ -796,8 +559,6 @@ Sample response:
}
```
-
-
### insertTablet
Request method: `POST`
@@ -808,28 +569,30 @@ Request path: `http://ip:port/rest/v2/insertTablet`
Parameter Description:
-| parameter name |parameter type |is required|parameter describe|
-|:---------------| :--- | :---| :---|
-| timestamps | array | yes | Time column |
-| measurements | array | yes | The name of the measuring point |
-| data_types | array | yes | The data type |
-| values | array | yes | Value columns, the values in each column can be `null` |
-| is_aligned | boolean | yes | Whether to align the timeseries |
-| device | string | yes | Device name |
+| parameter name | parameter type | is required | parameter describe |
+| :------------- | :------------- | :---------- | :----------------------------------------------------- |
+| timestamps | array | yes | Time column |
+| measurements | array | yes | The name of the measuring point |
+| data_types | array | yes | The data type |
+| values | array | yes | Value columns, the values in each column can be `null` |
+| is_aligned | boolean | yes | Whether to align the timeseries |
+| device | string | yes | Device name |
Example request:
+
```shell
curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X POST --data '{"timestamps":[1635232143960,1635232153960],"measurements":["s3","s4"],"data_types":["INT32","BOOLEAN"],"values":[[11,null],[false,true]],"is_aligned":false,"device":"root.sg27"}' http://127.0.0.1:18080/rest/v2/insertTablet
```
Sample response:
-|parameter name |parameter type |parameter describe|
-|:--- | :--- | :---|
-| code | integer | status code |
-| message | string | message |
+| parameter name | parameter type | parameter describe |
+| :------------- | :------------- | :----------------- |
+| code | integer | status code |
+| message | string | message |
Sample response:
+
```json
{
"code": 200,
@@ -847,28 +610,30 @@ Request path: `http://ip:port/rest/v2/insertRecords`
Parameter Description:
-| parameter name |parameter type |is required|parameter describe|
-|:------------------| :--- | :---| :---|
-| timestamps | array | yes | Time column |
-| measurements_list | array | yes | The name of the measuring point |
-| data_types_list | array | yes | The data type |
-| values_list | array | yes | Value columns, the values in each column can be `null` |
-| devices | string | yes | Device name |
-| is_aligned | boolean | yes | Whether to align the timeseries |
+| parameter name | parameter type | is required | parameter describe |
+| :---------------- | :------------- | :---------- | :----------------------------------------------------- |
+| timestamps | array | yes | Time column |
+| measurements_list | array | yes | The name of the measuring point |
+| data_types_list | array | yes | The data type |
+| values_list | array | yes | Value columns, the values in each column can be `null` |
+| devices | string | yes | Device name |
+| is_aligned | boolean | yes | Whether to align the timeseries |
Example request:
+
```shell
curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290" -X POST --data '{"timestamps":[1635232113960,1635232151960,1635232143960,1635232143960],"measurements_list":[["s33","s44"],["s55","s66"],["s77","s88"],["s771","s881"]],"data_types_list":[["INT32","INT64"],["FLOAT","DOUBLE"],["FLOAT","DOUBLE"],["BOOLEAN","TEXT"]],"values_list":[[1,11],[2.1,2],[4,6],[false,"cccccc"]],"is_aligned":false,"devices":["root.s1","root.s1","root.s1","root.s3"]}' http://127.0.0.1:18080/rest/v2/insertRecords
```
Sample response:
-|parameter name |parameter type |parameter describe|
-|:--- | :--- | :---|
-| code | integer | status code |
-| message | string | message |
+| parameter name | parameter type | parameter describe |
+| :------------- | :------------- | :----------------- |
+| code | integer | status code |
+| message | string | message |
Sample response:
+
```json
{
"code": 200,
@@ -876,88 +641,83 @@ Sample response:
}
```
-
## Configuration
The configuration is located in 'iotdb-system.properties'.
-* Set 'enable_rest_service' to 'true' to enable the module, and 'false' to disable the module. By default, this value is' false '.
+- Set 'enable_rest_service' to 'true' to enable the module, and 'false' to disable the module. By default, this value is' false '.
```properties
enable_rest_service=true
```
-* This parameter is valid only when 'enable_REST_service =true'. Set 'rest_service_port' to a number (1025 to 65535) to customize the REST service socket port. By default, the value is 18080.
+- This parameter is valid only when 'enable_REST_service =true'. Set 'rest_service_port' to a number (1025 to 65535) to customize the REST service socket port. By default, the value is 18080.
```properties
rest_service_port=18080
```
-* Set 'enable_swagger' to 'true' to display rest service interface information through swagger, and 'false' to do not display the rest service interface information through the swagger. By default, this value is' false '.
+- Set 'enable_swagger' to 'true' to display rest service interface information through swagger, and 'false' to do not display the rest service interface information through the swagger. By default, this value is' false '.
```properties
enable_swagger=false
```
-* The maximum number of rows in the result set that can be returned by a query. When the number of rows in the returned result set exceeds the limit, the status code `411` is returned.
+- The maximum number of rows in the result set that can be returned by a query. When the number of rows in the returned result set exceeds the limit, the status code `411` is returned.
-````properties
+```properties
rest_query_default_row_size_limit=10000
-````
+```
-* Expiration time for caching customer login information (used to speed up user authentication, in seconds, 8 hours by default)
+- Expiration time for caching customer login information (used to speed up user authentication, in seconds, 8 hours by default)
```properties
cache_expire=28800
```
-
-* Maximum number of users stored in the cache (default: 100)
+- Maximum number of users stored in the cache (default: 100)
```properties
cache_max_num=100
```
-* Initial cache size (default: 10)
+- Initial cache size (default: 10)
```properties
cache_init_num=10
```
-* REST Service whether to enable SSL configuration, set 'enable_https' to' true 'to enable the module, and set' false 'to disable the module. By default, this value is' false '.
+- REST Service whether to enable SSL configuration, set 'enable_https' to' true 'to enable the module, and set' false 'to disable the module. By default, this value is' false '.
```properties
enable_https=false
```
-* keyStore location path (optional)
+- keyStore location path (optional)
```properties
key_store_path=
```
-
-* keyStore password (optional)
+- keyStore password (optional)
```properties
key_store_pwd=
```
-
-* trustStore location path (optional)
+- trustStore location path (optional)
```properties
trust_store_path=
```
-* trustStore password (optional)
+- trustStore password (optional)
```properties
trust_store_pwd=
```
-
-* SSL timeout period, in seconds
+- SSL timeout period, in seconds
```properties
idle_timeout=5000
diff --git a/src/UserGuide/V2.0.1/Tree/Background-knowledge/Cluster-Concept.md b/src/UserGuide/V1.3.3/Background-knowledge/Cluster-Concept.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Background-knowledge/Cluster-Concept.md
rename to src/UserGuide/V1.3.3/Background-knowledge/Cluster-Concept.md
diff --git a/src/UserGuide/V2.0.1/Tree/Background-knowledge/Cluster-Concept_apache.md b/src/UserGuide/V1.3.3/Background-knowledge/Cluster-Concept_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Background-knowledge/Cluster-Concept_apache.md
rename to src/UserGuide/V1.3.3/Background-knowledge/Cluster-Concept_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/Background-knowledge/Cluster-Concept_timecho.md b/src/UserGuide/V1.3.3/Background-knowledge/Cluster-Concept_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Background-knowledge/Cluster-Concept_timecho.md
rename to src/UserGuide/V1.3.3/Background-knowledge/Cluster-Concept_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Background-knowledge/Data-Type.md b/src/UserGuide/V1.3.3/Background-knowledge/Data-Type.md
similarity index 71%
rename from src/UserGuide/V2.0.1/Tree/Background-knowledge/Data-Type.md
rename to src/UserGuide/V1.3.3/Background-knowledge/Data-Type.md
index bc1f03e1a..03fcf7a6e 100644
--- a/src/UserGuide/V2.0.1/Tree/Background-knowledge/Data-Type.md
+++ b/src/UserGuide/V1.3.3/Background-knowledge/Data-Type.md
@@ -1,22 +1,19 @@
# Data Type
@@ -25,40 +22,41 @@
IoTDB supports the following data types:
-* BOOLEAN (Boolean)
-* INT32 (Integer)
-* INT64 (Long Integer)
-* FLOAT (Single Precision Floating Point)
-* DOUBLE (Double Precision Floating Point)
-* TEXT (Long String)
-* STRING（String）
-* BLOB（Large binary Object）
-* TIMESTAMP（Timestamp）
-* DATE（Date）
-
+- BOOLEAN (Boolean)
+- INT32 (Integer)
+- INT64 (Long Integer)
+- FLOAT (Single Precision Floating Point)
+- DOUBLE (Double Precision Floating Point)
+- TEXT (Long String)
+- STRING（String）
+- BLOB（Large binary Object）
+- TIMESTAMP（Timestamp）
+- DATE（Date）
+
The difference between STRING and TEXT types is that STRING type has more statistical information and can be used to optimize value filtering queries, while TEXT type is suitable for storing long strings.
### Float Precision
-The time series of **FLOAT** and **DOUBLE** type can specify (MAX\_POINT\_NUMBER, see [this page](../SQL-Manual/SQL-Manual.md) 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.md) 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';
```
-* For Float data value, The data range is (-Integer.MAX_VALUE, Integer.MAX_VALUE), rather than Float.MAX_VALUE, and the max_point_number is 19, caused by the limition of function Math.round(float) in Java.
-* For Double data value, The data range is (-Long.MAX_VALUE, Long.MAX_VALUE), rather than Double.MAX_VALUE, and the max_point_number is 19, caused by the limition of function Math.round(double) in Java (Long.MAX_VALUE=9.22E18).
+- For Float data value, The data range is (-Integer.MAX_VALUE, Integer.MAX_VALUE), rather than Float.MAX_VALUE, and the max_point_number is 19, caused by the limitation of function Math.round(float) in Java.
+- For Double data value, The data range is (-Long.MAX_VALUE, Long.MAX_VALUE), rather than Double.MAX_VALUE, and the max_point_number is 19, caused by the limitation of function Math.round(double) in Java (Long.MAX_VALUE=9.22E18).
### Data Type Compatibility
When the written data type is inconsistent with the data type of time-series,
+
- If the data type of time-series is not compatible with the written data type, the system will give an error message.
- If the data type of time-series is compatible with the written data type, the system will automatically convert the data type.
The compatibility of each data type is shown in the following table:
| Series Data Type | Supported Written Data Types |
-|------------------|------------------------------|
+| ---------------- | ---------------------------- |
| BOOLEAN | BOOLEAN |
| INT32 | INT32 |
| INT64 | INT32 INT64 |
@@ -74,12 +72,10 @@ The timestamp is the time point at which data is produced. It includes absolute
Absolute timestamps in IoTDB are divided into two types: LONG and DATETIME (including DATETIME-INPUT and DATETIME-DISPLAY). When a user inputs a timestamp, he can use a LONG type timestamp or a DATETIME-INPUT type timestamp, and the supported formats of the DATETIME-INPUT type timestamp are shown in the table below:
-
+::: center
**Supported formats of DATETIME-INPUT type timestamp**
-
-
| Format |
| :--------------------------: |
| yyyy-MM-dd HH:mm:ss |
@@ -96,16 +92,14 @@ Absolute timestamps in IoTDB are divided into two types: LONG and DATETIME (incl
| yyyy.MM.dd HH:mm:ss.SSSZZ |
| ISO8601 standard time format |
-
-
+:::
IoTDB can support LONG types and DATETIME-DISPLAY types when displaying timestamps. The DATETIME-DISPLAY type can support user-defined time formats. The syntax of the custom time format is shown in the table below:
-
+::: center
**The syntax of the custom time format**
-
| Symbol | Meaning | Presentation | Examples |
| :----: | :-------------------------: | :----------: | :--------------------------------: |
| G | era | era | era |
@@ -138,25 +132,23 @@ IoTDB can support LONG types and DATETIME-DISPLAY types when displaying timestam
| ' | escape for text | delimiter | |
| '' | single quote | literal | ' |
-
+:::
### Relative timestamp
-Relative time refers to the time relative to the server time ```now()``` and ```DATETIME``` time.
+Relative time refers to the time relative to the server time `now()` and `DATETIME` time.
- Syntax:
+Syntax:
- ```
- Duration = (Digit+ ('Y'|'MO'|'W'|'D'|'H'|'M'|'S'|'MS'|'US'|'NS'))+
- RelativeTime = (now() | DATETIME) ((+|-) Duration)+
-
- ```
+```
+Duration = (Digit+ ('Y'|'MO'|'W'|'D'|'H'|'M'|'S'|'MS'|'US'|'NS'))+
+RelativeTime = (now() | DATETIME) ((+|-) Duration)+
+```
-
+::: center
**The syntax of the duration unit**
-
| Symbol | Meaning | Presentation | Examples |
| :----: | :---------: | :----------------------: | :------: |
| y | year | 1y=365 days | 1y |
@@ -172,13 +164,13 @@ Relative time refers to the time relative to the server time ```now()``` and ```
| us | microsecond | 1us=1000 nanoseconds | 1us |
| ns | nanosecond | 1ns=1 nanosecond | 1ns |
-
+:::
- eg：
+eg：
- ```
- now() - 1d2h //1 day and 2 hours earlier than the current server time
- now() - 1w //1 week earlier than the current server time
- ```
+```
+now() - 1d2h //1 day and 2 hours earlier than the current server time
+now() - 1w //1 week earlier than the current server time
+```
- > Note：There must be spaces on the left and right of '+' and '-'.
+> Note：There must be spaces on the left and right of '+' and '-'.
diff --git a/src/UserGuide/V2.0.1/Tree/Basic-Concept/Data-Model-and-Terminology.md b/src/UserGuide/V1.3.3/Basic-Concept/Data-Model-and-Terminology.md
similarity index 99%
rename from src/UserGuide/V2.0.1/Tree/Basic-Concept/Data-Model-and-Terminology.md
rename to src/UserGuide/V1.3.3/Basic-Concept/Data-Model-and-Terminology.md
index e1aeb3564..7a10118a9 100644
--- a/src/UserGuide/V2.0.1/Tree/Basic-Concept/Data-Model-and-Terminology.md
+++ b/src/UserGuide/V1.3.3/Basic-Concept/Data-Model-and-Terminology.md
@@ -94,6 +94,7 @@ The following are the constraints on the `nodeName`:
If you need to use special characters in the path node name, you can use reverse quotation marks to reference the path node name. For specific usage, please refer to [Reverse Quotation Marks](../Reference/Syntax-Rule.md#reverse-quotation-marks).
+
### Path Pattern
In order to make it easier and faster to express multiple timeseries paths, IoTDB provides users with the path pattern. Users can construct a path pattern by using wildcard `*` and `**`. Wildcard can appear in any node of the path.
diff --git a/src/UserGuide/V2.0.1/Tree/Basic-Concept/Navigating_Time_Series_Data.md b/src/UserGuide/V1.3.3/Basic-Concept/Navigating_Time_Series_Data.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Basic-Concept/Navigating_Time_Series_Data.md
rename to src/UserGuide/V1.3.3/Basic-Concept/Navigating_Time_Series_Data.md
diff --git a/src/zh/UserGuide/V2.0.1-Tree/Basic-Concept/Operate-Metadata.md b/src/UserGuide/V1.3.3/Basic-Concept/Operate-Metadata.md
similarity index 99%
rename from src/zh/UserGuide/V2.0.1-Tree/Basic-Concept/Operate-Metadata.md
rename to src/UserGuide/V1.3.3/Basic-Concept/Operate-Metadata.md
index e0ddf712e..4eb80c594 100644
--- a/src/zh/UserGuide/V2.0.1-Tree/Basic-Concept/Operate-Metadata.md
+++ b/src/UserGuide/V1.3.3/Basic-Concept/Operate-Metadata.md
@@ -20,4 +20,4 @@ redirectTo: Operate-Metadata_apache.html
specific language governing permissions and limitations
under the License.
--->
\ No newline at end of file
+-->
diff --git a/src/UserGuide/V2.0.1/Tree/Basic-Concept/Operate-Metadata_apache.md b/src/UserGuide/V1.3.3/Basic-Concept/Operate-Metadata_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Basic-Concept/Operate-Metadata_apache.md
rename to src/UserGuide/V1.3.3/Basic-Concept/Operate-Metadata_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/Basic-Concept/Operate-Metadata_timecho.md b/src/UserGuide/V1.3.3/Basic-Concept/Operate-Metadata_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Basic-Concept/Operate-Metadata_timecho.md
rename to src/UserGuide/V1.3.3/Basic-Concept/Operate-Metadata_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Basic-Concept/Query-Data.md b/src/UserGuide/V1.3.3/Basic-Concept/Query-Data.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Basic-Concept/Query-Data.md
rename to src/UserGuide/V1.3.3/Basic-Concept/Query-Data.md
diff --git a/src/UserGuide/V2.0.1/Tree/Basic-Concept/Write-Delete-Data.md b/src/UserGuide/V1.3.3/Basic-Concept/Write-Delete-Data.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Basic-Concept/Write-Delete-Data.md
rename to src/UserGuide/V1.3.3/Basic-Concept/Write-Delete-Data.md
diff --git a/src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/AINode_Deployment_timecho.md b/src/UserGuide/V1.3.3/Deployment-and-Maintenance/AINode_Deployment_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/AINode_Deployment_timecho.md
rename to src/UserGuide/V1.3.3/Deployment-and-Maintenance/AINode_Deployment_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/UserGuide/V1.3.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md
rename to src/UserGuide/V1.3.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md
diff --git a/src/UserGuide/V1.3.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/UserGuide/V1.3.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
new file mode 100644
index 000000000..08579e8a7
--- /dev/null
+++ b/src/UserGuide/V1.3.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
@@ -0,0 +1,384 @@
+
+# Cluster Deployment
+
+This section describes how to manually deploy an instance that includes 3 ConfigNodes and 3 DataNodes, commonly known as a 3C3D cluster.
+
+
+
+
@@ -119,6 +120,7 @@ The following table lists the recommended disk partitioning methods.
+
### Network Configuration
1. Disable the firewall
diff --git a/src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/IoTDB-Package.md b/src/UserGuide/V1.3.3/Deployment-and-Maintenance/IoTDB-Package.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/IoTDB-Package.md
rename to src/UserGuide/V1.3.3/Deployment-and-Maintenance/IoTDB-Package.md
diff --git a/src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/IoTDB-Package_apache.md b/src/UserGuide/V1.3.3/Deployment-and-Maintenance/IoTDB-Package_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/IoTDB-Package_apache.md
rename to src/UserGuide/V1.3.3/Deployment-and-Maintenance/IoTDB-Package_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/IoTDB-Package_timecho.md b/src/UserGuide/V1.3.3/Deployment-and-Maintenance/IoTDB-Package_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/IoTDB-Package_timecho.md
rename to src/UserGuide/V1.3.3/Deployment-and-Maintenance/IoTDB-Package_timecho.md
diff --git a/src/UserGuide/V2.0.1/Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md b/src/UserGuide/V1.3.3/Deployment-and-Maintenance/Monitoring-panel-deployment.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md
rename to src/UserGuide/V1.3.3/Deployment-and-Maintenance/Monitoring-panel-deployment.md
diff --git a/src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/src/UserGuide/V1.3.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
rename to src/UserGuide/V1.3.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
diff --git a/src/UserGuide/V1.3.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md b/src/UserGuide/V1.3.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
new file mode 100644
index 000000000..a4e3e3c59
--- /dev/null
+++ b/src/UserGuide/V1.3.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -0,0 +1,220 @@
+
+# Stand-Alone Deployment
+
+This chapter will introduce how to start an IoTDB standalone instance, which includes 1 ConfigNode and 1 DataNode (commonly known as 1C1D).
+
+## Matters Needing Attention
+
+1. Before installation, ensure that the system is complete by referring to [System configuration](./Environment-Requirements.md).
+
+2. It is recommended to prioritize using 'hostname' for IP configuration during deployment, which can avoid the problem of modifying the host IP in the later stage and causing the database to fail to start. To set the host name, you need to configure/etc/hosts on the target server. For example, if the local IP is 192.168.1.3 and the host name is iotdb-1, you can use the following command to set the server's host name and configure IoTDB's' cn_internal-address' using the host name dn_internal_address、dn_rpc_address。
+
+ ```shell
+ echo "192.168.1.3 iotdb-1" >> /etc/hosts
+ ```
+
+3. Some parameters cannot be modified after the first startup. Please refer to the "Parameter Configuration" section below for settings.
+
+4. Whether in linux or windows, ensure that the IoTDB installation path does not contain Spaces and Chinese characters to avoid software exceptions.
+
+5. Please note that when installing and deploying IoTDB (including activating and using software), it is necessary to use the same user for operations. You can:
+- Using root user (recommended): Using root user can avoid issues such as permissions.
+- Using a fixed non root user:
+ - Using the same user operation: Ensure that the same user is used for start, activation, stop, and other operations, and do not switch users.
+ - Avoid using sudo: Try to avoid using sudo commands as they execute commands with root privileges, which may cause confusion or security issues.
+
+6. It is recommended to deploy a monitoring panel, which can monitor important operational indicators and keep track of database operation status at any time. The monitoring panel can be obtained by contacting the business department, and the steps for deploying the monitoring panel can be referred to：[Monitoring Board Install and Deploy](./Monitoring-panel-deployment.md).
+
+## Installation Steps
+
+### 1、Unzip the installation package and enter the installation directory
+
+```shell
+unzip iotdb-enterprise-{version}-bin.zip
+cd iotdb-enterprise-{version}-bin
+```
+
+### 2、Parameter Configuration
+
+#### Environment Script Configuration
+
+- ./conf/confignode-env.sh (./conf/confignode-env.bat) configuration
+
+| **Configuration** | **Description** | **Default** | **Recommended value** | Note |
+| :---------------: | :----------------------------------------------------------: | :---------: | :----------------------------------------------------------: | :---------------------------------: |
+| MEMORY_SIZE | The total amount of memory that IoTDB ConfigNode nodes can use | empty | Can be filled in as needed, and the system will allocate memory based on the filled in values | Restarting the service takes effect |
+
+- ./conf/datanode-env.sh (./conf/datanode-env.bat) configuration
+
+| **Configuration** | **Description** | **Default** | **Recommended value** | **Note** |
+| :---------: | :----------------------------------: | :--------: | :----------------------------------------------: | :----------: |
+| MEMORY_SIZE | The total amount of memory that IoTDB DataNode nodes can use | empty | Can be filled in as needed, and the system will allocate memory based on the filled in values | Restarting the service takes effect |
+
+#### System General Configuration
+
+Open the general configuration file (./conf/iotdb-system. properties file) and set the following parameters:
+
+| **Configuration** | **Description** | **Default** | **Recommended value** | Note |
+| :-----------------------: | :----------------------------------------------------------: | :------------: | :----------------------------------------------------------: | :---------------------------------------------------: |
+| cluster_name | Cluster Name | defaultCluster | The cluster name can be set as needed, and if there are no special needs, the default can be kept | Cannot be modified after initial startup |
+| schema_replication_factor | Number of metadata replicas, set to 1 for the standalone version here | 1 | 1 | Default 1, cannot be modified after the first startup |
+| data_replication_factor | Number of data replicas, set to 1 for the standalone version here | 1 | 1 | Default 1, cannot be modified after the first startup |
+
+#### ConfigNode Configuration
+
+Open the ConfigNode configuration file (./conf/iotdb-system. properties file) and set the following parameters:
+
+| **Configuration** | **Description** | **Default** | **Recommended value** | Note |
+| :-----------------: | :----------------------------------------------------------: | :-------------: | :----------------------------------------------------------: | :--------------------------------------: |
+| cn_internal_address | The address used by ConfigNode for communication within the cluster | 127.0.0.1 | The IPV4 address or host name of the server where it is located, and it is recommended to use host name | Cannot be modified after initial startup |
+| cn_internal_port | The port used by ConfigNode for communication within the cluster | 10710 | 10710 | Cannot be modified after initial startup |
+| cn_consensus_port | The port used for ConfigNode replica group consensus protocol communication | 10720 | 10720 | Cannot be modified after initial startup |
+| cn_seed_config_node | The address of the ConfigNode that the node connects to when registering to join the cluster, cn_internal_address:cn_internal_port | 127.0.0.1:10710 | cn_internal_address:cn_internal_port | Cannot be modified after initial startup |
+
+#### DataNode Configuration
+
+Open the DataNode configuration file (./conf/iotdb-system. properties file) and set the following parameters:
+
+| **Configuration** | **Description** | **Default** | **Recommended value** | **Note** |
+| :------------------------------ | :----------------------------------------------------------- | :-------------- | :----------------------------------------------------------- | :--------------------------------------- |
+| dn_rpc_address | The address of 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 host name | Restarting the service takes effect |
+| dn_rpc_port | The port of the client RPC service | 6667 | 6667 | Restarting the service takes effect |
+| dn_internal_address | The address used by DataNode for communication within the cluster | 127.0.0.1 | The IPV4 address or host name of the server where it is located, and it is recommended to use host name | Cannot be modified after initial startup |
+| dn_internal_port | The port used by DataNode for communication within the cluster | 10730 | 10730 | Cannot be modified after initial startup |
+| dn_mpp_data_exchange_port | The port used by DataNode to receive data streams | 10740 | 10740 | Cannot be modified after initial startup |
+| dn_data_region_consensus_port | The port used by DataNode for data replica consensus protocol communication | 10750 | 10750 | Cannot be modified after initial startup |
+| dn_schema_region_consensus_port | The port used by DataNode for metadata replica consensus protocol communication | 10760 | 10760 | Cannot be modified after initial startup |
+| dn_seed_config_node | The ConfigNode address that the node connects to when registering to join the cluster, i.e. cn_internal-address: cn_internal_port | 127.0.0.1:10710 | cn_internal_address:cn_internal_port | Cannot be modified after initial startup |
+
+> ❗️Attention: Editors such as VSCode Remote do not have automatic configuration saving function. Please ensure that the modified files are saved persistently, otherwise the configuration items will not take effect
+
+### 3、Start ConfigNode
+
+Enter the sbin directory of iotdb and start confignode
+
+```shell
+./start-confignode.sh -d #The "- d" parameter will start in the background
+```
+If the startup fails, please refer to [Common Questions](#common-questions).
+
+### 4、Activate Database
+
+#### Method 1: Activate file copy activation
+
+- After starting the confignode node, enter the activation folder and copy the systeminfo file to the Timecho staff
+- Received the license file returned by the staff
+- Place the license file in the activation folder of the corresponding node;
+
+#### Method 2: Activate Script Activation
+
+- Obtain the required machine code for activation, enter the sbin directory of the installation directory, and execute the activation script:
+
+```shell
+ cd sbin
+./start-activate.sh
+```
+
+- The following information is displayed. Please copy the machine code (i.e. the string of characters) to the Timecho staff:
+
+```shell
+Please copy the system_info's content and send it to Timecho:
+01-KU5LDFFN-PNBEHDRH
+Please enter license:
+```
+
+- Enter the activation code returned by the staff into the previous command line prompt 'Please enter license:', as shown below:
+
+```shell
+Please enter license:
+JJw+MmF+AtexsfgNGOFgTm83Bxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxm6pF+APW1CiXLTSijK9Qh3nsLgzrW8OJPh26Vl6ljKUpCvpTiw==
+License has been stored to sbin/../activation/license
+Import completed. Please start cluster and excute 'show cluster' to verify activation status
+```
+
+### 5、Start DataNode
+
+Enter the sbin directory of iotdb and start datanode:
+
+```shell
+cd sbin
+./start-datanode.sh -d # The "- d" parameter will start in the background
+```
+
+### 6、Verify Deployment
+
+Can be executed directly/ Cli startup script in sbin directory:
+
+```shell
+./start-cli.sh -h ip(local IP or domain name) -p port(6667)
+```
+
+After successful startup, the following interface will appear displaying successful installation of IOTDB.
+
+
+
+After the installation success interface appears, continue to check if the activation is successful and use the `show cluster`command
+
+When you see the display "Activated" on the far right, it indicates successful activation
+
+
+
+
+> 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.
+
+## Common Problem
+1. Multiple prompts indicating activation failure during deployment process
+ - Use the `ls -al` command: Use the `ls -al` command to check if the owner information of the installation package root directory is the current user.
+ - Check activation directory: Check all files in the `./activation` directory and whether the owner information is the current user.
+
+2. Confignode failed to start
+
+ 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 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.
+
+ Step 4: Clean up the environment:
+
+ a. Terminate all ConfigNode Node and DataNode processes.
+ ```Bash
+ # 1. Stop the ConfigNode and DataNode services
+ sbin/stop-standalone.sh
+
+ # 2. Check for any remaining processes
+ jps
+ # Or
+ ps -ef|gerp iotdb
+
+ # 3. If there are any remaining processes, manually kill the
+ kill -9
+ # If you are sure there is only one iotdb on the machine, you can use the following command to clean up residual processes
+ ps -ef|grep iotdb|grep -v grep|tr -s ' ' ' ' |cut -d ' ' -f2|xargs kill -9
+ ```
+ b. Delete the data and logs directories.
+
+ Explanation: Deleting the data directory is necessary, deleting the logs directory is for clean logs and is not mandatory.
+
+ ```Bash
+ cd /data/iotdb
+ rm -rf data logs
+ ```
\ No newline at end of file
diff --git a/src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/workbench-deployment_timecho.md b/src/UserGuide/V1.3.3/Deployment-and-Maintenance/workbench-deployment_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/workbench-deployment_timecho.md
rename to src/UserGuide/V1.3.3/Deployment-and-Maintenance/workbench-deployment_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/DBeaver.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/DBeaver.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/DBeaver.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/DBeaver.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/DataEase.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/DataEase.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/DataEase.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/DataEase.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Flink-IoTDB.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Flink-IoTDB.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Flink-IoTDB.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/Flink-IoTDB.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Flink-TsFile.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Flink-TsFile.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Flink-TsFile.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/Flink-TsFile.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Grafana-Connector.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Grafana-Connector.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Grafana-Connector.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/Grafana-Connector.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Grafana-Plugin.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Grafana-Plugin.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Grafana-Plugin.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/Grafana-Plugin.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Hive-TsFile.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Hive-TsFile.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Hive-TsFile.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/Hive-TsFile.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Ignition-IoTDB-plugin_timecho.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Ignition-IoTDB-plugin_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Ignition-IoTDB-plugin_timecho.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/Ignition-IoTDB-plugin_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Kubernetes_apache.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Kubernetes_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Kubernetes_apache.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/Kubernetes_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Kubernetes_timecho.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Kubernetes_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Kubernetes_timecho.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/Kubernetes_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/NiFi-IoTDB.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/NiFi-IoTDB.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/NiFi-IoTDB.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/NiFi-IoTDB.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Spark-IoTDB.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Spark-IoTDB.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Spark-IoTDB.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/Spark-IoTDB.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Spark-TsFile.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Spark-TsFile.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Spark-TsFile.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/Spark-TsFile.md
diff --git a/src/UserGuide/V1.3.3/Ecosystem-Integration/Telegraf.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Telegraf.md
new file mode 100644
index 000000000..1c84d9bef
--- /dev/null
+++ b/src/UserGuide/V1.3.3/Ecosystem-Integration/Telegraf.md
@@ -0,0 +1,191 @@
+
+# Telegraf
+
+## 1、Product Overview
+
+### 1.1 Telegraf
+
+[Telegraf](https://www.influxdata.com/time-series-platform/telegraf/) is an open-source proxy tool developed by InfluxData for collecting, processing, and transmitting metric data.
+
+Telegraf has the following characteristics:
+
+- Plugin architecture: The strength of Telegraf lies in its extensive plugin ecosystem. It supports multiple input, output, and processor plugins, and can seamlessly integrate with various data sources and targets.
+ - Data collection: Telegraf excels at collecting metric data from various sources, such as system metrics, logs, databases, etc. Its versatility makes it suitable for monitoring applications, infrastructure, and IoT devices.
+ - Output target: Once data is collected, it can be sent to various output targets, including popular databases such as InfluxDB. This flexibility allows Telegraf to adapt to different monitoring and analysis settings.
+- Easy configuration: Telegraf is configured using TOML files. This simplicity enables users to easily define inputs, outputs, and processors, making customization simple and clear.
+- Community and Support: As an open-source project, Telegraf benefits from an active community. Users can contribute plugins, report issues, and seek help through forums and documents.
+
+### 1.2 Telegraf-IoTDB Plugin
+
+The Telegraf IoTDB plugin can output and store monitoring information saved in Telegraf to IoTDB. The output plugin uses IoTDB sessions for connection and data writing.
+
+
+
+## 2、Installation Requirements
+
+Telegraf supports multiple operating systems, including Linux, Windows, and macOS. It is recommended to use 'root' administrator privileges to successfully install Telegraf. Please refer to the installation requirements for specific [Installation Requirements](https://docs.influxdata.com/telegraf/v1/install/)
+
+## 3、Installation Steps
+
+Please refer to [Installation Steps](https://docs.influxdata.com/telegraf/v1/install/) for specific installation steps
+
+- Note: This plugin is a built-in plugin for Telegraf and does not require secondary installation
+
+## 4、Instructions
+
+### 4.1 Set Input Source
+
+Find 'INPUT PLUGINS' in the' telegraf. conf 'configuration file to configure the input source. The specific configuration content is shown in the table below
+
+| Configuration | Description | Notes |
+| ----------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| alias | Example of named plugin | |
+| interval |Collect the frequency of this indicator. Ordinary plugins use a single global interval, but if the running frequency of a specific input should be lower or higher, you can configure it here` Interval can be increased to reduce data input rate limitations. | |
+| precision | Overlay the settings of the 'precision' proxy. The collected indicators are rounded to the specified precision interval. When this value is set on the service input (e.g. `'statsd':`), the output database may merge multiple events that occur at the same timestamp. | |
+| collection_jitter | Overlay the settings of the 'collectic_jitter' proxy. Collection jitter is used to perform random intervals` | |
+| name_override | Custom time series path name used when outputting to IoTDB | The output path name must meet the "[Syntax Requirement](../Reference/Syntax-Rule.md)" requirement |
+| name_prefix | Specify the prefix attached to the measurement name | |
+| name_suffix | Specify the suffix attached to the measurement name | |
+
+
+
+### 4.2 Set Output Source
+
+Find "outputs. iotdb" in the "telegraf. conf" configuration file to configure the output source. The specific configuration content is shown in the table below. For specific input source examples, please refer to [Output Source Example](https://docs.influxdata.com/telegraf/v1/configuration/#output-configuration-examples)
+
+| Configuration | Description | Before Modification | After Modification | Notes |
+| ------------------- | -------------- | ----------------------------------- | ------------------------------------------------- | ------------------------------------------------------------ |
+| host | Host of IoTDB | # host = "127.0.0.1" | host = "Deploy IoTDB host" | Default is 127.0.0.1 |
+| port | The port number of IoTDB | # port = "6667" | port = "Port number for deploying IoTDB" | Default is 6667 |
+| user | Username for IoTDB | # user = "root" | user = "Username for IoTDB" |Default as root |
+| password | Password for IoTDB | # password = "root" | password= "Password for IoTDB" | Default as root |
+| timestamp_precision | Timestamp accuracy | timestamp_precision = "millisecond" | timestamp_precision = "Same timestamp accuracy as IoTDB" | You can check the 'timestamp-precision' field in 'iotdb system. properties' |
+| sanitize_tag | Database version | none | sanitize_tag = "0.13/1.0/1.1/1.2/1.3" | |
+
+
+
+### 4.3 Start Telegraf Service
+
+```Bash
+telegraf -config /path/to/telegraf.conf
+```
+
+## 5、Example Usage
+
+The following is an example of collecting CPU data using Telegraf and outputting it to IoTDB using Telegraf IoTDB. Generate configuration files using the telegraf command
+
+```Bash
+telegraf --sample-config --input-filter cpu --output-filter iotdb > cpu_iotdb.conf
+```
+
+1. Modify the configuration of the input CPU plugin in cpu_iotdb. conf. Among them, the "name_ooverride" field is the custom time-series path name used when outputting to IoTDB
+
+```Bash
+# Read metrics about cpu usage
+[[inputs.cpu]]
+ ## Whether to report per-cpu stats or not
+ percpu = true
+ ## Whether to report total system cpu stats or not
+ totalcpu = true
+ ## If true, collect raw CPU time metrics
+ collect_cpu_time = false
+ ## If true, compute and report the sum of all non-idle CPU states
+ report_active = false
+ ## If true and the info is available then add core_id and physical_id tags
+ core_tags = false
+ name_override = "root.demo.telgraf.cpu"
+```
+
+2. Modify the configuration of the output iotdb plugin in cpu_iotdb. conf
+
+| Configuration | Description | Before Modification | After Modification | Notes |
+| ------------------- | -------------- | ----------------------------------- | ------------------------------------------------- | ------------------------------------------------------------ |
+| host | Host of IoTDB | # host = "127.0.0.1" | host = "Deploy IoTDB host" | Default is 127.0.0.1 |
+| port | The port number of IoTDB | # port = "6667" | port = "Port number for deploying IoTDB" | Default is 6667 |
+| user | Username for IoTDB | # user = "root" | user = "Username for IoTDB" |Default as root |
+| password | Password for IoTDB | # password = "root" | password= "Password for IoTDB" | Default as root |
+| timestamp_precision | Timestamp accuracy | timestamp_precision = "millisecond" | timestamp_precision = "Same timestamp accuracy as IoTDB" | You can check the 'timestamp-precision' field in 'iotdb system. properties' |
+| sanitize_tag | Database version | none | sanitize_tag = "0.13/1.0/1.1/1.2/1.3" | |
+
+```Bash
+# Save metrics to an IoTDB Database
+[[outputs.iotdb]]
+ ## Configuration of IoTDB server connection
+ host = "127.0.0.1"
+ # port = "6667"
+
+ ## Configuration of authentication
+ # user = "root"
+ # password = "root"
+
+ ## Timeout to open a new session.
+ ## A value of zero means no timeout.
+ # timeout = "5s"
+
+ ## Configuration of type conversion for 64-bit unsigned int
+ ## IoTDB currently DOES NOT support unsigned integers (version 13.x).
+ ## 32-bit unsigned integers are safely converted into 64-bit signed integers by the plugin,
+ ## however, this is not true for 64-bit values in general as overflows may occur.
+ ## The following setting allows to specify the handling of 64-bit unsigned integers.
+ ## Available values are:
+ ## - "int64" -- convert to 64-bit signed integers and accept overflows
+ ## - "int64_clip" -- convert to 64-bit signed integers and clip the values on overflow to 9,223,372,036,854,775,807
+ ## - "text" -- convert to the string representation of the value
+ # uint64_conversion = "int64_clip"
+
+ ## Configuration of TimeStamp
+ ## TimeStamp is always saved in 64bits int. timestamp_precision specifies the unit of timestamp.
+ ## Available value:
+ ## "second", "millisecond", "microsecond", "nanosecond"(default)
+ timestamp_precision = "millisecond"
+
+ ## Handling of tags
+ ## Tags are not fully supported by IoTDB.
+ ## A guide with suggestions on how to handle tags can be found here:
+ ## https://iotdb.apache.org/UserGuide/Master/API/InfluxDB-Protocol.html
+ ##
+ ## Available values are:
+ ## - "fields" -- convert tags to fields in the measurement
+ ## - "device_id" -- attach tags to the device ID
+ ##
+ ## For Example, a metric named "root.sg.device" with the tags `tag1: "private"` and `tag2: "working"` and
+ ## fields `s1: 100` and `s2: "hello"` will result in the following representations in IoTDB
+ ## - "fields" -- root.sg.device, s1=100, s2="hello", tag1="private", tag2="working"
+ ## - "device_id" -- root.sg.device.private.working, s1=100, s2="hello"
+ # convert_tags_to = "device_id"
+ ## Handling of unsupported characters
+ ## Some characters in different versions of IoTDB are not supported in path name
+ ## A guide with suggetions on valid paths can be found here:
+ ## for iotdb 0.13.x -> https://iotdb.apache.org/UserGuide/V0.13.x/Reference/Syntax-Conventions.html#identifiers
+ ## for iotdb 1.x.x and above -> https://iotdb.apache.org/UserGuide/V1.3.x/User-Manual/Syntax-Rule.html#identifier
+ ##
+ ## Available values are:
+ ## - "1.0", "1.1", "1.2", "1.3" -- enclose in `` the world having forbidden character
+ ## such as @ $ # : [ ] { } ( ) space
+ ## - "0.13" -- enclose in `` the world having forbidden character
+ ## such as space
+ ##
+ ## Keep this section commented if you don't want to sanitize the path
+ sanitize_tag = "1.3"
+```
+
+3. Run Telegraf using the cpu_iotdb.exe configuration file: After running for a period of time, the data collected and reported by Telegraf can be queried in IoTDB
\ No newline at end of file
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Thingsboard.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Thingsboard.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Thingsboard.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/Thingsboard.md
diff --git a/src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Zeppelin-IoTDB.md b/src/UserGuide/V1.3.3/Ecosystem-Integration/Zeppelin-IoTDB.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Ecosystem-Integration/Zeppelin-IoTDB.md
rename to src/UserGuide/V1.3.3/Ecosystem-Integration/Zeppelin-IoTDB.md
diff --git a/src/UserGuide/V2.0.1/Tree/FAQ/Frequently-asked-questions.md b/src/UserGuide/V1.3.3/FAQ/Frequently-asked-questions.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/FAQ/Frequently-asked-questions.md
rename to src/UserGuide/V1.3.3/FAQ/Frequently-asked-questions.md
diff --git a/src/UserGuide/V2.0.1/Tree/IoTDB-Introduction/IoTDB-Introduction_apache.md b/src/UserGuide/V1.3.3/IoTDB-Introduction/IoTDB-Introduction_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/IoTDB-Introduction/IoTDB-Introduction_apache.md
rename to src/UserGuide/V1.3.3/IoTDB-Introduction/IoTDB-Introduction_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/IoTDB-Introduction/IoTDB-Introduction_timecho.md b/src/UserGuide/V1.3.3/IoTDB-Introduction/IoTDB-Introduction_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/IoTDB-Introduction/IoTDB-Introduction_timecho.md
rename to src/UserGuide/V1.3.3/IoTDB-Introduction/IoTDB-Introduction_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/IoTDB-Introduction/Scenario.md b/src/UserGuide/V1.3.3/IoTDB-Introduction/Scenario.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/IoTDB-Introduction/Scenario.md
rename to src/UserGuide/V1.3.3/IoTDB-Introduction/Scenario.md
diff --git a/src/UserGuide/V2.0.1/Table/QuickStart/QuickStart.md b/src/UserGuide/V1.3.3/QuickStart/QuickStart.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/QuickStart/QuickStart.md
rename to src/UserGuide/V1.3.3/QuickStart/QuickStart.md
diff --git a/src/UserGuide/V2.0.1/Tree/QuickStart/QuickStart_apache.md b/src/UserGuide/V1.3.3/QuickStart/QuickStart_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/QuickStart/QuickStart_apache.md
rename to src/UserGuide/V1.3.3/QuickStart/QuickStart_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/QuickStart/QuickStart_timecho.md b/src/UserGuide/V1.3.3/QuickStart/QuickStart_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/QuickStart/QuickStart_timecho.md
rename to src/UserGuide/V1.3.3/QuickStart/QuickStart_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Reference/Common-Config-Manual.md b/src/UserGuide/V1.3.3/Reference/Common-Config-Manual.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Reference/Common-Config-Manual.md
rename to src/UserGuide/V1.3.3/Reference/Common-Config-Manual.md
diff --git a/src/UserGuide/V2.0.1/Tree/Reference/ConfigNode-Config-Manual.md b/src/UserGuide/V1.3.3/Reference/ConfigNode-Config-Manual.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Reference/ConfigNode-Config-Manual.md
rename to src/UserGuide/V1.3.3/Reference/ConfigNode-Config-Manual.md
diff --git a/src/UserGuide/V2.0.1/Tree/Reference/DataNode-Config-Manual.md b/src/UserGuide/V1.3.3/Reference/DataNode-Config-Manual.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Reference/DataNode-Config-Manual.md
rename to src/UserGuide/V1.3.3/Reference/DataNode-Config-Manual.md
diff --git a/src/UserGuide/V2.0.1/Tree/Reference/DataNode-Config-Manual_apache.md b/src/UserGuide/V1.3.3/Reference/DataNode-Config-Manual_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Reference/DataNode-Config-Manual_apache.md
rename to src/UserGuide/V1.3.3/Reference/DataNode-Config-Manual_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/Reference/DataNode-Config-Manual_timecho.md b/src/UserGuide/V1.3.3/Reference/DataNode-Config-Manual_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Reference/DataNode-Config-Manual_timecho.md
rename to src/UserGuide/V1.3.3/Reference/DataNode-Config-Manual_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Reference/Keywords.md b/src/UserGuide/V1.3.3/Reference/Keywords.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Reference/Keywords.md
rename to src/UserGuide/V1.3.3/Reference/Keywords.md
diff --git a/src/UserGuide/V2.0.1/Tree/Reference/Modify-Config-Manual.md b/src/UserGuide/V1.3.3/Reference/Modify-Config-Manual.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Reference/Modify-Config-Manual.md
rename to src/UserGuide/V1.3.3/Reference/Modify-Config-Manual.md
diff --git a/src/UserGuide/V2.0.1/Tree/Reference/Status-Codes.md b/src/UserGuide/V1.3.3/Reference/Status-Codes.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Reference/Status-Codes.md
rename to src/UserGuide/V1.3.3/Reference/Status-Codes.md
diff --git a/src/UserGuide/V2.0.1/Tree/Reference/Syntax-Rule.md b/src/UserGuide/V1.3.3/Reference/Syntax-Rule.md
similarity index 99%
rename from src/UserGuide/V2.0.1/Tree/Reference/Syntax-Rule.md
rename to src/UserGuide/V1.3.3/Reference/Syntax-Rule.md
index 38dffc6ac..40d858e28 100644
--- a/src/UserGuide/V2.0.1/Tree/Reference/Syntax-Rule.md
+++ b/src/UserGuide/V1.3.3/Reference/Syntax-Rule.md
@@ -172,6 +172,7 @@ Below are basic constraints of identifiers, specific identifiers may have other
- [0-9 a-z A-Z _ ] (letters, digits and underscore)
- ['\u2E80'..'\u9FFF'] (UNICODE Chinese characters)
+
### Reverse quotation marks
**If the following situations occur, the identifier needs to be quoted using reverse quotes:**
@@ -278,4 +279,5 @@ create device template `t1't"t`
```sql
`root.db.*`
- ```
\ No newline at end of file
+ ```
+
diff --git a/src/UserGuide/V2.0.1/Tree/SQL-Manual/Function-and-Expression.md b/src/UserGuide/V1.3.3/SQL-Manual/Function-and-Expression.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/SQL-Manual/Function-and-Expression.md
rename to src/UserGuide/V1.3.3/SQL-Manual/Function-and-Expression.md
diff --git a/src/UserGuide/V2.0.1/Tree/SQL-Manual/Operator-and-Expression.md b/src/UserGuide/V1.3.3/SQL-Manual/Operator-and-Expression.md
similarity index 97%
rename from src/UserGuide/V2.0.1/Tree/SQL-Manual/Operator-and-Expression.md
rename to src/UserGuide/V1.3.3/SQL-Manual/Operator-and-Expression.md
index 1b6fd667f..c6fec7f61 100644
--- a/src/UserGuide/V2.0.1/Tree/SQL-Manual/Operator-and-Expression.md
+++ b/src/UserGuide/V1.3.3/SQL-Manual/Operator-and-Expression.md
@@ -25,7 +25,7 @@ This chapter describes the operators and functions supported by IoTDB. IoTDB pro
A list of all available functions, both built-in and custom, can be displayed with `SHOW FUNCTIONS` command.
-See the documentation [Select-Expression](../SQL-Manual/Function-and-Expression.md#selector-functions) for the behavior of operators and functions in SQL.
+See the documentation [Select-Expression](./Function-and-Expression.md#selector-functions) for the behavior of operators and functions in SQL.
## OPERATORS
@@ -41,7 +41,7 @@ See the documentation [Select-Expression](../SQL-Manual/Function-and-Expression.
| `+` | addition |
| `-` | subtraction |
-For details and examples, see the document [Arithmetic Operators and Functions](../SQL-Manual/Function-and-Expression.md#arithmetic-functions).
+For details and examples, see the document [Arithmetic Operators and Functions](./Function-and-Expression.md#arithmetic-functions).
### Comparison Operators
@@ -64,7 +64,7 @@ For details and examples, see the document [Arithmetic Operators and Functions](
| `IN` / `CONTAINS` | is a value in the specified list |
| `NOT IN` / `NOT CONTAINS` | is not a value in the specified list |
-For details and examples, see the document [Comparison Operators and Functions](../SQL-Manual/Function-and-Expression.md#comparison-operators-and-functions).
+For details and examples, see the document [Comparison Operators and Functions](./Function-and-Expression.md#comparison-operators-and-functions).
### Logical Operators
@@ -74,7 +74,7 @@ For details and examples, see the document [Comparison Operators and Functions](
| `AND` / `&` / `&&` | logical AND |
| `OR`/ | / || | logical OR |
-For details and examples, see the document [Logical Operators](../SQL-Manual/Function-and-Expression.md#logical-operators).
+For details and examples, see the document [Logical Operators](./Function-and-Expression.md#logical-operators).
### Operator Precedence
@@ -123,7 +123,7 @@ The built-in functions can be used in IoTDB without registration, and the functi
| MAX_BY | MAX_BY(x, y) returns the value of x corresponding to the maximum value of the input y. MAX_BY(time, x) returns the timestamp when x is at its maximum value. | The first input x can be of any type, while the second input y must be of type INT32, INT64, FLOAT, DOUBLE, STRING, TIMESTAMP or DATE. | / | Consistent with the data type of the first input x. |
| MIN_BY | MIN_BY(x, y) returns the value of x corresponding to the minimum value of the input y. MIN_BY(time, x) returns the timestamp when x is at its minimum value. | The first input x can be of any type, while the second input y must be of type INT32, INT64, FLOAT, DOUBLE, STRING, TIMESTAMP or DATE. | / | Consistent with the data type of the first input x. |
-For details and examples, see the document [Aggregate Functions](../SQL-Manual/Function-and-Expression.md#aggregate-functions).
+For details and examples, see the document [Aggregate Functions](./Function-and-Expression.md#aggregate-functions).
### Arithmetic Functions
@@ -150,7 +150,7 @@ For details and examples, see the document [Aggregate Functions](../SQL-Manual/F
| LOG10 | INT32 / INT64 / FLOAT / DOUBLE | DOUBLE | / | Math#log10(double) |
| SQRT | INT32 / INT64 / FLOAT / DOUBLE | DOUBLE | / | Math#sqrt(double) |
-For details and examples, see the document [Arithmetic Operators and Functions](../SQL-Manual/Function-and-Expression.md#arithmetic-operators-and-functions).
+For details and examples, see the document [Arithmetic Operators and Functions](./Function-and-Expression.md#arithmetic-operators-and-functions).
### Comparison Functions
@@ -159,7 +159,7 @@ For details and examples, see the document [Arithmetic Operators and Functions](
| ON_OFF | INT32 / INT64 / FLOAT / DOUBLE | `threshold`: a double type variate | BOOLEAN | Return `ts_value >= threshold`. |
| IN_RANGR | INT32 / INT64 / FLOAT / DOUBLE | `lower`: DOUBLE type `upper`: DOUBLE type | BOOLEAN | Return `ts_value >= lower && value <= upper`. |
-For details and examples, see the document [Comparison Operators and Functions](../SQL-Manual/Function-and-Expression.md#comparison-operators-and-functions).
+For details and examples, see the document [Comparison Operators and Functions](./Function-and-Expression.md#comparison-operators-and-functions).
### String Processing Functions
@@ -179,7 +179,7 @@ For details and examples, see the document [Comparison Operators and Functions](
| TRIM | TEXT STRING | / | TEXT | Get the string whose value is same to input series, with all leading and trailing space removed. |
| STRCMP | TEXT STRING | / | TEXT | Get the compare result of two input series. Returns `0` if series value are the same, a `negative integer` if value of series1 is smaller than series2,
a `positive integer` if value of series1 is more than series2. |
-For details and examples, see the document [String Processing](../SQL-Manual/Function-and-Expression.md#string-processing).
+For details and examples, see the document [String Processing](./Function-and-Expression.md#string-processing).
### Data Type Conversion Function
@@ -187,7 +187,7 @@ For details and examples, see the document [String Processing](../SQL-Manual/Fun
| ------------- | ------------------------------------------------------------ | ----------------------- | ------------------------------------------------------------ |
| CAST | `type`: Output data type, INT32 / INT64 / FLOAT / DOUBLE / BOOLEAN / TEXT | determined by `type` | Convert the data to the type specified by the `type` parameter. |
-For details and examples, see the document [Data Type Conversion Function](../SQL-Manual/Function-and-Expression.md#data-type-conversion-function).
+For details and examples, see the document [Data Type Conversion Function](./Function-and-Expression.md#data-type-conversion-function).
### Constant Timeseries Generating Functions
@@ -197,7 +197,7 @@ For details and examples, see the document [Data Type Conversion Function](../SQ
| PI | None | DOUBLE | Data point value: a `double` value of `π`, the ratio of the circumference of a circle to its diameter, which is equals to `Math.PI` in the *Java Standard Library*. |
| E | None | DOUBLE | Data point value: a `double` value of `e`, the base of the natural logarithms, which is equals to `Math.E` in the *Java Standard Library*. |
-For details and examples, see the document [Constant Timeseries Generating Functions](../SQL-Manual/Function-and-Expression.md#constant-timeseries-generating-functions).
+For details and examples, see the document [Constant Timeseries Generating Functions](./Function-and-Expression.md#constant-timeseries-generating-functions).
### Selector Functions
@@ -206,7 +206,7 @@ For details and examples, see the document [Constant Timeseries Generating Funct
| TOP_K | INT32 / INT64 / FLOAT / DOUBLE / TEXT / STRING / DATE / TIEMSTAMP | `k`: the maximum number of selected data points, must be greater than 0 and less than or equal to 1000 | Same type as the input series | Returns `k` data points with the largest values in a time series. |
| BOTTOM_K | INT32 / INT64 / FLOAT / DOUBLE / TEXT / STRING / DATE / TIEMSTAMP | `k`: the maximum number of selected data points, must be greater than 0 and less than or equal to 1000 | Same type as the input series | Returns `k` data points with the smallest values in a time series. |
-For details and examples, see the document [Selector Functions](../SQL-Manual/Function-and-Expression.md#selector-functions).
+For details and examples, see the document [Selector Functions](./Function-and-Expression.md#selector-functions).
### Continuous Interval Functions
@@ -217,7 +217,7 @@ For details and examples, see the document [Selector Functions](../SQL-Manual/Fu
| ZERO_COUNT | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:Optional with default value `1L` `max`:Optional with default value `Long.MAX_VALUE` | Long | Return intervals' start times and the number of data points in the interval in which the value is always 0(false). Data points number `n` satisfy `n >= min && n <= max` |
| NON_ZERO_COUNT | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:Optional with default value `1L` `max`:Optional with default value `Long.MAX_VALUE` | Long | Return intervals' start times and the number of data points in the interval in which the value is always not 0(false). Data points number `n` satisfy `n >= min && n <= max` |
-For details and examples, see the document [Continuous Interval Functions](../SQL-Manual/Function-and-Expression.md#continuous-interval-functions).
+For details and examples, see the document [Continuous Interval Functions](./Function-and-Expression.md#continuous-interval-functions).
### Variation Trend Calculation Functions
@@ -230,7 +230,7 @@ For details and examples, see the document [Continuous Interval Functions](../SQ
| NON_NEGATIVE_DERIVATIVE | INT32 / INT64 / FLOAT / DOUBLE | / | DOUBLE | Calculates the absolute value of the rate of change of a data point compared to the previous data point, the result is equals to NON_NEGATIVE_DIFFERENCE / TIME_DIFFERENCE. There is no corresponding output for the first data point. |
| DIFF | INT32 / INT64 / FLOAT / DOUBLE | `ignoreNull`：optional，default is true. If is true, the previous data point is ignored when it is null and continues to find the first non-null value forwardly. If the value is false, previous data point is not ignored when it is null, the result is also null because null is used for subtraction | DOUBLE | Calculates the difference between the value of a data point and the value of the previous data point. There is no corresponding output for the first data point, so output is null |
-For details and examples, see the document [Variation Trend Calculation Functions](../SQL-Manual/Function-and-Expression.md#variation-trend-calculation-functions).
+For details and examples, see the document [Variation Trend Calculation Functions](./Function-and-Expression.md#variation-trend-calculation-functions).
### Sample Functions
@@ -250,7 +250,7 @@ For details and examples, see the document [Sample Functions](../SQL-Manual/Func
| ------------- | ------------------------------- | ------------------- | ----------------------------- | ----------------------------------------------------------- |
| CHANGE_POINTS | INT32 / INT64 / FLOAT / DOUBLE | / | Same type as the input series | Remove consecutive identical values from an input sequence. |
-For details and examples, see the document [Time-Series](../SQL-Manual/Function-and-Expression.md#time-series-processing).
+For details and examples, see the document [Time-Series](./Function-and-Expression.md#time-series-processing).
## LAMBDA EXPRESSION
@@ -259,7 +259,7 @@ For details and examples, see the document [Time-Series](../SQL-Manual/Function-
| ------------- | ----------------------------------------------- | ------------------------------------------------------------ | ----------------------------------------------- | ------------------------------------------------------------ |
| JEXL | INT32 / INT64 / FLOAT / DOUBLE / TEXT / BOOLEAN | `expr` is a lambda expression that supports standard one or multi arguments in the form `x -> {...}` or `(x, y, z) -> {...}`, e.g. `x -> {x * 2}`, `(x, y, z) -> {x + y * z}` | INT32 / INT64 / FLOAT / DOUBLE / TEXT / BOOLEAN | Returns the input time series transformed by a lambda expression |
-For details and examples, see the document [Lambda](../SQL-Manual/Function-and-Expression.md#lambda-expression).
+For details and examples, see the document [Lambda](./Function-and-Expression.md#lambda-expression).
## CONDITIONAL EXPRESSION
@@ -267,7 +267,7 @@ For details and examples, see the document [Lambda](../SQL-Manual/Function-and-E
| --------------- | -------------------- |
| `CASE` | similar to "if else" |
-For details and examples, see the document [Conditional Expressions](../SQL-Manual/Function-and-Expression.md#conditional-expressions).
+For details and examples, see the document [Conditional Expressions](./Function-and-Expression.md#conditional-expressions).
## SELECT EXPRESSION
@@ -322,7 +322,7 @@ Aggregate functions are many-to-one functions. They perform aggregate calculatio
> select a, count(a) from root.sg group by ([10,100),10ms)
> ```
-For the aggregation functions supported by IoTDB, see the document [Aggregate Functions](../SQL-Manual/Function-and-Expression.md#aggregate-functions).
+For the aggregation functions supported by IoTDB, see the document [Aggregate Functions](./Function-and-Expression.md#aggregate-functions).
#### Time Series Generation Function
diff --git a/src/UserGuide/V2.0.1/Tree/SQL-Manual/SQL-Manual.md b/src/UserGuide/V1.3.3/SQL-Manual/SQL-Manual.md
similarity index 97%
rename from src/UserGuide/V2.0.1/Tree/SQL-Manual/SQL-Manual.md
rename to src/UserGuide/V1.3.3/SQL-Manual/SQL-Manual.md
index 2a078041c..4ac977278 100644
--- a/src/UserGuide/V2.0.1/Tree/SQL-Manual/SQL-Manual.md
+++ b/src/UserGuide/V1.3.3/SQL-Manual/SQL-Manual.md
@@ -602,7 +602,7 @@ IoTDB > select avg(temperature),
from root.ln.wf01.wt01;
IoTDB > select avg(*),
- (avg(*) + 1) * 3 / 2 -1
+ (avg(*) + 1) * 3 / 2 -1
from root.sg1
IoTDB > select avg(temperature),
@@ -1090,11 +1090,11 @@ select change_points(s1), change_points(s2), change_points(s3), change_points(s4
## DATA QUALITY FUNCTION LIBRARY
-For more details, see document [Operator-and-Expression](../SQL-Manual/UDF-Libraries.md).
+For more details, see document [Operator-and-Expression](./UDF-Libraries.md).
### Data Quality
-For details and examples, see the document [Data-Quality](../SQL-Manual/UDF-Libraries.md#data-quality).
+For details and examples, see the document [Data-Quality](./UDF-Libraries.md#data-quality).
```sql
# Completeness
@@ -1119,7 +1119,7 @@ select Accuracy(t1,t2,t3,m1,m2,m3) from root.test
### Data Profiling
-For details and examples, see the document [Data-Profiling](../SQL-Manual/UDF-Libraries.md#data-profiling).
+For details and examples, see the document [Data-Profiling](./UDF-Libraries.md#data-profiling).
```sql
# ACF
@@ -1199,7 +1199,7 @@ select zscore(s1) from root.test
### Anomaly Detection
-For details and examples, see the document [Anomaly-Detection](../SQL-Manual/UDF-Libraries.md#anomaly-detection).
+For details and examples, see the document [Anomaly-Detection](./UDF-Libraries.md#anomaly-detection).
```sql
# IQR
@@ -1234,7 +1234,7 @@ select MasterDetect(lo,la,m_lo,m_la,model,'output_type'='anomaly','p'='3','k'='3
### Frequency Domain
-For details and examples, see the document [Frequency-Domain](../SQL-Manual/UDF-Libraries.md#frequency-domain-analysis).
+For details and examples, see the document [Frequency-Domain](./UDF-Libraries.md#frequency-domain-analysis).
```sql
# Conv
@@ -1266,7 +1266,7 @@ select envelope(s1) from root.test.d1
### Data Matching
-For details and examples, see the document [Data-Matching](../SQL-Manual/UDF-Libraries.md#data-matching).
+For details and examples, see the document [Data-Matching](./UDF-Libraries.md#data-matching).
```sql
# Cov
@@ -1287,7 +1287,7 @@ select xcorr(s1, s2) from root.test.d1 where time <= 2020-01-01 00:00:05
### Data Repairing
-For details and examples, see the document [Data-Repairing](../SQL-Manual/UDF-Libraries.md#data-repairing).
+For details and examples, see the document [Data-Repairing](./UDF-Libraries.md#data-repairing).
```sql
# TimestampRepair
@@ -1312,7 +1312,7 @@ select seasonalrepair(s1,'method'='improved','period'=3) from root.test.d2
### Series Discovery
-For details and examples, see the document [Series-Discovery](../SQL-Manual/UDF-Libraries.md#series-discovery).
+For details and examples, see the document [Series-Discovery](./UDF-Libraries.md#series-discovery).
```sql
# ConsecutiveSequences
@@ -1325,7 +1325,7 @@ select consecutivewindows(s1,s2,'length'='10m') from root.test.d1
### Machine Learning
-For details and examples, see the document [Machine-Learning](../SQL-Manual/UDF-Libraries.md#machine-learning).
+For details and examples, see the document [Machine-Learning](./UDF-Libraries.md#machine-learning).
```sql
# AR
@@ -1340,7 +1340,7 @@ select rm(s0, s1,"tb"="3","vb"="2") from root.test.d0
## LAMBDA EXPRESSION
-For details and examples, see the document [Lambda](../SQL-Manual/UDF-Libraries.md#lambda-expression).
+For details and examples, see the document [Lambda](./UDF-Libraries.md#lambda-expression).
```sql
select jexl(temperature, 'expr'='x -> {x + x}') as jexl1, jexl(temperature, 'expr'='x -> {x * 3}') as jexl2, jexl(temperature, 'expr'='x -> {x * x}') as jexl3, jexl(temperature, 'expr'='x -> {multiply(x, 100)}') as jexl4, jexl(temperature, st, 'expr'='(x, y) -> {x + y}') as jexl5, jexl(temperature, st, str, 'expr'='(x, y, z) -> {x + y + z}') as jexl6 from root.ln.wf01.wt01;```
@@ -1348,7 +1348,7 @@ select jexl(temperature, 'expr'='x -> {x + x}') as jexl1, jexl(temperature, 'exp
## CONDITIONAL EXPRESSION
-For details and examples, see the document [Conditional Expressions](../SQL-Manual/UDF-Libraries.md#conditional-expressions).
+For details and examples, see the document [Conditional Expressions](./UDF-Libraries.md#conditional-expressions).
```sql
select T, P, case
@@ -1548,7 +1548,7 @@ CQs can't be altered once they're created. To change a CQ, you must `DROP` and r
## USER-DEFINED FUNCTION (UDF)
-For more details, see document [Operator-and-Expression](../SQL-Manual/UDF-Libraries.md).
+For more details, see document [Operator-and-Expression](./UDF-Libraries.md).
### UDF Registration
diff --git a/src/UserGuide/V2.0.1/Tree/SQL-Manual/UDF-Libraries.md b/src/UserGuide/V1.3.3/SQL-Manual/UDF-Libraries.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/SQL-Manual/UDF-Libraries.md
rename to src/UserGuide/V1.3.3/SQL-Manual/UDF-Libraries.md
diff --git a/src/UserGuide/V2.0.1/Tree/SQL-Manual/UDF-Libraries_apache.md b/src/UserGuide/V1.3.3/SQL-Manual/UDF-Libraries_apache.md
similarity index 99%
rename from src/UserGuide/V2.0.1/Tree/SQL-Manual/UDF-Libraries_apache.md
rename to src/UserGuide/V1.3.3/SQL-Manual/UDF-Libraries_apache.md
index c2a0dcd54..8bab853b8 100644
--- a/src/UserGuide/V2.0.1/Tree/SQL-Manual/UDF-Libraries_apache.md
+++ b/src/UserGuide/V1.3.3/SQL-Manual/UDF-Libraries_apache.md
@@ -37,7 +37,7 @@ Based on the ability of user-defined functions, IoTDB provides a series of funct
| apache-UDF-1.3.2.zip | V1.0.0～V1.3.2 | Please contact Timecho 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.
+3. In the SQL operation interface of IoTDB's SQL command line terminal (CLI), execute the corresponding function registration statement as follows.
4. Batch registration: Two registration methods: registration script or SQL full statement
- Register Script
- Copy the registration script (register-UDF.sh or register-UDF.bat) from the compressed package to the `tools` directory of IoTDB as needed, and modify the parameters in the script (default is host=127.0.0.1, rpcPort=6667, user=root, pass=root);
@@ -46,6 +46,7 @@ Based on the ability of user-defined functions, IoTDB provides a series of funct
- All SQL statements
- Open the SQl file in the compressed package, copy all SQL statements, and in the SQL operation interface of IoTDB's SQL command line terminal (CLI), execute all SQl statements to batch register UDFs
+
## Data Quality
### Completeness
diff --git a/src/UserGuide/V2.0.1/Tree/SQL-Manual/UDF-Libraries_timecho.md b/src/UserGuide/V1.3.3/SQL-Manual/UDF-Libraries_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/SQL-Manual/UDF-Libraries_timecho.md
rename to src/UserGuide/V1.3.3/SQL-Manual/UDF-Libraries_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Technical-Insider/Cluster-data-partitioning.md b/src/UserGuide/V1.3.3/Technical-Insider/Cluster-data-partitioning.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Technical-Insider/Cluster-data-partitioning.md
rename to src/UserGuide/V1.3.3/Technical-Insider/Cluster-data-partitioning.md
diff --git a/src/UserGuide/V2.0.1/Tree/Technical-Insider/Encoding-and-Compression.md b/src/UserGuide/V1.3.3/Technical-Insider/Encoding-and-Compression.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Technical-Insider/Encoding-and-Compression.md
rename to src/UserGuide/V1.3.3/Technical-Insider/Encoding-and-Compression.md
diff --git a/src/UserGuide/V2.0.1/Tree/Technical-Insider/Publication.md b/src/UserGuide/V1.3.3/Technical-Insider/Publication.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Technical-Insider/Publication.md
rename to src/UserGuide/V1.3.3/Technical-Insider/Publication.md
diff --git a/src/UserGuide/V2.0.1/Tree/Tools-System/Benchmark.md b/src/UserGuide/V1.3.3/Tools-System/Benchmark.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Tools-System/Benchmark.md
rename to src/UserGuide/V1.3.3/Tools-System/Benchmark.md
diff --git a/src/UserGuide/V2.0.1/Tree/Tools-System/CLI.md b/src/UserGuide/V1.3.3/Tools-System/CLI.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Tools-System/CLI.md
rename to src/UserGuide/V1.3.3/Tools-System/CLI.md
diff --git a/src/UserGuide/V2.0.1/Tree/Tools-System/Data-Export-Tool.md b/src/UserGuide/V1.3.3/Tools-System/Data-Export-Tool.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Tools-System/Data-Export-Tool.md
rename to src/UserGuide/V1.3.3/Tools-System/Data-Export-Tool.md
diff --git a/src/UserGuide/V2.0.1/Tree/Tools-System/Data-Import-Tool.md b/src/UserGuide/V1.3.3/Tools-System/Data-Import-Tool.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Tools-System/Data-Import-Tool.md
rename to src/UserGuide/V1.3.3/Tools-System/Data-Import-Tool.md
diff --git a/src/UserGuide/V2.0.1/Tree/Tools-System/Maintenance-Tool_apache.md b/src/UserGuide/V1.3.3/Tools-System/Maintenance-Tool_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Tools-System/Maintenance-Tool_apache.md
rename to src/UserGuide/V1.3.3/Tools-System/Maintenance-Tool_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/Tools-System/Maintenance-Tool_timecho.md b/src/UserGuide/V1.3.3/Tools-System/Maintenance-Tool_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Tools-System/Maintenance-Tool_timecho.md
rename to src/UserGuide/V1.3.3/Tools-System/Maintenance-Tool_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Tools-System/Monitor-Tool_apache.md b/src/UserGuide/V1.3.3/Tools-System/Monitor-Tool_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Tools-System/Monitor-Tool_apache.md
rename to src/UserGuide/V1.3.3/Tools-System/Monitor-Tool_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/Tools-System/Monitor-Tool_timecho.md b/src/UserGuide/V1.3.3/Tools-System/Monitor-Tool_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Tools-System/Monitor-Tool_timecho.md
rename to src/UserGuide/V1.3.3/Tools-System/Monitor-Tool_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Tools-System/Workbench_timecho.md b/src/UserGuide/V1.3.3/Tools-System/Workbench_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Tools-System/Workbench_timecho.md
rename to src/UserGuide/V1.3.3/Tools-System/Workbench_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/AINode_timecho.md b/src/UserGuide/V1.3.3/User-Manual/AINode_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/AINode_timecho.md
rename to src/UserGuide/V1.3.3/User-Manual/AINode_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Audit-Log_timecho.md b/src/UserGuide/V1.3.3/User-Manual/Audit-Log_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Audit-Log_timecho.md
rename to src/UserGuide/V1.3.3/User-Manual/Audit-Log_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Authority-Management.md b/src/UserGuide/V1.3.3/User-Manual/Authority-Management.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Authority-Management.md
rename to src/UserGuide/V1.3.3/User-Manual/Authority-Management.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Data-Recovery.md b/src/UserGuide/V1.3.3/User-Manual/Data-Recovery.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Data-Recovery.md
rename to src/UserGuide/V1.3.3/User-Manual/Data-Recovery.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Data-Sync_apache.md b/src/UserGuide/V1.3.3/User-Manual/Data-Sync_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Data-Sync_apache.md
rename to src/UserGuide/V1.3.3/User-Manual/Data-Sync_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Data-Sync_timecho.md b/src/UserGuide/V1.3.3/User-Manual/Data-Sync_timecho.md
similarity index 99%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Data-Sync_timecho.md
rename to src/UserGuide/V1.3.3/User-Manual/Data-Sync_timecho.md
index 425bf0118..4669d357f 100644
--- a/src/UserGuide/V2.0.1/Tree/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/V1.3.3/User-Manual/Data-Sync_timecho.md
@@ -457,7 +457,6 @@ with sink (
| Unknown | GAP
XL—GAP | No Limit | No Limit |
-
### Compression Synchronization (V1.3.3+)
IoTDB supports specifying data compression methods during synchronization. Real time compression and transmission of data can be achieved by configuring the `compressor` parameter. `Compressor` currently supports 5 optional algorithms: snappy/gzip/lz4/zstd/lzma2, and can choose multiple compression algorithm combinations to compress in the order of configuration `rate-limit-bytes-per-second`(supported in V1.3.3 and later versions) is the maximum number of bytes allowed to be transmitted per second, calculated as compressed bytes. If it is less than 0, there is no limit.
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Data-subscription.md b/src/UserGuide/V1.3.3/User-Manual/Data-subscription.md
similarity index 99%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Data-subscription.md
rename to src/UserGuide/V1.3.3/User-Manual/Data-subscription.md
index 250115e36..3eefc3f8f 100644
--- a/src/UserGuide/V2.0.1/Tree/User-Manual/Data-subscription.md
+++ b/src/UserGuide/V1.3.3/User-Manual/Data-subscription.md
@@ -80,7 +80,6 @@ WITH (
'start-time' = '2023-01-01',
'end-time' = '2023-12-31'
);
-```
#### 3.1.2 Delete Topic
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Database-Programming.md b/src/UserGuide/V1.3.3/User-Manual/Database-Programming.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Database-Programming.md
rename to src/UserGuide/V1.3.3/User-Manual/Database-Programming.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/IoTDB-View_timecho.md b/src/UserGuide/V1.3.3/User-Manual/IoTDB-View_timecho.md
similarity index 99%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/IoTDB-View_timecho.md
rename to src/UserGuide/V1.3.3/User-Manual/IoTDB-View_timecho.md
index 195847395..b84bfef7a 100644
--- a/src/UserGuide/V2.0.1/Tree/User-Manual/IoTDB-View_timecho.md
+++ b/src/UserGuide/V1.3.3/User-Manual/IoTDB-View_timecho.md
@@ -434,6 +434,8 @@ DELETE VIEW root.view.device.avg_temperatue
### View Synchronisation
+
+
#### If the dependent original sequence is deleted
When the sequence view is queried (when the sequence is parsed), **the empty result set** is returned if the dependent time series does not exist.
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Load-Balance.md b/src/UserGuide/V1.3.3/User-Manual/Load-Balance.md
similarity index 99%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Load-Balance.md
rename to src/UserGuide/V1.3.3/User-Manual/Load-Balance.md
index 45ae3299b..3453ea107 100644
--- a/src/UserGuide/V2.0.1/Tree/User-Manual/Load-Balance.md
+++ b/src/UserGuide/V1.3.3/User-Manual/Load-Balance.md
@@ -101,4 +101,4 @@ Here is a schematic diagram of the region migration process :
```plain
IoTDB> set configuration "wal_throttle_threshold_in_byte"="536870912000"
Msg: The statement is executed successfully.
- ```
\ No newline at end of file
+ ```
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Query-Performance-Analysis.md b/src/UserGuide/V1.3.3/User-Manual/Query-Performance-Analysis.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Query-Performance-Analysis.md
rename to src/UserGuide/V1.3.3/User-Manual/Query-Performance-Analysis.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Streaming_apache.md b/src/UserGuide/V1.3.3/User-Manual/Streaming_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Streaming_apache.md
rename to src/UserGuide/V1.3.3/User-Manual/Streaming_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Streaming_timecho.md b/src/UserGuide/V1.3.3/User-Manual/Streaming_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Streaming_timecho.md
rename to src/UserGuide/V1.3.3/User-Manual/Streaming_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Tiered-Storage_timecho.md b/src/UserGuide/V1.3.3/User-Manual/Tiered-Storage_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Tiered-Storage_timecho.md
rename to src/UserGuide/V1.3.3/User-Manual/Tiered-Storage_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/Trigger.md b/src/UserGuide/V1.3.3/User-Manual/Trigger.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/Trigger.md
rename to src/UserGuide/V1.3.3/User-Manual/Trigger.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/UDF-development.md b/src/UserGuide/V1.3.3/User-Manual/UDF-development.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/UDF-development.md
rename to src/UserGuide/V1.3.3/User-Manual/UDF-development.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/User-defined-function_apache.md b/src/UserGuide/V1.3.3/User-Manual/User-defined-function_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/User-defined-function_apache.md
rename to src/UserGuide/V1.3.3/User-Manual/User-defined-function_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/User-defined-function_timecho.md b/src/UserGuide/V1.3.3/User-Manual/User-defined-function_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/User-defined-function_timecho.md
rename to src/UserGuide/V1.3.3/User-Manual/User-defined-function_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/User-Manual/White-List_timecho.md b/src/UserGuide/V1.3.3/User-Manual/White-List_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/User-Manual/White-List_timecho.md
rename to src/UserGuide/V1.3.3/User-Manual/White-List_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/UserGuideReadme.md b/src/UserGuide/V1.3.3/UserGuideReadme.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/UserGuideReadme.md
rename to src/UserGuide/V1.3.3/UserGuideReadme.md
diff --git a/src/UserGuide/V2.0.1/Table/Basic-Concept/Sample-Data.md b/src/UserGuide/V2.0.1-Table/Basic-Concept/Sample-Data.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/Basic-Concept/Sample-Data.md
rename to src/UserGuide/V2.0.1-Table/Basic-Concept/Sample-Data.md
diff --git a/src/UserGuide/V2.0.1/Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
rename to src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Database-Resources.md b/src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Database-Resources.md
similarity index 99%
rename from src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Database-Resources.md
rename to src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Database-Resources.md
index d6210318a..374b03e2f 100644
--- a/src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Database-Resources.md
+++ b/src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Database-Resources.md
@@ -188,7 +188,6 @@ Calculation formula: Number of measurement points * Sampling frequency (Hz) * Si
Example: 1000 devices, each with 100 measurement points, a total of 100000 sequences, INT32 type. Sampling frequency 1Hz (once per second), storage for 1 year, 3 copies.
- Complete calculation formula: 1000 devices * 100 measurement points * 12 bytes per data point * 86400 seconds per day * 365 days per year * 3 copies / 10 compression ratio / 1024 / 1024 / 1024 / 1024 =11T
- Simplified calculation formula: 1000 * 100 * 12 * 86400 * 365 * 3 / 10 / 1024 / 1024 / 1024 / 1024 =11T
-
### Storage Configuration
If the number of nodes is over 10000000 or the query load is high, it is recommended to configure SSD
## Network (Network card)
diff --git a/src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Docker-Deployment_apache.md b/src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Docker-Deployment_apache.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Docker-Deployment_apache.md
rename to src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Docker-Deployment_apache.md
diff --git a/src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Docker-Deployment_timecho.md b/src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Docker-Deployment_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Docker-Deployment_timecho.md
rename to src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Docker-Deployment_timecho.md
diff --git a/src/UserGuide/V2.0.1/Table/Deployment-and-Maintenance/Dual-Active-Deployment_timecho.md b/src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Dual-Active-Deployment_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/Deployment-and-Maintenance/Dual-Active-Deployment_timecho.md
rename to src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Dual-Active-Deployment_timecho.md
diff --git a/src/UserGuide/V2.0.1/Table/Deployment-and-Maintenance/Environment-Requirements.md b/src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Environment-Requirements.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/Deployment-and-Maintenance/Environment-Requirements.md
rename to src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Environment-Requirements.md
diff --git a/src/UserGuide/V2.0.1/Table/Deployment-and-Maintenance/IoTDB-Package_timecho.md b/src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/IoTDB-Package_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/Deployment-and-Maintenance/IoTDB-Package_timecho.md
rename to src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/IoTDB-Package_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Monitoring-panel-deployment.md b/src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/Deployment-and-Maintenance/Monitoring-panel-deployment.md
rename to src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md
diff --git a/src/UserGuide/V2.0.1/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md b/src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
rename to src/UserGuide/V2.0.1-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
diff --git a/src/UserGuide/V2.0.1/Tree/QuickStart/QuickStart.md b/src/UserGuide/V2.0.1-Table/QuickStart/QuickStart.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Tree/QuickStart/QuickStart.md
rename to src/UserGuide/V2.0.1-Table/QuickStart/QuickStart.md
diff --git a/src/UserGuide/V2.0.1/Table/QuickStart/QuickStart_timecho.md b/src/UserGuide/V2.0.1-Table/QuickStart/QuickStart_timecho.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/QuickStart/QuickStart_timecho.md
rename to src/UserGuide/V2.0.1-Table/QuickStart/QuickStart_timecho.md
diff --git a/src/UserGuide/V2.0.1/Table/Reference/System-Config-Manual.md b/src/UserGuide/V2.0.1-Table/Reference/System-Config-Manual.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/Reference/System-Config-Manual.md
rename to src/UserGuide/V2.0.1-Table/Reference/System-Config-Manual.md
diff --git a/src/UserGuide/V2.0.1/Table/SQL-Manual/Fill-Clause.md b/src/UserGuide/V2.0.1-Table/SQL-Manual/Fill-Clause.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/SQL-Manual/Fill-Clause.md
rename to src/UserGuide/V2.0.1-Table/SQL-Manual/Fill-Clause.md
diff --git a/src/UserGuide/V2.0.1/Table/SQL-Manual/From-Join-Clause.md b/src/UserGuide/V2.0.1-Table/SQL-Manual/From-Join-Clause.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/SQL-Manual/From-Join-Clause.md
rename to src/UserGuide/V2.0.1-Table/SQL-Manual/From-Join-Clause.md
diff --git a/src/UserGuide/V2.0.1/Table/SQL-Manual/GroupBy-Clause.md b/src/UserGuide/V2.0.1-Table/SQL-Manual/GroupBy-Clause.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/SQL-Manual/GroupBy-Clause.md
rename to src/UserGuide/V2.0.1-Table/SQL-Manual/GroupBy-Clause.md
diff --git a/src/UserGuide/V2.0.1/Table/SQL-Manual/Having-Clause.md b/src/UserGuide/V2.0.1-Table/SQL-Manual/Having-Clause.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/SQL-Manual/Having-Clause.md
rename to src/UserGuide/V2.0.1-Table/SQL-Manual/Having-Clause.md
diff --git a/src/UserGuide/V2.0.1/Table/SQL-Manual/Identifier.md b/src/UserGuide/V2.0.1-Table/SQL-Manual/Identifier.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/SQL-Manual/Identifier.md
rename to src/UserGuide/V2.0.1-Table/SQL-Manual/Identifier.md
diff --git a/src/UserGuide/V2.0.1/Table/SQL-Manual/Keywords.md b/src/UserGuide/V2.0.1-Table/SQL-Manual/Keywords.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/SQL-Manual/Keywords.md
rename to src/UserGuide/V2.0.1-Table/SQL-Manual/Keywords.md
diff --git a/src/UserGuide/V2.0.1/Table/SQL-Manual/Limit-Offset-Clause.md b/src/UserGuide/V2.0.1-Table/SQL-Manual/Limit-Offset-Clause.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/SQL-Manual/Limit-Offset-Clause.md
rename to src/UserGuide/V2.0.1-Table/SQL-Manual/Limit-Offset-Clause.md
diff --git a/src/UserGuide/V2.0.1/Table/SQL-Manual/OrderBy-Clause.md b/src/UserGuide/V2.0.1-Table/SQL-Manual/OrderBy-Clause.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/SQL-Manual/OrderBy-Clause.md
rename to src/UserGuide/V2.0.1-Table/SQL-Manual/OrderBy-Clause.md
diff --git a/src/UserGuide/V2.0.1/Table/SQL-Manual/Select-Clause.md b/src/UserGuide/V2.0.1-Table/SQL-Manual/Select-Clause.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/SQL-Manual/Select-Clause.md
rename to src/UserGuide/V2.0.1-Table/SQL-Manual/Select-Clause.md
diff --git a/src/UserGuide/V2.0.1/Table/SQL-Manual/Where-Clause.md b/src/UserGuide/V2.0.1-Table/SQL-Manual/Where-Clause.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/SQL-Manual/Where-Clause.md
rename to src/UserGuide/V2.0.1-Table/SQL-Manual/Where-Clause.md
diff --git a/src/UserGuide/V2.0.1/Table/SQL-Manual/overview.md b/src/UserGuide/V2.0.1-Table/SQL-Manual/overview.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/SQL-Manual/overview.md
rename to src/UserGuide/V2.0.1-Table/SQL-Manual/overview.md
diff --git a/src/UserGuide/V2.0.1/Table/Tools-System/CLI.md b/src/UserGuide/V2.0.1-Table/Tools-System/CLI.md
similarity index 100%
rename from src/UserGuide/V2.0.1/Table/Tools-System/CLI.md
rename to src/UserGuide/V2.0.1-Table/Tools-System/CLI.md
diff --git a/src/UserGuide/V2.0.1/Tree/API/Programming-Go-Native-API.md b/src/UserGuide/V2.0.1/Tree/API/Programming-Go-Native-API.md
deleted file mode 100644
index b227ed672..000000000
--- a/src/UserGuide/V2.0.1/Tree/API/Programming-Go-Native-API.md
+++ /dev/null
@@ -1,64 +0,0 @@
-
-
-# Go Native API
-
-The Git repository for the Go Native API client is located [here](https://github.com/apache/iotdb-client-go/)
-
-## Dependencies
-
- * golang >= 1.13
- * make >= 3.0
- * curl >= 7.1.1
- * thrift 0.15.0
- * Linux、Macos or other unix-like systems
- * Windows+bash (WSL、cygwin、Git Bash)
-
-## Installation
-
- * go mod
-
-```sh
-export GO111MODULE=on
-export GOPROXY=https://goproxy.io
-
-mkdir session_example && cd session_example
-
-curl -o session_example.go -L https://github.com/apache/iotdb-client-go/raw/main/example/session_example.go
-
-go mod init session_example
-go run session_example.go
-```
-
-* GOPATH
-
-```sh
-# get thrift 0.15.0
-go get github.com/apache/thrift
-cd $GOPATH/src/github.com/apache/thrift
-git checkout 0.15.0
-
-mkdir -p $GOPATH/src/iotdb-client-go-example/session_example
-cd $GOPATH/src/iotdb-client-go-example/session_example
-curl -o session_example.go -L https://github.com/apache/iotdb-client-go/raw/main/example/session_example.go
-go run session_example.go
-```
-
diff --git a/src/UserGuide/V2.0.1/Tree/API/Programming-Kafka.md b/src/UserGuide/V2.0.1/Tree/API/Programming-Kafka.md
deleted file mode 100644
index 0a041448f..000000000
--- a/src/UserGuide/V2.0.1/Tree/API/Programming-Kafka.md
+++ /dev/null
@@ -1,118 +0,0 @@
-
-
-# Kafka
-
-[Apache Kafka](https://kafka.apache.org/) is an open-source distributed event streaming platform used by thousands of companies for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications.
-
-## Coding Example
-
-### kafka Producer Producing Data Java Code Example
-
-```java
- Properties props = new Properties();
- props.put("bootstrap.servers", "127.0.0.1:9092");
- props.put("key.serializer", StringSerializer.class);
- props.put("value.serializer", StringSerializer.class);
- KafkaProducer producer = new KafkaProducer<>(props);
- producer.send(
- new ProducerRecord<>(
- "Kafka-Test", "key", "root.kafka," + System.currentTimeMillis() + ",value,INT32,100"));
- producer.close();
-```
-
-### kafka Consumer Receiving Data Java Code Example
-
-```java
- Properties props = new Properties();
- props.put("bootstrap.servers", "127.0.0.1:9092");
- props.put("key.deserializer", StringDeserializer.class);
- props.put("value.deserializer", StringDeserializer.class);
- props.put("auto.offset.reset", "earliest");
- props.put("group.id", "Kafka-Test");
- KafkaConsumer kafkaConsumer = new KafkaConsumer<>(props);
- kafkaConsumer.subscribe(Collections.singleton("Kafka-Test"));
- ConsumerRecords records = kafkaConsumer.poll(Duration.ofSeconds(1));
- ```
-
-### Example of Java Code Stored in IoTDB Server
-
-```java
- SessionPool pool =
- new SessionPool.Builder()
- .host("127.0.0.1")
- .port(6667)
- .user("root")
- .password("root")
- .maxSize(3)
- .build();
- List datas = new ArrayList<>(records.count());
- for (ConsumerRecord record : records) {
- datas.add(record.value());
- }
- int size = datas.size();
- List deviceIds = new ArrayList<>(size);
- List times = new ArrayList<>(size);
- List> measurementsList = new ArrayList<>(size);
- List> typesList = new ArrayList<>(size);
- List> valuesList = new ArrayList<>(size);
- for (String data : datas) {
- String[] dataArray = data.split(",");
- String device = dataArray[0];
- long time = Long.parseLong(dataArray[1]);
- List measurements = Arrays.asList(dataArray[2].split(":"));
- List types = new ArrayList<>();
- for (String type : dataArray[3].split(":")) {
- types.add(TSDataType.valueOf(type));
- }
- List
+
-
-其中包括了 IoTDB 集群使用中用户常接触到的几个概念，包括：
-- **节点**（ConfigNode、DataNode、AINode）；
-- **槽**（SchemaSlot、DataSlot）；
-- **Region**（SchemaRegion、DataRegion）；
-- ***副本组***。
-
-下文将重点对以上概念进行介绍。
-
-## 节点
-IoTDB 集群包括三种节点（进程），**ConfigNode**（管理节点），**DataNode**（数据节点）和 **AINode**（分析节点），如下所示：
-- **ConfigNode**：存储集群的配置信息、数据库的元数据、时间序列元数据和数据的路由信息，监控集群节点并实施负载均衡，所有 ConfigNode 之间互为全量备份，如上图中的 ConfigNode-1，ConfigNode-2 和 ConfigNode-3 所示。ConfigNode 不直接接收客户端读写请求，它会通过一系列[负载均衡算法](../Technical-Insider/Cluster-data-partitioning.md)对集群中元数据和数据的分布提供指导。
-- **DataNode**：负责时间序列元数据和数据的读写，每个 DataNode 都能接收客户端读写请求并提供相应服务，如上图中的 DataNode-1，DataNode-2 和 DataNode-3 所示。接收客户端读写请求时，若 DataNode 缓存有对应的路由信息，它能直接在本地执行或是转发这些请求；否则它会向 ConfigNode 询问并缓存路由信息，以加速后续请求的服务效率。
-- **AINode**：负责与 ConfigNode 和 DataNode 交互来扩展 IoTDB 集群对时间序列进行智能分析的能力，支持从外部引入已有机器学习模型进行注册，并使用注册的模型在指定时序数据上通过简单 SQL 语句完成时序分析任务的过程，将模型的创建、管理及推理融合在数据库引擎中。目前已提供常见时序分析场景（例如预测与异常检测）的机器学习算法或自研模型。
-
-## 槽
-IoTDB 内部将元数据和数据划分成多个更小的、更易于管理的单元，每个单元称为一个**槽**。槽是一个逻辑概念，在 IoTDB 集群中，**元数据槽**和**数据槽**定义如下：
-- **元数据槽**（SchemaSlot）：一部分元数据集合，元数据槽总数固定，默认数量为 1000，IoTDB 使用哈希算法将所有设备均匀地分配到这些元数据槽中。
-- **数据槽**（DataSlot）：一部分数据集合，在元数据槽的基础上，将对应设备的数据按时间范围划分为数据槽，默认的时间范围为 7 天。
-
-## Region
-在 IoTDB 中，元数据和数据被复制到各个 DataNode 以获得集群高可用性。然而以槽为粒度进行复制会增加集群管理成本、降低写入吞吐。因此 IoTDB 引入 **Region** 这一概念，将元数据槽和数据槽分别分配给 SchemaRegion 和 DataRegion 后，以 Region 为单位进行复制。**SchemRegion** 和 **DataRegion** 的详细定义如下：
-- **SchemaRegion**：元数据存储和复制的基本单元，集群每个数据库的所有元数据槽会被均匀分配给该数据库的所有 SchemaRegion。拥有相同 RegionID 的 SchemaRegion 互为副本，如上图中 SchemaRegion-1 拥有三个副本，分别放置于 DataNode-1，DataNode-2 和 DataNode-3。
-- **DataRegion**：数据存储和复制的基本单元，集群每个数据库的所有数据槽会被均匀分配给该数据库的所有 DataRegion。拥有相同 RegionID 的 DataRegion 互为副本，如上图中 DataRegion-2 拥有两个副本，分别放置于 DataNode-1 和 DataNode-2。
-
-## 副本组
-Region 的副本对集群的容灾能力至关重要。对于每个 Region 的所有副本，它们的角色分为 **leader** 和 **follower**，共同提供读写服务。不同架构下的副本组配置推荐如下：
-| 类别 | 配置项 | 单机推荐配置 | 分布式推荐配置 |
-| :-: | :-: | :-: | :-: |
-| 元数据 | schema_replication_factor | 1 | 3 |
-| 数据 | data_replication_factor | 1 | 2 |
\ No newline at end of file
+-->
\ No newline at end of file
diff --git a/src/zh/UserGuide/Master/Table/Background-knowledge/Cluster-Concept_apache.md b/src/zh/UserGuide/Master/Table/Background-knowledge/Cluster-Concept_apache.md
new file mode 100644
index 000000000..7121d0564
--- /dev/null
+++ b/src/zh/UserGuide/Master/Table/Background-knowledge/Cluster-Concept_apache.md
@@ -0,0 +1,107 @@
+
+
+# 常见概念
+
+## 数据模型相关概念
+
+| 概念 | 含义 |
+| ----------------------- | ------------------------------------------------------------ |
+| 数据模型（sql_dialect） | IoTDB 支持两种时序数据模型（SQL语法），管理的对象均为设备和测点树：以层级路径的方式管理数据，一条路径对应一个设备的一个测点表：以关系表的方式管理数据，一张表对应一类设备 |
+| 元数据（Schema） | 元数据是数据库的数据模型信息，即树形结构或表结构。包括测点的名称、数据类型等定义。 |
+| 设备（Device） | 对应一个实际场景中的物理设备，通常包含多个测点。 |
+| 测点（Timeseries） | 又名：物理量、时间序列、时间线、点位、信号量、指标、测量值等。是多个数据点按时间戳递增排列形成的一个时间序列。通常一个测点代表一个采集点位，能够定期采集所在环境的物理量。 |
+| 编码（Encoding） | 编码是一种压缩技术，将数据以二进制的形式进行表示，可以提高存储效率。IoTDB 支持多种针对不同类型的数据的编码方法，详细信息请查看：[压缩和编码](../Technical-Insider/Encoding-and-Compression.md) |
+| 压缩（Compression） | IoTDB 在数据编码后，使用压缩技术进一步压缩二进制数据，提升存储效率。IoTDB 支持多种压缩方法，详细信息请查看：[压缩和编码](../Technical-Insider/Encoding-and-Compression.md) |
+
+## 分布式相关概念
+
+下图展示了一个常见的 IoTDB 3C3D（3 个 ConfigNode、3 个 DataNode）的集群部署模式：
+
+
+
+IoTDB 的集群包括如下常见概念：
+
+- 节点（ConfigNode、DataNode、AINode）
+- Region（SchemaRegion、DataRegion）
+- 多副本
+
+下文将对以上概念进行介绍。
+
+
+### 节点
+
+IoTDB 集群包括三种节点（进程）：ConfigNode（管理节点），DataNode（数据节点）和 AINode（分析节点），如下所示：
+
+- ConfigNode：管理集群的节点信息、配置信息、用户权限、元数据、分区信息等，负责分布式操作的调度和负载均衡，所有 ConfigNode 之间互为全量备份，如上图中的 ConfigNode-1，ConfigNode-2 和 ConfigNode-3 所示。
+- DataNode：服务客户端请求，负责数据的存储和计算，如上图中的 DataNode-1，DataNode-2 和 DataNode-3 所示。
+- AINode：负责提供机器学习能力，支持注册已训练好的机器学习模型，并通过 SQL 调用模型进行推理，目前已内置自研时序大模型和常见的机器学习算法（如预测与异常检测）。
+
+### 数据分区
+
+在 IoTDB 中，元数据和数据都被分为小的分区，即 Region，由集群的各个 DataNode 进行管理。
+
+- SchemaRegion：元数据分区，管理一部分设备和测点的元数据。不同 DataNode 相同 RegionID 的 SchemaRegion 互为副本，如上图中 SchemaRegion-1 拥有三个副本，分别放置于 DataNode-1，DataNode-2 和 DataNode-3。
+- DataRegion：数据分区，管理一部分设备的一段时间的数据。不同 DataNode 相同 RegionID 的 DataRegion 互为副本，如上图中 DataRegion-2 拥有两个副本，分别放置于 DataNode-1 和 DataNode-2。
+- 具体分区算法可参考：[数据分区](../Technical-Insider/Cluster-data-partitioning.md)
+
+### 多副本
+
+数据和元数据的副本数可配置，不同部署模式下的副本数推荐如下配置，其中多副本时可提供高可用服务。
+
+| 类别 | 配置项 | 单机推荐配置 | 集群推荐配置 |
+| :----- | :------------------------ | :----------- | :----------- |
+| 元数据 | schema_replication_factor | 1 | 3 |
+| 数据 | data_replication_factor | 1 | 2 |
+
+
+## 部署相关概念
+
+IoTDB 有两种运行模式：单机模式、集群模式。
+
+### 单机模式
+
+IoTDB单机实例包括 1 个ConfigNode、1个DataNode，即1C1D；
+
+- **特点**：便于开发者安装部署，部署和维护成本较低，操作方便。
+- **适用场景**：资源有限或对高可用要求不高的场景，例如边缘端服务器。
+- **部署方法**：[单机版部署](../Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md)
+
+
+### 集群模式
+
+IoTDB 集群实例为 3 个ConfigNode 和不少于 3 个 DataNode，通常为 3 个 DataNode，即3C3D；当部分节点出现故障时，剩余节点仍然能对外提供服务，保证数据库服务的高可用性，且可随节点增加提升数据库性能。
+
+- **特点**：具有高可用性、高扩展性，可通过增加 DataNode 提高系统性能。
+- **适用场景**：需要提供高可用和可靠性的企业级应用场景。
+- **部署方法**：[集群版部署](../Deployment-and-Maintenance/Cluster-Deployment_timecho.md)
+
+### 特点总结
+
+| 维度 | 单机模式 | 集群模式 |
+| ------------ | ---------------------------- | ------------------------ |
+| 适用场景 | 边缘侧部署、对高可用要求不高 | 高可用性业务、容灾场景等 |
+| 所需机器数量 | 1 | ≥3 |
+| 安全可靠性 | 无法容忍单点故障 | 高，可容忍单点故障 |
+| 扩展性 | 可扩展 DataNode 提升性能 | 可扩展 DataNode 提升性能 |
+| 性能 | 可随 DataNode 数量扩展 | 可随 DataNode 数量扩展 |
+
+- 单机模式和集群模式，部署步骤类似（逐个增加 ConfigNode 和 DataNode），仅副本数和可提供服务的最少节点数不同。
\ No newline at end of file
diff --git a/src/zh/UserGuide/V2.0.1/Table/Background-knowledge/Cluster-Concept_timecho.md b/src/zh/UserGuide/Master/Table/Background-knowledge/Cluster-Concept_timecho.md
similarity index 100%
rename from src/zh/UserGuide/V2.0.1/Table/Background-knowledge/Cluster-Concept_timecho.md
rename to src/zh/UserGuide/Master/Table/Background-knowledge/Cluster-Concept_timecho.md
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
new file mode 100644
index 000000000..b66dfa675
--- /dev/null
+++ b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -0,0 +1,326 @@
+
+# 集群版安装部署
+
+本小节描述如何手动部署包括3个ConfigNode和3个DataNode的实例，即通常所说的3C3D集群。
+
+