Skip to content

Commit 95582dd

Browse files
committed
Modify the position of the document to add new content
1 parent 0ffae08 commit 95582dd

File tree

12 files changed

+53
-45
lines changed

12 files changed

+53
-45
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,8 @@ Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The
9494

9595
![](https://alioss.timecho.com/docs/img/Data-Sync02.png)
9696

97+
After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task.
98+
9799
Provide the following SQL statements for state management of synchronization tasks.
98100

99101
### Create Task
@@ -120,7 +122,7 @@ WITH SINK (
120122

121123
### Start Task
122124

123-
After creation, the task directly enters the running state without the need to execute the startup task. When using the `STOP PIPE` statement to stop a task, you need to manually use the `START PIPE` statement to start the task. If PIPE encounters an abnormal situation and stops, it will automatically restart the task to start processing data:
125+
Start processing data:
124126

125127
```SQL
126128
START PIPE<PipeId>

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,6 +96,8 @@ Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The
9696

9797
![](https://alioss.timecho.com/docs/img/Data-Sync02.png)
9898

99+
After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task.
100+
99101
Provide the following SQL statements for state management of synchronization tasks.
100102

101103
### Create Task
@@ -122,7 +124,7 @@ WITH SINK (
122124

123125
### Start Task
124126

125-
After creation, the task directly enters the running state without the need to execute the startup task. When using the `STOP PIPE` statement to stop a task, you need to manually use the `START PIPE` statement to start the task. If PIPE encounters an abnormal situation and stops, it will automatically restart the task to start processing data:
127+
Start processing data:
126128

127129
```SQL
128130
START PIPE<PipeId>

src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -92,11 +92,15 @@ The schema and auth synchronization functions have the following limitations:
9292

9393
Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram:
9494

95-
V1.3.0:
95+
V1.3.0 and earlier versions:
96+
97+
After creation, it will not start immediately and needs to execute the `START PIPE` statement to start the task.
9698

9799
![](https://alioss.timecho.com/docs/img/sync_en_02.png)
98100

99-
V1.3.1/2:
101+
V1.3.1 and later versions:
102+
103+
After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task.
100104

101105
![](https://alioss.timecho.com/docs/img/Data-Sync02.png)
102106

@@ -126,15 +130,7 @@ WITH SINK (
126130

127131
### Start Task
128132

129-
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:
130-
131-
V1.3.0:
132-
133-
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:
134-
135-
V1.3.1/2:
136-
137-
After creation, the task directly enters the running state without the need to execute the startup task. When using the `STOP PIPE` statement to stop a task, you need to manually use the `START PIPE` statement to start the task. If PIPE encounters an abnormal situation and stops, it will automatically restart the task to start processing data:
133+
Start processing data:
138134

139135

140136
```SQL

src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -94,11 +94,16 @@ The schema and auth synchronization functions have the following limitations:
9494

9595
Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram:
9696

97-
V1.3.0:
97+
98+
V1.3.0 and earlier versions:
99+
100+
After creation, it will not start immediately and needs to execute the `START PIPE` statement to start the task.
98101

99102
![](https://alioss.timecho.com/docs/img/sync_en_02.png)
100103

101-
V1.3.1/2:
104+
V1.3.1 and later versions:
105+
106+
After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task.
102107

103108
![](https://alioss.timecho.com/docs/img/Data-Sync02.png)
104109

@@ -127,13 +132,8 @@ WITH SINK (
127132
```
128133

129134
### Start Task
130-
V1.3.0:
131-
132-
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:
133-
134-
V1.3.1/2:
135135

136-
After creation, the task directly enters the running state without the need to execute the startup task. When using the `STOP PIPE` statement to stop a task, you need to manually use the `START PIPE` statement to start the task. If PIPE encounters an abnormal situation and stops, it will automatically restart the task to start processing data:
136+
Start processing data:
137137

138138
```SQL
139139
START PIPE<PipeId>

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,8 @@ Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The
9494

9595
![](https://alioss.timecho.com/docs/img/Data-Sync02.png)
9696

97+
After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task.
98+
9799
Provide the following SQL statements for state management of synchronization tasks.
98100

99101
### Create Task
@@ -120,7 +122,7 @@ WITH SINK (
120122

121123
### Start Task
122124

123-
After creation, the task directly enters the running state without the need to execute the startup task. When using the `STOP PIPE` statement to stop a task, you need to manually use the `START PIPE` statement to start the task. If PIPE encounters an abnormal situation and stops, it will automatically restart the task to start processing data:
125+
Start processing data:
124126

125127
```SQL
126128
START PIPE<PipeId>

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,6 +96,8 @@ Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The
9696

9797
![](https://alioss.timecho.com/docs/img/Data-Sync02.png)
9898

99+
After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task.
100+
99101
Provide the following SQL statements for state management of synchronization tasks.
100102

101103
### Create Task
@@ -122,7 +124,7 @@ WITH SINK (
122124

123125
### Start Task
124126

125-
After creation, the task directly enters the running state without the need to execute the startup task. When using the `STOP PIPE` statement to stop a task, you need to manually use the `START PIPE` statement to start the task. If PIPE encounters an abnormal situation and stops, it will automatically restart the task to start processing data:
127+
Start processing data:
126128

127129
```SQL
128130
START PIPE<PipeId>

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,6 +93,8 @@
9393

9494
![](https://alioss.timecho.com/docs/img/Data-Sync01.png)
9595

96+
创建后任务会直接启动,同时当任务发生异常停止后,系统会自动尝试重启任务。
97+
9698
提供以下 SQL 语句对同步任务进行状态管理。
9799

98100
### 创建任务
@@ -119,7 +121,7 @@ WITH SINK (
119121

120122
### 开始任务
121123

122-
创建之后,任务直接进入运行状态,不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务,PIPE发生异常情况停止后会自动重新启动任务,从而开始处理数据
124+
开始处理数据
123125

124126
```SQL
125127
START PIPE<PipeId>

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,6 +95,8 @@
9595

9696
![](https://alioss.timecho.com/docs/img/Data-Sync01.png)
9797

98+
创建后任务会直接启动,同时当任务发生异常停止后,系统会自动尝试重启任务。
99+
98100
提供以下 SQL 语句对同步任务进行状态管理。
99101

100102
### 创建任务
@@ -121,7 +123,7 @@ WITH SINK (
121123

122124
### 开始任务
123125

124-
创建之后,任务直接进入运行状态,不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务,PIPE发生异常情况停止后会自动重新启动任务,从而开始处理数据
126+
开始处理数据
125127

126128
```SQL
127129
START PIPE<PipeId>

src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -91,11 +91,15 @@
9191

9292
数据同步任务有三种状态:RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示:
9393

94-
V1.3.0:
94+
V1.3.0及之前版本:
95+
96+
在创建后不会立即启动,需要执行`START PIPE`语句启动任务。
9597

9698
![](https://alioss.timecho.com/docs/img/dataSync02.png)
9799

98-
V1.3.1/2:
100+
V1.3.1及之后版本:
101+
102+
创建后任务会直接启动,同时当任务发生异常停止后,系统会自动尝试重启任务。
99103

100104
![](https://alioss.timecho.com/docs/img/Data-Sync01.png)
101105

@@ -125,13 +129,7 @@ WITH SINK (
125129

126130
### 开始任务
127131

128-
V1.3.0:
129-
130-
创建之后,任务不会立即被处理,需要启动任务。使用`START PIPE`语句来启动任务,从而开始处理数据:
131-
132-
V1.3.1/2:
133-
134-
创建之后,任务直接进入运行状态,不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务,PIPE发生异常情况停止后会自动重新启动任务,从而开始处理数据:
132+
开始处理数据:
135133

136134
```SQL
137135
START PIPE<PipeId>

src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -93,11 +93,15 @@
9393

9494
数据同步任务有三种状态:RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示:
9595

96-
V1.3.0:
96+
V1.3.0及之前版本:
97+
98+
在创建后不会立即启动,需要执行`START PIPE`语句启动任务。
9799

98100
![](https://alioss.timecho.com/docs/img/dataSync02.png)
99101

100-
V1.3.1/2:
102+
V1.3.1及之后版本:
103+
104+
创建后任务会直接启动,同时当任务发生异常停止后,系统会自动尝试重启任务。
101105

102106
![](https://alioss.timecho.com/docs/img/Data-Sync01.png)
103107

@@ -127,13 +131,7 @@ WITH SINK (
127131

128132
### 开始任务
129133

130-
V1.3.0:
131-
132-
创建之后,任务不会立即被处理,需要启动任务。使用`START PIPE`语句来启动任务,从而开始处理数据:
133-
134-
V1.3.1/2:
135-
136-
创建之后,任务直接进入运行状态,不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务,PIPE发生异常情况停止后会自动重新启动任务,从而开始处理数据:
134+
开始处理数据:
137135

138136
```SQL
139137
START PIPE<PipeId>

0 commit comments

Comments
 (0)