Skip to content

Commit d36a0ef

Browse files
authored
update (#2768)
1 parent c191485 commit d36a0ef

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

docs/en/sql-reference/10-sql-commands/00-ddl/04-task/01-ddl-create_task.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ The CREATE TASK statement is used to define a new task that executes a specified
1717
CREATE [ OR REPLACE ] TASK [ IF NOT EXISTS ] <name>
1818
WAREHOUSE = <string>
1919
SCHEDULE = { <num> MINUTE | <num> SECOND | USING CRON <expr> <time_zone> }
20-
[ AFTER <string> [ , <string> , ... ]]
20+
[ AFTER <string>
2121
[ WHEN <boolean_expr> ]
2222
[ SUSPEND_TASK_AFTER_NUM_FAILURES = <num> ]
2323
[ ERROR_INTEGRATION = <string> ]
@@ -34,7 +34,7 @@ AS
3434
| WAREHOUSE | Required. Specifies the virtual warehouse to use for the task. |
3535
| SCHEDULE | Required. Defines the schedule on which the task will run. Can be specified in minutes or using a CRON expression along with a time zone. |
3636
| SUSPEND_TASK_AFTER_NUM_FAILURES | Optional. The number of consecutive failures after which the task will be automatically suspended. |
37-
| AFTER | Lists tasks that must be completed before this task starts. |
37+
| AFTER | List task that must be completed before this task starts. |
3838
| WHEN boolean_expr | A condition that must be true for the task to run. |
3939
| [ERROR_INTEGRATION](../16-notification/index.md) | Optional. The name of the notification integration to use for the task error notification with specific [task error payload ](./10-task-error-integration-payload.md)applied |
4040
| COMMENT | Optional. A string literal that serves as a comment or description for the task. |
@@ -151,7 +151,7 @@ In this example, a task named `daily_sales_summary` is created with **second-lev
151151
```sql
152152
CREATE TASK IF NOT EXISTS process_orders
153153
WAREHOUSE = 'etl'
154-
AFTER task1, task2
154+
AFTER task1
155155
AS
156156
INSERT INTO data_warehouse.orders SELECT * FROM staging.orders;
157157
```

docs/en/sql-reference/10-sql-commands/00-ddl/04-task/02-ddl-alter-task.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ ALTER TASK [ IF EXISTS ] <name> SET
2929
ALTER TASK [ IF EXISTS ] <name> MODIFY AS <sql>
3030

3131
--- modify DAG when condition and after condition
32-
ALTER TASK [ IF EXISTS ] <name> REMOVE AFTER <string> [ , <string> , ... ] | ADD AFTER <string> [ , <string> , ... ]
32+
ALTER TASK [ IF EXISTS ] <name> REMOVE AFTER <string> | ADD AFTER <string>
3333
--- allow to change condition for task execution
3434
ALTER TASK [ IF EXISTS ] <name> MODIFY WHEN <boolean_expr>
3535
```
@@ -41,8 +41,8 @@ ALTER TASK [ IF EXISTS ] <name> MODIFY WHEN <boolean_expr>
4141
| RESUME \| SUSPEND | Resume or suspend the task. |
4242
| SET | Change task settings. details parameter descriptions could be found on see [Create Task](01-ddl-create_task.md). |
4343
| MODIFY AS | Change task SQL. |
44-
| REMOVE AFTER | Remove predecessor tasks from the task dag, task would become a standalone task or a root task if no predecessor tasks left. |
45-
| ADD AFTER | Add predecessor tasks to the task dag. |
44+
| REMOVE AFTER | Remove predecessor task from the task dag, task would become a standalone task or a root task if no predecessor tasks left. |
45+
| ADD AFTER | Add predecessor task to the task dag. |
4646
| MODIFY WHEN | Change the condition for task execution. |
4747

4848
## Examples
@@ -72,7 +72,7 @@ ALTER TASK mytaskchild MODIFY WHEN STREAM_STATUS('stream3') = False;
7272
In this example, we are modifying the mytaskchild task to change its WHEN condition. The task will now only run if the STREAM_STATUS function for 'stream3' evaluates to False. This means the task will execute when 'stream3' does not contain change data.
7373

7474
```sql
75-
ALTER TASK MyTask1 ADD AFTER 'task2', 'task3';
75+
ALTER TASK MyTask1 ADD AFTER 'task2';
7676
```
7777
In this example, we are adding dependencies to the MyTask1 task. It will now run after the successful completion of both 'task2' and 'task3'. This creates a dependency relationship in a Directed Acyclic Graph (DAG) of tasks.
7878

0 commit comments

Comments
 (0)