Skip to content

Commit adfe0c9

Browse files
leto-bbqleto-bbq
committed
remove bidirectional examples in table model apache
1 parent 94f9507 commit adfe0c9

4 files changed

Lines changed: 16 additions & 154 deletions

File tree

‎src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md‎

Lines changed: 4 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -292,41 +292,7 @@ WITH SINK (
292292
'node-urls' = '127.0.0.1:6668' -- The URL of the DataNode's data service port in the target IoTDB instance.
293293
)
294294
```
295-
### 3.3 Bidirectional Data Transmission
296-
297-
This example demonstrates a scenario where two IoTDB instances act as dual-active systems. The data pipeline is shown below:
298-
299-
![](/img/e3.png)
300-
301-
To avoid infinite data loops, the `source.mode.double-living` parameter must be set to `true` on both IoTDB A and B, indicating that data forwarded from another pipe will not be retransmitted.
302-
303-
SQL Example: On IoTDB A:
304-
305-
```SQL
306-
CREATE PIPE AB
307-
WITH SOURCE (
308-
'source.mode.double-living' = 'true' -- Do not forward data from other pipes
309-
)
310-
WITH SINK (
311-
'sink' = 'iotdb-thrift-sink',
312-
'node-urls' = '127.0.0.1:6668' -- URL of the DataNode service port on the target IoTDB
313-
)
314-
```
315-
316-
On IoTDB B:
317-
318-
```SQL
319-
CREATE PIPE BA
320-
WITH SOURCE (
321-
'source.mode.double-living' = 'true' -- Do not forward data from other pipes
322-
)
323-
WITH SINK (
324-
'sink' = 'iotdb-thrift-sink',
325-
'node-urls' = '127.0.0.1:6667' -- URL of the DataNode service port on the target IoTDB
326-
)
327-
```
328-
329-
### 3.4 Edge-to-Cloud Data Transmission
295+
### 3.3 Edge-to-Cloud Data Transmission
330296

331297
This example demonstrates synchronizing data from multiple IoTDB clusters (B, C, D) to a central IoTDB cluster (A). The data pipeline is shown below:
332298

@@ -376,7 +342,7 @@ WITH SINK (
376342
)
377343
```
378344

379-
### 3.5 Cascaded Data Transmission
345+
### 3.4 Cascaded Data Transmission
380346

381347
This example demonstrates cascading data transmission from IoTDB A to IoTDB B and then to IoTDB C. The data pipeline is shown below:
382348

@@ -407,7 +373,7 @@ WITH SINK (
407373
```
408374

409375

410-
### 3.6 Compressed Synchronization
376+
### 3.5 Compressed Synchronization
411377

412378
IoTDB supports specifying data compression methods during synchronization. The `compressor` parameter can be configured to enable real-time data compression and transmission. Supported algorithms include `snappy`, `gzip`, `lz4`, `zstd`, and `lzma2`. Multiple algorithms can be combined and applied in the configured order. The `rate-limit-bytes-per-second` parameter (supported in V1.3.3 and later) limits the maximum number of bytes transmitted per second (calculated after compression). If set to a value less than 0, there is no limit.
413379

@@ -423,7 +389,7 @@ WITH SINK (
423389
```
424390

425391

426-
### 3.7 Encrypted Synchronization
392+
### 3.6 Encrypted Synchronization
427393

428394
IoTDB supports SSL encryption during synchronization to securely transmit data between IoTDB instances. By configuring SSL-related parameters such as the certificate path (`ssl.trust-store-path`) and password (`ssl.trust-store-pwd`), data can be protected by SSL encryption during synchronization.
429395

‎src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md‎

Lines changed: 4 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -292,41 +292,7 @@ WITH SINK (
292292
'node-urls' = '127.0.0.1:6668' -- The URL of the DataNode's data service port in the target IoTDB instance.
293293
)
294294
```
295-
### 3.3 Bidirectional Data Transmission
296-
297-
This example demonstrates a scenario where two IoTDB instances act as dual-active systems. The data pipeline is shown below:
298-
299-
![](/img/e3.png)
300-
301-
To avoid infinite data loops, the `source.mode.double-living` parameter must be set to `true` on both IoTDB A and B, indicating that data forwarded from another pipe will not be retransmitted.
302-
303-
SQL Example: On IoTDB A:
304-
305-
```SQL
306-
CREATE PIPE AB
307-
WITH SOURCE (
308-
'source.mode.double-living' = 'true' -- Do not forward data from other pipes
309-
)
310-
WITH SINK (
311-
'sink' = 'iotdb-thrift-sink',
312-
'node-urls' = '127.0.0.1:6668' -- URL of the DataNode service port on the target IoTDB
313-
)
314-
```
315-
316-
On IoTDB B:
317-
318-
```SQL
319-
CREATE PIPE BA
320-
WITH SOURCE (
321-
'source.mode.double-living' = 'true' -- Do not forward data from other pipes
322-
)
323-
WITH SINK (
324-
'sink' = 'iotdb-thrift-sink',
325-
'node-urls' = '127.0.0.1:6667' -- URL of the DataNode service port on the target IoTDB
326-
)
327-
```
328-
329-
### 3.4 Edge-to-Cloud Data Transmission
295+
### 3.3 Edge-to-Cloud Data Transmission
330296

331297
This example demonstrates synchronizing data from multiple IoTDB clusters (B, C, D) to a central IoTDB cluster (A). The data pipeline is shown below:
332298

@@ -376,7 +342,7 @@ WITH SINK (
376342
)
377343
```
378344

379-
### 3.5 Cascaded Data Transmission
345+
### 3.4 Cascaded Data Transmission
380346

381347
This example demonstrates cascading data transmission from IoTDB A to IoTDB B and then to IoTDB C. The data pipeline is shown below:
382348

@@ -407,7 +373,7 @@ WITH SINK (
407373
```
408374

409375

410-
### 3.6 Compressed Synchronization
376+
### 3.5 Compressed Synchronization
411377

412378
IoTDB supports specifying data compression methods during synchronization. The `compressor` parameter can be configured to enable real-time data compression and transmission. Supported algorithms include `snappy`, `gzip`, `lz4`, `zstd`, and `lzma2`. Multiple algorithms can be combined and applied in the configured order. The `rate-limit-bytes-per-second` parameter (supported in V1.3.3 and later) limits the maximum number of bytes transmitted per second (calculated after compression). If set to a value less than 0, there is no limit.
413379

@@ -423,7 +389,7 @@ WITH SINK (
423389
```
424390

425391

426-
### 3.7 Encrypted Synchronization
392+
### 3.6 Encrypted Synchronization
427393

428394
IoTDB supports SSL encryption during synchronization to securely transmit data between IoTDB instances. By configuring SSL-related parameters such as the certificate path (`ssl.trust-store-path`) and password (`ssl.trust-store-pwd`), data can be protected by SSL encryption during synchronization.
429395

‎src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md‎

Lines changed: 4 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -286,42 +286,7 @@ with SINK (
286286
)
287287
```
288288

289-
### 3.3 双向数据传输
290-
291-
本例子用来演示两个 IoTDB 之间互为双活的场景，数据链路如下图所示：
292-
293-
![](/img/1706698592139.jpg)
294-
295-
在这个例子中，为了避免数据无限循环，需要将 A 和 B 上的参数`source.mode.double-living` 均设置为 `true`，表示不转发从另一 pipe 传输而来的数据。
296-
297-
详细语句如下：
298-
299-
在 A IoTDB 上执行下列语句：
300-
301-
```SQL
302-
create pipe AB
303-
with source (
304-
'source.mode.double-living' ='true' --不转发由其他 Pipe 写入的数据
305-
)
306-
with sink (
307-
'sink'='iotdb-thrift-sink',
308-
'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
309-
)
310-
```
311-
312-
在 B IoTDB 上执行下列语句：
313-
314-
```SQL
315-
create pipe BA
316-
with source (
317-
'source.mode.double-living' ='true' --不转发由其他 Pipe 写入的数据
318-
)
319-
with sink (
320-
'sink'='iotdb-thrift-sink',
321-
'node-urls' = '127.0.0.1:6667', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
322-
)
323-
```
324-
### 3.4 边云数据传输
289+
### 3.3 边云数据传输
325290

326291
本例子用来演示多个 IoTDB 之间边云传输数据的场景，数据由 B 、C、D 集群分别都同步至 A 集群，数据链路如下图所示：
327292

@@ -371,7 +336,7 @@ with sink (
371336
)
372337
```
373338

374-
### 3.5 级联数据传输
339+
### 3.4 级联数据传输
375340

376341
本例子用来演示多个 IoTDB 之间级联传输数据的场景，数据由 A 集群同步至 B 集群，再同步至 C 集群，数据链路如下图所示：
377342

@@ -401,7 +366,7 @@ with sink (
401366
)
402367
```
403368

404-
### 3.6 压缩同步
369+
### 3.5 压缩同步
405370

406371
IoTDB 支持在同步过程中指定数据压缩方式。可通过配置 `compressor` 参数，实现数据的实时压缩和传输。`compressor`目前支持 snappy / gzip / lz4 / zstd / lzma2 5 种可选算法，且可以选择多种压缩算法组合，按配置的顺序进行压缩。`rate-limit-bytes-per-second`（V1.3.3 及以后版本支持）每秒最大允许传输的byte数,计算压缩后的byte，若小于0则不限制。
407372

@@ -417,7 +382,7 @@ with sink (
417382
```
418383

419384

420-
### 3.7 加密同步
385+
### 3.6 加密同步
421386

422387
IoTDB 支持在同步过程中使用 SSL 加密，从而在不同的 IoTDB 实例之间安全地传输数据。通过配置 SSL 相关的参数，如证书地址和密码（`ssl.trust-store-path`）、（`ssl.trust-store-pwd`）可以确保数据在同步过程中被 SSL 加密所保护。
423388

‎src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md‎

Lines changed: 4 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -286,42 +286,7 @@ with SINK (
286286
)
287287
```
288288

289-
### 3.3 双向数据传输
290-
291-
本例子用来演示两个 IoTDB 之间互为双活的场景，数据链路如下图所示：
292-
293-
![](/img/1706698592139.jpg)
294-
295-
在这个例子中，为了避免数据无限循环，需要将 A 和 B 上的参数`source.mode.double-living` 均设置为 `true`，表示不转发从另一 pipe 传输而来的数据。
296-
297-
详细语句如下：
298-
299-
在 A IoTDB 上执行下列语句：
300-
301-
```SQL
302-
create pipe AB
303-
with source (
304-
'source.mode.double-living' ='true' --不转发由其他 Pipe 写入的数据
305-
)
306-
with sink (
307-
'sink'='iotdb-thrift-sink',
308-
'node-urls' = '127.0.0.1:6668', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
309-
)
310-
```
311-
312-
在 B IoTDB 上执行下列语句：
313-
314-
```SQL
315-
create pipe BA
316-
with source (
317-
'source.mode.double-living' ='true' --不转发由其他 Pipe 写入的数据
318-
)
319-
with sink (
320-
'sink'='iotdb-thrift-sink',
321-
'node-urls' = '127.0.0.1:6667', -- 目标端 IoTDB 中 DataNode 节点的数据服务端口的 url
322-
)
323-
```
324-
### 3.4 边云数据传输
289+
### 3.3 边云数据传输
325290

326291
本例子用来演示多个 IoTDB 之间边云传输数据的场景，数据由 B 、C、D 集群分别都同步至 A 集群，数据链路如下图所示：
327292

@@ -371,7 +336,7 @@ with sink (
371336
)
372337
```
373338

374-
### 3.5 级联数据传输
339+
### 3.4 级联数据传输
375340

376341
本例子用来演示多个 IoTDB 之间级联传输数据的场景，数据由 A 集群同步至 B 集群，再同步至 C 集群，数据链路如下图所示：
377342

@@ -401,7 +366,7 @@ with sink (
401366
)
402367
```
403368

404-
### 3.6 压缩同步
369+
### 3.5 压缩同步
405370

406371
IoTDB 支持在同步过程中指定数据压缩方式。可通过配置 `compressor` 参数，实现数据的实时压缩和传输。`compressor`目前支持 snappy / gzip / lz4 / zstd / lzma2 5 种可选算法，且可以选择多种压缩算法组合，按配置的顺序进行压缩。`rate-limit-bytes-per-second`（V1.3.3 及以后版本支持）每秒最大允许传输的byte数,计算压缩后的byte，若小于0则不限制。
407372

@@ -417,7 +382,7 @@ with sink (
417382
```
418383

419384

420-
### 3.7 加密同步
385+
### 3.6 加密同步
421386

422387
IoTDB 支持在同步过程中使用 SSL 加密，从而在不同的 IoTDB 实例之间安全地传输数据。通过配置 SSL 相关的参数，如证书地址和密码（`ssl.trust-store-path`）、（`ssl.trust-store-pwd`）可以确保数据在同步过程中被 SSL 加密所保护。
423388

0 commit comments

Comments
 (0)