zhongjiajie commented on code in PR #11275:
URL: https://github.com/apache/dolphinscheduler/pull/11275#discussion_r936318641
##########
docs/docs/en/guide/project/workflow-definition.md:
##########
@@ -97,24 +97,47 @@ The following are the operation functions of the workflow
definition list:
* Recipient: select notification policy||timeout alarm||when fault tolerance
occurs, process result information or alarm email will be sent to the recipient
list.
* Cc: select notification policy||timeout alarm||when fault tolerance
occurs, the process result information or warning email will be copied to the
CC list.
* Startup parameter: Set or overwrite global parameter values when starting
a new process instance.
- * Complement: includes serial complement and parallel complement and
supports manual date input and date selection. Serial complement defines,
within the specified time range, executes the complements from the start date
to the end date by sequential and N process instances are generated in
sequence. Parallel complement defines executing the complement concurrently in
the multiple days to generate N process instances within the specified time
range. Manual date input defines: manually input the date following the date
format `yyyy-MM-dd HH:mm:ss` and separate dates by a comma. Date selection
defines: to select dates via UI.
- * Dependent Mode: Trigger the complement of workflow instances that the
downstream dependent node depends on the current workflow(It is required that
the scheduled status of the workflow instance of the current replenishment is
online, and only the downstream supplement directly dependent on the current
workflow will be triggered).
- * You can select complement time range (When the scheduled configuration
is not online, the daily complement will be performed by default according to
the selected time range.If the timing configuration is online, it will be
complemented according to the selected time range in combination with the
timing configuration) when executing a timing workflow definition. For example,
need to fill in the data from 1st May to 10th May, as shown in the figure below:
-
- 
-
- > Serial mode: the complement execute sequentially from 9th May to 10th
May, and the process instance page generates 2 process instances;
-
- > Parallel mode: The tasks from 9th May to 10th May execute
simultaneously, and the process instance page generates 2 process instances;
-
- * You can manually enter the complement dates (independent from the timing
configuration) to execute the complement data to workflow definitions. The
figure below is an example to make complement data from 9th May to 10th May:
-
-
-
- > Serial mode: the complement execute sequentially from 9th May to 10th
May, and the process instance page generates 2 process instances;
-
- > Parallel mode: The tasks from 9th May to 10th May execute
simultaneously, and the process instance page generates 2 process instances;
-
+ * Complement: refers to running the workflow definition within the specified
date range and generating the corresponding workflow instance according to the
complement policy. The complement policy includes two modes: serial complement
and parallel complement. The date can be selected on the page or entered
manually.
Review Comment:
```suggestion
* Complement: refers to running the workflow definition within the
specified date range and generating the corresponding workflow instance
according to the complement policy. The complement policy includes two modes:
**serial complement** and **parallel complement**. The date can be selected on
the page or entered manually.
```
##########
docs/docs/en/guide/project/workflow-definition.md:
##########
@@ -97,24 +97,47 @@ The following are the operation functions of the workflow
definition list:
* Recipient: select notification policy||timeout alarm||when fault tolerance
occurs, process result information or alarm email will be sent to the recipient
list.
* Cc: select notification policy||timeout alarm||when fault tolerance
occurs, the process result information or warning email will be copied to the
CC list.
* Startup parameter: Set or overwrite global parameter values when starting
a new process instance.
- * Complement: includes serial complement and parallel complement and
supports manual date input and date selection. Serial complement defines,
within the specified time range, executes the complements from the start date
to the end date by sequential and N process instances are generated in
sequence. Parallel complement defines executing the complement concurrently in
the multiple days to generate N process instances within the specified time
range. Manual date input defines: manually input the date following the date
format `yyyy-MM-dd HH:mm:ss` and separate dates by a comma. Date selection
defines: to select dates via UI.
- * Dependent Mode: Trigger the complement of workflow instances that the
downstream dependent node depends on the current workflow(It is required that
the scheduled status of the workflow instance of the current replenishment is
online, and only the downstream supplement directly dependent on the current
workflow will be triggered).
- * You can select complement time range (When the scheduled configuration
is not online, the daily complement will be performed by default according to
the selected time range.If the timing configuration is online, it will be
complemented according to the selected time range in combination with the
timing configuration) when executing a timing workflow definition. For example,
need to fill in the data from 1st May to 10th May, as shown in the figure below:
-
- 
-
- > Serial mode: the complement execute sequentially from 9th May to 10th
May, and the process instance page generates 2 process instances;
-
- > Parallel mode: The tasks from 9th May to 10th May execute
simultaneously, and the process instance page generates 2 process instances;
-
- * You can manually enter the complement dates (independent from the timing
configuration) to execute the complement data to workflow definitions. The
figure below is an example to make complement data from 9th May to 10th May:
-
-
-
- > Serial mode: the complement execute sequentially from 9th May to 10th
May, and the process instance page generates 2 process instances;
-
- > Parallel mode: The tasks from 9th May to 10th May execute
simultaneously, and the process instance page generates 2 process instances;
-
+ * Complement: refers to running the workflow definition within the specified
date range and generating the corresponding workflow instance according to the
complement policy. The complement policy includes two modes: serial complement
and parallel complement. The date can be selected on the page or entered
manually.
+
+ * Serial complement: within the specified time range, complement is
executed from the start date to the end date, and multiple process instances
are generated in turn; Click Run workflow and select the serial complement
mode: for example, from July 9 to July 10, execute in sequence, and generate
two process instances in sequence on the process instance page.
+
+
+
+ * Parallel Replenishment: within the specified time range, replenishment
is performed simultaneously for multiple days, and multiple process instances
are generated at the same time. Enter date manually: manually enter a date in
the comma separated date format of 'yyyy MM DD hh:mm:ss'.Click Run workflow and
select the parallel complement mode: for example, execute the tasks from July 9
to July 10 at the same time, and generate two process instances on the process
instance page at the same time.
+
+
+
+ * Concurrency: refers to the maximum number of instances executed in
parallel in the parallel complement mode.For example, if tasks from July 6 to
July 10 are executed at the same time, and the concurrency is 2, then the
process instance is:
+
+
+
+
Review Comment:
It seems is a sub part of *Parallel Replenishment*, please make it as sub
part by adding four space
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
