Data subscription and synchronization support create if not exists an… (#420)

* Data subscription and synchronization support create if not exists and drop if exists interfaces

* The pipe plugin supports the create if not exists and drop if exists interfaces

Author: W1y1r

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

@@ -103,7 +103,7 @@ Use the `CREATE PIPE` statement to create a data synchronization task. The `Pipe
 The SQL example is as follows:
 
 ```SQL
-CREATE PIPE <PipeId> -- PipeId is the name that uniquely identifies the task.
+CREATE PIPE [IF NOT EXISTS] <PipeId> -- PipeId is the name that uniquely identifies the task. 
 -- Data extraction plugin, optional plugin
 WITH SOURCE (
   [<parameter> = <value>,],
@@ -118,6 +118,8 @@ WITH SINK (
 )
 ```
 
+**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified Pipe does not exist, preventing errors caused by attempting to create an existing Pipe.
+
 ### Start Task
 
 After creation, the task will not be processed immediately and needs to be started. Use the `START PIPE` statement to start the task and begin processing data: 
@@ -139,8 +141,9 @@ STOP PIPE <PipeId>
 Deletes the specified task:
 
 ```SQL
-DROP PIPE <PipeId>
+DROP PIPE [IF EXISTS] <PipeId>
 ```
+**IF EXISTS semantics**: Used in deletion operations to ensure that when a specified Pipe exists, the delete command is executed to prevent errors caused by attempting to delete non-existent Pipes.
 
 Deleting a task does not require stopping the synchronization task first.
 

src/UserGuide/Master/User-Manual/Data-Sync_timecho.md

@@ -105,7 +105,7 @@ Use the `CREATE PIPE` statement to create a data synchronization task. The `Pipe
 The SQL example is as follows:
 
 ```SQL
-CREATE PIPE <PipeId> -- PipeId is the name that uniquely identifies the task.
+CREATE PIPE [IF NOT EXISTS] <PipeId> -- PipeId is the name that uniquely identifies the task.
 -- Data extraction plugin, optional plugin
 WITH SOURCE (
   [<parameter> = <value>,],
@@ -120,6 +120,8 @@ WITH SINK (
 )
 ```
 
+**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified Pipe does not exist, preventing errors caused by attempting to create an existing Pipe.
+
 ### Start Task
 
 After creation, the task will not be processed immediately and needs to be started. Use the `START PIPE` statement to start the task and begin processing data: 
@@ -141,8 +143,9 @@ STOP PIPE <PipeId>
 Deletes the specified task:
 
 ```SQL
-DROP PIPE <PipeId>
+DROP PIPE [IF EXISTS] <PipeId>
 ```
+**IF EXISTS semantics**: Used in deletion operations to ensure that when a specified Pipe exists, the delete command is executed to prevent errors caused by attempting to delete non-existent Pipes.
 
 Deleting a task does not require stopping the synchronization task first.
 

src/UserGuide/Master/User-Manual/Data-subscription.md

@@ -46,12 +46,14 @@ IoTDB supports the creation, deletion, and viewing of Topics through SQL stateme
 The SQL statement is as follows:
 
 ```SQL
-    CREATE TOPIC <topicName> 
+    CREATE TOPIC [IF NOT EXISTS] <topicName> 
     WITH (
     [<parameter> = <value>,],
     );
 ```
 
+**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified topic does not exist, preventing errors caused by attempting to create an existing topic.
+
 Detailed explanation of each parameter is as follows:
 
 | Key	                                          | Required or Optional with Default		                 | Description                                                     |
@@ -74,7 +76,7 @@ Examples are as follows:
 CREATE TOPIC root_all;
 
 -- Custom subscription
-CREATE TOPIC db_timerange
+CREATE TOPIC IF NOT EXISTS db_timerange
 WITH (
   'path' = 'root.db.**',
   'start-time' = '2023-01-01',
@@ -87,8 +89,9 @@ WITH (
 A Topic can only be deleted if it is not subscribed to. When a Topic is deleted, its related consumption progress will be cleared.
 
 ```SQL
-DROP TOPIC <topicName>;
+DROP TOPIC [IF EXISTS] <topicName>;
 ```
+**IF EXISTS semantics**: Used in deletion operations to ensure that the delete command is executed when a specified topic exists, preventing errors caused by attempting to delete non-existent topics.
 
 #### 3.1.3 View Topic
 
@@ -142,7 +145,7 @@ The `SubscriptionSession` class in the IoTDB subscription client provides interf
 #### 4.1.1 Create Topic
 
 ```Java
-Topic createTopic(String topicName, Properties properties) throws Exception;
+ void createTopicIfNotExists(String topicName, Properties properties) throws Exception;
 ```
 
 Example:
@@ -159,7 +162,7 @@ try (final SubscriptionSession session = new SubscriptionSession(host, port)) {
 #### 4.1.2 Delete Topic
 
 ```Java
-void dropTopic(String topicName) throws Exception;
+void dropTopicIfExists(String topicName) throws Exception;
 ```
 
 #### 4.1.3 View Topic

src/UserGuide/Master/User-Manual/Streaming_apache.md

@@ -445,15 +445,17 @@ In IoTDB, to dynamically load a user-defined plugin into the system, you first n
 The syntax of the loading plugin management statement is as follows:
 
 ```sql
-CREATE PIPEPLUGIN <alias>
+CREATE PIPEPLUGIN [IF NOT EXISTS] <alias>
 AS <Full class name>
 USING <URL of jar file>
 ```
 
+**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified Pipe Plugin does not exist, preventing errors caused by attempting to create an existing Pipe Plugin.
+
 For example, if a user implements a data processing plugin with the fully qualified class name "edu.tsinghua.iotdb.pipe.ExampleProcessor" and packages it into a jar file, which is stored at "https://example.com:8080/iotdb/pipe-plugin.jar", and the user wants to use this plugin in the stream processing engine, marking the plugin as "example". The creation statement for this data processing plugin is as follows:
 
 ```sql
-CREATE PIPEPLUGIN example
+CREATE PIPEPLUGIN IF NOT EXISTS example
 AS 'edu.tsinghua.iotdb.pipe.ExampleProcessor'
 USING URI '<https://example.com:8080/iotdb/pipe-plugin.jar>'
 ```
@@ -462,9 +464,11 @@ USING URI '<https://example.com:8080/iotdb/pipe-plugin.jar>'
 
 When user no longer wants to use a plugin and needs to uninstall the plugin from the system, you can use the Remove plugin statement as shown below.
 ```sql
-DROP PIPEPLUGIN <alias>
+DROP PIPEPLUGIN [IF EXISTS] <alias>
 ```
 
+**IF EXISTS semantics**: Used in deletion operations to ensure that when a specified Pipe Plugin exists, the delete command is executed to prevent errors caused by attempting to delete a non-existent Pipe Plugin.
+
 ### Show Plugin Statement
 
 User can also view the plugin in the system on need. The statement to view plugin is as follows.

src/UserGuide/Master/User-Manual/Streaming_timecho.md

@@ -451,10 +451,11 @@ Then the plugin class needs to be compiled and packaged into a jar executable fi
 The syntax of the management statement for loading the plugin is shown in the figure.
 
 ```sql
-CREATE PIPEPLUGIN <alias>
+CREATE PIPEPLUGIN [IF NOT EXISTS] <alias>
 AS <full class name>
 USING <URI of JAR package>
 ```
+**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified Pipe Plugin does not exist, preventing errors caused by attempting to create an existing Pipe Plugin.
 
 Example: If you implement a data processing plugin named edu.tsinghua.iotdb.pipe.ExampleProcessor, and the packaged jar package is pipe-plugin.jar, you want to use this plugin in the stream processing engine, and mark the plugin as example. There are two ways to use the plugin package, one is to upload to the URI server, and the other is to upload to the local directory of the cluster.
 
@@ -465,7 +466,7 @@ Preparation: To register in this way, you need to upload the JAR package to the
 SQL：
 
 ```sql
-CREATE PIPEPLUGIN example 
+CREATE PIPEPLUGIN IF NOT EXISTS example 
 AS 'edu.tsinghua.iotdb.pipe.ExampleProcessor' 
 USING URI '<https://example.com:8080/iotdb/pipe-plugin.jar>'
 ```
@@ -477,7 +478,7 @@ Preparation: To register in this way, you need to place the JAR package in any p
 SQL：
 
 ```sql
-CREATE PIPEPLUGIN example 
+CREATE PIPEPLUGIN IF NOT EXISTS example 
 AS 'edu.tsinghua.iotdb.pipe.ExampleProcessor' 
 USING URI '<file:/IoTDB installation path/iotdb-1.x.x-bin/ext/pipe/pipe-plugin.jar>'
 ```
@@ -487,9 +488,11 @@ USING URI '<file:/IoTDB installation path/iotdb-1.x.x-bin/ext/pipe/pipe-plugin.j
 When the user no longer wants to use a plugin and needs to uninstall the plugin from the system, he can use the delete plugin statement as shown in the figure.
 
 ```sql
-DROP PIPEPLUGIN <alias>
+DROP PIPEPLUGIN [IF EXISTS] <alias>
 ```
 
+**IF EXISTS semantics**: Used in deletion operations to ensure that when a specified Pipe Plugin exists, the delete command is executed to prevent errors caused by attempting to delete a non-existent Pipe Plugin.
+
 ### View plugin statements
 
 Users can also view plugins in the system on demand. View the statement of the plugin as shown in the figure.

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

@@ -103,7 +103,7 @@ Use the `CREATE PIPE` statement to create a data synchronization task. The `Pipe
 The SQL example is as follows:
 
 ```SQL
-CREATE PIPE <PipeId> -- PipeId is the name that uniquely identifies the task.
+CREATE PIPE [IF NOT EXISTS] <PipeId> -- PipeId is the name that uniquely identifies the task. 
 -- Data extraction plugin, optional plugin
 WITH SOURCE (
   [<parameter> = <value>,],
@@ -118,6 +118,8 @@ WITH SINK (
 )
 ```
 
+**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified Pipe does not exist, preventing errors caused by attempting to create an existing Pipe.
+
 ### Start Task
 
 After creation, the task will not be processed immediately and needs to be started. Use the `START PIPE` statement to start the task and begin processing data: 
@@ -139,8 +141,9 @@ STOP PIPE <PipeId>
 Deletes the specified task:
 
 ```SQL
-DROP PIPE <PipeId>
+DROP PIPE [IF EXISTS] <PipeId>
 ```
+**IF EXISTS semantics**: Used in deletion operations to ensure that when a specified Pipe exists, the delete command is executed to prevent errors caused by attempting to delete non-existent Pipes.
 
 Deleting a task does not require stopping the synchronization task first.
 

src/UserGuide/latest/User-Manual/Data-Sync_timecho.md

@@ -105,7 +105,7 @@ Use the `CREATE PIPE` statement to create a data synchronization task. The `Pipe
 The SQL example is as follows:
 
 ```SQL
-CREATE PIPE <PipeId> -- PipeId is the name that uniquely identifies the task.
+CREATE PIPE [IF NOT EXISTS] <PipeId> -- PipeId is the name that uniquely identifies the task.
 -- Data extraction plugin, optional plugin
 WITH SOURCE (
   [<parameter> = <value>,],
@@ -120,6 +120,8 @@ WITH SINK (
 )
 ```
 
+**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified Pipe does not exist, preventing errors caused by attempting to create an existing Pipe.
+
 ### Start Task
 
 After creation, the task will not be processed immediately and needs to be started. Use the `START PIPE` statement to start the task and begin processing data: 
@@ -141,8 +143,9 @@ STOP PIPE <PipeId>
 Deletes the specified task:
 
 ```SQL
-DROP PIPE <PipeId>
+DROP PIPE [IF EXISTS] <PipeId>
 ```
+**IF EXISTS semantics**: Used in deletion operations to ensure that when a specified Pipe exists, the delete command is executed to prevent errors caused by attempting to delete non-existent Pipes.
 
 Deleting a task does not require stopping the synchronization task first.
 

src/UserGuide/latest/User-Manual/Data-subscription.md

@@ -46,12 +46,14 @@ IoTDB supports the creation, deletion, and viewing of Topics through SQL stateme
 The SQL statement is as follows:
 
 ```SQL
-    CREATE TOPIC <topicName> 
+    CREATE TOPIC [IF NOT EXISTS] <topicName> 
     WITH (
     [<parameter> = <value>,],
     );
 ```
 
+**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified topic does not exist, preventing errors caused by attempting to create an existing topic.
+
 Detailed explanation of each parameter is as follows:
 
 | Key	                                          | Required or Optional with Default		                 | Description                                                     |
@@ -74,7 +76,7 @@ Examples are as follows:
 CREATE TOPIC root_all;
 
 -- Custom subscription
-CREATE TOPIC db_timerange
+CREATE TOPIC IF NOT EXISTS db_timerange
 WITH (
   'path' = 'root.db.**',
   'start-time' = '2023-01-01',
@@ -87,8 +89,9 @@ WITH (
 A Topic can only be deleted if it is not subscribed to. When a Topic is deleted, its related consumption progress will be cleared.
 
 ```SQL
-DROP TOPIC <topicName>;
+DROP TOPIC [IF EXISTS] <topicName>;
 ```
+**IF EXISTS semantics**: Used in deletion operations to ensure that the delete command is executed when a specified topic exists, preventing errors caused by attempting to delete non-existent topics.
 
 #### 3.1.3 View Topic
 
@@ -142,7 +145,7 @@ The `SubscriptionSession` class in the IoTDB subscription client provides interf
 #### 4.1.1 Create Topic
 
 ```Java
-Topic createTopic(String topicName, Properties properties) throws Exception;
+ void createTopicIfNotExists(String topicName, Properties properties) throws Exception;
 ```
 
 Example:
@@ -159,7 +162,7 @@ try (final SubscriptionSession session = new SubscriptionSession(host, port)) {
 #### 4.1.2 Delete Topic
 
 ```Java
-void dropTopic(String topicName) throws Exception;
+void dropTopicIfExists(String topicName) throws Exception;
 ```
 
 #### 4.1.3 View Topic

src/UserGuide/latest/User-Manual/Streaming_apache.md

@@ -445,15 +445,17 @@ In IoTDB, to dynamically load a user-defined plugin into the system, you first n
 The syntax of the loading plugin management statement is as follows:
 
 ```sql
-CREATE PIPEPLUGIN <alias>
+CREATE PIPEPLUGIN [IF NOT EXISTS] <alias>
 AS <Full class name>
 USING <URL of jar file>
 ```
 
+**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified Pipe Plugin does not exist, preventing errors caused by attempting to create an existing Pipe Plugin.
+
 For example, if a user implements a data processing plugin with the fully qualified class name "edu.tsinghua.iotdb.pipe.ExampleProcessor" and packages it into a jar file, which is stored at "https://example.com:8080/iotdb/pipe-plugin.jar", and the user wants to use this plugin in the stream processing engine, marking the plugin as "example". The creation statement for this data processing plugin is as follows:
 
 ```sql
-CREATE PIPEPLUGIN example
+CREATE PIPEPLUGIN IF NOT EXISTS example
 AS 'edu.tsinghua.iotdb.pipe.ExampleProcessor'
 USING URI '<https://example.com:8080/iotdb/pipe-plugin.jar>'
 ```
@@ -462,9 +464,11 @@ USING URI '<https://example.com:8080/iotdb/pipe-plugin.jar>'
 
 When user no longer wants to use a plugin and needs to uninstall the plugin from the system, you can use the Remove plugin statement as shown below.
 ```sql
-DROP PIPEPLUGIN <alias>
+DROP PIPEPLUGIN [IF EXISTS] <alias>
 ```
 
+**IF EXISTS semantics**: Used in deletion operations to ensure that when a specified Pipe Plugin exists, the delete command is executed to prevent errors caused by attempting to delete a non-existent Pipe Plugin.
+
 ### Show Plugin Statement
 
 User can also view the plugin in the system on need. The statement to view plugin is as follows.

src/UserGuide/latest/User-Manual/Streaming_timecho.md

@@ -451,10 +451,11 @@ Then the plugin class needs to be compiled and packaged into a jar executable fi
 The syntax of the management statement for loading the plugin is shown in the figure.
 
 ```sql
-CREATE PIPEPLUGIN <alias>
+CREATE PIPEPLUGIN [IF NOT EXISTS] <alias>
 AS <full class name>
 USING <URI of JAR package>
 ```
+**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified Pipe Plugin does not exist, preventing errors caused by attempting to create an existing Pipe Plugin.
 
 Example: If you implement a data processing plugin named edu.tsinghua.iotdb.pipe.ExampleProcessor, and the packaged jar package is pipe-plugin.jar, you want to use this plugin in the stream processing engine, and mark the plugin as example. There are two ways to use the plugin package, one is to upload to the URI server, and the other is to upload to the local directory of the cluster.
 
@@ -465,7 +466,7 @@ Preparation: To register in this way, you need to upload the JAR package to the
 SQL：
 
 ```sql
-CREATE PIPEPLUGIN example 
+CREATE PIPEPLUGIN IF NOT EXISTS example 
 AS 'edu.tsinghua.iotdb.pipe.ExampleProcessor' 
 USING URI '<https://example.com:8080/iotdb/pipe-plugin.jar>'
 ```
@@ -477,7 +478,7 @@ Preparation: To register in this way, you need to place the JAR package in any p
 SQL：
 
 ```sql
-CREATE PIPEPLUGIN example 
+CREATE PIPEPLUGIN IF NOT EXISTS example 
 AS 'edu.tsinghua.iotdb.pipe.ExampleProcessor' 
 USING URI '<file:/IoTDB installation path/iotdb-1.x.x-bin/ext/pipe/pipe-plugin.jar>'
 ```
@@ -487,9 +488,11 @@ USING URI '<file:/IoTDB installation path/iotdb-1.x.x-bin/ext/pipe/pipe-plugin.j
 When the user no longer wants to use a plugin and needs to uninstall the plugin from the system, he can use the delete plugin statement as shown in the figure.
 
 ```sql
-DROP PIPEPLUGIN <alias>
+DROP PIPEPLUGIN [IF EXISTS] <alias>
 ```
 
+**IF EXISTS semantics**: Used in deletion operations to ensure that when a specified Pipe Plugin exists, the delete command is executed to prevent errors caused by attempting to delete a non-existent Pipe Plugin.
+
 ### View plugin statements
 
 Users can also view plugins in the system on demand. View the statement of the plugin as shown in the figure.