From 0ffae08aaf2496690603d4032c1b8c27ec03066f Mon Sep 17 00:00:00 2001 From: W1y1r <2730956796@qq.com> Date: Mon, 18 Nov 2024 10:57:00 +0800 Subject: [PATCH 1/2] After data synchronization is created, it will automatically start (version 1.3.1+) --- .../Master/User-Manual/Data-Sync_apache.md | 4 ++-- .../Master/User-Manual/Data-Sync_timecho.md | 4 ++-- .../V1.3.0-2/User-Manual/Data-Sync_apache.md | 15 +++++++++++++++ .../V1.3.0-2/User-Manual/Data-Sync_timecho.md | 11 +++++++++++ .../latest/User-Manual/Data-Sync_apache.md | 4 ++-- .../latest/User-Manual/Data-Sync_timecho.md | 4 ++-- .../Master/User-Manual/Data-Sync_apache.md | 4 ++-- .../Master/User-Manual/Data-Sync_timecho.md | 4 ++-- .../V1.3.0-2/User-Manual/Data-Sync_apache.md | 12 ++++++++++++ .../V1.3.0-2/User-Manual/Data-Sync_timecho.md | 12 ++++++++++++ .../latest/User-Manual/Data-Sync_apache.md | 4 ++-- .../latest/User-Manual/Data-Sync_timecho.md | 4 ++-- 12 files changed, 66 insertions(+), 16 deletions(-) diff --git a/src/UserGuide/Master/User-Manual/Data-Sync_apache.md b/src/UserGuide/Master/User-Manual/Data-Sync_apache.md index 122b60202..c47889495 100644 --- a/src/UserGuide/Master/User-Manual/Data-Sync_apache.md +++ b/src/UserGuide/Master/User-Manual/Data-Sync_apache.md @@ -92,7 +92,7 @@ The schema and auth synchronization functions have the following limitations: Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram: -![](https://alioss.timecho.com/docs/img/sync_en_02.png) +![](https://alioss.timecho.com/docs/img/Data-Sync02.png) Provide the following SQL statements for state management of synchronization tasks. @@ -120,7 +120,7 @@ WITH SINK ( ### 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: +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: ```SQL START PIPE diff --git a/src/UserGuide/Master/User-Manual/Data-Sync_timecho.md b/src/UserGuide/Master/User-Manual/Data-Sync_timecho.md index 83a5aacbe..899f3a0ae 100644 --- a/src/UserGuide/Master/User-Manual/Data-Sync_timecho.md +++ b/src/UserGuide/Master/User-Manual/Data-Sync_timecho.md @@ -94,7 +94,7 @@ The schema and auth synchronization functions have the following limitations: Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram: -![](https://alioss.timecho.com/docs/img/sync_en_02.png) +![](https://alioss.timecho.com/docs/img/Data-Sync02.png) Provide the following SQL statements for state management of synchronization tasks. @@ -122,7 +122,7 @@ WITH SINK ( ### 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: +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: ```SQL START PIPE diff --git a/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md b/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md index 7da2d03cb..8b65d453c 100644 --- a/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md +++ b/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md @@ -92,8 +92,14 @@ The schema and auth synchronization functions have the following limitations: Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram: +V1.3.0: + ![](https://alioss.timecho.com/docs/img/sync_en_02.png) +V1.3.1/2: + +![](https://alioss.timecho.com/docs/img/Data-Sync02.png) + Provide the following SQL statements for state management of synchronization tasks. ### Create Task @@ -122,6 +128,15 @@ WITH SINK ( 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: +V1.3.0: + +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: + +V1.3.1/2: + +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: + + ```SQL START PIPE ``` diff --git a/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md b/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md index 739f63092..152a0dc91 100644 --- a/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md +++ b/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md @@ -94,8 +94,14 @@ The schema and auth synchronization functions have the following limitations: Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram: +V1.3.0: + ![](https://alioss.timecho.com/docs/img/sync_en_02.png) +V1.3.1/2: + +![](https://alioss.timecho.com/docs/img/Data-Sync02.png) + Provide the following SQL statements for state management of synchronization tasks. ### Create Task @@ -121,9 +127,14 @@ WITH SINK ( ``` ### Start Task +V1.3.0: 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: +V1.3.1/2: + +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: + ```SQL START PIPE ``` diff --git a/src/UserGuide/latest/User-Manual/Data-Sync_apache.md b/src/UserGuide/latest/User-Manual/Data-Sync_apache.md index 122b60202..c47889495 100644 --- a/src/UserGuide/latest/User-Manual/Data-Sync_apache.md +++ b/src/UserGuide/latest/User-Manual/Data-Sync_apache.md @@ -92,7 +92,7 @@ The schema and auth synchronization functions have the following limitations: Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram: -![](https://alioss.timecho.com/docs/img/sync_en_02.png) +![](https://alioss.timecho.com/docs/img/Data-Sync02.png) Provide the following SQL statements for state management of synchronization tasks. @@ -120,7 +120,7 @@ WITH SINK ( ### 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: +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: ```SQL START PIPE diff --git a/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md b/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md index 83a5aacbe..899f3a0ae 100644 --- a/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md +++ b/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md @@ -94,7 +94,7 @@ The schema and auth synchronization functions have the following limitations: Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram: -![](https://alioss.timecho.com/docs/img/sync_en_02.png) +![](https://alioss.timecho.com/docs/img/Data-Sync02.png) Provide the following SQL statements for state management of synchronization tasks. @@ -122,7 +122,7 @@ WITH SINK ( ### 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: +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: ```SQL START PIPE diff --git a/src/zh/UserGuide/Master/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/Master/User-Manual/Data-Sync_apache.md index 8a89c377e..06949947d 100644 --- a/src/zh/UserGuide/Master/User-Manual/Data-Sync_apache.md +++ b/src/zh/UserGuide/Master/User-Manual/Data-Sync_apache.md @@ -91,7 +91,7 @@ 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示： -![](https://alioss.timecho.com/docs/img/dataSync02.png) +![](https://alioss.timecho.com/docs/img/Data-Sync01.png) 提供以下 SQL 语句对同步任务进行状态管理。 @@ -119,7 +119,7 @@ WITH SINK ( ### 开始任务 -创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据： +创建之后，任务直接进入运行状态，不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务，PIPE发生异常情况停止后会自动重新启动任务，从而开始处理数据： ```SQL START PIPE diff --git a/src/zh/UserGuide/Master/User-Manual/Data-Sync_timecho.md b/src/zh/UserGuide/Master/User-Manual/Data-Sync_timecho.md index 5d8fa9a91..8631ba3cf 100644 --- a/src/zh/UserGuide/Master/User-Manual/Data-Sync_timecho.md +++ b/src/zh/UserGuide/Master/User-Manual/Data-Sync_timecho.md @@ -93,7 +93,7 @@ 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示： -![](https://alioss.timecho.com/docs/img/dataSync02.png) +![](https://alioss.timecho.com/docs/img/Data-Sync01.png) 提供以下 SQL 语句对同步任务进行状态管理。 @@ -121,7 +121,7 @@ WITH SINK ( ### 开始任务 -创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据： +创建之后，任务直接进入运行状态，不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务，PIPE发生异常情况停止后会自动重新启动任务，从而开始处理数据： ```SQL START PIPE diff --git a/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md index 452c54961..ae6589db4 100644 --- a/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md +++ b/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md @@ -91,8 +91,14 @@ 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示： +V1.3.0: + ![](https://alioss.timecho.com/docs/img/dataSync02.png) +V1.3.1/2: + +![](https://alioss.timecho.com/docs/img/Data-Sync01.png) + 提供以下 SQL 语句对同步任务进行状态管理。 ### 创建任务 @@ -119,8 +125,14 @@ WITH SINK ( ### 开始任务 +V1.3.0: + 创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据： +V1.3.1/2: + +创建之后，任务直接进入运行状态，不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务，PIPE发生异常情况停止后会自动重新启动任务，从而开始处理数据： + ```SQL START PIPE ``` diff --git a/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md b/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md index ebba2dc10..c9d01a6ac 100644 --- a/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md +++ b/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md @@ -93,8 +93,14 @@ 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示： +V1.3.0: + ![](https://alioss.timecho.com/docs/img/dataSync02.png) +V1.3.1/2: + +![](https://alioss.timecho.com/docs/img/Data-Sync01.png) + 提供以下 SQL 语句对同步任务进行状态管理。 ### 创建任务 @@ -121,8 +127,14 @@ WITH SINK ( ### 开始任务 +V1.3.0: + 创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据： +V1.3.1/2: + +创建之后，任务直接进入运行状态，不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务，PIPE发生异常情况停止后会自动重新启动任务，从而开始处理数据： + ```SQL START PIPE ``` diff --git a/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md index 8a89c377e..06949947d 100644 --- a/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md +++ b/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md @@ -91,7 +91,7 @@ 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示： -![](https://alioss.timecho.com/docs/img/dataSync02.png) +![](https://alioss.timecho.com/docs/img/Data-Sync01.png) 提供以下 SQL 语句对同步任务进行状态管理。 @@ -119,7 +119,7 @@ WITH SINK ( ### 开始任务 -创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据： +创建之后，任务直接进入运行状态，不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务，PIPE发生异常情况停止后会自动重新启动任务，从而开始处理数据： ```SQL START PIPE diff --git a/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md b/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md index 5d8fa9a91..8631ba3cf 100644 --- a/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md +++ b/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md @@ -93,7 +93,7 @@ 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示： -![](https://alioss.timecho.com/docs/img/dataSync02.png) +![](https://alioss.timecho.com/docs/img/Data-Sync01.png) 提供以下 SQL 语句对同步任务进行状态管理。 @@ -121,7 +121,7 @@ WITH SINK ( ### 开始任务 -创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据： +创建之后，任务直接进入运行状态，不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务，PIPE发生异常情况停止后会自动重新启动任务，从而开始处理数据： ```SQL START PIPE From 95582ddd5935ad0117badaaa4b417c15ddb1566b Mon Sep 17 00:00:00 2001 From: W1y1r <2730956796@qq.com> Date: Mon, 18 Nov 2024 14:56:43 +0800 Subject: [PATCH 2/2] Modify the position of the document to add new content --- .../Master/User-Manual/Data-Sync_apache.md | 4 +++- .../Master/User-Manual/Data-Sync_timecho.md | 4 +++- .../V1.3.0-2/User-Manual/Data-Sync_apache.md | 18 +++++++----------- .../V1.3.0-2/User-Manual/Data-Sync_timecho.md | 16 ++++++++-------- .../latest/User-Manual/Data-Sync_apache.md | 4 +++- .../latest/User-Manual/Data-Sync_timecho.md | 4 +++- .../Master/User-Manual/Data-Sync_apache.md | 4 +++- .../Master/User-Manual/Data-Sync_timecho.md | 4 +++- .../V1.3.0-2/User-Manual/Data-Sync_apache.md | 16 +++++++--------- .../V1.3.0-2/User-Manual/Data-Sync_timecho.md | 16 +++++++--------- .../latest/User-Manual/Data-Sync_apache.md | 4 +++- .../latest/User-Manual/Data-Sync_timecho.md | 4 +++- 12 files changed, 53 insertions(+), 45 deletions(-) diff --git a/src/UserGuide/Master/User-Manual/Data-Sync_apache.md b/src/UserGuide/Master/User-Manual/Data-Sync_apache.md index c47889495..70f13d7c4 100644 --- a/src/UserGuide/Master/User-Manual/Data-Sync_apache.md +++ b/src/UserGuide/Master/User-Manual/Data-Sync_apache.md @@ -94,6 +94,8 @@ Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The ![](https://alioss.timecho.com/docs/img/Data-Sync02.png) +After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task. + Provide the following SQL statements for state management of synchronization tasks. ### Create Task @@ -120,7 +122,7 @@ WITH SINK ( ### Start Task -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: +Start processing data: ```SQL START PIPE diff --git a/src/UserGuide/Master/User-Manual/Data-Sync_timecho.md b/src/UserGuide/Master/User-Manual/Data-Sync_timecho.md index 899f3a0ae..a54752c69 100644 --- a/src/UserGuide/Master/User-Manual/Data-Sync_timecho.md +++ b/src/UserGuide/Master/User-Manual/Data-Sync_timecho.md @@ -96,6 +96,8 @@ Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The ![](https://alioss.timecho.com/docs/img/Data-Sync02.png) +After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task. + Provide the following SQL statements for state management of synchronization tasks. ### Create Task @@ -122,7 +124,7 @@ WITH SINK ( ### Start Task -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: +Start processing data: ```SQL START PIPE diff --git a/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md b/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md index 8b65d453c..8bfd5e39d 100644 --- a/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md +++ b/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md @@ -92,11 +92,15 @@ The schema and auth synchronization functions have the following limitations: Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram: -V1.3.0: +V1.3.0 and earlier versions: + +After creation, it will not start immediately and needs to execute the `START PIPE` statement to start the task. ![](https://alioss.timecho.com/docs/img/sync_en_02.png) -V1.3.1/2: +V1.3.1 and later versions: + +After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task. ![](https://alioss.timecho.com/docs/img/Data-Sync02.png) @@ -126,15 +130,7 @@ WITH SINK ( ### 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: - -V1.3.0: - -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: - -V1.3.1/2: - -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: +Start processing data: ```SQL diff --git a/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md b/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md index 152a0dc91..81c1aeac3 100644 --- a/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md +++ b/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md @@ -94,11 +94,16 @@ The schema and auth synchronization functions have the following limitations: Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram: -V1.3.0: + +V1.3.0 and earlier versions: + +After creation, it will not start immediately and needs to execute the `START PIPE` statement to start the task. ![](https://alioss.timecho.com/docs/img/sync_en_02.png) -V1.3.1/2: +V1.3.1 and later versions: + +After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task. ![](https://alioss.timecho.com/docs/img/Data-Sync02.png) @@ -127,13 +132,8 @@ WITH SINK ( ``` ### Start Task -V1.3.0: - -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: - -V1.3.1/2: -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: +Start processing data: ```SQL START PIPE diff --git a/src/UserGuide/latest/User-Manual/Data-Sync_apache.md b/src/UserGuide/latest/User-Manual/Data-Sync_apache.md index c47889495..70f13d7c4 100644 --- a/src/UserGuide/latest/User-Manual/Data-Sync_apache.md +++ b/src/UserGuide/latest/User-Manual/Data-Sync_apache.md @@ -94,6 +94,8 @@ Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The ![](https://alioss.timecho.com/docs/img/Data-Sync02.png) +After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task. + Provide the following SQL statements for state management of synchronization tasks. ### Create Task @@ -120,7 +122,7 @@ WITH SINK ( ### Start Task -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: +Start processing data: ```SQL START PIPE diff --git a/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md b/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md index 899f3a0ae..a54752c69 100644 --- a/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md +++ b/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md @@ -96,6 +96,8 @@ Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The ![](https://alioss.timecho.com/docs/img/Data-Sync02.png) +After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task. + Provide the following SQL statements for state management of synchronization tasks. ### Create Task @@ -122,7 +124,7 @@ WITH SINK ( ### Start Task -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: +Start processing data: ```SQL START PIPE diff --git a/src/zh/UserGuide/Master/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/Master/User-Manual/Data-Sync_apache.md index 06949947d..5c5e19c0c 100644 --- a/src/zh/UserGuide/Master/User-Manual/Data-Sync_apache.md +++ b/src/zh/UserGuide/Master/User-Manual/Data-Sync_apache.md @@ -93,6 +93,8 @@ ![](https://alioss.timecho.com/docs/img/Data-Sync01.png) +创建后任务会直接启动，同时当任务发生异常停止后，系统会自动尝试重启任务。 + 提供以下 SQL 语句对同步任务进行状态管理。 ### 创建任务 @@ -119,7 +121,7 @@ WITH SINK ( ### 开始任务 -创建之后，任务直接进入运行状态，不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务，PIPE发生异常情况停止后会自动重新启动任务，从而开始处理数据： +开始处理数据： ```SQL START PIPE diff --git a/src/zh/UserGuide/Master/User-Manual/Data-Sync_timecho.md b/src/zh/UserGuide/Master/User-Manual/Data-Sync_timecho.md index 8631ba3cf..ab2459659 100644 --- a/src/zh/UserGuide/Master/User-Manual/Data-Sync_timecho.md +++ b/src/zh/UserGuide/Master/User-Manual/Data-Sync_timecho.md @@ -95,6 +95,8 @@ ![](https://alioss.timecho.com/docs/img/Data-Sync01.png) +创建后任务会直接启动，同时当任务发生异常停止后，系统会自动尝试重启任务。 + 提供以下 SQL 语句对同步任务进行状态管理。 ### 创建任务 @@ -121,7 +123,7 @@ WITH SINK ( ### 开始任务 -创建之后，任务直接进入运行状态，不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务，PIPE发生异常情况停止后会自动重新启动任务，从而开始处理数据： +开始处理数据： ```SQL START PIPE diff --git a/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md index ae6589db4..f2d1bf5f7 100644 --- a/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md +++ b/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md @@ -91,11 +91,15 @@ 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示： -V1.3.0: +V1.3.0及之前版本: + +在创建后不会立即启动，需要执行`START PIPE`语句启动任务。 ![](https://alioss.timecho.com/docs/img/dataSync02.png) -V1.3.1/2: +V1.3.1及之后版本: + +创建后任务会直接启动，同时当任务发生异常停止后，系统会自动尝试重启任务。 ![](https://alioss.timecho.com/docs/img/Data-Sync01.png) @@ -125,13 +129,7 @@ WITH SINK ( ### 开始任务 -V1.3.0: - -创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据： - -V1.3.1/2: - -创建之后，任务直接进入运行状态，不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务，PIPE发生异常情况停止后会自动重新启动任务，从而开始处理数据： +开始处理数据： ```SQL START PIPE diff --git a/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md b/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md index c9d01a6ac..b22db4067 100644 --- a/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md +++ b/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md @@ -93,11 +93,15 @@ 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示： -V1.3.0: +V1.3.0及之前版本: + +在创建后不会立即启动，需要执行`START PIPE`语句启动任务。 ![](https://alioss.timecho.com/docs/img/dataSync02.png) -V1.3.1/2: +V1.3.1及之后版本: + +创建后任务会直接启动，同时当任务发生异常停止后，系统会自动尝试重启任务。 ![](https://alioss.timecho.com/docs/img/Data-Sync01.png) @@ -127,13 +131,7 @@ WITH SINK ( ### 开始任务 -V1.3.0: - -创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据： - -V1.3.1/2: - -创建之后，任务直接进入运行状态，不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务，PIPE发生异常情况停止后会自动重新启动任务，从而开始处理数据： +开始处理数据： ```SQL START PIPE diff --git a/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md index 06949947d..5c5e19c0c 100644 --- a/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md +++ b/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md @@ -93,6 +93,8 @@ ![](https://alioss.timecho.com/docs/img/Data-Sync01.png) +创建后任务会直接启动，同时当任务发生异常停止后，系统会自动尝试重启任务。 + 提供以下 SQL 语句对同步任务进行状态管理。 ### 创建任务 @@ -119,7 +121,7 @@ WITH SINK ( ### 开始任务 -创建之后，任务直接进入运行状态，不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务，PIPE发生异常情况停止后会自动重新启动任务，从而开始处理数据： +开始处理数据： ```SQL START PIPE diff --git a/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md b/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md index 8631ba3cf..ab2459659 100644 --- a/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md +++ b/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md @@ -95,6 +95,8 @@ ![](https://alioss.timecho.com/docs/img/Data-Sync01.png) +创建后任务会直接启动，同时当任务发生异常停止后，系统会自动尝试重启任务。 + 提供以下 SQL 语句对同步任务进行状态管理。 ### 创建任务 @@ -121,7 +123,7 @@ WITH SINK ( ### 开始任务 -创建之后，任务直接进入运行状态，不需要执行启动任务。当使用`STOP PIPE`语句停止任务时需手动使用`START PIPE`语句来启动任务，PIPE发生异常情况停止后会自动重新启动任务，从而开始处理数据： +开始处理数据： ```SQL START PIPE