This is an automated email from the ASF dual-hosted git repository.
HTHou pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iotdb-docs.git
The following commit(s) were added to refs/heads/main by this push:
new 27f06181 docs: improve data sync examples and section numbering (#1193)
27f06181 is described below
commit 27f06181fe98858c89d211c7ccd005b253e48666
Author: leto-bbq <[email protected]>
AuthorDate: Wed Aug 12 12:00:42 2026 +0800
docs: improve data sync examples and section numbering (#1193)
---
.../TimeSeries-Large-Model_Upgrade_apache.md | 4 +-
.../Master/Table/User-Manual/Data-Sync_apache.md | 73 +++++++++++++--------
.../TimeSeries-Large-Model_Upgrade_apache.md | 4 +-
.../Master/Tree/User-Manual/Data-Sync_apache.md | 73 ++++++++++++++-------
.../TimeSeries-Large-Model_Upgrade_apache.md | 4 +-
.../latest-Table/User-Manual/Data-Sync_apache.md | 73 +++++++++++++--------
.../TimeSeries-Large-Model_Upgrade_apache.md | 4 +-
.../latest/User-Manual/Data-Sync_apache.md | 73 ++++++++++++++-------
.../TimeSeries-Large-Model_Upgrade_apache.md | 4 +-
.../Master/Table/User-Manual/Data-Sync_apache.md | 73 ++++++++++++++-------
.../TimeSeries-Large-Model_Upgrade_apache.md | 4 +-
.../Master/Tree/User-Manual/Data-Sync_apache.md | 74 +++++++++++++++-------
.../TimeSeries-Large-Model_Upgrade_apache.md | 4 +-
.../latest-Table/User-Manual/Data-Sync_apache.md | 73 ++++++++++++++-------
.../TimeSeries-Large-Model_Upgrade_apache.md | 4 +-
.../latest/User-Manual/Data-Sync_apache.md | 74 +++++++++++++++-------
16 files changed, 412 insertions(+), 206 deletions(-)
diff --git
a/src/UserGuide/Master/Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
b/src/UserGuide/Master/Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
index 760052da..414e41e6 100644
---
a/src/UserGuide/Master/Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
+++
b/src/UserGuide/Master/Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
@@ -90,7 +90,7 @@ Toto<sup><a href="#appendix5" id="ref5"
style="text-decoration: none;">[5]</a></
-## 9. Performance Showcase
+## 8. Performance Showcase
Time Series Large Models can adapt to real time series data from various
different domains and scenarios, demonstrating excellent processing
capabilities across various tasks. The following shows the actual performance
on different datasets:
@@ -112,7 +112,7 @@ Using Time Series Large Models to accurately identify
outliers that deviate sign
-## 10. Deployment and Usage
+## 9. Deployment and Usage
1. Open the IoTDB CLI console and check that the ConfigNode, DataNode, and
AINode nodes are all Running.
diff --git a/src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md
b/src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md
index 557a0bb2..b05adcd8 100644
--- a/src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md
+++ b/src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md
@@ -339,7 +339,7 @@ SQL Example:
CREATE PIPE A2B
WITH SINK (
'sink' = 'iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668' -- URL of the DataNode service port on the
target IoTDB
+ 'node-urls' = '127.0.0.1:6668'
)
```
@@ -357,17 +357,24 @@ SQL Example:
CREATE PIPE A2B
WITH SOURCE (
'source' = 'iotdb-source',
- 'mode.streaming' = 'true' -- Extraction mode for newly inserted data (after
the pipe is created):
- -- Whether to extract data in streaming mode (if
set to false, batch mode is used).
- 'database-name'='testdb.*', -- Scope of Data Synchronization
- 'start-time' = '2023.08.23T08:00:00+00:00', -- The event time at which data
synchronization starts (inclusive).
- 'end-time' = '2023.10.23T08:00:00+00:00' -- The event time at which data
synchronization ends (inclusive).
+ 'mode.streaming' = 'true',
+ 'database-name'='testdb.*',
+ 'start-time' = '2023.08.23T08:00:00+00:00',
+ 'end-time' = '2023.10.23T08:00:00+00:00'
)
WITH SINK (
'sink' = 'iotdb-thrift-async-sink',
- 'node-urls' = '127.0.0.1:6668' -- The URL of the DataNode's data service
port in the target IoTDB instance.
+ 'node-urls' = '127.0.0.1:6668'
)
```
+
+Where:
+
+- `mode.streaming`: Extraction mode for newly inserted data (after the pipe is
created): Whether to extract data in streaming mode (if set to false, batch
mode is used).
+- `database-name`: Scope of Data Synchronization
+- `start-time`: The event time at which data synchronization starts
(inclusive).
+- `end-time`: The event time at which data synchronization ends (inclusive).
+
### 3.3 Edge-to-Cloud Data Transmission
This example demonstrates synchronizing data from multiple IoTDB clusters (B,
C, D) to a central IoTDB cluster (A). The data pipeline is shown below:
@@ -381,12 +388,12 @@ SQL Example: On IoTDB B:
```SQL
CREATE PIPE BA
WITH SOURCE (
- 'database-name' = 'db_b.*', -- Restrict the database scope
- 'table-name' = '.*' -- Match all tables
+ 'database-name' = 'db_b.*',
+ 'table-name' = '.*'
)
WITH SINK (
'sink' = 'iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6667' -- URL of the DataNode service port on the
target IoTDB
+ 'node-urls' = '127.0.0.1:6667'
)
```
@@ -395,12 +402,12 @@ On IoTDB C ：
```SQL
CREATE PIPE CA
WITH SOURCE (
- 'database-name' = 'db_c.*', -- Restrict the database scope
- 'table-name' = '.*' -- Match all tables
+ 'database-name' = 'db_c.*',
+ 'table-name' = '.*'
)
WITH SINK (
'sink' = 'iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668' -- URL of the DataNode service port on the
target IoTDB
+ 'node-urls' = '127.0.0.1:6668'
)
```
@@ -409,29 +416,34 @@ On IoTDB D：
```SQL
CREATE PIPE DA
WITH SOURCE (
- 'database-name' = 'db_d.*', -- Restrict the database scope
- 'table-name' = '.*' -- Match all tables
+ 'database-name' = 'db_d.*',
+ 'table-name' = '.*'
)
WITH SINK (
'sink' = 'iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669' -- URL of the DataNode service port on the
target IoTDB
+ 'node-urls' = '127.0.0.1:6669'
)
```
+The parameters in the preceding two examples have the same meanings as those
below:
+
+- `database-name`: Restrict the database scope
+- `table-name`: Match all tables
+- `node-urls`: URL of the DataNode service port on the target IoTDB
+
### 3.4 Cascaded Data Transmission
This example demonstrates cascading data transmission from IoTDB A to IoTDB B
and then to IoTDB C. The data pipeline is shown below:
-
SQL Example: On IoTDB A:
```SQL
CREATE PIPE AB
WITH SINK (
'sink' = 'iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668' -- URL of the DataNode service port on the
target IoTDB
+ 'node-urls' = '127.0.0.1:6668'
)
```
@@ -443,10 +455,13 @@ WITH SOURCE (
)
WITH SINK (
'sink' = 'iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669' -- URL of the DataNode service port on the
target IoTDB
+ 'node-urls' = '127.0.0.1:6669'
)
```
+The parameters in the preceding example have the same meanings as those below:
+
+- `node-urls`: URL of the DataNode service port on the target IoTDB
### 3.5 Compressed Synchronization
@@ -457,12 +472,15 @@ IoTDB supports specifying data compression methods during
synchronization. The `
```SQL
CREATE PIPE A2B
WITH SINK (
- 'node-urls' = '127.0.0.1:6668', -- URL of the DataNode service port on the
target IoTDB
- 'compressor' = 'snappy,lz4', -- Compression algorithms
- 'rate-limit-bytes-per-second' = '1048576' -- Maximum bytes allowed per
second
+ 'node-urls' = '127.0.0.1:6668',
+ 'compressor' = 'snappy,lz4',
+ 'rate-limit-bytes-per-second' = '1048576'
)
```
+Where:
+
+- `node-urls`: URL of the DataNode service port on the target IoTDB
### 3.6 Encrypted Synchronization
@@ -474,12 +492,17 @@ IoTDB supports SSL encryption during synchronization to
securely transmit data b
CREATE PIPE A2B
WITH SINK (
'sink' = 'iotdb-thrift-ssl-sink',
- 'node-urls' = '127.0.0.1:6667', -- URL of the DataNode service port on the
target IoTDB
- 'ssl.trust-store-path' = 'pki/trusted', -- Path to the trust store
certificate
- 'ssl.trust-store-pwd' = 'root' -- Password for the trust store
certificate
+ 'node-urls' = '127.0.0.1:6667',
+ 'ssl.trust-store-path' = 'pki/trusted',
+ 'ssl.trust-store-pwd' = 'root'
)
```
+Where:
+
+- `node-urls`: URL of the DataNode service port on the target IoTDB
+- `ssl.trust-store-path`: The trust store certificate path required to connect
to the target DataNode
+- `ssl.trust-store-pwd`: The trust store certificate password required to
connect to the target DataNode
## Reference: Notes
diff --git
a/src/UserGuide/Master/Tree/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
b/src/UserGuide/Master/Tree/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
index 760052da..414e41e6 100644
---
a/src/UserGuide/Master/Tree/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
+++
b/src/UserGuide/Master/Tree/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
@@ -90,7 +90,7 @@ Toto<sup><a href="#appendix5" id="ref5"
style="text-decoration: none;">[5]</a></
-## 9. Performance Showcase
+## 8. Performance Showcase
Time Series Large Models can adapt to real time series data from various
different domains and scenarios, demonstrating excellent processing
capabilities across various tasks. The following shows the actual performance
on different datasets:
@@ -112,7 +112,7 @@ Using Time Series Large Models to accurately identify
outliers that deviate sign
-## 10. Deployment and Usage
+## 9. Deployment and Usage
1. Open the IoTDB CLI console and check that the ConfigNode, DataNode, and
AINode nodes are all Running.
diff --git a/src/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md
b/src/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md
index 4bc7d5af..06bcfaea 100644
--- a/src/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md
+++ b/src/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md
@@ -365,7 +365,7 @@ In this example, we can create a synchronization task named
A2B to synchronize t
create pipe A2B
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6668',
```
### 3.2 Partial data synchronization
@@ -382,17 +382,24 @@ The detailed statements are as follows:
create pipe A2B
WITH SOURCE (
'source'= 'iotdb-source',
- 'realtime.mode' = 'stream' -- The extraction mode for newly inserted data
(after pipe creation)
- 'path' = 'root.vehicle.**', -- Scope of Data Synchronization
- 'start-time' = '2023.08.23T08:00:00+00:00', -- The start event time for
synchronizing all data, including start-time
- 'end-time' = '2023.10.23T08:00:00+00:00' -- The end event time for
synchronizing all data, including end-time
+ 'realtime.mode' = 'stream',
+ 'path' = 'root.vehicle.**',
+ 'start-time' = '2023.08.23T08:00:00+00:00',
+ 'end-time' = '2023.10.23T08:00:00+00:00'
)
with SINK (
'sink'='iotdb-thrift-async-sink',
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6668',
)
```
+Where:
+
+- `realtime.mode`: The extraction mode for newly inserted data (after pipe
creation)
+- `path`: Scope of Data Synchronization
+- `start-time`: The start event time for synchronizing all data, including
start-time
+- `end-time`: The end event time for synchronizing all data, including end-time
+
### 3.3 Edge-cloud data transfer
This example is used to demonstrate the scenario where data from multiple
IoTDB is transferred to the cloud, with data from clusters B, C, and D all
synchronized to cluster A, as shown in the figure below:
@@ -406,12 +413,12 @@ On B IoTDB, execute the following statement to
synchronize data from B to A:
```SQL
create pipe BA
with source (
- 'inclusion'='all', -- Indicates synchronization of full data, schema ,
and auth
- 'path'='root.db.**', -- Limit the range
+ 'inclusion'='all',
+ 'path'='root.db.**',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6668',
)
)
```
@@ -421,11 +428,11 @@ On C IoTDB, execute the following statement to
synchronize data from C to A:
```SQL
create pipe CA
with source (
- 'inclusion'='all', -- Indicates synchronization of full data, schema , and
auth
- 'path'='root.db.**', -- Limit the range
+ 'inclusion'='all',
+ 'path'='root.db.**',
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6668',
)
)
```
@@ -435,16 +442,22 @@ On D IoTDB, execute the following statement to
synchronize data from D to A:
```SQL
create pipe DA
with source (
- 'inclusion'='all', -- Indicates synchronization of full data, schema , and
auth
- 'path'='root.db.**', -- Limit the range
+ 'inclusion'='all',
+ 'path'='root.db.**',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6668',
)
)
```
+The parameters in the preceding two examples have the same meanings as those
below:
+
+- `inclusion`: Indicates synchronization of full data, schema , and auth
+- `path`: Limit the range
+- `node-urls`: The URL of the data service port of the DataNode node on the
target IoTDB
+
### 3.4 Cascading data transfer
This example is used to demonstrate the scenario where data is transferred in
a cascading manner between multiple IoTDB, with data from cluster A
synchronized to cluster B, and then to cluster C, as shown in the figure below:
@@ -459,7 +472,7 @@ On A IoTDB, execute the following statement to synchronize
data from A to B:
create pipe AB
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6668',
)
)
```
@@ -469,15 +482,19 @@ On B IoTDB, execute the following statement to
synchronize data from B to C:
```SQL
create pipe BC
with source (
- 'forwarding-pipe-requests' = 'true' -- Whether to forward data written by
other Pipes
+ 'forwarding-pipe-requests' = 'true'
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6669',
)
)
```
+The `node-urls` parameter in the preceding example has the same meaning as
below:
+
+- `forwarding-pipe-requests`: Whether to forward data written by other Pipes
+- `node-urls`: The URL of the data service port of the DataNode node on the
target IoTDB
### 3.5 Compression Synchronization (V1.3.3+)
@@ -488,11 +505,15 @@ For example, to create a synchronization task named A2B:
```SQL
create pipe A2B
with sink (
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
- 'compressor' = 'snappy,lz4' -- Compression algorithms
+ 'node-urls' = '127.0.0.1:6668',
+ 'compressor' = 'snappy,lz4'
)
```
+Where:
+
+- `node-urls`: The URL of the data service port of the DataNode node on the
target IoTDB
+
### 3.6 Encrypted Synchronization (V1.3.1+)
IoTDB supports the use of SSL encryption during the synchronization process,
ensuring the secure transfer of data between different IoTDB instances. By
configuring SSL-related parameters, such as the certificate address and
password （`ssl.trust-store-path`）、（`ssl.trust-store-pwd`）, data can be
protected by SSL encryption during the synchronization process.
@@ -503,12 +524,18 @@ For example, to create a synchronization task named A2B:
create pipe A2B
with sink (
'sink'='iotdb-thrift-ssl-sink',
- 'node-urls'='127.0.0.1:6667', -- The URL of the data service port of the
DataNode node on the target IoTDB
- 'ssl.trust-store-path'='pki/trusted', -- The trust store certificate path
required to connect to the target DataNode
- 'ssl.trust-store-pwd'='root' -- The trust store certificate password
required to connect to the target DataNode
+ 'node-urls'='127.0.0.1:6667',
+ 'ssl.trust-store-path'='pki/trusted',
+ 'ssl.trust-store-pwd'='root'
)
```
+Where:
+
+- `node-urls`: The URL of the data service port of the DataNode node on the
target IoTDB
+- `ssl.trust-store-path`: The trust store certificate path required to connect
to the target DataNode
+- `ssl.trust-store-pwd`: The trust store certificate password required to
connect to the target DataNode
+
## 4. Reference: Notes
You can adjust the parameters for data synchronization by modifying the IoTDB
configuration file （`iotdb-system.properties`）, such as the directory for
storing synchronized data. The complete configuration is as follows:
diff --git
a/src/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
b/src/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
index 760052da..414e41e6 100644
---
a/src/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
+++
b/src/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
@@ -90,7 +90,7 @@ Toto<sup><a href="#appendix5" id="ref5"
style="text-decoration: none;">[5]</a></
-## 9. Performance Showcase
+## 8. Performance Showcase
Time Series Large Models can adapt to real time series data from various
different domains and scenarios, demonstrating excellent processing
capabilities across various tasks. The following shows the actual performance
on different datasets:
@@ -112,7 +112,7 @@ Using Time Series Large Models to accurately identify
outliers that deviate sign
-## 10. Deployment and Usage
+## 9. Deployment and Usage
1. Open the IoTDB CLI console and check that the ConfigNode, DataNode, and
AINode nodes are all Running.
diff --git a/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md
b/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md
index 575a4e88..2650b277 100644
--- a/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md
+++ b/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md
@@ -339,7 +339,7 @@ SQL Example:
CREATE PIPE A2B
WITH SINK (
'sink' = 'iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668' -- URL of the DataNode service port on the
target IoTDB
+ 'node-urls' = '127.0.0.1:6668'
)
```
@@ -357,17 +357,24 @@ SQL Example:
CREATE PIPE A2B
WITH SOURCE (
'source' = 'iotdb-source',
- 'mode.streaming' = 'true' -- Extraction mode for newly inserted data (after
the pipe is created):
- -- Whether to extract data in streaming mode (if
set to false, batch mode is used).
- 'database-name'='testdb.*', -- Scope of Data Synchronization
- 'start-time' = '2023.08.23T08:00:00+00:00', -- The event time at which data
synchronization starts (inclusive).
- 'end-time' = '2023.10.23T08:00:00+00:00' -- The event time at which data
synchronization ends (inclusive).
+ 'mode.streaming' = 'true',
+ 'database-name'='testdb.*',
+ 'start-time' = '2023.08.23T08:00:00+00:00',
+ 'end-time' = '2023.10.23T08:00:00+00:00'
)
WITH SINK (
'sink' = 'iotdb-thrift-async-sink',
- 'node-urls' = '127.0.0.1:6668' -- The URL of the DataNode's data service
port in the target IoTDB instance.
+ 'node-urls' = '127.0.0.1:6668'
)
```
+
+Where:
+
+- `mode.streaming`: Extraction mode for newly inserted data (after the pipe is
created): Whether to extract data in streaming mode (if set to false, batch
mode is used).
+- `database-name`: Scope of Data Synchronization
+- `start-time`: The event time at which data synchronization starts
(inclusive).
+- `end-time`: The event time at which data synchronization ends (inclusive).
+
### 3.3 Edge-to-Cloud Data Transmission
This example demonstrates synchronizing data from multiple IoTDB clusters (B,
C, D) to a central IoTDB cluster (A). The data pipeline is shown below:
@@ -381,12 +388,12 @@ SQL Example: On IoTDB B:
```SQL
CREATE PIPE BA
WITH SOURCE (
- 'database-name' = 'db_b.*', -- Restrict the database scope
- 'table-name' = '.*' -- Match all tables
+ 'database-name' = 'db_b.*',
+ 'table-name' = '.*'
)
WITH SINK (
'sink' = 'iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6667' -- URL of the DataNode service port on the
target IoTDB
+ 'node-urls' = '127.0.0.1:6667'
)
```
@@ -395,12 +402,12 @@ On IoTDB C ：
```SQL
CREATE PIPE CA
WITH SOURCE (
- 'database-name' = 'db_c.*', -- Restrict the database scope
- 'table-name' = '.*' -- Match all tables
+ 'database-name' = 'db_c.*',
+ 'table-name' = '.*'
)
WITH SINK (
'sink' = 'iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668' -- URL of the DataNode service port on the
target IoTDB
+ 'node-urls' = '127.0.0.1:6668'
)
```
@@ -409,29 +416,34 @@ On IoTDB D：
```SQL
CREATE PIPE DA
WITH SOURCE (
- 'database-name' = 'db_d.*', -- Restrict the database scope
- 'table-name' = '.*' -- Match all tables
+ 'database-name' = 'db_d.*',
+ 'table-name' = '.*'
)
WITH SINK (
'sink' = 'iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669' -- URL of the DataNode service port on the
target IoTDB
+ 'node-urls' = '127.0.0.1:6669'
)
```
+The parameters in the preceding two examples have the same meanings as those
below:
+
+- `database-name`: Restrict the database scope
+- `table-name`: Match all tables
+- `node-urls`: URL of the DataNode service port on the target IoTDB
+
### 3.4 Cascaded Data Transmission
This example demonstrates cascading data transmission from IoTDB A to IoTDB B
and then to IoTDB C. The data pipeline is shown below:
-
SQL Example: On IoTDB A:
```SQL
CREATE PIPE AB
WITH SINK (
'sink' = 'iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668' -- URL of the DataNode service port on the
target IoTDB
+ 'node-urls' = '127.0.0.1:6668'
)
```
@@ -443,10 +455,13 @@ WITH SOURCE (
)
WITH SINK (
'sink' = 'iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669' -- URL of the DataNode service port on the
target IoTDB
+ 'node-urls' = '127.0.0.1:6669'
)
```
+The parameters in the preceding example have the same meanings as those below:
+
+- `node-urls`: URL of the DataNode service port on the target IoTDB
### 3.5 Compressed Synchronization
@@ -457,12 +472,15 @@ IoTDB supports specifying data compression methods during
synchronization. The `
```SQL
CREATE PIPE A2B
WITH SINK (
- 'node-urls' = '127.0.0.1:6668', -- URL of the DataNode service port on the
target IoTDB
- 'compressor' = 'snappy,lz4', -- Compression algorithms
- 'rate-limit-bytes-per-second' = '1048576' -- Maximum bytes allowed per
second
+ 'node-urls' = '127.0.0.1:6668',
+ 'compressor' = 'snappy,lz4',
+ 'rate-limit-bytes-per-second' = '1048576'
)
```
+Where:
+
+- `node-urls`: URL of the DataNode service port on the target IoTDB
### 3.6 Encrypted Synchronization
@@ -474,12 +492,17 @@ IoTDB supports SSL encryption during synchronization to
securely transmit data b
CREATE PIPE A2B
WITH SINK (
'sink' = 'iotdb-thrift-ssl-sink',
- 'node-urls' = '127.0.0.1:6667', -- URL of the DataNode service port on the
target IoTDB
- 'ssl.trust-store-path' = 'pki/trusted', -- Path to the trust store
certificate
- 'ssl.trust-store-pwd' = 'root' -- Password for the trust store
certificate
+ 'node-urls' = '127.0.0.1:6667',
+ 'ssl.trust-store-path' = 'pki/trusted',
+ 'ssl.trust-store-pwd' = 'root'
)
```
+Where:
+
+- `node-urls`: URL of the DataNode service port on the target IoTDB
+- `ssl.trust-store-path`: The trust store certificate path required to connect
to the target DataNode
+- `ssl.trust-store-pwd`: The trust store certificate password required to
connect to the target DataNode
## Reference: Notes
diff --git
a/src/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
b/src/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
index 760052da..414e41e6 100644
---
a/src/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
+++
b/src/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
@@ -90,7 +90,7 @@ Toto<sup><a href="#appendix5" id="ref5"
style="text-decoration: none;">[5]</a></
-## 9. Performance Showcase
+## 8. Performance Showcase
Time Series Large Models can adapt to real time series data from various
different domains and scenarios, demonstrating excellent processing
capabilities across various tasks. The following shows the actual performance
on different datasets:
@@ -112,7 +112,7 @@ Using Time Series Large Models to accurately identify
outliers that deviate sign
-## 10. Deployment and Usage
+## 9. Deployment and Usage
1. Open the IoTDB CLI console and check that the ConfigNode, DataNode, and
AINode nodes are all Running.
diff --git a/src/UserGuide/latest/User-Manual/Data-Sync_apache.md
b/src/UserGuide/latest/User-Manual/Data-Sync_apache.md
index 4bc7d5af..06bcfaea 100644
--- a/src/UserGuide/latest/User-Manual/Data-Sync_apache.md
+++ b/src/UserGuide/latest/User-Manual/Data-Sync_apache.md
@@ -365,7 +365,7 @@ In this example, we can create a synchronization task named
A2B to synchronize t
create pipe A2B
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6668',
```
### 3.2 Partial data synchronization
@@ -382,17 +382,24 @@ The detailed statements are as follows:
create pipe A2B
WITH SOURCE (
'source'= 'iotdb-source',
- 'realtime.mode' = 'stream' -- The extraction mode for newly inserted data
(after pipe creation)
- 'path' = 'root.vehicle.**', -- Scope of Data Synchronization
- 'start-time' = '2023.08.23T08:00:00+00:00', -- The start event time for
synchronizing all data, including start-time
- 'end-time' = '2023.10.23T08:00:00+00:00' -- The end event time for
synchronizing all data, including end-time
+ 'realtime.mode' = 'stream',
+ 'path' = 'root.vehicle.**',
+ 'start-time' = '2023.08.23T08:00:00+00:00',
+ 'end-time' = '2023.10.23T08:00:00+00:00'
)
with SINK (
'sink'='iotdb-thrift-async-sink',
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6668',
)
```
+Where:
+
+- `realtime.mode`: The extraction mode for newly inserted data (after pipe
creation)
+- `path`: Scope of Data Synchronization
+- `start-time`: The start event time for synchronizing all data, including
start-time
+- `end-time`: The end event time for synchronizing all data, including end-time
+
### 3.3 Edge-cloud data transfer
This example is used to demonstrate the scenario where data from multiple
IoTDB is transferred to the cloud, with data from clusters B, C, and D all
synchronized to cluster A, as shown in the figure below:
@@ -406,12 +413,12 @@ On B IoTDB, execute the following statement to
synchronize data from B to A:
```SQL
create pipe BA
with source (
- 'inclusion'='all', -- Indicates synchronization of full data, schema ,
and auth
- 'path'='root.db.**', -- Limit the range
+ 'inclusion'='all',
+ 'path'='root.db.**',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6668',
)
)
```
@@ -421,11 +428,11 @@ On C IoTDB, execute the following statement to
synchronize data from C to A:
```SQL
create pipe CA
with source (
- 'inclusion'='all', -- Indicates synchronization of full data, schema , and
auth
- 'path'='root.db.**', -- Limit the range
+ 'inclusion'='all',
+ 'path'='root.db.**',
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6668',
)
)
```
@@ -435,16 +442,22 @@ On D IoTDB, execute the following statement to
synchronize data from D to A:
```SQL
create pipe DA
with source (
- 'inclusion'='all', -- Indicates synchronization of full data, schema , and
auth
- 'path'='root.db.**', -- Limit the range
+ 'inclusion'='all',
+ 'path'='root.db.**',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6668',
)
)
```
+The parameters in the preceding two examples have the same meanings as those
below:
+
+- `inclusion`: Indicates synchronization of full data, schema , and auth
+- `path`: Limit the range
+- `node-urls`: The URL of the data service port of the DataNode node on the
target IoTDB
+
### 3.4 Cascading data transfer
This example is used to demonstrate the scenario where data is transferred in
a cascading manner between multiple IoTDB, with data from cluster A
synchronized to cluster B, and then to cluster C, as shown in the figure below:
@@ -459,7 +472,7 @@ On A IoTDB, execute the following statement to synchronize
data from A to B:
create pipe AB
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6668',
)
)
```
@@ -469,15 +482,19 @@ On B IoTDB, execute the following statement to
synchronize data from B to C:
```SQL
create pipe BC
with source (
- 'forwarding-pipe-requests' = 'true' -- Whether to forward data written by
other Pipes
+ 'forwarding-pipe-requests' = 'true'
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669', -- The URL of the data service port of the
DataNode node on the target IoTDB
+ 'node-urls' = '127.0.0.1:6669',
)
)
```
+The `node-urls` parameter in the preceding example has the same meaning as
below:
+
+- `forwarding-pipe-requests`: Whether to forward data written by other Pipes
+- `node-urls`: The URL of the data service port of the DataNode node on the
target IoTDB
### 3.5 Compression Synchronization (V1.3.3+)
@@ -488,11 +505,15 @@ For example, to create a synchronization task named A2B:
```SQL
create pipe A2B
with sink (
- 'node-urls' = '127.0.0.1:6668', -- The URL of the data service port of the
DataNode node on the target IoTDB
- 'compressor' = 'snappy,lz4' -- Compression algorithms
+ 'node-urls' = '127.0.0.1:6668',
+ 'compressor' = 'snappy,lz4'
)
```
+Where:
+
+- `node-urls`: The URL of the data service port of the DataNode node on the
target IoTDB
+
### 3.6 Encrypted Synchronization (V1.3.1+)
IoTDB supports the use of SSL encryption during the synchronization process,
ensuring the secure transfer of data between different IoTDB instances. By
configuring SSL-related parameters, such as the certificate address and
password （`ssl.trust-store-path`）、（`ssl.trust-store-pwd`）, data can be
protected by SSL encryption during the synchronization process.
@@ -503,12 +524,18 @@ For example, to create a synchronization task named A2B:
create pipe A2B
with sink (
'sink'='iotdb-thrift-ssl-sink',
- 'node-urls'='127.0.0.1:6667', -- The URL of the data service port of the
DataNode node on the target IoTDB
- 'ssl.trust-store-path'='pki/trusted', -- The trust store certificate path
required to connect to the target DataNode
- 'ssl.trust-store-pwd'='root' -- The trust store certificate password
required to connect to the target DataNode
+ 'node-urls'='127.0.0.1:6667',
+ 'ssl.trust-store-path'='pki/trusted',
+ 'ssl.trust-store-pwd'='root'
)
```
+Where:
+
+- `node-urls`: The URL of the data service port of the DataNode node on the
target IoTDB
+- `ssl.trust-store-path`: The trust store certificate path required to connect
to the target DataNode
+- `ssl.trust-store-pwd`: The trust store certificate password required to
connect to the target DataNode
+
## 4. Reference: Notes
You can adjust the parameters for data synchronization by modifying the IoTDB
configuration file （`iotdb-system.properties`）, such as the directory for
storing synchronized data. The complete configuration is as follows:
diff --git
a/src/zh/UserGuide/Master/Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
b/src/zh/UserGuide/Master/Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
index 537acb5b..b518d2b2 100644
---
a/src/zh/UserGuide/Master/Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
+++
b/src/zh/UserGuide/Master/Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
@@ -90,7 +90,7 @@ Toto<sup><a href="#appendix5" id="ref5"
style="text-decoration: none;">[5]</a></
-## 9. 效果展示
+## 8. 效果展示
时序大模型能够适应多种不同领域和场景的真实时序数据，在各种任务上拥有优异的处理效果，以下是在不同数据上的真实表现：
@@ -112,7 +112,7 @@ Toto<sup><a href="#appendix5" id="ref5"
style="text-decoration: none;">[5]</a></
-## 10. 部署使用
+## 9. 部署使用
1. 打开 IoTDB cli 控制台，检查 ConfigNode、DataNode、AINode 节点确保均为 Running。
diff --git a/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md
b/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md
index 4f420260..262ef66f 100644
--- a/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md
+++ b/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md
@@ -334,7 +334,7 @@ IoTDB> SHOW PIPEPLUGINS
create pipe A2B
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
@@ -352,17 +352,24 @@ with sink (
create pipe A2B
WITH SOURCE (
'source'= 'iotdb-source',
- 'mode.streaming' = 'true' -- 新插入数据（pipe创建后）的抽取模式：是否按流式抽取（false 时为批式）
- 'database-name'='testdb.*', -- 同步数据的范围
- 'start-time' = '2023.08.23T08:00:00+00:00', -- 同步所有数据的开始 event time，包含
start-time
- 'end-time' = '2023.10.23T08:00:00+00:00' -- 同步所有数据的结束 event time，包含 end-time
+ 'mode.streaming' = 'true',
+ 'database-name'='testdb.*',
+ 'start-time' = '2023.08.23T08:00:00+00:00',
+ 'end-time' = '2023.10.23T08:00:00+00:00'
)
with SINK (
'sink'='iotdb-thrift-async-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
+其中：
+
+- `mode.streaming`: 新插入数据（pipe创建后）的抽取模式：是否按流式抽取（false 时为批式）
+- `database-name`: 同步数据的范围
+- `start-time`: 同步所有数据的开始 event time，包含 start-time
+- `end-time`: 同步所有数据的结束 event time，包含 end-time
+
### 3.3 边云数据传输
本例子用来演示多个 IoTDB 之间边云传输数据的场景，数据由 B 、C、D 集群分别都同步至 A 集群，数据链路如下图所示：
@@ -376,12 +383,12 @@ with SINK (
```SQL
create pipe BA
with source (
- 'database-name'='db_b.*', -- 限制范围
- 'table-name'='.*', -- 可选择匹配所有
+ 'database-name'='db_b.*',
+ 'table-name'='.*',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6667', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6667',
)
```
@@ -390,12 +397,12 @@ with sink (
```SQL
create pipe CA
with source (
- 'database-name'='db_c.*', -- 限制范围
- 'table-name'='.*', -- 可选择匹配所有
+ 'database-name'='db_c.*',
+ 'table-name'='.*',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
@@ -404,29 +411,34 @@ with sink (
```SQL
create pipe DA
with source (
- 'database-name'='db_d.*', -- 限制范围
- 'table-name'='.*', -- 可选择匹配所有
+ 'database-name'='db_d.*',
+ 'table-name'='.*',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6669',
)
```
+前两个示例中的参数含义与此处相同：
+
+- `database-name`: 限制范围
+- `table-name`: 可选择匹配所有
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+
### 3.4 级联数据传输
本例子用来演示多个 IoTDB 之间级联传输数据的场景，数据由 A 集群同步至 B 集群，再同步至 C 集群，数据链路如下图所示：
-
在 A IoTDB 上执行下列语句，将 A 中数据同步至 B：
```SQL
create pipe AB
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
@@ -438,10 +450,14 @@ with source (
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6669',
)
```
+前一个示例中的参数含义与此处相同：
+
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+
### 3.5 压缩同步
IoTDB 支持在同步过程中指定数据压缩方式。可通过配置 `compressor` 参数，实现数据的实时压缩和传输。`compressor`目前支持
snappy / gzip / lz4 / zstd / lzma2 5
种可选算法，且可以选择多种压缩算法组合，按配置的顺序进行压缩。`rate-limit-bytes-per-second`（V1.3.3
及以后版本支持）每秒最大允许传输的byte数,计算压缩后的byte，若小于0则不限制。
@@ -451,12 +467,15 @@ IoTDB 支持在同步过程中指定数据压缩方式。可通过配置 `compre
```SQL
create pipe A2B
with sink (
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
- 'compressor' = 'snappy,lz4' --
- 'rate-limit-bytes-per-second'='1048576' -- 每秒最大允许传输的byte数
+ 'node-urls' = '127.0.0.1:6668',
+ 'compressor' = 'snappy,lz4',
+ 'rate-limit-bytes-per-second'='1048576'
)
```
+其中：
+
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
### 3.6 加密同步
@@ -468,12 +487,18 @@ IoTDB 支持在同步过程中使用 SSL 加密，从而在不同的 IoTDB 实
create pipe A2B
with sink (
'sink'='iotdb-thrift-ssl-sink',
- 'node-urls'='127.0.0.1:6667', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
- 'ssl.trust-store-path'='pki/trusted', -- 连接目标端 DataNode 所需的 trust store 证书路径
- 'ssl.trust-store-pwd'='root' -- 连接目标端 DataNode 所需的 trust store 证书密码
+ 'node-urls'='127.0.0.1:6667',
+ 'ssl.trust-store-path'='pki/trusted',
+ 'ssl.trust-store-pwd'='root'
)
```
+其中：
+
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+- `ssl.trust-store-path`: 连接目标端 DataNode 所需的 trust store 证书路径
+- `ssl.trust-store-pwd`: 连接目标端 DataNode 所需的 trust store 证书密码
+
## 参考：注意事项
可通过修改 IoTDB 配置文件（`iotdb-system.properties`）以调整数据同步的参数，如同步数据存储目录等。完整配置如下：：
diff --git
a/src/zh/UserGuide/Master/Tree/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
b/src/zh/UserGuide/Master/Tree/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
index 537acb5b..b518d2b2 100644
---
a/src/zh/UserGuide/Master/Tree/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
+++
b/src/zh/UserGuide/Master/Tree/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
@@ -90,7 +90,7 @@ Toto<sup><a href="#appendix5" id="ref5"
style="text-decoration: none;">[5]</a></
-## 9. 效果展示
+## 8. 效果展示
时序大模型能够适应多种不同领域和场景的真实时序数据，在各种任务上拥有优异的处理效果，以下是在不同数据上的真实表现：
@@ -112,7 +112,7 @@ Toto<sup><a href="#appendix5" id="ref5"
style="text-decoration: none;">[5]</a></
-## 10. 部署使用
+## 9. 部署使用
1. 打开 IoTDB cli 控制台，检查 ConfigNode、DataNode、AINode 节点确保均为 Running。
diff --git a/src/zh/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md
b/src/zh/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md
index 2bb46b1d..0da6bb54 100644
--- a/src/zh/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md
+++ b/src/zh/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md
@@ -368,7 +368,7 @@ IoTDB> SHOW PIPEPLUGINS
create pipe A2B
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
@@ -386,17 +386,24 @@ with sink (
create pipe A2B
WITH SOURCE (
'source'= 'iotdb-source',
- 'realtime.mode' = 'stream' -- 新插入数据（pipe创建后）的抽取模式
- 'path' = 'root.vehicle.**', -- 同步数据的范围
- 'start-time' = '2023.08.23T08:00:00+00:00', -- 同步所有数据的开始 event time，包含
start-time
- 'end-time' = '2023.10.23T08:00:00+00:00' -- 同步所有数据的结束 event time，包含 end-time
+ 'realtime.mode' = 'stream',
+ 'path' = 'root.vehicle.**',
+ 'start-time' = '2023.08.23T08:00:00+00:00',
+ 'end-time' = '2023.10.23T08:00:00+00:00'
)
with SINK (
'sink'='iotdb-thrift-async-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
+其中：
+
+- `realtime.mode`: 新插入数据（pipe创建后）的抽取模式
+- `path`: 同步数据的范围
+- `start-time`: 同步所有数据的开始 event time，包含 start-time
+- `end-time`: 同步所有数据的结束 event time，包含 end-time
+
### 3.3 边云数据传输
本例子用来演示多个 IoTDB 之间边云传输数据的场景，数据由 B 、C、D 集群分别都同步至 A 集群，数据链路如下图所示：
@@ -410,12 +417,12 @@ with SINK (
```SQL
create pipe BA
with source (
- 'inclusion'='all', -- 表示同步全量数据、元数据和权限
- 'path'='root.db.**', -- 限制范围
+ 'inclusion'='all',
+ 'path'='root.db.**',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6667', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6667',
)
```
@@ -424,12 +431,12 @@ with sink (
```SQL
create pipe CA
with source (
- 'inclusion'='all', -- 表示同步全量数据、元数据和权限
- 'path'='root.db.**', -- 限制范围
+ 'inclusion'='all',
+ 'path'='root.db.**',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
@@ -438,15 +445,21 @@ with sink (
```SQL
create pipe DA
with source (
- 'inclusion'='all', -- 表示同步全量数据、元数据和权限
- 'path'='root.db.**', -- 限制范围
+ 'inclusion'='all',
+ 'path'='root.db.**',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6669',
)
```
+前两个示例中的参数含义与此处相同：
+
+- `inclusion`: 表示同步全量数据、元数据和权限
+- `path`: 限制范围
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+
### 3.4 级联数据传输
本例子用来演示多个 IoTDB 之间级联传输数据的场景，数据由 A 集群同步至 B 集群，再同步至 C 集群，数据链路如下图所示：
@@ -461,7 +474,7 @@ with sink (
create pipe AB
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
@@ -470,14 +483,19 @@ with sink (
```SQL
create pipe BC
with source (
- 'forwarding-pipe-requests' = 'true' --是否转发由其他 Pipe 写入的数据
+ 'forwarding-pipe-requests' = 'true'
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6669',
)
```
+前一个示例中的 `node-urls` 参数含义与此处相同：
+
+- `forwarding-pipe-requests`: 是否转发由其他 Pipe 写入的数据
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+
### 3.5 压缩同步
IoTDB 支持在同步过程中指定数据压缩方式。可通过配置 `compressor` 参数，实现数据的实时压缩和传输。`compressor`目前支持
snappy / gzip / lz4 / zstd / lzma2 5
种可选算法，且可以选择多种压缩算法组合，按配置的顺序进行压缩。`rate-limit-bytes-per-second`（V1.3.3
及以后版本支持）每秒最大允许传输的byte数,计算压缩后的byte，若小于0则不限制。
@@ -487,11 +505,15 @@ IoTDB 支持在同步过程中指定数据压缩方式。可通过配置 `compre
```SQL
create pipe A2B
with sink (
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
- 'compressor' = 'snappy,lz4' -- 压缩算法
+ 'node-urls' = '127.0.0.1:6668',
+ 'compressor' = 'snappy,lz4'
)
```
+其中：
+
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+
### 3.6 加密同步
IoTDB 支持在同步过程中使用 SSL 加密，从而在不同的 IoTDB 实例之间安全地传输数据。通过配置 SSL
相关的参数，如证书地址和密码（`ssl.trust-store-path`）、（`ssl.trust-store-pwd`）可以确保数据在同步过程中被 SSL
加密所保护。
@@ -502,12 +524,18 @@ IoTDB 支持在同步过程中使用 SSL 加密，从而在不同的 IoTDB 实
create pipe A2B
with sink (
'sink'='iotdb-thrift-ssl-sink',
- 'node-urls'='127.0.0.1:6667', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
- 'ssl.trust-store-path'='pki/trusted', -- 连接目标端 DataNode 所需的 trust store 证书路径
- 'ssl.trust-store-pwd'='root' -- 连接目标端 DataNode 所需的 trust store 证书密码
+ 'node-urls'='127.0.0.1:6667',
+ 'ssl.trust-store-path'='pki/trusted',
+ 'ssl.trust-store-pwd'='root'
)
```
+其中：
+
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+- `ssl.trust-store-path`: 连接目标端 DataNode 所需的 trust store 证书路径
+- `ssl.trust-store-pwd`: 连接目标端 DataNode 所需的 trust store 证书密码
+
## 4. 参考：注意事项
可通过修改 IoTDB 配置文件（`iotdb-system.properties`）以调整数据同步的参数，如同步数据存储目录等。完整配置如下：：
diff --git
a/src/zh/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
b/src/zh/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
index 45ee65df..0dcf408a 100644
---
a/src/zh/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
+++
b/src/zh/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
@@ -90,7 +90,7 @@ Toto<sup><a href="#appendix5" id="ref5"
style="text-decoration: none;">[5]</a></
-## 9. 效果展示
+## 8. 效果展示
时序大模型能够适应多种不同领域和场景的真实时序数据，在各种任务上拥有优异的处理效果，以下是在不同数据上的真实表现：
@@ -112,7 +112,7 @@ Toto<sup><a href="#appendix5" id="ref5"
style="text-decoration: none;">[5]</a></
-## 10. 部署使用
+## 9. 部署使用
1. 打开 IoTDB cli 控制台，检查 ConfigNode、DataNode、AINode 节点确保均为 Running。
diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md
b/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md
index 300abc8e..1fa296f7 100644
--- a/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md
+++ b/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md
@@ -334,7 +334,7 @@ IoTDB> SHOW PIPEPLUGINS
create pipe A2B
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
@@ -352,17 +352,24 @@ with sink (
create pipe A2B
WITH SOURCE (
'source'= 'iotdb-source',
- 'mode.streaming' = 'true' -- 新插入数据（pipe创建后）的抽取模式：是否按流式抽取（false 时为批式）
- 'database-name'='testdb.*', -- 同步数据的范围
- 'start-time' = '2023.08.23T08:00:00+00:00', -- 同步所有数据的开始 event time，包含
start-time
- 'end-time' = '2023.10.23T08:00:00+00:00' -- 同步所有数据的结束 event time，包含 end-time
+ 'mode.streaming' = 'true',
+ 'database-name'='testdb.*',
+ 'start-time' = '2023.08.23T08:00:00+00:00',
+ 'end-time' = '2023.10.23T08:00:00+00:00'
)
with SINK (
'sink'='iotdb-thrift-async-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
+其中：
+
+- `mode.streaming`: 新插入数据（pipe创建后）的抽取模式：是否按流式抽取（false 时为批式）
+- `database-name`: 同步数据的范围
+- `start-time`: 同步所有数据的开始 event time，包含 start-time
+- `end-time`: 同步所有数据的结束 event time，包含 end-time
+
### 3.3 边云数据传输
本例子用来演示多个 IoTDB 之间边云传输数据的场景，数据由 B 、C、D 集群分别都同步至 A 集群，数据链路如下图所示：
@@ -376,12 +383,12 @@ with SINK (
```SQL
create pipe BA
with source (
- 'database-name'='db_b.*', -- 限制范围
- 'table-name'='.*', -- 可选择匹配所有
+ 'database-name'='db_b.*',
+ 'table-name'='.*',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6667', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6667',
)
```
@@ -390,12 +397,12 @@ with sink (
```SQL
create pipe CA
with source (
- 'database-name'='db_c.*', -- 限制范围
- 'table-name'='.*', -- 可选择匹配所有
+ 'database-name'='db_c.*',
+ 'table-name'='.*',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
@@ -404,29 +411,34 @@ with sink (
```SQL
create pipe DA
with source (
- 'database-name'='db_d.*', -- 限制范围
- 'table-name'='.*', -- 可选择匹配所有
+ 'database-name'='db_d.*',
+ 'table-name'='.*',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6669',
)
```
+前两个示例中的参数含义与此处相同：
+
+- `database-name`: 限制范围
+- `table-name`: 可选择匹配所有
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+
### 3.4 级联数据传输
本例子用来演示多个 IoTDB 之间级联传输数据的场景，数据由 A 集群同步至 B 集群，再同步至 C 集群，数据链路如下图所示：
-
在 A IoTDB 上执行下列语句，将 A 中数据同步至 B：
```SQL
create pipe AB
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
@@ -438,10 +450,14 @@ with source (
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6669',
)
```
+前一个示例中的参数含义与此处相同：
+
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+
### 3.5 压缩同步
IoTDB 支持在同步过程中指定数据压缩方式。可通过配置 `compressor` 参数，实现数据的实时压缩和传输。`compressor`目前支持
snappy / gzip / lz4 / zstd / lzma2 5
种可选算法，且可以选择多种压缩算法组合，按配置的顺序进行压缩。`rate-limit-bytes-per-second`（V1.3.3
及以后版本支持）每秒最大允许传输的byte数,计算压缩后的byte，若小于0则不限制。
@@ -451,12 +467,15 @@ IoTDB 支持在同步过程中指定数据压缩方式。可通过配置 `compre
```SQL
create pipe A2B
with sink (
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
- 'compressor' = 'snappy,lz4' --
- 'rate-limit-bytes-per-second'='1048576' -- 每秒最大允许传输的byte数
+ 'node-urls' = '127.0.0.1:6668',
+ 'compressor' = 'snappy,lz4',
+ 'rate-limit-bytes-per-second'='1048576'
)
```
+其中：
+
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
### 3.6 加密同步
@@ -468,12 +487,18 @@ IoTDB 支持在同步过程中使用 SSL 加密，从而在不同的 IoTDB 实
create pipe A2B
with sink (
'sink'='iotdb-thrift-ssl-sink',
- 'node-urls'='127.0.0.1:6667', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
- 'ssl.trust-store-path'='pki/trusted', -- 连接目标端 DataNode 所需的 trust store 证书路径
- 'ssl.trust-store-pwd'='root' -- 连接目标端 DataNode 所需的 trust store 证书密码
+ 'node-urls'='127.0.0.1:6667',
+ 'ssl.trust-store-path'='pki/trusted',
+ 'ssl.trust-store-pwd'='root'
)
```
+其中：
+
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+- `ssl.trust-store-path`: 连接目标端 DataNode 所需的 trust store 证书路径
+- `ssl.trust-store-pwd`: 连接目标端 DataNode 所需的 trust store 证书密码
+
## 参考：注意事项
可通过修改 IoTDB 配置文件（`iotdb-system.properties`）以调整数据同步的参数，如同步数据存储目录等。完整配置如下：：
diff --git
a/src/zh/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
b/src/zh/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
index 45ee65df..0dcf408a 100644
---
a/src/zh/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
+++
b/src/zh/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md
@@ -90,7 +90,7 @@ Toto<sup><a href="#appendix5" id="ref5"
style="text-decoration: none;">[5]</a></
-## 9. 效果展示
+## 8. 效果展示
时序大模型能够适应多种不同领域和场景的真实时序数据，在各种任务上拥有优异的处理效果，以下是在不同数据上的真实表现：
@@ -112,7 +112,7 @@ Toto<sup><a href="#appendix5" id="ref5"
style="text-decoration: none;">[5]</a></
-## 10. 部署使用
+## 9. 部署使用
1. 打开 IoTDB cli 控制台，检查 ConfigNode、DataNode、AINode 节点确保均为 Running。
diff --git a/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md
b/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md
index 2bb46b1d..0da6bb54 100644
--- a/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md
+++ b/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md
@@ -368,7 +368,7 @@ IoTDB> SHOW PIPEPLUGINS
create pipe A2B
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
@@ -386,17 +386,24 @@ with sink (
create pipe A2B
WITH SOURCE (
'source'= 'iotdb-source',
- 'realtime.mode' = 'stream' -- 新插入数据（pipe创建后）的抽取模式
- 'path' = 'root.vehicle.**', -- 同步数据的范围
- 'start-time' = '2023.08.23T08:00:00+00:00', -- 同步所有数据的开始 event time，包含
start-time
- 'end-time' = '2023.10.23T08:00:00+00:00' -- 同步所有数据的结束 event time，包含 end-time
+ 'realtime.mode' = 'stream',
+ 'path' = 'root.vehicle.**',
+ 'start-time' = '2023.08.23T08:00:00+00:00',
+ 'end-time' = '2023.10.23T08:00:00+00:00'
)
with SINK (
'sink'='iotdb-thrift-async-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
+其中：
+
+- `realtime.mode`: 新插入数据（pipe创建后）的抽取模式
+- `path`: 同步数据的范围
+- `start-time`: 同步所有数据的开始 event time，包含 start-time
+- `end-time`: 同步所有数据的结束 event time，包含 end-time
+
### 3.3 边云数据传输
本例子用来演示多个 IoTDB 之间边云传输数据的场景，数据由 B 、C、D 集群分别都同步至 A 集群，数据链路如下图所示：
@@ -410,12 +417,12 @@ with SINK (
```SQL
create pipe BA
with source (
- 'inclusion'='all', -- 表示同步全量数据、元数据和权限
- 'path'='root.db.**', -- 限制范围
+ 'inclusion'='all',
+ 'path'='root.db.**',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6667', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6667',
)
```
@@ -424,12 +431,12 @@ with sink (
```SQL
create pipe CA
with source (
- 'inclusion'='all', -- 表示同步全量数据、元数据和权限
- 'path'='root.db.**', -- 限制范围
+ 'inclusion'='all',
+ 'path'='root.db.**',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
@@ -438,15 +445,21 @@ with sink (
```SQL
create pipe DA
with source (
- 'inclusion'='all', -- 表示同步全量数据、元数据和权限
- 'path'='root.db.**', -- 限制范围
+ 'inclusion'='all',
+ 'path'='root.db.**',
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6669',
)
```
+前两个示例中的参数含义与此处相同：
+
+- `inclusion`: 表示同步全量数据、元数据和权限
+- `path`: 限制范围
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+
### 3.4 级联数据传输
本例子用来演示多个 IoTDB 之间级联传输数据的场景，数据由 A 集群同步至 B 集群，再同步至 C 集群，数据链路如下图所示：
@@ -461,7 +474,7 @@ with sink (
create pipe AB
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6668',
)
```
@@ -470,14 +483,19 @@ with sink (
```SQL
create pipe BC
with source (
- 'forwarding-pipe-requests' = 'true' --是否转发由其他 Pipe 写入的数据
+ 'forwarding-pipe-requests' = 'true'
)
with sink (
'sink'='iotdb-thrift-sink',
- 'node-urls' = '127.0.0.1:6669', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+ 'node-urls' = '127.0.0.1:6669',
)
```
+前一个示例中的 `node-urls` 参数含义与此处相同：
+
+- `forwarding-pipe-requests`: 是否转发由其他 Pipe 写入的数据
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+
### 3.5 压缩同步
IoTDB 支持在同步过程中指定数据压缩方式。可通过配置 `compressor` 参数，实现数据的实时压缩和传输。`compressor`目前支持
snappy / gzip / lz4 / zstd / lzma2 5
种可选算法，且可以选择多种压缩算法组合，按配置的顺序进行压缩。`rate-limit-bytes-per-second`（V1.3.3
及以后版本支持）每秒最大允许传输的byte数,计算压缩后的byte，若小于0则不限制。
@@ -487,11 +505,15 @@ IoTDB 支持在同步过程中指定数据压缩方式。可通过配置 `compre
```SQL
create pipe A2B
with sink (
- 'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
- 'compressor' = 'snappy,lz4' -- 压缩算法
+ 'node-urls' = '127.0.0.1:6668',
+ 'compressor' = 'snappy,lz4'
)
```
+其中：
+
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+
### 3.6 加密同步
IoTDB 支持在同步过程中使用 SSL 加密，从而在不同的 IoTDB 实例之间安全地传输数据。通过配置 SSL
相关的参数，如证书地址和密码（`ssl.trust-store-path`）、（`ssl.trust-store-pwd`）可以确保数据在同步过程中被 SSL
加密所保护。
@@ -502,12 +524,18 @@ IoTDB 支持在同步过程中使用 SSL 加密，从而在不同的 IoTDB 实
create pipe A2B
with sink (
'sink'='iotdb-thrift-ssl-sink',
- 'node-urls'='127.0.0.1:6667', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
- 'ssl.trust-store-path'='pki/trusted', -- 连接目标端 DataNode 所需的 trust store 证书路径
- 'ssl.trust-store-pwd'='root' -- 连接目标端 DataNode 所需的 trust store 证书密码
+ 'node-urls'='127.0.0.1:6667',
+ 'ssl.trust-store-path'='pki/trusted',
+ 'ssl.trust-store-pwd'='root'
)
```
+其中：
+
+- `node-urls`: 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
+- `ssl.trust-store-path`: 连接目标端 DataNode 所需的 trust store 证书路径
+- `ssl.trust-store-pwd`: 连接目标端 DataNode 所需的 trust store 证书密码
+
## 4. 参考：注意事项
可通过修改 IoTDB 配置文件（`iotdb-system.properties`）以调整数据同步的参数，如同步数据存储目录等。完整配置如下：：
