mirror of
https://gitee.com/dolphinscheduler/DolphinScheduler.git
synced 2024-11-29 18:58:05 +08:00
[doc] Change subprocess dependent (#10637)
(cherry picked from commit 1f46078ab8
)
This commit is contained in:
parent
4324ddd28e
commit
c4c4771435
@ -7,20 +7,24 @@ Dependent nodes are **dependency check nodes**. For example, process A depends o
|
||||
|
||||
## Create Task
|
||||
|
||||
- Click `Project -> Management-Project -> Name-Workflow Definition`, and click the `Create Workflow` button to enter the DAG editing page.
|
||||
- Drag from the toolbar <img src="/img/tasks/icons/dependent.png" width="15"/> task node to canvas.
|
||||
- Click `Project Management -> Project Name -> Workflow Definition`, and click the `Create Workflow` button to enter the DAG editing page.
|
||||
- Drag from the toolbar <img src="../../../../img/tasks/icons/dependent.png" width="15"/> task node to canvas.
|
||||
|
||||
## Task Parameter
|
||||
|
||||
- **Node name**: The node name in a workflow definition is unique.
|
||||
- **Run flag**: Identifies whether this node schedules normally, if it does not need to execute, select the `prohibition execution`.
|
||||
- **Descriptive information**: Describe the function of the node.
|
||||
- **Task priority**: When the number of worker threads is insufficient, execute in the order of priority from high to low, and tasks with the same priority will execute in a first-in first-out order.
|
||||
- **Worker grouping**: Assign tasks to the machines of the worker group to execute. If `Default` is selected, randomly select a worker machine for execution.
|
||||
- **Environment Name**: Configure the environment name in which run the script.
|
||||
- **Times of failed retry attempts**: The number of times the task failed to resubmit.
|
||||
- **Failed retry interval**: The time interval (unit minute) for resubmitting the task after a failed task.
|
||||
- **Delayed execution time**: The time (unit minute) that a task delays in execution.
|
||||
| **Parameter** | **Description** |
|
||||
| ----- | -----------|
|
||||
| Node name | Unique name of node in workflow definition. |
|
||||
| Run flag | Identifies whether this node schedules normally. |
|
||||
| Description | Describe the function of the node. |
|
||||
| Task priority | When the number of worker threads is insufficient, execute in the order of priority from high to low, and tasks with the same priority will execute in a first-in first-out order. |
|
||||
| Worker group | Assign tasks to the machines of the worker group to execute. If `Default` is selected, randomly select a worker machine for execution. |
|
||||
| Task group name | The group in Resources, if not configured, it will not be used. |
|
||||
| Environment Name | Configure the environment name in which run the script. |
|
||||
| Number of failed retries | The number of times the task failed to resubmit. |
|
||||
| Failed retry interval | The time interval (unit minute) for resubmitting the task after a failed task. |
|
||||
| Delayed execution time | The time (unit minute) that a task delays in execution. |
|
||||
| Pre task | Selecting a predecessor task for the current task, will set the selected predecessor task as upstream of the current task. |
|
||||
|
||||
|
||||
## Task Examples
|
||||
@ -29,12 +33,12 @@ The Dependent node provides a logical judgment function, which can detect the ex
|
||||
|
||||
For example, process A is a weekly task, processes B and C are daily tasks, and task A requires tasks B and C to be successfully executed every day of the last week.
|
||||
|
||||
![dependent_task01](/img/tasks/demo/dependent_task01.png)
|
||||
![dependent_task01](../../../../img/tasks/demo/dependent_task01.png)
|
||||
|
||||
And another example is that process A is a weekly report task, processes B and C are daily tasks, and task A requires tasks B or C to be successfully executed every day of the last week:
|
||||
|
||||
![dependent_task02](/img/tasks/demo/dependent_task02.png)
|
||||
![dependent_task02](../../../../img/tasks/demo/dependent_task02.png)
|
||||
|
||||
If the weekly report A also needs to be executed successfully last Tuesday:
|
||||
|
||||
![dependent_task03](/img/tasks/demo/dependent_task03.png)
|
||||
![dependent_task03](../../../../img/tasks/demo/dependent_task03.png)
|
||||
|
@ -6,7 +6,7 @@ The sub-process node is to execute an external workflow definition as a task nod
|
||||
|
||||
## Create Task
|
||||
|
||||
- Click `Project Management -> Project Name -> Workflow Definition`, and click the `Create Workflow` button to enter the DAG editing page.
|
||||
- Click `Project Management-> Project Name -> Workflow Definition`, and click the `Create Workflow` button to enter the DAG editing page.
|
||||
- Drag from the toolbar <img src="../../../../img/tasks/icons/sub_process.png" width="15"/> task node to canvas to create a new SubProcess task.
|
||||
|
||||
## Task Parameter
|
||||
|
Loading…
Reference in New Issue
Block a user