You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/05/12 01:19:58 UTC
[GitHub] [dolphinscheduler] QuakeWang opened a new pull request, #10001: [Feature][Doc] Add example and notice about task type Dependent
QuakeWang opened a new pull request, #10001:
URL: https://github.com/apache/dolphinscheduler/pull/10001
close: #8018
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] QuakeWang commented on pull request #10001: [Feature][Doc] Add example and notice about task type Dependent
Posted by GitBox <gi...@apache.org>.
QuakeWang commented on PR #10001:
URL: https://github.com/apache/dolphinscheduler/pull/10001#issuecomment-1124459146
@zhongjiajie PTAL
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] zhongjiajie commented on a diff in pull request #10001: [Feature][Doc] Add example and notice about task type Dependent
Posted by GitBox <gi...@apache.org>.
zhongjiajie commented on code in PR #10001:
URL: https://github.com/apache/dolphinscheduler/pull/10001#discussion_r871210309
##########
docs/docs/en/guide/task/dependent.md:
##########
@@ -1,27 +1,39 @@
-# Dependent Node
+# Dependent
-- Dependent nodes are **dependency check nodes**. For example, process A depends on the successful execution of process B from yesterday, and the dependent node will check whether process B run successful yesterday.
+## Overview
-> Drag from the toolbar  task node to the canvas, as shown in the figure below:
+Dependent nodes are **dependency check nodes**. For example, process A depends on the successful execution of process B from yesterday, and the dependent node will check whether process B run successful yesterday.
-<p align="center">
- <img src="/img/dependent-nodes-en.png" width="80%" />
- </p>
-> The dependent node provides a logical judgment function, such as checking whether the B process was successful yesterday, or whether the C process was executed successfully.
+## Create Task
- <p align="center">
- <img src="/img/depend-node-en.png" width="80%" />
- </p>
+- 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.
-> For example, process A is a weekly report 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, as shown in the figure:
+## Task Parameter
- <p align="center">
- <img src="/img/depend-node1-en.png" width="80%" />
- </p>
+- **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.
-> If the weekly report A also needs to be executed successfully last Tuesday:
+## Examples
- <p align="center">
- <img src="/img/depend-node3-en.png" width="80%" />
- </p>
\ No newline at end of file
+The Dependent node provides a logical judgment function, which can detect the execution of the dependent node according to the logic.
+
+For example, process A is a weekly report 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, as shown in the figure:
+
+
+
+For example, 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, as shown in the figure:
Review Comment:
```suggestion
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:
```
##########
docs/docs/en/guide/task/dependent.md:
##########
@@ -1,27 +1,39 @@
-# Dependent Node
+# Dependent
-- Dependent nodes are **dependency check nodes**. For example, process A depends on the successful execution of process B from yesterday, and the dependent node will check whether process B run successful yesterday.
+## Overview
-> Drag from the toolbar  task node to the canvas, as shown in the figure below:
+Dependent nodes are **dependency check nodes**. For example, process A depends on the successful execution of process B from yesterday, and the dependent node will check whether process B run successful yesterday.
-<p align="center">
- <img src="/img/dependent-nodes-en.png" width="80%" />
- </p>
-> The dependent node provides a logical judgment function, such as checking whether the B process was successful yesterday, or whether the C process was executed successfully.
+## Create Task
- <p align="center">
- <img src="/img/depend-node-en.png" width="80%" />
- </p>
+- 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.
-> For example, process A is a weekly report 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, as shown in the figure:
+## Task Parameter
- <p align="center">
- <img src="/img/depend-node1-en.png" width="80%" />
- </p>
+- **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.
-> If the weekly report A also needs to be executed successfully last Tuesday:
+## Examples
- <p align="center">
- <img src="/img/depend-node3-en.png" width="80%" />
- </p>
\ No newline at end of file
+The Dependent node provides a logical judgment function, which can detect the execution of the dependent node according to the logic.
+
+For example, process A is a weekly report 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, as shown in the figure:
Review Comment:
```suggestion
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.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] zhongjiajie merged pull request #10001: [doc] Add example and notice about task type Dependent
Posted by GitBox <gi...@apache.org>.
zhongjiajie merged PR #10001:
URL: https://github.com/apache/dolphinscheduler/pull/10001
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org