This is an automated email from the ASF dual-hosted git repository.
critas 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 906aa207 add sink param batch.max-delay-ms to tree model 13x (#930)
906aa207 is described below
commit 906aa207108fbb4813557b5c22f2cdc9739daad3
Author: leto-b <[email protected]>
AuthorDate: Fri Dec 26 11:12:21 2025 +0800
add sink param batch.max-delay-ms to tree model 13x (#930)
---
src/UserGuide/V1.3.x/User-Manual/Data-Sync_apache.md | 4 +++-
src/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md | 4 +++-
src/UserGuide/dev-1.3/User-Manual/Data-Sync_apache.md | 18 ++++++++++--------
src/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md | 4 +++-
.../UserGuide/V1.3.x/User-Manual/Data-Sync_apache.md | 2 ++
.../UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md | 18 ++++++++++--------
.../UserGuide/dev-1.3/User-Manual/Data-Sync_apache.md | 2 ++
.../UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md | 4 +++-
8 files changed, 36 insertions(+), 20 deletions(-)
diff --git a/src/UserGuide/V1.3.x/User-Manual/Data-Sync_apache.md
b/src/UserGuide/V1.3.x/User-Manual/Data-Sync_apache.md
index a6cf1c24..658b9d47 100644
--- a/src/UserGuide/V1.3.x/User-Manual/Data-Sync_apache.md
+++ b/src/UserGuide/V1.3.x/User-Manual/Data-Sync_apache.md
@@ -505,7 +505,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
> - **batch**: In this mode, tasks process and send data in batches (according
> to the underlying data files). It is characterized by low timeliness and
> high throughput.
-## sink parameter
+### sink parameter
> In versions 1.3.3 and above, when only the sink is included, the additional
> "with sink" prefix is no longer required.
@@ -518,6 +518,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | The URL of the data service port of any DataNode
nodes on the target IoTDB (please note that synchronization tasks do not
support forwarding to its own service) | String. Example:
'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | Required
| - |
| batch.enable | Whether to enable batched log transmission mode to
improve transmission throughput and reduce IOPS | Boolean: true, false
| Optional | true |
| batch.max-delay-seconds | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: s) | Integer
| Optional | 1 |
+| batch.max-delay-ms | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: ms) (Available since v1.3.6) | Integer
| Optional | 1
|
| batch.size-bytes | Effective when batched log transmission mode
is enabled, it represents the maximum batch size for a batch of data (unit:
byte) | Long |
Optional | 16*1024*1024 |
#### iotdb-thrift-ssl-sink
@@ -528,6 +529,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | The URL of the data service port of any DataNode
nodes on the target IoTDB (please note that synchronization tasks do not
support forwarding to its own service) | String. Example:
'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | Required
| - |
| batch.enable | Whether to enable batched log transmission mode to
improve transmission throughput and reduce IOPS | Boolean: true, false
| Optional | true |
| batch.max-delay-seconds | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: s) | Integer
| Optional | 1 |
+| batch.max-delay-ms | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: ms) (Available since v1.3.6) | Integer
| Optional | 1
|
| batch.size-bytes | Effective when batched log transmission mode is
enabled, it represents the maximum batch size for a batch of data (unit: byte)
| Long | Optional
| 16*1024*1024 |
| ssl.trust-store-path | The trust store certificate path required to
connect to the target DataNode | String: certificate
directory name, when configured as a relative directory, it is relative to the
IoTDB root directory. Example: '127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669',
'127.0.0.1:6667'| Required | - |
| ssl.trust-store-pwd | The trust store certificate password required to
connect to the target DataNode | Integer
| Required | - |
diff --git a/src/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
b/src/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
index df000cfa..4bfb5c6b 100644
--- a/src/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
@@ -590,7 +590,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
> - **batch**: In this mode, tasks process and send data in batches (according
> to the underlying data files). It is characterized by low timeliness and
> high throughput.
-## sink parameter
+### sink parameter
> In versions 1.3.3 and above, when only the sink is included, the additional
> "with sink" prefix is no longer required.
@@ -603,6 +603,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | The URL of the data service port of any DataNode
nodes on the target IoTDB (please note that synchronization tasks do not
support forwarding to its own service) | String. Example:
'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | Required
| - |
| batch.enable | Whether to enable batched log transmission mode to
improve transmission throughput and reduce IOPS | Boolean: true, false
| Optional | true |
| batch.max-delay-seconds | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: s) | Integer
| Optional | 1 |
+| batch.max-delay-ms | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: ms) (Available since v1.3.6) | Integer
| Optional | 1
|
| batch.size-bytes | Effective when batched log transmission mode
is enabled, it represents the maximum batch size for a batch of data (unit:
byte) | Long |
Optional | 16*1024*1024 |
#### iotdb-air-gap-sink
@@ -621,6 +622,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | The URL of the data service port of any DataNode
nodes on the target IoTDB (please note that synchronization tasks do not
support forwarding to its own service) | String. Example:
'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | Required
| - |
| batch.enable | Whether to enable batched log transmission mode to
improve transmission throughput and reduce IOPS | Boolean: true, false
| Optional | true |
| batch.max-delay-seconds | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: s) | Integer
| Optional | 1 |
+| batch.max-delay-ms | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: ms) (Available since v1.3.6) | Integer
| Optional | 1
|
| batch.size-bytes | Effective when batched log transmission mode is
enabled, it represents the maximum batch size for a batch of data (unit: byte)
| Long | Optional
| 16*1024*1024 |
| ssl.trust-store-path | The trust store certificate path required to
connect to the target DataNode | String: certificate
directory name, when configured as a relative directory, it is relative to the
IoTDB root directory. Example: '127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669',
'127.0.0.1:6667'| Required | - |
| ssl.trust-store-pwd | The trust store certificate password required to
connect to the target DataNode | Integer
| Required | - |
diff --git a/src/UserGuide/dev-1.3/User-Manual/Data-Sync_apache.md
b/src/UserGuide/dev-1.3/User-Manual/Data-Sync_apache.md
index a6cf1c24..d48c05be 100644
--- a/src/UserGuide/dev-1.3/User-Manual/Data-Sync_apache.md
+++ b/src/UserGuide/dev-1.3/User-Manual/Data-Sync_apache.md
@@ -505,20 +505,21 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
> - **batch**: In this mode, tasks process and send data in batches (according
> to the underlying data files). It is characterized by low timeliness and
> high throughput.
-## sink parameter
+### sink parameter
> In versions 1.3.3 and above, when only the sink is included, the additional
> "with sink" prefix is no longer required.
#### iotdb-thrift-sink
-| key | value
| value Range |
required or not | Default Value |
-| :--------------------------- |
:----------------------------------------------------------- |
:----------------------------------------------------------- | :------- |
:----------- |
-| sink | iotdb-thrift-sink or iotdb-thrift-async-sink
| String: iotdb-thrift-sink or iotdb-thrift-async-sink |
Required | |
-| node-urls | The URL of the data service port of any DataNode
nodes on the target IoTDB (please note that synchronization tasks do not
support forwarding to its own service) | String. Example:
'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | Required
| - |
-| batch.enable | Whether to enable batched log transmission mode to
improve transmission throughput and reduce IOPS | Boolean: true, false
| Optional | true |
-| batch.max-delay-seconds | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: s) | Integer
| Optional | 1 |
-| batch.size-bytes | Effective when batched log transmission mode
is enabled, it represents the maximum batch size for a batch of data (unit:
byte) | Long |
Optional | 16*1024*1024 |
+| key | value
| value Range
| required or not | Default
Value |
+| :---------------------------
|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------------------|
:------- | :----------- |
+| sink | iotdb-thrift-sink or iotdb-thrift-async-sink
| String: iotdb-thrift-sink or
iotdb-thrift-async-sink | Required |
|
+| node-urls | The URL of the data service port of any DataNode
nodes on the target IoTDB (please note that synchronization tasks do not
support forwarding to its own service) | String. Example:
'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | Required
| - |
+| batch.enable | Whether to enable batched log transmission mode to
improve transmission throughput and reduce IOPS
| Boolean: true, false
| Optional | true |
+| batch.max-delay-seconds | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: s) | Integer
| Optional | 1 |
+| batch.max-delay-ms | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: ms) (Available since v1.3.6) | Integer
| Optional | 1
|
+| batch.size-bytes | Effective when batched log transmission mode
is enabled, it represents the maximum batch size for a batch of data (unit:
byte) | Long
| Optional |
16*1024*1024 |
#### iotdb-thrift-ssl-sink
@@ -528,6 +529,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | The URL of the data service port of any DataNode
nodes on the target IoTDB (please note that synchronization tasks do not
support forwarding to its own service) | String. Example:
'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | Required
| - |
| batch.enable | Whether to enable batched log transmission mode to
improve transmission throughput and reduce IOPS | Boolean: true, false
| Optional | true |
| batch.max-delay-seconds | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: s) | Integer
| Optional | 1 |
+| batch.max-delay-ms | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: ms) (Available since v1.3.6) | Integer
| Optional | 1
|
| batch.size-bytes | Effective when batched log transmission mode is
enabled, it represents the maximum batch size for a batch of data (unit: byte)
| Long | Optional
| 16*1024*1024 |
| ssl.trust-store-path | The trust store certificate path required to
connect to the target DataNode | String: certificate
directory name, when configured as a relative directory, it is relative to the
IoTDB root directory. Example: '127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669',
'127.0.0.1:6667'| Required | - |
| ssl.trust-store-pwd | The trust store certificate password required to
connect to the target DataNode | Integer
| Required | - |
diff --git a/src/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
b/src/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
index df000cfa..4bfb5c6b 100644
--- a/src/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
@@ -590,7 +590,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
> - **batch**: In this mode, tasks process and send data in batches (according
> to the underlying data files). It is characterized by low timeliness and
> high throughput.
-## sink parameter
+### sink parameter
> In versions 1.3.3 and above, when only the sink is included, the additional
> "with sink" prefix is no longer required.
@@ -603,6 +603,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | The URL of the data service port of any DataNode
nodes on the target IoTDB (please note that synchronization tasks do not
support forwarding to its own service) | String. Example:
'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | Required
| - |
| batch.enable | Whether to enable batched log transmission mode to
improve transmission throughput and reduce IOPS | Boolean: true, false
| Optional | true |
| batch.max-delay-seconds | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: s) | Integer
| Optional | 1 |
+| batch.max-delay-ms | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: ms) (Available since v1.3.6) | Integer
| Optional | 1
|
| batch.size-bytes | Effective when batched log transmission mode
is enabled, it represents the maximum batch size for a batch of data (unit:
byte) | Long |
Optional | 16*1024*1024 |
#### iotdb-air-gap-sink
@@ -621,6 +622,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | The URL of the data service port of any DataNode
nodes on the target IoTDB (please note that synchronization tasks do not
support forwarding to its own service) | String. Example:
'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | Required
| - |
| batch.enable | Whether to enable batched log transmission mode to
improve transmission throughput and reduce IOPS | Boolean: true, false
| Optional | true |
| batch.max-delay-seconds | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: s) | Integer
| Optional | 1 |
+| batch.max-delay-ms | Effective when batched log transmission mode is
enabled, it represents the maximum waiting time for a batch of data before
sending (unit: ms) (Available since v1.3.6) | Integer
| Optional | 1
|
| batch.size-bytes | Effective when batched log transmission mode is
enabled, it represents the maximum batch size for a batch of data (unit: byte)
| Long | Optional
| 16*1024*1024 |
| ssl.trust-store-path | The trust store certificate path required to
connect to the target DataNode | String: certificate
directory name, when configured as a relative directory, it is relative to the
IoTDB root directory. Example: '127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669',
'127.0.0.1:6667'| Required | - |
| ssl.trust-store-pwd | The trust store certificate password required to
connect to the target DataNode | Integer
| Required | - |
diff --git a/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync_apache.md
b/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync_apache.md
index e50f52ce..abd8b35c 100644
--- a/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync_apache.md
+++ b/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync_apache.md
@@ -513,6 +513,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | 目标端 IoTDB 任意多个 DataNode 节点的数据服务端口的
url(请注意同步任务不支持向自身服务进行转发) | String.
例:'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | 必填 | -
|
| batch.enable | 是否开启日志攒批发送模式,用于提高传输吞吐,降低 IOPS | Boolean:
true, false | 选填 | true |
| batch.max-delay-seconds | 在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:s) | Integer
| 选填 | 1 |
+| batch.max-delay-ms |
在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:ms)(V1.3.6及以后的V1.x版本支持) | Integer
| 选填 | 1
|
| batch.size-bytes | 在开启日志攒批发送模式时生效,表示一批数据最大的攒批大小(单位:byte) | Long
| 选填 | 16*1024*1024 |
#### iotdb-thrift-ssl-sink
@@ -523,6 +524,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | 目标端 IoTDB 任意多个 DataNode 节点的数据服务端口的
url(请注意同步任务不支持向自身服务进行转发) | String.
例:'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | 必填 | -
|
| batch.enable | 是否开启日志攒批发送模式,用于提高传输吞吐,降低 IOPS | Boolean:
true, false | 选填 | true |
| batch.max-delay-seconds | 在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:s) | Integer
| 选填 | 1 |
+| batch.max-delay-ms |
在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:ms)(V1.3.6及以后的V1.x版本支持) | Integer
| 选填 | 1
|
| batch.size-bytes | 在开启日志攒批发送模式时生效,表示一批数据最大的攒批大小(单位:byte) | Long
| 选填 | 16*1024*1024 |
| ssl.trust-store-path | 连接目标端 DataNode 所需的 trust store 证书路径 |
String.Example: '127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669',
'127.0.0.1:6667' | 必填 | - |
| ssl.trust-store-pwd | 连接目标端 DataNode 所需的 trust store 证书密码 |
Integer | 必填 | -
|
diff --git a/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
b/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
index c4e7dc84..ffaa79dc 100644
--- a/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
@@ -587,19 +587,20 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
> - **batch**:该模式下,任务将对数据进行批量(按底层数据文件)处理、发送,其特点是低时效、高吞吐
-## sink **参数**
+### sink **参数**
> 在 1.3.3 及以上的版本中,只包含sink的情况下,不再需要额外增加with sink 前缀
#### iotdb-thrift-sink
-| key | value
| value 取值范围 | 是否必填 |
默认取值 |
-| ----------------------- |
------------------------------------------------------------ |
------------------------------------------------------------ | -------- |
------------ |
-| sink | iotdb-thrift-sink 或 iotdb-thrift-async-sink
| String: iotdb-thrift-sink 或 iotdb-thrift-async-sink | 必填
| - |
-| node-urls | 目标端 IoTDB 任意多个 DataNode 节点的数据服务端口的
url(请注意同步任务不支持向自身服务进行转发) | String.
例:'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | 必填 | -
|
-| batch.enable | 是否开启日志攒批发送模式,用于提高传输吞吐,降低 IOPS | Boolean:
true, false | 选填 | true |
-| batch.max-delay-seconds | 在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:s) | Integer
| 选填 | 1 |
-| batch.size-bytes | 在开启日志攒批发送模式时生效,表示一批数据最大的攒批大小(单位:byte) | Long
| 选填 | 16*1024*1024 |
+| key | value
| value 取值范围
| 是否必填 | 默认取值 |
+|-------------------------|--------------------------------------------------------------|----------------------------------------------------------------------------|
-------- |--------------|
+| sink | iotdb-thrift-sink 或 iotdb-thrift-async-sink
| String: iotdb-thrift-sink 或 iotdb-thrift-async-sink
| 必填 | - |
+| node-urls | 目标端 IoTDB 任意多个 DataNode 节点的数据服务端口的
url(请注意同步任务不支持向自身服务进行转发) | String.
例:'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | 必填 | -
|
+| batch.enable | 是否开启日志攒批发送模式,用于提高传输吞吐,降低 IOPS
| Boolean: true, false
| 选填 | true |
+| batch.max-delay-seconds | 在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:s)
| Integer
| 选填 | 1 |
+| batch.max-delay-ms |
在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:ms)(V1.3.6及以后的V1.x版本支持) | Integer
| 选填 | 1
|
+| batch.size-bytes | 在开启日志攒批发送模式时生效,表示一批数据最大的攒批大小(单位:byte)
| Long
| 选填 | 16*1024*1024 |
#### iotdb-air-gap-sink
@@ -617,6 +618,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | 目标端 IoTDB 任意多个 DataNode 节点的数据服务端口的
url(请注意同步任务不支持向自身服务进行转发) | String.
例:'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | 必填 | -
|
| batch.enable | 是否开启日志攒批发送模式,用于提高传输吞吐,降低 IOPS | Boolean:
true, false | 选填 | true |
| batch.max-delay-seconds | 在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:s) | Integer
| 选填 | 1 |
+| batch.max-delay-ms |
在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:ms)(V1.3.6及以后的V1.x版本支持) | Integer
| 选填 | 1
|
| batch.size-bytes | 在开启日志攒批发送模式时生效,表示一批数据最大的攒批大小(单位:byte) | Long
| 选填 | 16*1024*1024 |
| ssl.trust-store-path | 连接目标端 DataNode 所需的 trust store 证书路径 |
String.Example: '127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669',
'127.0.0.1:6667' | 必填 | - |
| ssl.trust-store-pwd | 连接目标端 DataNode 所需的 trust store 证书密码 |
Integer | 必填 | -
|
diff --git a/src/zh/UserGuide/dev-1.3/User-Manual/Data-Sync_apache.md
b/src/zh/UserGuide/dev-1.3/User-Manual/Data-Sync_apache.md
index dfb8cdae..cb9b315d 100644
--- a/src/zh/UserGuide/dev-1.3/User-Manual/Data-Sync_apache.md
+++ b/src/zh/UserGuide/dev-1.3/User-Manual/Data-Sync_apache.md
@@ -513,6 +513,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | 目标端 IoTDB 任意多个 DataNode 节点的数据服务端口的
url(请注意同步任务不支持向自身服务进行转发) | String.
例:'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | 必填 | -
|
| batch.enable | 是否开启日志攒批发送模式,用于提高传输吞吐,降低 IOPS | Boolean:
true, false | 选填 | true |
| batch.max-delay-seconds | 在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:s) | Integer
| 选填 | 1 |
+| batch.max-delay-ms |
在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:ms)(V1.3.6及以后的V1.x版本支持) | Integer
| 选填 | 1
|
| batch.size-bytes | 在开启日志攒批发送模式时生效,表示一批数据最大的攒批大小(单位:byte) | Long
| 选填 | 16*1024*1024 |
#### iotdb-thrift-ssl-sink
@@ -523,6 +524,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | 目标端 IoTDB 任意多个 DataNode 节点的数据服务端口的
url(请注意同步任务不支持向自身服务进行转发) | String.
例:'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | 必填 | -
|
| batch.enable | 是否开启日志攒批发送模式,用于提高传输吞吐,降低 IOPS | Boolean:
true, false | 选填 | true |
| batch.max-delay-seconds | 在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:s) | Integer
| 选填 | 1 |
+| batch.max-delay-ms |
在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:ms)(V1.3.6及以后的V1.x版本支持) | Integer
| 选填 | 1
|
| batch.size-bytes | 在开启日志攒批发送模式时生效,表示一批数据最大的攒批大小(单位:byte) | Long
| 选填 | 16*1024*1024 |
| ssl.trust-store-path | 连接目标端 DataNode 所需的 trust store 证书路径 |
String.Example: '127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669',
'127.0.0.1:6667' | 必填 | - |
| ssl.trust-store-pwd | 连接目标端 DataNode 所需的 trust store 证书密码 |
Integer | 必填 | -
|
diff --git a/src/zh/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
b/src/zh/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
index eb918581..8a74c427 100644
--- a/src/zh/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
@@ -588,7 +588,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
> - **batch**:该模式下,任务将对数据进行批量(按底层数据文件)处理、发送,其特点是低时效、高吞吐
-## sink **参数**
+### sink **参数**
> 在 1.3.3 及以上的版本中,只包含sink的情况下,不再需要额外增加with sink 前缀
@@ -600,6 +600,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | 目标端 IoTDB 任意多个 DataNode 节点的数据服务端口的
url(请注意同步任务不支持向自身服务进行转发) | String.
例:'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | 必填 | -
|
| batch.enable | 是否开启日志攒批发送模式,用于提高传输吞吐,降低 IOPS | Boolean:
true, false | 选填 | true |
| batch.max-delay-seconds | 在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:s) | Integer
| 选填 | 1 |
+| batch.max-delay-ms |
在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:ms)(V1.3.6及以后的V1.x版本支持) | Integer
| 选填 | 1
|
| batch.size-bytes | 在开启日志攒批发送模式时生效,表示一批数据最大的攒批大小(单位:byte) | Long
| 选填 | 16*1024*1024 |
#### iotdb-air-gap-sink
@@ -618,6 +619,7 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
| node-urls | 目标端 IoTDB 任意多个 DataNode 节点的数据服务端口的
url(请注意同步任务不支持向自身服务进行转发) | String.
例:'127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | 必填 | -
|
| batch.enable | 是否开启日志攒批发送模式,用于提高传输吞吐,降低 IOPS | Boolean:
true, false | 选填 | true |
| batch.max-delay-seconds | 在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:s) | Integer
| 选填 | 1 |
+| batch.max-delay-ms |
在开启日志攒批发送模式时生效,表示一批数据在发送前的最长等待时间(单位:ms)(V1.3.6及以后的V1.x版本支持) | Integer
| 选填 | 1
|
| batch.size-bytes | 在开启日志攒批发送模式时生效,表示一批数据最大的攒批大小(单位:byte) | Long
| 选填 | 16*1024*1024 |
| ssl.trust-store-path | 连接目标端 DataNode 所需的 trust store 证书路径 |
String.Example: '127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669',
'127.0.0.1:6667' | 必填 | - |
| ssl.trust-store-pwd | 连接目标端 DataNode 所需的 trust store 证书密码 |
Integer | 必填 | -
|