?????? [DISCUSS] Process definithon json split design

Fri, 27 Nov 2020 01:53:27 -0800 

Dear all


I think it is better to combine one table structure and three table structure 
in the current workflow.


The disadvantages of one table architecture are as follows:


1. The master needs to load the task details into the memory. When the 
scheduling is frequent, the memory pressure of the master is relatively large


2. The master and the worker communicate the task details in RPC, and the 
network io of the master is relatively large






The advantages of one table architecture are as follows:


3. Query the database only once, and the pressure on the database is small


4. Front end display is convenient


5. It is convenient to assemble the DAG of task (only query once)






Disadvantages of the three table architecture:


6. It is troublesome to organize the DAG of task during scheduling. If a 
workflow has 1000 tasks, you need to query the relationship of these 1000 
tasks. Query 1000 times or query 1000 records at a time.


7. When the front-end displays and the back-end generates DAGs, it is also OK 
to query the relationships of these 1000 tasks and splice them into DAGs






Advantages of three table architecture:


8. The workflow editing and task editing are decoupled, and the details of a 
task need not be changed


9. The pressure of master is relatively small, and the amount of data to be 
dispatched and transmitted is small






The combination of one table architecture and three table architecture:


1) In one table schema, t_ds_process_definithon stores all the details of the 
task, and only stores the fields of the task DAG diagram. The workflow table 
only stores the DAG relationship of task.


It solves new problems such as 1, 2, 6, 7, and retains the advantages of 
problems 3, 4, 5, 8 and 9


2) Task related table t_ds_task_relation and t_ds_task_definithon table 
maintains task relation data and task detail data, and solves 8 problems


shortcoming


1??t_ds_process_definithon table holds the DAG relationship of the task, while 
_ds_task_relation also stores the relationship of task, which needs to be 
modified 2 times.




   ????????????????????????????????????????????????????????
    ????????????????????:
    
1.master??????????????????????????????????????????????master??????????????
    2.master??worker??????????????rpc??????master??????io??????


    ????????????????????:
    3.??????????????1??????????????????
    4.????????????????
    5.????task??dag??????????????????????


    ????????????????:
    
6.??????????task??dag??????????????1??????????1000??task????????????1000??task??????????????.????1000??????1??????1000????????
    
7.??????????????????????dag????????????????1000??task??????????????????????dag


    ??????????????????
    
8.????????????task??????????????????task????????????????????????????
    9.master??????????????????????????????????


    ????????????????????????????
    
1??????????????t_ds_process_definithon????task????????????????????????????task????dag????????????????????????task??dag??????
    ????1??2??6??7????????????????????3??4??5??8??9??????????
    
2??task??????t_ds_task_relation??t_ds_task_definithon??????task??????????task????????????8????
    ????
    
1??t_ds_process_definithon??????????????task??dag????????t_ds_task_relation??????task??????????????????????2????






liukunyuan








------------------ ???????? ------------------
??????:                                                                         
                                               "dev"                            
                                                        <[email protected]&gt;;
????????:&nbsp;2020??11??27??(??????) ????4:03
??????:&nbsp;"dev"<[email protected]&gt;;

????:&nbsp;?????? [DISCUSS] Process definithon json split design



+1




------------------&amp;nbsp;????????&amp;nbsp;------------------
??????:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 
"dev"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 <[email protected]&amp;gt;;
????????:&amp;nbsp;2020??11??27??(??????) ????3:53
??????:&amp;nbsp;"dev"<[email protected]&amp;gt;;

????:&amp;nbsp;Re: [DISCUSS] Process definithon json split design



There are two solutions for the query timing of job details:
- The Master is only responsible for DAG scheduling. When a job is
executed, it sends the job code to the Worker, and the Worker is
responsible for querying the job details and executing the job
- The Master executes DAG scheduling, queries the job details when a job is
executed, and then sends it to the Worker to execute the job

---------------------------------------------------------------------------------------------------------

????????????????????????????????????????

- 
Master??????DAG??????????????????????????????????????Worker??Worker??????????????????????????
- Master????DAG??????????????????????????????????????????????Worker????????

--------------------
DolphinScheduler(Incubator) Commtter
Hemin Wen&amp;nbsp; ??????
[email protected]
--------------------


Hemin Wen <[email protected]&amp;gt; ??2020??11??25?????? ????10:01??????

&amp;gt; Hi!
&amp;gt;
&amp;gt; About json splitting of workflow definition, The following is the 
design
&amp;gt; plan for splitting three tables.
&amp;gt;
&amp;gt; Everyone can discuss together.
&amp;gt;
&amp;gt;
&amp;gt; 
--------------------------------------------------------------------------------------------------------------
&amp;gt;
&amp;gt; ## 1. Currently
&amp;gt; The workflow definition of the current DS system includes task 
definition
&amp;gt; data and task relationship data. In the design of the database, task 
data
&amp;gt; and task relationship data are stored in the workflow as a string type
&amp;gt; field (process_definition_json) Definition table 
(t_ds_process_definition).
&amp;gt;
&amp;gt; With the increase of workflow and tasks, the following problems will 
arise:
&amp;gt;
&amp;gt; -Task data, relational data and workflow data are coupled together, 
which
&amp;gt; is not friendly to the scenario of single-task scheduling. The task 
must be
&amp;gt; created in the workflow
&amp;gt;
&amp;gt; -The task cannot be reused because the task is created in the workflow
&amp;gt;
&amp;gt; -The maintenance cost is high. If you move the whole body and modify 
any
&amp;gt; task, you need to update the data in the workflow as a whole, and it 
also
&amp;gt; increases the log cost
&amp;gt;
&amp;gt; -When there are many tasks in the workflow, the efficiency of global
&amp;gt; search and statistical analysis is low, such as querying which tasks 
use
&amp;gt; which data source
&amp;gt;
&amp;gt; -Poor scalability, for example, the realization of blood relationship
&amp;gt; function in the future will only lead to more and more bloated workflow
&amp;gt; definitions
&amp;gt;
&amp;gt; -Tasks, relationships, and workflow boundaries are blurred. Condition
&amp;gt; nodes and delay nodes are also regarded as a task, which is actually a
&amp;gt; combination of relationships and conditions
&amp;gt;
&amp;gt; Based on the above pain points, we need to redefine the business
&amp;gt; boundaries of tasks, relationships, and workflows, and redesign their 
data
&amp;gt; structures based on this
&amp;gt;
&amp;gt; ## 2. Design Ideas
&amp;gt;
&amp;gt; ### 2.1 Workflow, relation, job
&amp;gt;
&amp;gt; First of all, we set aside the current implementation and clarify the
&amp;gt; business boundaries of tasks (the subsequent description is changed to
&amp;gt; jobs), relationships, and workflows, and how to decouple
&amp;gt;
&amp;gt; -Job: the task that the scheduling system really needs to execute, the 
job
&amp;gt; only contains the data and resources needed to execute the job
&amp;gt; -relation: the relationship between the job and the job and the 
execution
&amp;gt; conditions, including the execution relationship (after A completes,
&amp;gt; execute B) and execution conditions (after A completes and succeeds,
&amp;gt; execute B; after A completes and fails, execute C; A completes 30 After
&amp;gt; minutes, execute D)
&amp;gt; -Workflow: the carrier of a set of relationships, the workflow only 
saves
&amp;gt; the relationships between jobs (DAG is a display form of workflow, a 
way to
&amp;gt; create relationships)
&amp;gt;
&amp;gt; Combined with the functions supported by the current DS, we can make a
&amp;gt; classification
&amp;gt;
&amp;gt; -Job: Dependency check, sub-process, Shell, stored procedure, Sql, 
Spark,
&amp;gt; Flink, MR, Python, Http, DataX, Sqoop
&amp;gt; -Relationship: serial execution, parallel execution, aggregate 
execution,
&amp;gt; conditional branch, delayed execution
&amp;gt; -Workflow: the boundary of scheduling execution, including a set of
&amp;gt; relationships
&amp;gt;
&amp;gt; #### 2.1.1 Further refinement
&amp;gt;
&amp;gt; The job definition data is not much different from the current job
&amp;gt; definition data. Both are composed of public fields and custom fields. 
You
&amp;gt; only need to remove the fields related to the relationship.
&amp;gt;
&amp;gt; The workflow definition data is not much different from the current
&amp;gt; workflow definition data, just remove the json field.
&amp;gt;
&amp;gt; Relational data, we can abstract into two nodes and one path according 
to
&amp;gt; classification. The node is the job, and the path includes the 
conditional
&amp;gt; rules that need to be met from the pre-node to the post-node. The
&amp;gt; conditional rules include: unconditional, judgment condition, and delay
&amp;gt; condition.
&amp;gt;
&amp;gt; ### 2.2 Version Management
&amp;gt;
&amp;gt; We clarify the business boundaries. After decoupling, they become a
&amp;gt; reference relationship. The workflow and the relationship are 
one-to-many,
&amp;gt; and the relationship and the job are one-to-many. Not only is the
&amp;gt; definition of data, we also need to consider instance data. Every time 
a
&amp;gt; workflow is scheduled and executed, a workflow instance will be 
generated.
&amp;gt; Jobs and workflows can be changed, and the workflow instance must 
support
&amp;gt; viewing, rerun, recovery failure, etc. . This requires the 
introduction of
&amp;gt; version management of the definition data. Every time workflow,
&amp;gt; relationship, and job changes need to save old version data and 
generate
&amp;gt; new version data.
&amp;gt;
&amp;gt; So the design idea here is:
&amp;gt;
&amp;gt; To define data, you need to add a version field
&amp;gt;
&amp;gt; The definition table needs to add the corresponding log table
&amp;gt;
&amp;gt; When creating definition data, double write to the definition table and
&amp;gt; log table. When modifying the definition data, save the modified 
version to
&amp;gt; the log table
&amp;gt;
&amp;gt; There is no need to save version information in the reference data of 
the
&amp;gt; definition table (refer to the latest version), and the version 
information
&amp;gt; at the time of execution is saved in the instance data
&amp;gt;
&amp;gt; ### 2.3 Coding Design
&amp;gt;
&amp;gt; This also involves the import and export of workflow and job definition
&amp;gt; data. According to the previous community discussion, a coding scheme 
needs
&amp;gt; to be introduced. Each piece of data in workflow, relationship, and job
&amp;gt; will have a unique code. Related Issues: https://github
&amp;gt; .com/apache/incubator-dolphinscheduler/issues/3820
&amp;gt;
&amp;gt; Resource: RESOURCE_xxx
&amp;gt;
&amp;gt; Task: TASK_xxx
&amp;gt;
&amp;gt; Relation: RELATION_xxx
&amp;gt;
&amp;gt; Workflow: PROCESS_xxx
&amp;gt;
&amp;gt; Project: PROJECT_xxx
&amp;gt;
&amp;gt; ## 3. Design plan
&amp;gt;
&amp;gt; ### 3.1 Table model design
&amp;gt;
&amp;gt; #### 3.1.1 Job definition table: t_ds_task_definithon
&amp;gt;
&amp;gt; | Column Name | Description |
&amp;gt; | ----------------------- | -------------- |
&amp;gt; | id | Self-incrementing ID |
&amp;gt; | union_code | unique code |
&amp;gt; | version | Version |
&amp;gt; | name | Job name |
&amp;gt; | description | description |
&amp;gt; | task_type | Job type |
&amp;gt; | task_params | Job custom parameters |
&amp;gt; | run_flag | Run flag |
&amp;gt; | task_priority | Job priority |
&amp;gt; | worker_group | worker group |
&amp;gt; | fail_retry_times | Number of failed retries |
&amp;gt; | fail_retry_interval | Failure retry interval |
&amp;gt; | timeout_flag | Timeout flag |
&amp;gt; | timeout_notify_strategy | Timeout notification strategy |
&amp;gt; | timeout_duration | Timeout duration |
&amp;gt; | create_time | Creation time |
&amp;gt; | update_time | Modification time |
&amp;gt;
&amp;gt; #### 3.1.2 Task relation table: t_ds_task_relation
&amp;gt;
&amp;gt; | Column Name | Description |
&amp;gt; | ----------------------- | ------------------------- ------------- |
&amp;gt; | id | Self-incrementing ID |
&amp;gt; | union_code | unique code |
&amp;gt; | version | Version |
&amp;gt; | process_definition_code | Workflow coding |
&amp;gt; | node_code | Node code (workflow code/job code) |
&amp;gt; | post_node_code | Post node code (workflow code/job code) |
&amp;gt; | condition_type | Condition type 0: None 1: Judgment condition 2: 
Delay
&amp;gt; condition |
&amp;gt; | condition_params | Condition parameters |
&amp;gt; | create_time | Creation time |
&amp;gt; | update_time | Modification time |
&amp;gt;
&amp;gt; #### 3.1.3 Workflow definition table: t_ds_process_definithon
&amp;gt;
&amp;gt; | Column Name | Description |
&amp;gt; | ---- | ---- |
&amp;gt; | id | Self-incrementing ID |
&amp;gt; | union_code | unique code |
&amp;gt; | version | Version |
&amp;gt; | name | Workflow name |
&amp;gt; | project_code | Project code |
&amp;gt; | release_state | Release state |
&amp;gt; | user_id | Owning user ID |
&amp;gt; | description | description |
&amp;gt; | global_params | Global parameters |
&amp;gt; | flag | Whether the process is available: 0 is not available, 1 is
&amp;gt; available |
&amp;gt; | receivers | recipients |
&amp;gt; | receivers_cc | CC |
&amp;gt; | timeout | Timeout time |
&amp;gt; | tenant_id | tenant ID |
&amp;gt; | create_time | Creation time |
&amp;gt; | update_time | Modification time |
&amp;gt;
&amp;gt; #### 3.1.4 Job definition log table: t_ds_task_definithon_log
&amp;gt;
&amp;gt; Add operation type (add, modify, delete), operator, and operation time
&amp;gt; based on the job definition table
&amp;gt;
&amp;gt; #### 3.1.5 Job relation log table: t_ds_task_relation_log
&amp;gt;
&amp;gt; Add operation type (add, modify, delete), operator, and operation time
&amp;gt; based on the job relationship table
&amp;gt;
&amp;gt; #### 3.1.6 Workflow definition log table: t_ds_process_definithon_log
&amp;gt;
&amp;gt; Add operation type (add, modify, delete), operator, and operation time
&amp;gt; based on the workflow definition table
&amp;gt;
&amp;gt; ### 3.2 Frontend
&amp;gt;
&amp;gt; *The design here is just a personal idea, and the front-end help is 
needed
&amp;gt; to design the interaction*
&amp;gt;
&amp;gt; Need to add job management related functions, including: job list, job
&amp;gt; creation, update, delete, view details operations
&amp;gt;
&amp;gt; To create a workflow page, you need to split json into workflow 
definition
&amp;gt; data and job relationship data to the back-end API layer to save/update
&amp;gt;
&amp;gt; Workflow page, when dragging task nodes, add reference job options
&amp;gt;
&amp;gt; The conditional branch nodes and delay nodes need to be resolved into 
the
&amp;gt; conditional rule data in the relationship; conversely, the conditional 
rule
&amp;gt; data returned by the backend needs to be displayed as the corresponding
&amp;gt; node when querying the workflow
&amp;gt;
&amp;gt; ### 3.3 Master
&amp;gt;
&amp;gt; When the Master schedules the workflow, you need to modify <Build dag 
from
&amp;gt; json&amp;gt; to <Build dag from relational data&amp;gt;. When 
executing a workflow, first
&amp;gt; load the relational data in full (no job data is loaded here), generate
&amp;gt; DAG, and traverse DAG execution , And then get the job data that needs 
to
&amp;gt; be executed
&amp;gt;
&amp;gt; Other execution processes are consistent with existing processes
&amp;gt;
&amp;gt;
&amp;gt; 
--------------------------------------------------------------------------------------------------------------
&amp;gt;
&amp;gt; ## 1.????
&amp;gt;
&amp;gt; 
????DS??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????process_definition_json??????????????????????????????t_ds_process_definition??????
&amp;gt;
&amp;gt; ????????????????????????????????????????
&amp;gt;
&amp;gt; - 
??????????????????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; - ????????????????????????????????????????
&amp;gt;
&amp;gt; - 
????????????????????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; - 
??????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; - ??????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; - 
??????????????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; 
????????????????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; ## 2.????????
&amp;gt;
&amp;gt; ### 2.1 ??????????????????
&amp;gt;
&amp;gt; 
????????????????????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; - ??????????????????????????????????????????????????????????????????
&amp;gt; -
&amp;gt; 
??????????????????????????????????????????????????????A????????????B??????????????A??????????????????B??A??????????????????C??A????30????????????D??
&amp;gt; - 
??????????????????????????????????????????????????DAG????????????????????????????????????????????
&amp;gt;
&amp;gt; ????????DS??????????????????????????????
&amp;gt;
&amp;gt; - 
????????????????????????Shell????????????Sql??Spark??Flink??MR??Python??Http??DataX??Sqoop
&amp;gt; - ??????????????????????????????????????????????????????
&amp;gt; - ????????????????????????????????????
&amp;gt;
&amp;gt; #### 2.1.1 ??????????
&amp;gt;
&amp;gt; 
??????????????????????????????????????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; 
??????????????????????????????????????????????????????json??????????????
&amp;gt;
&amp;gt;
&amp;gt; 
????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; ### 2.2 ????????
&amp;gt;
&amp;gt;
&amp;gt; 
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; ??????????????????????
&amp;gt;
&amp;gt; ????????????????????????
&amp;gt;
&amp;gt; ??????????????????????????
&amp;gt;
&amp;gt; 
??????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; 
????????????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; ### 2.3 ????????
&amp;gt;
&amp;gt; 
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????Issue??
&amp;gt; https://github.com/apache/incubator-dolphinscheduler/issues/3820
&amp;gt;
&amp;gt; ??????RESOURCE_xxx
&amp;gt;
&amp;gt; ??????TASK_xxx
&amp;gt;
&amp;gt; ??????RELATION_xxx
&amp;gt;
&amp;gt; ????????PROCESS_xxx
&amp;gt;
&amp;gt; ??????PROJECT_xxx
&amp;gt;
&amp;gt; ## 3.????????
&amp;gt;
&amp;gt; ### 3.1 ??????????
&amp;gt;
&amp;gt; #### 3.1.1 ????????????t_ds_task_definithon
&amp;gt;
&amp;gt; | 
????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | ----------------------- | -------------- |
&amp;gt; | 
id&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????ID&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | 
union_code&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |
&amp;gt; | 
version&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | 
name&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |
&amp;gt; | 
description&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | 
task_type&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |
&amp;gt; | 
task_params&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ?????????????? |
&amp;gt; | 
run_flag&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |
&amp;gt; | 
task_priority&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ??????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |
&amp;gt; | 
worker_group&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | worker????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |
&amp;gt; | 
fail_retry_times&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ????????????&amp;nbsp;&amp;nbsp; |
&amp;gt; | fail_retry_interval&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | 
????????????&amp;nbsp;&amp;nbsp; |
&amp;gt; | 
timeout_flag&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |
&amp;gt; | timeout_notify_strategy | ????????????&amp;nbsp;&amp;nbsp; |
&amp;gt; | 
timeout_duration&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |
&amp;gt; | 
create_time&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |
&amp;gt; | 
update_time&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |
&amp;gt;
&amp;gt; #### 3.1.2 ????????????t_ds_task_relation
&amp;gt;
&amp;gt; | 
????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | ----------------------- | -------------------------------------- |
&amp;gt; | 
id&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????ID&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | 
union_code&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | 
version&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | process_definition_code | 
??????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | 
node_code&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????????????????????/??????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | 
post_node_code&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ????????????????????????/??????????&amp;nbsp;&amp;nbsp;&amp;nbsp; |
&amp;gt; | 
condition_type&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ???????? 0???? 1?????????? 2?????????? |
&amp;gt; | 
condition_params&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | 
create_time&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | 
update_time&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt;
&amp;gt; #### 3.1.3 ??????????????t_ds_process_definithon
&amp;gt;
&amp;gt; | ???? | ???? |
&amp;gt; | ---- | ---- |
&amp;gt; | 
id&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
????ID&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | union_code&amp;nbsp;&amp;nbsp;&amp;nbsp; | 
????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | version&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 
| 
????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | 
name&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | 
??????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | project_code&amp;nbsp; | 
????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | release_state | 
????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | user_id&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 
| 
????????ID&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | description&amp;nbsp;&amp;nbsp; | 
????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | global_params | 
????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | 
flag&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 | ??????????????0 ????????1 ???? |
&amp;gt; | receivers&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | 
??????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | receivers_cc&amp;nbsp; | 
??????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | timeout&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 
| 
????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | tenant_id&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | 
????ID&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | create_time&amp;nbsp;&amp;nbsp; | 
????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt; | update_time&amp;nbsp;&amp;nbsp; | 
????????&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
 |
&amp;gt;
&amp;gt; #### 3.1.4 ????????????????t_ds_task_definithon_log
&amp;gt;
&amp;gt; ??????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; #### 3.1.5 ????????????????t_ds_task_relation_log
&amp;gt;
&amp;gt; ??????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; #### 3.1.6 ??????????????????t_ds_process_definithon_log
&amp;gt;
&amp;gt; ????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; ### 3.2 ????
&amp;gt;
&amp;gt; *??????????????????????????????????????????????????*
&amp;gt;
&amp;gt; 
??????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; 
??????????????????????json??????????????????????????????????????????API??????/????
&amp;gt;
&amp;gt; ????????????????????????????????????????????
&amp;gt;
&amp;gt; 
????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
&amp;gt;
&amp;gt; ### 3.3 Master
&amp;gt;
&amp;gt;
&amp;gt; 
Master????????????????????<??json????dag&amp;gt;??????<??????????????dag&amp;gt;????????????????????????????????????????????????????????????????DAG??????DAG????????????????????????????????
&amp;gt;
&amp;gt; ??????????????????????????
&amp;gt;
&amp;gt; --------------------
&amp;gt; DolphinScheduler(Incubator) Commtter
&amp;gt; Hemin Wen&amp;nbsp; ??????
&amp;gt; [email protected]
&amp;gt; --------------------
&amp;gt;

Reply via email to