You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/UserGuide/Master/User-Manual/Data-Sync_apache.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,7 +103,7 @@ Use the `CREATE PIPE` statement to create a data synchronization task. The `Pipe
103
103
The SQL example is as follows:
104
104
105
105
```SQL
106
-
CREATE PIPE <PipeId>-- PipeId is the name that uniquely identifies the task.
106
+
CREATE PIPE [IF NOT EXISTS] <PipeId>-- PipeId is the name that uniquely identifies the task.
107
107
-- Data extraction plugin, optional plugin
108
108
WITH SOURCE (
109
109
[<parameter>=<value>,],
@@ -118,6 +118,8 @@ WITH SINK (
118
118
)
119
119
```
120
120
121
+
**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified object does not exist, preventing errors caused by attempting to create an existing object.
122
+
121
123
### Start Task
122
124
123
125
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>
139
141
Deletes the specified task:
140
142
141
143
```SQL
142
-
DROP PIPE <PipeId>
144
+
DROP PIPE [IF EXISTS] <PipeId>
143
145
```
146
+
**IF EXISTS semantics**: Used in deletion operations to ensure that the delete command is executed when the specified object exists, preventing errors caused by attempting to delete non-existent objects.
144
147
145
148
Deleting a task does not require stopping the synchronization task first.
Copy file name to clipboardExpand all lines: src/UserGuide/Master/User-Manual/Data-Sync_timecho.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ Use the `CREATE PIPE` statement to create a data synchronization task. The `Pipe
105
105
The SQL example is as follows:
106
106
107
107
```SQL
108
-
CREATE PIPE <PipeId>-- PipeId is the name that uniquely identifies the task.
108
+
CREATE PIPE [IF NOT EXISTS] <PipeId>-- PipeId is the name that uniquely identifies the task.
109
109
-- Data extraction plugin, optional plugin
110
110
WITH SOURCE (
111
111
[<parameter>=<value>,],
@@ -120,6 +120,8 @@ WITH SINK (
120
120
)
121
121
```
122
122
123
+
**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified object does not exist, preventing errors caused by attempting to create an existing object.
124
+
123
125
### Start Task
124
126
125
127
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>
141
143
Deletes the specified task:
142
144
143
145
```SQL
144
-
DROP PIPE <PipeId>
146
+
DROP PIPE [IF EXISTS] <PipeId>
145
147
```
148
+
**IF EXISTS semantics**: Used in deletion operations to ensure that the delete command is executed when the specified object exists, preventing errors caused by attempting to delete non-existent objects.
146
149
147
150
Deleting a task does not require stopping the synchronization task first.
Copy file name to clipboardExpand all lines: src/UserGuide/Master/User-Manual/Data-subscription.md
+8-5Lines changed: 8 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,12 +46,14 @@ IoTDB supports the creation, deletion, and viewing of Topics through SQL stateme
46
46
The SQL statement is as follows:
47
47
48
48
```SQL
49
-
CREATE TOPIC <topicName>
49
+
CREATE TOPIC [IF NOT EXISTS] <topicName>
50
50
WITH (
51
51
[<parameter>=<value>,],
52
52
);
53
53
```
54
54
55
+
**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified object does not exist, preventing errors caused by attempting to create an existing object.
56
+
55
57
Detailed explanation of each parameter is as follows:
56
58
57
59
| Key | Required or Optional with Default | Description |
@@ -74,7 +76,7 @@ Examples are as follows:
74
76
CREATE TOPIC root_all;
75
77
76
78
-- Custom subscription
77
-
CREATE TOPIC db_timerange
79
+
CREATE TOPIC IF NOT EXISTS db_timerange
78
80
WITH (
79
81
'path'='root.db.**',
80
82
'start-time'='2023-01-01',
@@ -87,8 +89,9 @@ WITH (
87
89
A Topic can only be deleted if it is not subscribed to. When a Topic is deleted, its related consumption progress will be cleared.
88
90
89
91
```SQL
90
-
DROP TOPIC <topicName>;
92
+
DROP TOPIC [IF EXISTS] <topicName>;
91
93
```
94
+
**IF EXISTS semantics**: Used in deletion operations to ensure that the delete command is executed when the specified object exists, preventing errors caused by attempting to delete non-existent objects.
92
95
93
96
#### 3.1.3 View Topic
94
97
@@ -142,7 +145,7 @@ The `SubscriptionSession` class in the IoTDB subscription client provides interf
Copy file name to clipboardExpand all lines: src/UserGuide/latest/User-Manual/Data-Sync_apache.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,7 +103,7 @@ Use the `CREATE PIPE` statement to create a data synchronization task. The `Pipe
103
103
The SQL example is as follows:
104
104
105
105
```SQL
106
-
CREATE PIPE <PipeId>-- PipeId is the name that uniquely identifies the task.
106
+
CREATE PIPE [IF NOT EXISTS] <PipeId>-- PipeId is the name that uniquely identifies the task.
107
107
-- Data extraction plugin, optional plugin
108
108
WITH SOURCE (
109
109
[<parameter>=<value>,],
@@ -118,6 +118,8 @@ WITH SINK (
118
118
)
119
119
```
120
120
121
+
**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified object does not exist, preventing errors caused by attempting to create an existing object.
122
+
121
123
### Start Task
122
124
123
125
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>
139
141
Deletes the specified task:
140
142
141
143
```SQL
142
-
DROP PIPE <PipeId>
144
+
DROP PIPE [IF EXISTS] <PipeId>
143
145
```
146
+
**IF EXISTS semantics**: Used in deletion operations to ensure that the delete command is executed when the specified object exists, preventing errors caused by attempting to delete non-existent objects.
144
147
145
148
Deleting a task does not require stopping the synchronization task first.
Copy file name to clipboardExpand all lines: src/UserGuide/latest/User-Manual/Data-Sync_timecho.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ Use the `CREATE PIPE` statement to create a data synchronization task. The `Pipe
105
105
The SQL example is as follows:
106
106
107
107
```SQL
108
-
CREATE PIPE <PipeId>-- PipeId is the name that uniquely identifies the task.
108
+
CREATE PIPE [IF NOT EXISTS] <PipeId>-- PipeId is the name that uniquely identifies the task.
109
109
-- Data extraction plugin, optional plugin
110
110
WITH SOURCE (
111
111
[<parameter>=<value>,],
@@ -120,6 +120,8 @@ WITH SINK (
120
120
)
121
121
```
122
122
123
+
**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified object does not exist, preventing errors caused by attempting to create an existing object.
124
+
123
125
### Start Task
124
126
125
127
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>
141
143
Deletes the specified task:
142
144
143
145
```SQL
144
-
DROP PIPE <PipeId>
146
+
DROP PIPE [IF EXISTS] <PipeId>
145
147
```
148
+
**IF EXISTS semantics**: Used in deletion operations to ensure that the delete command is executed when the specified object exists, preventing errors caused by attempting to delete non-existent objects.
146
149
147
150
Deleting a task does not require stopping the synchronization task first.
Copy file name to clipboardExpand all lines: src/UserGuide/latest/User-Manual/Data-subscription.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,11 +46,12 @@ IoTDB supports the creation, deletion, and viewing of Topics through SQL stateme
46
46
The SQL statement is as follows:
47
47
48
48
```SQL
49
-
CREATE TOPIC <topicName>
49
+
CREATE TOPIC [IF NOT EXISTS] <topicName>
50
50
WITH (
51
51
[<parameter>=<value>,],
52
52
);
53
53
```
54
+
**IF NOT EXISTS semantics**: Used in creation operations to ensure that the create command is executed when the specified object does not exist, preventing errors caused by attempting to create an existing object.
54
55
55
56
Detailed explanation of each parameter is as follows:
56
57
@@ -74,7 +75,7 @@ Examples are as follows:
74
75
CREATE TOPIC root_all;
75
76
76
77
-- Custom subscription
77
-
CREATE TOPIC db_timerange
78
+
CREATE TOPIC IF NOT EXISTS db_timerange
78
79
WITH (
79
80
'path'='root.db.**',
80
81
'start-time'='2023-01-01',
@@ -87,8 +88,9 @@ WITH (
87
88
A Topic can only be deleted if it is not subscribed to. When a Topic is deleted, its related consumption progress will be cleared.
88
89
89
90
```SQL
90
-
DROP TOPIC <topicName>;
91
+
DROP TOPIC [IF EXISTS] <topicName>;
91
92
```
93
+
**IF EXISTS semantics**: Used in deletion operations to ensure that the delete command is executed when the specified object exists, preventing errors caused by attempting to delete non-existent objects.
92
94
93
95
#### 3.1.3 View Topic
94
96
@@ -142,7 +144,7 @@ The `SubscriptionSession` class in the IoTDB subscription client provides interf
0 commit comments