apache · leto-b · May 28, 2026
diff --git a/src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md b/src/UserGuide/Master/Table/User-Manual/Data-Sync_apache.md
@@ -214,7 +214,32 @@ IoTDB> show pipe alldatapipe_realtime
 ```
 
 
-### 2.6 Synchronization Plugins
+### 2.6 Modify a Task
+
+The `ALTER PIPE` statement dynamically updates an existing PIPE and supports modifying or replacing the configuration of source, processor, and sink.
+
+```SQL
+ALTER PIPE [IF EXISTS] <PipeId>
+    MODIFY/REPLACE SOURCE(...)
+    MODIFY/REPLACE PROCESSOR(...)
+    MODIFY/REPLACE SINK(...)
+```
+
+Description:
+
+* Executing this operation does not change the running state of the PIPE. It is equivalent to keeping the processing progress of the original PipeId and creating a new PIPE at the original progress position.
+* The modify/replace parameters for source/processor/sink are all optional. If no modification parameter is specified, it is equivalent to deleting the current PIPE and recreating it with the original configuration and progress.
+* For a plugin specified with modify, the plugin's other parameters are retained, and only the given parameters are replaced or added.
+* For a plugin specified with replace, all parameters of the plugin are replaced directly.
+* When the [IF EXISTS] keyword is used, execution succeeds even if no Pipe with the same name exists, but no operation is actually performed.
+
+Example:
+
+```SQL
+ALTER PIPE A2B REPLACE SINK ('sink'='iotdb-thrift-sink', 'node-urls' = '127.0.0.1:6668');
+```
+
+### 2.7 Synchronization Plugins
 
 To make the architecture more flexible and adaptable to different synchronization scenarios, IoTDB supports plugin assembly in the synchronization task framework. The system provides some common pre-installed plugins, and you can also customize `processor` and `sink` plugins and load them into the IoTDB system.
 
@@ -564,4 +589,4 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
 | load-tsfile-strategy        | When synchronizing file data, whether the receiver waits for the local load tsfile operation to complete before responding to the sender:<br>sync: Wait for the local load tsfile operation to complete before returning the response.<br>async: Do not wait for the local load tsfile operation to complete; return the response immediately.                                                                                                                                                                                                  | String: sync / async                                                             | No       | sync           |
 | ssl.trust-store-path        | Path to the trust store certificate for SSL connection.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | String.Example: '127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | Yes      | -             |
 | ssl.trust-store-pwd         | Password for the trust store certificate.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Integer                                                                          | Yes      | -             |
-| format                      | The payload formats for data transmission include the following options:<br>  - hybrid: The format depends on what is passed from the processor (either tsfile or tablet), and the sink performs no conversion.<br> - tsfile: Data is forcibly converted to tsfile format before transmission. This is suitable for scenarios like data file backup.<br> - tablet: Data is forcibly converted to tsfile format before transmission. This is useful for data synchronization when the sender and receiver have incompatible data types (to minimize errors). | String: hybrid / tsfile / tablet                                                 | No       | hybrid |
+| format                      | The payload formats for data transmission include the following options:<br>  - hybrid: The format depends on what is passed from the processor (either tsfile or tablet), and the sink performs no conversion.<br> - tsfile: Data is forcibly converted to tsfile format before transmission. This is suitable for scenarios like data file backup.<br> - tablet: Data is forcibly converted to tsfile format before transmission. This is useful for data synchronization when the sender and receiver have incompatible data types (to minimize errors). | String: hybrid / tsfile / tablet                                                 | No       | hybrid |
diff --git a/src/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md b/src/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
@@ -213,7 +213,32 @@ IoTDB> show pipe alldatapipe_realtime
 ```
 
 
-### 2.6 Synchronization Plugins
+### 2.6 Modify a Task
+
+The `ALTER PIPE` statement dynamically updates an existing PIPE and supports modifying or replacing the configuration of source, processor, and sink.
+
+```SQL
+ALTER PIPE [IF EXISTS] <PipeId>
+    MODIFY/REPLACE SOURCE(...)
+    MODIFY/REPLACE PROCESSOR(...)
+    MODIFY/REPLACE SINK(...)
+```
+
+Description:
+
+* Executing this operation does not change the running state of the PIPE. It is equivalent to keeping the processing progress of the original PipeId and creating a new PIPE at the original progress position.
+* The modify/replace parameters for source/processor/sink are all optional. If no modification parameter is specified, it is equivalent to deleting the current PIPE and recreating it with the original configuration and progress.
+* For a plugin specified with modify, the plugin's other parameters are retained, and only the given parameters are replaced or added.
+* For a plugin specified with replace, all parameters of the plugin are replaced directly.
+* When the [IF EXISTS] keyword is used, execution succeeds even if no Pipe with the same name exists, but no operation is actually performed.
+
+Example:
+
+```SQL
+ALTER PIPE A2B REPLACE SINK ('sink'='iotdb-thrift-sink', 'node-urls' = '127.0.0.1:6668');
+```
+
+### 2.7 Synchronization Plugins
 
 To make the architecture more flexible and adaptable to different synchronization scenarios, IoTDB supports plugin assembly in the synchronization task framework. The system provides some common pre-installed plugins, and you can also customize `processor` and `sink` plugins and load them into the IoTDB system.
 

diff --git a/src/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md b/src/UserGuide/Master/Tree/User-Manual/Data-Sync_apache.md
@@ -234,7 +234,32 @@ IoTDB> show pipe alldatapipe_realtime
 +--------------------+-----------------------+-------+---------------------------------------------------------------------------+-------------+--------------------------+----------------+-------------------+-------------------------+
 ```
 
-### 2.6 Synchronization Plugins
+### 2.6 Modify Task
+
+The `ALTER PIPE` statement dynamically updates an existing PIPE and supports modifying or replacing the configuration of source, processor, and sink.
+
+```SQL
+ALTER PIPE [IF EXISTS] <PipeId>
+    MODIFY/REPLACE SOURCE(...)
+    MODIFY/REPLACE PROCESSOR(...)
+    MODIFY/REPLACE SINK(...)
+```
+
+Description:
+
+* Executing this operation does not change the running state of the PIPE. It is equivalent to keeping the processing progress of the original PipeId and creating a new PIPE at the original progress position.
+* The modify/replace parameters for source/processor/sink are all optional. If no modification parameter is specified, it is equivalent to deleting the current PIPE and recreating it with the original configuration and progress.
+* For a plugin specified with modify, the plugin's other parameters are retained, and only the given parameters are replaced or added.
+* For a plugin specified with replace, all parameters of the plugin are replaced directly.
+* When the [IF EXISTS] keyword is used, execution succeeds even if no Pipe with the same name exists, but no operation is actually performed.
+
+Example:
+
+```SQL
+ALTER PIPE A2B REPLACE SINK ('sink'='iotdb-thrift-sink', 'node-urls' = '127.0.0.1:6668');
+```
+
+### 2.7 Synchronization Plugins
 
 To make the overall architecture more flexible to match different synchronization scenario requirements, we support plugin assembly within the synchronization task framework. The system comes with some pre-installed common plugins that you can use directly. At the same time, you can also customize processor plugins and Sink plugins, and load them into the IoTDB system for use. You can view the plugins in the system (including custom and built-in plugins) with the following statement:
 

diff --git a/src/UserGuide/Master/Tree/User-Manual/Data-Sync_timecho.md b/src/UserGuide/Master/Tree/User-Manual/Data-Sync_timecho.md
@@ -236,7 +236,32 @@ IoTDB> show pipe alldatapipe_realtime
 ```
 
 
-### 2.6 Synchronization Plugins
+### 2.6 Modify Task
+
+The `ALTER PIPE` statement dynamically updates an existing PIPE and supports modifying or replacing the configuration of source, processor, and sink.
+
+```SQL
+ALTER PIPE [IF EXISTS] <PipeId>
+    MODIFY/REPLACE SOURCE(...)
+    MODIFY/REPLACE PROCESSOR(...)
+    MODIFY/REPLACE SINK(...)
+```
+
+Description:
+
+* Executing this operation does not change the running state of the PIPE. It is equivalent to keeping the processing progress of the original PipeId and creating a new PIPE at the original progress position.
+* The modify/replace parameters for source/processor/sink are all optional. If no modification parameter is specified, it is equivalent to deleting the current PIPE and recreating it with the original configuration and progress.
+* For a plugin specified with modify, the plugin's other parameters are retained, and only the given parameters are replaced or added.
+* For a plugin specified with replace, all parameters of the plugin are replaced directly.
+* When the [IF EXISTS] keyword is used, execution succeeds even if no Pipe with the same name exists, but no operation is actually performed.
+
+Example:
+
+```SQL
+ALTER PIPE A2B REPLACE SINK ('sink'='iotdb-thrift-sink', 'node-urls' = '127.0.0.1:6668');
+```
+
+### 2.7 Synchronization Plugins
 
 To make the overall architecture more flexible to match different synchronization scenario requirements, we support plugin assembly within the synchronization task framework. The system comes with some pre-installed common plugins that you can use directly. At the same time, you can also customize processor plugins and Sink plugins, and load them into the IoTDB system for use. You can view the plugins in the system (including custom and built-in plugins) with the following statement:
 

diff --git a/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md b/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md
@@ -214,7 +214,32 @@ IoTDB> show pipe alldatapipe_realtime
 ```
 
 
-### 2.6 Synchronization Plugins
+### 2.6 Modify a Task
+
+The `ALTER PIPE` statement dynamically updates an existing PIPE and supports modifying or replacing the configuration of source, processor, and sink.
+
+```SQL
+ALTER PIPE [IF EXISTS] <PipeId>
+    MODIFY/REPLACE SOURCE(...)
+    MODIFY/REPLACE PROCESSOR(...)
+    MODIFY/REPLACE SINK(...)
+```
+
+Description:
+
+* Executing this operation does not change the running state of the PIPE. It is equivalent to keeping the processing progress of the original PipeId and creating a new PIPE at the original progress position.
+* The modify/replace parameters for source/processor/sink are all optional. If no modification parameter is specified, it is equivalent to deleting the current PIPE and recreating it with the original configuration and progress.
+* For a plugin specified with modify, the plugin's other parameters are retained, and only the given parameters are replaced or added.
+* For a plugin specified with replace, all parameters of the plugin are replaced directly.
+* When the [IF EXISTS] keyword is used, execution succeeds even if no Pipe with the same name exists, but no operation is actually performed.
+
+Example:
+
+```SQL
+ALTER PIPE A2B REPLACE SINK ('sink'='iotdb-thrift-sink', 'node-urls' = '127.0.0.1:6668');
+```
+
+### 2.7 Synchronization Plugins
 
 To make the architecture more flexible and adaptable to different synchronization scenarios, IoTDB supports plugin assembly in the synchronization task framework. The system provides some common pre-installed plugins, and you can also customize `processor` and `sink` plugins and load them into the IoTDB system.
 
@@ -564,4 +589,4 @@ pipe_all_sinks_rate_limit_bytes_per_second=-1
 | load-tsfile-strategy        | When synchronizing file data, whether the receiver waits for the local load tsfile operation to complete before responding to the sender:<br>sync: Wait for the local load tsfile operation to complete before returning the response.<br>async: Do not wait for the local load tsfile operation to complete; return the response immediately.                                                                                                                                                                                                  | String: sync / async                                                             | No       | sync           |
 | ssl.trust-store-path        | Path to the trust store certificate for SSL connection.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | String.Example: '127.0.0.1:6667,127.0.0.1:6668,127.0.0.1:6669', '127.0.0.1:6667' | Yes      | -             |
 | ssl.trust-store-pwd         | Password for the trust store certificate.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Integer                                                                          | Yes      | -             |
-| format                      | The payload formats for data transmission include the following options:<br>  - hybrid: The format depends on what is passed from the processor (either tsfile or tablet), and the sink performs no conversion.<br> - tsfile: Data is forcibly converted to tsfile format before transmission. This is suitable for scenarios like data file backup.<br> - tablet: Data is forcibly converted to tsfile format before transmission. This is useful for data synchronization when the sender and receiver have incompatible data types (to minimize errors). | String: hybrid / tsfile / tablet                                                 | No       | hybrid |
+| format                      | The payload formats for data transmission include the following options:<br>  - hybrid: The format depends on what is passed from the processor (either tsfile or tablet), and the sink performs no conversion.<br> - tsfile: Data is forcibly converted to tsfile format before transmission. This is suitable for scenarios like data file backup.<br> - tablet: Data is forcibly converted to tsfile format before transmission. This is useful for data synchronization when the sender and receiver have incompatible data types (to minimize errors). | String: hybrid / tsfile / tablet                                                 | No       | hybrid |
diff --git a/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md b/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
@@ -213,7 +213,32 @@ IoTDB> show pipe alldatapipe_realtime
 ```
 
 
-### 2.6 Synchronization Plugins
+### 2.6 Modify a Task
+
+The `ALTER PIPE` statement dynamically updates an existing PIPE and supports modifying or replacing the configuration of source, processor, and sink.
+
+```SQL
+ALTER PIPE [IF EXISTS] <PipeId>
+    MODIFY/REPLACE SOURCE(...)
+    MODIFY/REPLACE PROCESSOR(...)
+    MODIFY/REPLACE SINK(...)
+```
+
+Description:
+
+* Executing this operation does not change the running state of the PIPE. It is equivalent to keeping the processing progress of the original PipeId and creating a new PIPE at the original progress position.
+* The modify/replace parameters for source/processor/sink are all optional. If no modification parameter is specified, it is equivalent to deleting the current PIPE and recreating it with the original configuration and progress.
+* For a plugin specified with modify, the plugin's other parameters are retained, and only the given parameters are replaced or added.
+* For a plugin specified with replace, all parameters of the plugin are replaced directly.
+* When the [IF EXISTS] keyword is used, execution succeeds even if no Pipe with the same name exists, but no operation is actually performed.
+
+Example:
+
+```SQL
+ALTER PIPE A2B REPLACE SINK ('sink'='iotdb-thrift-sink', 'node-urls' = '127.0.0.1:6668');
+```
+
+### 2.7 Synchronization Plugins
 
 To make the architecture more flexible and adaptable to different synchronization scenarios, IoTDB supports plugin assembly in the synchronization task framework. The system provides some common pre-installed plugins, and you can also customize `processor` and `sink` plugins and load them into the IoTDB system.
 

diff --git a/src/UserGuide/latest/User-Manual/Data-Sync_apache.md b/src/UserGuide/latest/User-Manual/Data-Sync_apache.md
@@ -234,7 +234,32 @@ IoTDB> show pipe alldatapipe_realtime
 +--------------------+-----------------------+-------+---------------------------------------------------------------------------+-------------+--------------------------+----------------+-------------------+-------------------------+
 ```
 
-### 2.6 Synchronization Plugins
+### 2.6 Modify Task
+
+The `ALTER PIPE` statement dynamically updates an existing PIPE and supports modifying or replacing the configuration of source, processor, and sink.
+
+```SQL
+ALTER PIPE [IF EXISTS] <PipeId>
+    MODIFY/REPLACE SOURCE(...)
+    MODIFY/REPLACE PROCESSOR(...)
+    MODIFY/REPLACE SINK(...)
+```
+
+Description:
+
+* Executing this operation does not change the running state of the PIPE. It is equivalent to keeping the processing progress of the original PipeId and creating a new PIPE at the original progress position.
+* The modify/replace parameters for source/processor/sink are all optional. If no modification parameter is specified, it is equivalent to deleting the current PIPE and recreating it with the original configuration and progress.
+* For a plugin specified with modify, the plugin's other parameters are retained, and only the given parameters are replaced or added.
+* For a plugin specified with replace, all parameters of the plugin are replaced directly.
+* When the [IF EXISTS] keyword is used, execution succeeds even if no Pipe with the same name exists, but no operation is actually performed.
+
+Example:
+
+```SQL
+ALTER PIPE A2B REPLACE SINK ('sink'='iotdb-thrift-sink', 'node-urls' = '127.0.0.1:6668');
+```
+
+### 2.7 Synchronization Plugins
 
 To make the overall architecture more flexible to match different synchronization scenario requirements, we support plugin assembly within the synchronization task framework. The system comes with some pre-installed common plugins that you can use directly. At the same time, you can also customize processor plugins and Sink plugins, and load them into the IoTDB system for use. You can view the plugins in the system (including custom and built-in plugins) with the following statement: