Nothing Special   »   [go: up one dir, main page]

CN114625509B - Workflow processing method and device - Google Patents

Workflow processing method and device Download PDF

Info

Publication number
CN114625509B
CN114625509B CN202210269882.6A CN202210269882A CN114625509B CN 114625509 B CN114625509 B CN 114625509B CN 202210269882 A CN202210269882 A CN 202210269882A CN 114625509 B CN114625509 B CN 114625509B
Authority
CN
China
Prior art keywords
execution
workflow
task
hierarchy
storage space
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202210269882.6A
Other languages
Chinese (zh)
Other versions
CN114625509A (en
Inventor
肖苏阳
郭冰
张园超
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhejiang eCommerce Bank Co Ltd
Original Assignee
Zhejiang eCommerce Bank Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zhejiang eCommerce Bank Co Ltd filed Critical Zhejiang eCommerce Bank Co Ltd
Priority to CN202210269882.6A priority Critical patent/CN114625509B/en
Publication of CN114625509A publication Critical patent/CN114625509A/en
Application granted granted Critical
Publication of CN114625509B publication Critical patent/CN114625509B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/48Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806Task transfer initiation or dispatching
    • G06F9/4843Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23Updating
    • G06F16/2365Ensuring data consistency and integrity
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28Databases characterised by their database models, e.g. relational or object models
    • G06F16/284Relational databases

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Software Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the specification provides a workflow processing method and a workflow processing device, wherein the workflow processing method comprises the following steps: receiving a workflow diagram, wherein the workflow diagram comprises a plurality of task nodes and an execution sequence of each task node; and executing the workflow tasks formed by the task nodes according to the execution sequence, and recording the execution data generated by the execution hierarchy to a preset storage space according to the current execution hierarchy in the execution process of the workflow tasks, wherein the execution process of the workflow tasks comprises a plurality of execution hierarchies. By storing the execution data in the general workflow processing process, the support for transactions is increased, and the atomicity, consistency, isolation and durability of workflow processing in cross-site, cross-platform and cross-data source scenes are ensured.

Description

Workflow processing method and device
Technical Field
The embodiment of the specification relates to the technical field of computers, in particular to a workflow processing method.
Background
With the rapid development of computer technology, various engine layers are endless, and stream computing engines are rapidly developed. To expand the application scope of the stream computation engine, the stream computation engine may be used for generic workflows. However, when a lightweight stream computing engine is used to run a general workflow, cross-platform unified modeling is required for various resources and computing capabilities, and cross-platform characteristics are required to ensure the integrity of computation through transactions.
Disclosure of Invention
In view of this, the present embodiments provide a workflow processing method. One or more embodiments of the present specification also relate to a workflow processing apparatus, a computing device, a computer-readable storage medium, and a computer program that solve the technical drawbacks existing in the prior art.
According to a first aspect of embodiments of the present specification, there is provided a workflow processing method, including:
Receiving a workflow diagram, wherein the workflow diagram comprises a plurality of task nodes and an execution sequence of each task node;
And executing the workflow tasks formed by the task nodes according to the execution sequence, and recording the execution data generated by the execution hierarchy to a preset storage space according to the current execution hierarchy in the execution process of the workflow tasks, wherein the execution process of the workflow tasks comprises a plurality of execution hierarchies.
Optionally, the execution hierarchy includes a main execution hierarchy, where the main execution hierarchy is an execution hierarchy corresponding to the workflow task;
In the executing process of the workflow task, recording the execution data generated by the execution hierarchy to a preset storage space according to the current execution hierarchy, including:
And in the execution process of the workflow task, if the current execution level is a main execution level, recording a main execution state generated by the main execution level to a main storage space in the preset storage space.
Optionally, the main execution state includes at least one of an initialization state, an on state, an execution state, a ready state, and a commit state.
Optionally, in the executing process of the workflow task, before recording the main execution state generated by the main execution hierarchy to the main storage space in the preset storage space if the current execution hierarchy is the main execution hierarchy, the method further includes:
Creating a main identifier for the main execution hierarchy according to the workflow diagram and a preset first configuration parameter;
The recording the main execution state generated by the main execution hierarchy to the main storage space in the preset storage space includes:
and associating and recording the main execution state generated by the main execution hierarchy and the main identifier to a main storage space in the preset storage space.
Optionally, the execution hierarchy further includes a sub-execution hierarchy, where the sub-execution hierarchy is an execution hierarchy corresponding to the task node;
In the executing process of the workflow task, recording the execution data generated by the execution hierarchy to a preset storage space according to the current execution hierarchy, including:
and in the execution process of the workflow task, if the current execution level is a sub-execution level, recording a task node execution result generated by the sub-execution level to a sub-storage space in the preset storage space.
Optionally, in the executing process of the workflow task, before recording the task node execution result generated by the sub-execution hierarchy to the sub-storage space in the preset storage space if the current execution hierarchy is the sub-execution hierarchy, the method further includes:
creating a sub-identifier for the sub-execution hierarchy according to the workflow diagram and a preset second configuration parameter;
The recording the task node execution result generated by the sub-execution hierarchy to the sub-storage space in the preset storage space includes:
and the task node execution result generated by the sub-execution hierarchy and the sub-identifier are recorded in a sub-storage space in the preset storage space in an associated mode.
Optionally, the execution hierarchy further includes a slave execution hierarchy, where the slave execution hierarchy is an execution hierarchy corresponding to a task element in the task node;
In the executing process of the workflow task, recording the execution data generated by the execution hierarchy to a preset storage space according to the current execution hierarchy, including:
and in the execution process of the workflow task, if the current execution level is a slave execution level, recording the task element execution result generated by the slave execution level to a slave storage space in the preset storage space.
Optionally, in the executing process of the workflow task, before recording the execution result of the task element generated from the execution hierarchy to the slave storage space in the preset storage space if the current execution hierarchy is the slave execution hierarchy, the method further includes:
creating a slave identifier for the slave execution hierarchy according to the workflow diagram and a preset third configuration parameter;
the recording the task element execution result generated from the execution hierarchy to the slave storage space in the preset storage space comprises the following steps:
and associating and recording the task element execution result generated from the execution hierarchy and the slave identification to a slave storage space in the preset storage space.
Optionally, the executing the workflow task formed by the task nodes according to the execution sequence includes:
Dividing workflow tasks corresponding to the workflow diagram into a plurality of subtasks according to the execution sequence of each task node and sending the subtasks to execution units corresponding to each task node, wherein the subtasks are in one-to-one correspondence with the task nodes;
And processing subtasks corresponding to any execution unit in the execution units according to the execution sequence.
According to a second aspect of embodiments of the present specification, there is provided a workflow processing apparatus comprising:
A receiving module configured to receive a workflow graph, wherein the workflow graph includes a plurality of task nodes, and an execution order of the task nodes;
the execution module is configured to execute the workflow tasks formed by the task nodes according to the execution sequence, and record the execution data generated by the execution hierarchy to a preset storage space according to the current execution hierarchy in the execution process of the workflow tasks, wherein the execution process of the workflow tasks comprises a plurality of execution hierarchies.
Optionally, the execution hierarchy includes a main execution hierarchy, where the main execution hierarchy is an execution hierarchy corresponding to the workflow task;
the execution module is further configured to:
And in the execution process of the workflow task, if the current execution level is a main execution level, recording a main execution state generated by the main execution level to a main storage space in the preset storage space.
Optionally, the main execution state includes at least one of an initialization state, an on state, an execution state, a ready state, and a commit state.
Optionally, the apparatus further comprises a first creation module configured to:
Creating a main identifier for the main execution hierarchy according to the workflow diagram and a preset first configuration parameter;
the execution module is further configured to:
and associating and recording the main execution state generated by the main execution hierarchy and the main identifier to a main storage space in the preset storage space.
Optionally, the execution hierarchy further includes a sub-execution hierarchy, where the sub-execution hierarchy is an execution hierarchy corresponding to the task node;
the execution module is further configured to:
and in the execution process of the workflow task, if the current execution level is a sub-execution level, recording a task node execution result generated by the sub-execution level to a sub-storage space in the preset storage space.
Optionally, the apparatus further comprises a second creation module configured to:
creating a sub-identifier for the sub-execution hierarchy according to the workflow diagram and a preset second configuration parameter;
the execution module is further configured to:
and the task node execution result generated by the sub-execution hierarchy and the sub-identifier are recorded in a sub-storage space in the preset storage space in an associated mode.
Optionally, the execution hierarchy further includes a slave execution hierarchy, where the slave execution hierarchy is an execution hierarchy corresponding to a task element in the task node;
the execution module is further configured to:
and in the execution process of the workflow task, if the current execution level is a slave execution level, recording the task element execution result generated by the slave execution level to a slave storage space in the preset storage space.
Optionally, the apparatus further comprises a third creation module configured to:
creating a slave identifier for the slave execution hierarchy according to the workflow diagram and a preset third configuration parameter;
the execution module is further configured to:
and associating and recording the task element execution result generated from the execution hierarchy and the slave identification to a slave storage space in the preset storage space.
Optionally, the execution module is further configured to:
Dividing workflow tasks corresponding to the workflow diagram into a plurality of subtasks according to the execution sequence of each task node and sending the subtasks to execution units corresponding to each task node, wherein the subtasks are in one-to-one correspondence with the task nodes;
And processing subtasks corresponding to any execution unit in the execution units according to the execution sequence.
According to a third aspect of embodiments of the present specification, there is provided a computing device comprising:
a memory and a processor;
The memory is configured to store computer-executable instructions that, when executed by the processor, perform the steps of the workflow processing method described above.
According to a fourth aspect of embodiments of the present specification, there is provided a computer readable storage medium storing computer executable instructions which, when executed by a processor, implement the steps of the workflow processing method described above.
According to a fifth aspect of embodiments of the present specification, there is provided a computer program, wherein the computer program, when executed in a computer, causes the computer to perform the steps of the workflow processing method described above.
The embodiment of the specification provides a workflow processing method, which is used for receiving a workflow diagram, wherein the workflow diagram comprises a plurality of task nodes and an execution sequence of each task node; and executing the workflow tasks formed by the task nodes according to the execution sequence, and recording the execution data generated by the execution hierarchy to a preset storage space according to the current execution hierarchy in the execution process of the workflow tasks, wherein the execution process of the workflow tasks comprises a plurality of execution hierarchies. After using the flow computation for the generic workflow project, the compute scheduling integration engine supports a canonical on-line/off-line control-compute project. For the control workflow, by increasing the support of the transaction ACID characteristic on the basis of workflow processing, the efficiency of processing the workflow is improved, namely, by storing execution data in the general workflow processing process, the support of the transaction is increased, and the atomicity, consistency, isolation and durability of the workflow processing in the cross-site, cross-platform and cross-data source scenes are ensured.
Drawings
FIG. 1 is a flow chart of a workflow processing method provided in one embodiment of the present disclosure;
FIG. 2 is a process flow diagram of a workflow processing method provided in one embodiment of the present disclosure;
FIG. 3 is a schematic diagram of a workflow processing apparatus according to one embodiment of the present disclosure;
FIG. 4 is a block diagram of a computing device provided in one embodiment of the present description.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many other forms than described herein and similarly generalized by those skilled in the art to whom this disclosure pertains without departing from the spirit of the disclosure and, therefore, this disclosure is not limited by the specific implementations disclosed below.
The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that, although the terms first, second, etc. may be used in one or more embodiments of this specification to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first may also be referred to as a second, and similarly, a second may also be referred to as a first, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" depending on the context.
First, terms related to one or more embodiments of the present specification will be explained.
Transaction: a program execution unit accesses and possibly updates various data items in the database. The transaction should have 4 attributes: atomicity (atomicity), consistency (consistency), isolation (independence), persistence (durability), these four properties are commonly referred to as ACID properties.
The workflow (WorkFlow) is a computational model of the workflow, i.e., the logic and rules of how the work in the workflow is organized together, expressed in a computer in the appropriate model, and calculated for implementation. The main problems to be solved by the workflow are: to achieve a project goal, a computer is used to automatically communicate among a plurality of participants according to a predetermined rule.
Directed acyclic graphs (DAGs, DIRECTED ACYCLIC GRAPH) refer to a directed graph that cannot start from a vertex and go back to that point through several edges.
A brief description will be given of a workflow processing method provided in one or more embodiments of the present specification.
With the rapid development of computer technology, various engine layers are endless, and stream computing engines are rapidly developed. To expand the application scope of the stream computation engine, the stream computation engine may be used for generic workflows. However, when a lightweight stream computing engine is used to run a general workflow, cross-platform unified modeling needs to be performed on various resources and computing capabilities, and cross-platform characteristics are needed, such as batch/stream/interactive computing can share a set of operators, support custom UDF/UDAF/UDTF, can refer to any server, and handle class server operators can be automatically integrated into a relational database system, so as to ensure the integrity of computing through transactions.
Accordingly, embodiments of the present disclosure provide a workflow processing method, receiving a workflow diagram, where the workflow diagram includes a plurality of task nodes and an execution order of the task nodes; and executing the workflow tasks formed by the task nodes according to the execution sequence, and recording the execution data generated by the execution hierarchy to a preset storage space according to the current execution hierarchy in the execution process of the workflow tasks, wherein the execution process of the workflow tasks comprises a plurality of execution hierarchies. After using the flow computation for the generic workflow project, the compute scheduling integration engine supports a canonical on-line/off-line control-compute project. For the control workflow, by increasing the support of the transaction ACID characteristic on the basis of workflow processing, the efficiency of processing the workflow is improved, namely, by storing execution data in the general workflow processing process, the support of the transaction is increased, and the atomicity, consistency, isolation and durability of the workflow processing in the cross-site, cross-platform and cross-data source scenes are ensured.
In the present specification, a workflow processing method is provided, and the present specification relates to a workflow processing apparatus, a computing device, and a computer-readable storage medium, one by one, as described in detail in the following embodiments.
Referring to fig. 1, fig. 1 shows a flowchart of a workflow processing method according to an embodiment of the present disclosure, which specifically includes the following steps.
Step 102: a workflow diagram is received, wherein the workflow diagram includes a plurality of task nodes and an execution order of the task nodes.
The execution body implementing the workflow processing method may be a computing device having a workflow processing function, such as a server, a terminal, etc. having a workflow processing function.
Specifically, the workflow diagram refers to a directed acyclic graph carrying workflow tasks, namely a DAG graph; the task node refers to each link for processing workflow tasks; the execution order refers to the order in which certain task nodes are executed.
In practical applications, there are various ways of receiving the workflow diagram, for example, an operator sends a receiving request carrying the workflow diagram to an executing body, the executing body obtains the workflow diagram from the receiving request after receiving the receiving request, or the operator sends a receiving instruction for the workflow to the executing body, and the executing body starts to obtain the workflow after receiving the receiving instruction; the server may automatically acquire the workflow diagram every preset time, for example, after the preset time, the server with the workflow processing function automatically acquires the workflow diagram in the designated access area; or after a preset time length, the terminal with the workflow processing function automatically acquires the workflow diagram stored locally. The manner in which the workflow diagrams are received is not limited in this specification.
Step 104: and executing the workflow tasks formed by the task nodes according to the execution sequence, and recording the execution data generated by the execution hierarchy to a preset storage space according to the current execution hierarchy in the execution process of the workflow tasks, wherein the execution process of the workflow tasks comprises a plurality of execution hierarchies.
Further, on the basis of receiving the workflow diagram, executing workflow tasks formed by task nodes according to an execution sequence, and recording execution data generated by the execution hierarchy to a preset storage space according to the current execution hierarchy in the execution process of the workflow tasks.
Specifically, a workflow Task (Flow Task) refers to a workflow Task formed by a group of internal nodes meeting the requirements of one project scene; the execution level refers to a level corresponding to a current execution node, such as a first level, a second level, and the like; execution data refers to data related to execution, such as execution results, execution states, and the like.
In practical application, after the workflow diagram is received, the workflow tasks formed by the task nodes are executed according to the execution sequence of the task nodes in the workflow diagram. In the process of executing the workflow task, it is also required to store the execution data generated by the execution hierarchy into a preset storage space corresponding to the execution hierarchy according to the execution stage, that is, the execution hierarchy, or store the execution data generated by the execution hierarchy into an area corresponding to the execution hierarchy in the preset storage space.
In one possible implementation manner of the embodiments of the present disclosure, the execution hierarchy may include a main execution hierarchy, where the main execution hierarchy is an execution hierarchy corresponding to the workflow task. At this time, when the current execution hierarchy is the main execution hierarchy, the execution data is the main execution state, and at this time, in the process of executing the workflow, the main execution state of the main execution hierarchy needs to be recorded into the preset storage space. That is, when the execution hierarchy includes a main execution hierarchy, during the execution of the workflow task, according to the current execution hierarchy, the execution data generated by the execution hierarchy is recorded into a preset storage space, and the specific implementation process may be as follows:
And in the execution process of the workflow task, if the current execution level is a main execution level, recording a main execution state generated by the main execution level to a main storage space in the preset storage space.
Specifically, the main execution hierarchy refers to an execution hierarchy corresponding to a workflow task; the main memory space refers to an area in the preset memory space for storing execution data generated by the main execution hierarchy. The main execution state refers to a state of a current workflow task in the execution process, and the main execution state comprises at least one of an initialization state, an on state, an execution state, a preparation state and a submission state.
In practical application, in the process of executing the workflow task formed by each task node according to the execution sequence, if the current execution level is in the main execution level, the main execution state generated by the main execution level is recorded in the main storage space of the preset storage space. Thus, the record main execution state is recorded in the main storage space, and the atomicity, consistency, isolation and durability of workflow processing can be improved.
For example, in the execution process of the workflow task, the current execution hierarchy is an initialization hierarchy in the main execution hierarchy, the main execution state is an initialization state, and then the initialization state is recorded in the main storage space; in another example, the current execution hierarchy is a commit hierarchy in the primary execution hierarchy, the primary execution state is a commit state, and then the commit state is recorded in the primary storage space.
Optionally, to further improve the atomicity, consistency, isolation, and durability of the workflow process, it is necessary to create a master identification for the master execution hierarchy and to associate the master identification with the master execution state when recording the master execution state. That is, in the execution process of the workflow task, if the current execution level is a main execution level, before recording the main execution state generated by the main execution level to the main storage space in the preset storage space, the method further includes:
Creating a main identifier for the main execution hierarchy according to the workflow diagram and a preset first configuration parameter;
correspondingly, the recording the main execution state generated by the main execution hierarchy to the main storage space in the preset storage space includes:
and associating and recording the main execution state generated by the main execution hierarchy and the main identifier to a main storage space in the preset storage space.
Specifically, the first configuration parameter refers to a parameter aiming at a main execution level or workflow task in preset execution parameters.
In practical application, after receiving the workflow diagram, the execution subject creates a unique main identifier for the workflow task based on the workflow diagram and a preset first configuration parameter, that is, creates a main identifier for the main execution hierarchy. Further, in the process of executing the workflow task, if the workflow task is in the main execution level, the main execution state and the main identifier generated by the main execution level are associated and recorded in a storage area corresponding to the main execution level in the preset storage air, namely, a main storage space.
In a possible implementation manner of the embodiment of the present disclosure, the execution hierarchy may include not only a main execution hierarchy but also a sub-execution hierarchy, where the sub-execution hierarchy is an execution hierarchy corresponding to the task node. At this time, when the current execution hierarchy is a sub-execution hierarchy, the execution data is a task node execution result, and at this time, in the process of executing the workflow, the task node execution result of the sub-execution hierarchy needs to be recorded into a preset storage space. That is, when the execution hierarchy further includes a sub-execution hierarchy, in the execution process of the workflow task, according to the current execution hierarchy, the execution data generated by the execution hierarchy is recorded into a preset storage space, and the specific implementation process may be as follows:
and in the execution process of the workflow task, if the current execution level is a sub-execution level, recording a task node execution result generated by the sub-execution level to a sub-storage space in the preset storage space.
Specifically, the sub-execution hierarchy refers to an execution hierarchy corresponding to a task node; the sub-storage space is a region in the preset storage space for storing the execution result of the task node generated by the sub-execution level; the task node execution result refers to an execution result generated in the execution process of the current task node.
In practical application, in the process of executing the workflow task formed by each task node according to the execution sequence, if the current execution level is at the sub-execution level, recording the task node execution result generated by the sub-execution level in the sub-storage space of the preset storage space. Thus, the execution result of the recording task node is recorded in the main storage space, and the atomicity, consistency, isolation and durability of workflow processing can be improved.
For example, in the execution process of the workflow task, the current execution hierarchy is a first sub-execution hierarchy in the sub-execution hierarchies, the task node execution result generated by the first sub-execution hierarchy is a first execution result, and then the first execution result is recorded in the sub-storage space; in the execution process of the workflow task, the current execution hierarchy is the Nth sub-execution hierarchy in the sub-execution hierarchies, the execution result of the task node generated by the Nth sub-execution hierarchy is the execution success, and then the execution success is recorded in the sub-storage space.
Optionally, in order to further improve atomicity, consistency, isolation, and durability of the workflow process, it is necessary to create a child identifier for the child execution hierarchy and to record the child identifier in association with the task node execution result when recording the task node execution result. That is, in the executing process of the workflow task, if the current execution level is a sub-execution level, before recording the task node execution result generated by the sub-execution level to the sub-storage space in the preset storage space, the method further includes:
creating a sub-identifier for the sub-execution hierarchy according to the workflow diagram and a preset second configuration parameter;
Correspondingly, the recording the task node execution result generated by the sub-execution hierarchy to the sub-storage space in the preset storage space includes:
and the task node execution result generated by the sub-execution hierarchy and the sub-identifier are recorded in a sub-storage space in the preset storage space in an associated mode.
Specifically, the second configuration parameter refers to a parameter for a sub-execution level in preset execution parameters.
In practical application, after receiving the workflow diagram, when executing the workflow task composed of each task node, at the initial stage of executing the current sub-execution hierarchy, or before executing the workflow task composed of each task node, a unique sub-identifier may be created for the current task node based on the workflow diagram and a preset second configuration parameter, that is, a main identifier is created for the sub-execution hierarchy. Further, in the process of executing the workflow task, if the workflow task is in the sub-execution level, the task node execution result and the sub-identifier generated by the sub-execution level are associated and recorded in a storage area corresponding to the sub-execution level in the preset storage air, namely, a sub-storage space.
It should be noted that, when creating the child identifier for the child execution hierarchy according to the workflow diagram and the preset second configuration parameter, the child identifier may also be created for the child execution hierarchy based on the main identifier of the main execution hierarchy according to the workflow diagram and the preset second configuration parameter. That is, the main identifier is created first, and then the sub-identifiers are created.
In one possible implementation manner of the embodiment of the present disclosure, the execution hierarchy may include not only a main execution hierarchy and a sub-execution hierarchy, but also a slave execution hierarchy, where the slave execution hierarchy is an execution hierarchy corresponding to a task element in the task node. At this time, when the current execution hierarchy is the slave execution hierarchy, the execution data is the task element execution result, and at this time, in the process of executing the workflow, the task element execution result of the slave execution hierarchy needs to be recorded into the preset storage space. That is, when the execution hierarchy further includes a slave execution hierarchy, in the execution process of the workflow task, according to the current execution hierarchy, the execution data generated by the execution hierarchy is recorded into a preset storage space, and the specific implementation process may be as follows:
and in the execution process of the workflow task, if the current execution level is a slave execution level, recording the task element execution result generated by the slave execution level to a slave storage space in the preset storage space.
Specifically, the task element refers to an execution step in the task node, for example, an execution step corresponding to an assignment statement, a four-rule operation, and the like; the slave execution hierarchy refers to an execution hierarchy corresponding to a task element in a task node; the slave storage space refers to a region in the preset storage space for storing the execution result of the task element generated from the execution hierarchy; the task element execution result refers to an execution result generated in the execution process of the current task element.
In practical application, in the process of executing workflow tasks composed of task nodes according to an execution sequence, if a current execution level is in a slave execution level, recording a task element execution result generated from the execution level in a slave storage space of a preset storage space. Thus, the record task element execution result is recorded in the slave storage space, and the atomicity, consistency, isolation and durability of workflow processing can be improved.
For example, in the execution process of the workflow task, the current execution level is the execution process of the second task element in the sub-execution level, that is, the second slave execution level, the execution result of the task element generated by the first slave execution level is 2=1+1, and then 2 is recorded in the slave storage space; in the execution process of the workflow task, the current execution hierarchy is the mth slave execution hierarchy in the slave execution hierarchies, the execution result of the task element generated by the mth slave execution hierarchy is i=1, and then 1 is recorded in the slave storage space.
Optionally, to further improve the atomicity, consistency, isolation, and durability of the workflow process, it is necessary to create a slave identifier for the slave execution hierarchy and to associate the slave identifier with the task element execution result when recording the task element execution result. That is, in the executing process of the workflow task, if the current execution level is a slave execution level, before recording the execution result of the task element generated from the slave execution level to the slave storage space in the preset storage space, the method further includes:
creating a slave identifier for the slave execution hierarchy according to the workflow diagram and a preset third configuration parameter;
Correspondingly, the recording the task element execution result generated from the execution hierarchy to the slave storage space in the preset storage space includes:
and associating and recording the task element execution result generated from the execution hierarchy and the slave identification to a slave storage space in the preset storage space.
Specifically, the third configuration parameter refers to a parameter for the slave execution hierarchy among preset execution parameters.
In practical application, after receiving the workflow diagram, when executing the workflow task composed of each task node, at the initial stage of executing the current sub-execution hierarchy, or before executing the workflow task composed of each task node, a unique sub-identifier may be created for the current task node based on the workflow diagram and a preset second configuration parameter, that is, a main identifier is created for the sub-execution hierarchy. Further, in the process of executing the workflow task, if the workflow task is in the sub-execution level, the task node execution result and the sub-identifier generated by the sub-execution level are associated and recorded in a storage area corresponding to the sub-execution level in the preset storage air, namely, a sub-storage space.
It should be noted that, according to the workflow diagram and the preset third configuration parameter, a slave identifier is created for the slave execution hierarchy, and a slave identifier may also be created for the slave execution hierarchy based on the sub-identifier of the sub-execution hierarchy according to the workflow diagram and the preset third configuration parameter. That is, a master identity is created first, then a child identity is created, and then a slave identity is created.
By setting the main execution level, the sub-execution level and the sub-execution level, the support for the transaction is increased, so that the whole workflow has atomicity, consistency, isolation and durability, the key control flow carried by the engine is ensured to be respectively controllable at the flow level, the sub-task level and the operator level, and the whole flow is ensured to be completely executed at the flow level, the sub-task level and the operator level.
In one possible implementation manner of the embodiments of the present disclosure, in order to improve the workflow processing efficiency, a workflow task may be divided into a plurality of subtasks, and each subtask is executed by each execution unit. That is, the workflow task formed by the task nodes is executed according to the execution sequence, and the specific implementation process may be as follows:
Dividing workflow tasks corresponding to the workflow diagram into a plurality of subtasks according to the execution sequence of each task node and sending the subtasks to execution units corresponding to each task node, wherein the subtasks are in one-to-one correspondence with the task nodes;
And processing subtasks corresponding to any execution unit in the execution units according to the execution sequence.
Specifically, the execution unit refers to a functional unit that processes subtasks corresponding to task nodes.
In practical application, on the basis of receiving the workflow diagram, the workflow tasks represented by the workflow diagram are divided into a plurality of subtasks according to the number of task nodes and the execution sequence of the task nodes, and each subtask is further sent to an execution unit corresponding to each task node. The execution unit executes the corresponding subtasks based on the execution sequence of the task nodes. In this way, the processing efficiency of the workflow can be improved.
For example, if there are 4 task nodes, the workflow task is divided into four sub-tasks, the first sub-task is sent to a first execution unit corresponding to the task node with the first execution order, the second sub-task is sent to a second execution unit corresponding to the task node with the second execution order, the third sub-task is sent to a third execution unit corresponding to the task node with the third execution order, and the fourth sub-task is sent to a fourth execution unit corresponding to the task node with the fourth execution order. Further, based on the execution order, the first execution unit processes the first subtask, the second execution unit processes the second subtask, the third execution unit processes the third subtask, and the fourth execution unit processes the fourth subtask.
The workflow processing method is further described below with reference to fig. 2. FIG. 2 shows a process flow diagram of a workflow processing method provided in one embodiment of the present disclosure. The workflow system uses a DAG (directed acyclic graph) to uniquely define a particular workflow and its execution. The control flow graph is stored in a relational database in different levels in the form of a domain specific language (DSL, domain-specific language), and an operational Operator is generated by using a dynamic compiling and dynamic unfolding technology at the time of operation and is calculated in a streaming mode:
1. When each workflow graph (DAG) is submitted, a transaction record is automatically created to generate a unique identifier (tid) of the transaction, that is, a master identifier is created for the workflow task, and the master transaction record is only one master identifier and is stored in a master transaction space (bkcs _transaction) corresponding to a master storage space (bkcs _statias_db_, bkcs _transaction_ accessor) in a preset storage space (bkcs _statias.
The main execution hierarchy mainly comprises: an initialization operation (initializer operator), namely an operator first (initialiazer), responsible for initializing transactions (init_trans) and starting transactions (begin_trans), and writing the master identity into the communication mechanism (xcom) between the distributed nodes during the lifecycle of this execution to propagate the master identity (tid) to the subsequent operation (operator); the first cooperative operation (coordinator operator), i.e., the first coordinator, is responsible for inheriting transactions (inheret_trans) and executing transactions (execution_trans); a finalization operation (finalizer operator), namely an operator last (finalizer), responsible for inheriting transactions (inhereit_trans), preparing transactions (preparation_trans) and committing transactions (commit_trans);
2. Sub-execution hierarchy, corresponding to transaction subspace: during execution, a workflow task may have a plurality of subtasks, that is, task operators (task) executing in parallel, that is, sub dag operator # (task), in order to avoid that the task operators change the context of a main transaction, a transaction subspace is separately generated for each task operator for use by the task operators, a plurality of transaction subspace records may be stored in a bkcs _stab_interfaces_b_interfaces_b_interfaces_sub_space table corresponding to bkcs _stab_operator.
The sub-execution hierarchy mainly comprises: task_operator, transaction sub-operation, sub dag operator # (task), is responsible for inheriting the transaction (inhereit_trans) and manipulating the transaction subspace (update transaction _sub_space).
For any subtask, generating the identifier of the subtask, such as tid 1s 1, tid 1s 2, tid 1s 3 and tid 1s 4, and storing the identifier in a sub-storage space (bkcs _stabilates. Db_access. Bkcs_transaction_sub_space) in a preset storage space (bkcs _stabilators. Operator. Bkcs_tran_ bsae _operator) in a transaction subspace (bkcs _transaction_sub_space) corresponding to the subtask.
3. From the execution hierarchy, the corresponding item table transaction space: because each item is different, the data cannot be stored by using the transaction subspace completely, and for the item expected to have the transaction characteristic, a tid field can be added in the item table, and when the data is written, the tid attribute is attached, so that the transaction capability is supported; the slave execution hierarchy mainly comprises various item operations (expressions), such as an operation input (expression input), an operation operator 1 (expression p 1), an operation operator 2 (expression p 2) and an operation output (expression output), and is responsible for attaching a tid attribute when outputting data.
For any slave task, a designated storage space is set, such as bkcs _ assets _a and bkcs_ assets _b, and identification of the directory slave task, such as tid1 v1, tid1 v2, tid1 v3 and tid1 v4, is generated based on the identification of the master task.
It should be noted that, the project table needs to be updated based on the identification of the master transaction, the master transaction or the transaction is the task, the transaction sub is the subtask, and the project operation is the slave task.
The specification provides a workflow processing method, which receives a workflow diagram, wherein the workflow diagram comprises a plurality of task nodes and an execution sequence of each task node; and executing the workflow tasks formed by the task nodes according to the execution sequence, and recording the execution data generated by the execution hierarchy to a preset storage space according to the current execution hierarchy in the execution process of the workflow tasks, wherein the execution process of the workflow tasks comprises a plurality of execution hierarchies. After using the flow computation for the generic workflow project, the compute scheduling integration engine supports a canonical on-line/off-line control-compute project. For the control workflow, by increasing the support of the transaction ACID characteristic on the basis of workflow processing, the efficiency of processing the workflow is improved, namely, by storing execution data in the general workflow processing process, the support of the transaction is increased, and the atomicity, consistency, isolation and durability of the workflow processing in the cross-site, cross-platform and cross-data source scenes are ensured. In addition, by setting the execution level, the granularity of the controllable workflow is controllable, so that the workflow processing method can be effectively applied to information security projects of the management and control whole network.
Corresponding to the above method embodiments, the present disclosure further provides an embodiment of a workflow processing apparatus, and fig. 3 shows a schematic structural diagram of a workflow processing apparatus according to one embodiment of the present disclosure. As shown in fig. 3, the apparatus includes:
a receiving module 302 configured to receive a workflow diagram, wherein the workflow diagram includes a plurality of task nodes, and an execution order of the task nodes;
The execution module 304 is configured to execute the workflow task formed by the task nodes according to the execution sequence, and record, in the execution process of the workflow task, the execution data generated by the execution hierarchy to a preset storage space according to a current execution hierarchy, where the execution process of the workflow task includes a plurality of execution hierarchies.
In one or more optional embodiments of the present disclosure, the execution hierarchy includes a main execution hierarchy, where the main execution hierarchy is an execution hierarchy corresponding to the workflow task;
The execution module 304 is further configured to:
And in the execution process of the workflow task, if the current execution level is a main execution level, recording a main execution state generated by the main execution level to a main storage space in the preset storage space.
In one or more alternative embodiments of the present specification, the main execution state includes at least one of an initialization state, an on state, an execution state, a ready state, and a commit state.
In one or more optional embodiments of the present specification, the apparatus further comprises a first creation module configured to:
Creating a main identifier for the main execution hierarchy according to the workflow diagram and a preset first configuration parameter;
The execution module 304 is further configured to:
and associating and recording the main execution state generated by the main execution hierarchy and the main identifier to a main storage space in the preset storage space.
In one or more optional embodiments of the present disclosure, the execution hierarchy further includes a sub-execution hierarchy, where the sub-execution hierarchy is an execution hierarchy corresponding to the task node;
The execution module 304 is further configured to:
and in the execution process of the workflow task, if the current execution level is a sub-execution level, recording a task node execution result generated by the sub-execution level to a sub-storage space in the preset storage space.
In one or more optional embodiments of the present specification, the apparatus further comprises a second creation module configured to:
creating a sub-identifier for the sub-execution hierarchy according to the workflow diagram and a preset second configuration parameter;
The execution module 304 is further configured to:
and the task node execution result generated by the sub-execution hierarchy and the sub-identifier are recorded in a sub-storage space in the preset storage space in an associated mode.
In one or more optional embodiments of the present disclosure, the execution hierarchy further includes a slave execution hierarchy, where the slave execution hierarchy is an execution hierarchy corresponding to a task element in the task node;
The execution module 304 is further configured to:
and in the execution process of the workflow task, if the current execution level is a slave execution level, recording the task element execution result generated by the slave execution level to a slave storage space in the preset storage space.
In one or more optional embodiments of the present specification, the apparatus further comprises a third creation module configured to:
creating a slave identifier for the slave execution hierarchy according to the workflow diagram and a preset third configuration parameter;
The execution module 304 is further configured to:
and associating and recording the task element execution result generated from the execution hierarchy and the slave identification to a slave storage space in the preset storage space.
In one or more alternative embodiments of the present disclosure, the execution module 304 is further configured to:
Dividing workflow tasks corresponding to the workflow diagram into a plurality of subtasks according to the execution sequence of each task node and sending the subtasks to execution units corresponding to each task node, wherein the subtasks are in one-to-one correspondence with the task nodes;
And processing subtasks corresponding to any execution unit in the execution units according to the execution sequence.
The embodiment of the specification provides a workflow processing device, which receives a workflow diagram, wherein the workflow diagram comprises a plurality of task nodes and an execution sequence of each task node; and executing the workflow tasks formed by the task nodes according to the execution sequence, and recording the execution data generated by the execution hierarchy to a preset storage space according to the current execution hierarchy in the execution process of the workflow tasks, wherein the execution process of the workflow tasks comprises a plurality of execution hierarchies. After using the flow computation for the generic workflow project, the compute scheduling integration engine supports a canonical on-line/off-line control-compute project. For the control workflow, by increasing the support of the transaction ACID characteristic on the basis of workflow processing, the efficiency of processing the workflow is improved, namely, by storing execution data in the general workflow processing process, the support of the transaction is increased, and the atomicity, consistency, isolation and durability of the workflow processing in the cross-site, cross-platform and cross-data source scenes are ensured. In addition, by setting the execution level, the granularity of the controllable workflow is controllable, so that the workflow processing device can be effectively applied to information security projects of the management and control whole network.
The above is a schematic solution of a workflow processing apparatus of the present embodiment. It should be noted that, the technical solution of the workflow processing apparatus and the technical solution of the workflow processing method belong to the same concept, and details of the technical solution of the workflow processing apparatus, which are not described in detail, can be referred to the description of the technical solution of the workflow processing method.
Fig. 4 illustrates a block diagram of a computing device 400 provided by one embodiment of the present description. The components of the computing device 400 include, but are not limited to, a memory 410 and a processor 420. Processor 420 is coupled to memory 410 via bus 430 and database 450 is used to hold data.
Computing device 400 also includes access device 440, access device 440 enabling computing device 400 to communicate via one or more networks 460. Examples of such networks include public switched telephone networks (PSTN, public Switched Telephone Network), local area networks (LAN, local Area Network), wide area networks (WAN, wide Area Network), personal area networks (PAN, personal Area Network), or combinations of communication networks such as the internet. The access device 440 may include one or more of any type of network interface, wired or wireless, such as a network interface card (NIC, network Interface Controller), such as an IEEE802.11 wireless local area network (WLAN, wireless Local Area Network) wireless interface, a worldwide interoperability for microwave access (Wi-MAX, worldwide Interoperability for Microwave Access) interface, an ethernet interface, a universal serial bus (USB, universal Serial Bus) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.
In one embodiment of the present description, the above-described components of computing device 400, as well as other components not shown in FIG. 4, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device shown in FIG. 4 is for exemplary purposes only and is not intended to limit the scope of the present description. Those skilled in the art may add or replace other components as desired.
Computing device 400 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smart phone), wearable computing device (e.g., smart watch, smart glasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 400 may also be a mobile or stationary server.
Wherein the processor 420 is configured to execute computer-executable instructions that, when executed by the processor, perform the steps of the workflow processing method described above.
The foregoing is a schematic illustration of a computing device of this embodiment. It should be noted that, the technical solution of the computing device and the technical solution of the workflow processing method belong to the same concept, and details of the technical solution of the computing device, which are not described in detail, can be referred to the description of the technical solution of the workflow processing method.
An embodiment of the present disclosure also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the workflow processing method described above.
The above is an exemplary version of a computer-readable storage medium of the present embodiment. It should be noted that, the technical solution of the storage medium and the technical solution of the workflow processing method belong to the same concept, and details of the technical solution of the storage medium which are not described in detail can be referred to the description of the technical solution of the workflow processing method.
An embodiment of the present disclosure further provides a computer program, where the computer program, when executed in a computer, causes the computer to perform the steps of the workflow processing method described above.
The above is an exemplary version of a computer program of the present embodiment. It should be noted that, the technical solution of the computer program and the technical solution of the workflow processing method belong to the same conception, and details of the technical solution of the computer program which are not described in detail can be referred to the description of the technical solution of the workflow processing method.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The computer instructions include computer program code that may be in source code form, object code form, executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth.
It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of combinations of actions, but it should be understood by those skilled in the art that the embodiments are not limited by the order of actions described, as some steps may be performed in other order or simultaneously according to the embodiments of the present disclosure. Further, those skilled in the art will appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily all required for the embodiments described in the specification.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to the related descriptions of other embodiments.
The preferred embodiments of the present specification disclosed above are merely used to help clarify the present specification. Alternative embodiments are not intended to be exhaustive or to limit the invention to the precise form disclosed. Obviously, many modifications and variations are possible in light of the teaching of the embodiments. The embodiments were chosen and described in order to best explain the principles of the embodiments and the practical application, to thereby enable others skilled in the art to best understand and utilize the invention. This specification is to be limited only by the claims and the full scope and equivalents thereof.

Claims (12)

1. A workflow processing method, comprising:
Receiving a workflow diagram, wherein the workflow diagram comprises a plurality of task nodes and an execution sequence of each task node;
And executing the workflow tasks formed by the task nodes according to the execution sequence, and recording the execution data generated by the execution hierarchy to a preset storage space corresponding to the execution hierarchy according to the current execution hierarchy in the execution process of the workflow tasks, wherein the execution process of the workflow tasks comprises a plurality of execution hierarchies, and the plurality of execution hierarchies comprise a main execution hierarchy corresponding to the workflow tasks, a sub-execution hierarchy corresponding to the task nodes and a slave execution hierarchy corresponding to task elements in the task nodes.
2. The method according to claim 1, wherein in the process of executing the workflow task, according to a current execution hierarchy, recording the execution data generated by the execution hierarchy into a preset storage space corresponding to the execution hierarchy, includes:
And in the execution process of the workflow task, if the current execution level is a main execution level, recording a main execution state generated by the main execution level to a main storage space in the preset storage space.
3. The method of claim 2, the master execution state comprising at least one of an initialization state, an on state, an execution state, a ready state, and a commit state.
4. The method according to claim 2, wherein during the execution of the workflow task, if the current execution level is a main execution level, before recording the main execution state generated by the main execution level to the main storage space in the preset storage space, further comprises:
Creating a main identifier for the main execution hierarchy according to the workflow diagram and a preset first configuration parameter;
The recording the main execution state generated by the main execution hierarchy to the main storage space in the preset storage space includes:
and associating and recording the main execution state generated by the main execution hierarchy and the main identifier to a main storage space in the preset storage space.
5. The method according to claim 2, wherein in the process of executing the workflow task, according to a current execution hierarchy, recording the execution data generated by the execution hierarchy into a preset storage space corresponding to the execution hierarchy, includes:
and in the execution process of the workflow task, if the current execution level is a sub-execution level, recording a task node execution result generated by the sub-execution level to a sub-storage space in the preset storage space.
6. The method according to claim 5, wherein during the execution of the workflow task, if the current execution level is a sub-execution level, before recording the task node execution result generated by the sub-execution level to the sub-storage space in the preset storage space, further comprises:
creating a sub-identifier for the sub-execution hierarchy according to the workflow diagram and a preset second configuration parameter;
The recording the task node execution result generated by the sub-execution hierarchy to the sub-storage space in the preset storage space includes:
and the task node execution result generated by the sub-execution hierarchy and the sub-identifier are recorded in a sub-storage space in the preset storage space in an associated mode.
7. The method according to claim 5, wherein during the execution of the workflow task, recording the execution data generated by the execution hierarchy to the preset storage space corresponding to the execution hierarchy according to the current execution hierarchy, includes:
and in the execution process of the workflow task, if the current execution level is a slave execution level, recording the task element execution result generated by the slave execution level to a slave storage space in the preset storage space.
8. The method according to claim 7, wherein during the execution of the workflow task, if the current execution hierarchy is a slave execution hierarchy, before recording the execution result of the task element generated from the slave execution hierarchy to the slave storage space in the preset storage space, further comprises:
creating a slave identifier for the slave execution hierarchy according to the workflow diagram and a preset third configuration parameter;
the recording the task element execution result generated from the execution hierarchy to the slave storage space in the preset storage space comprises the following steps:
and associating and recording the task element execution result generated from the execution hierarchy and the slave identification to a slave storage space in the preset storage space.
9. The method according to claim 1, wherein said executing the workflow task composed of the task nodes according to the execution order comprises:
Dividing workflow tasks corresponding to the workflow diagram into a plurality of subtasks according to the execution sequence of each task node and sending the subtasks to execution units corresponding to each task node, wherein the subtasks are in one-to-one correspondence with the task nodes;
And processing subtasks corresponding to any execution unit in the execution units according to the execution sequence.
10. A workflow processing apparatus comprising:
A receiving module configured to receive a workflow graph, wherein the workflow graph includes a plurality of task nodes, and an execution order of the task nodes;
The execution module is configured to execute the workflow tasks formed by the task nodes according to the execution sequence, and record the execution data generated by the execution hierarchy to a preset storage space corresponding to the execution hierarchy according to the current execution hierarchy in the execution process of the workflow tasks, wherein the execution process of the workflow tasks comprises a plurality of execution hierarchies, and the plurality of execution hierarchies comprise a main execution hierarchy corresponding to the workflow tasks, a sub-execution hierarchy corresponding to the task nodes and a slave execution hierarchy corresponding to task elements in the task nodes.
11. A computing device, comprising:
a memory and a processor;
the memory is configured to store computer executable instructions, and the processor is configured to execute the computer executable instructions, which when executed by the processor, implement the steps of the workflow processing method of any one of claims 1 to 9.
12. A computer readable storage medium storing computer executable instructions which when executed by a processor implement the steps of the workflow processing method of any one of claims 1 to 9.
CN202210269882.6A 2022-03-18 2022-03-18 Workflow processing method and device Active CN114625509B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210269882.6A CN114625509B (en) 2022-03-18 2022-03-18 Workflow processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210269882.6A CN114625509B (en) 2022-03-18 2022-03-18 Workflow processing method and device

Publications (2)

Publication Number Publication Date
CN114625509A CN114625509A (en) 2022-06-14
CN114625509B true CN114625509B (en) 2024-09-27

Family

ID=81901953

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210269882.6A Active CN114625509B (en) 2022-03-18 2022-03-18 Workflow processing method and device

Country Status (1)

Country Link
CN (1) CN114625509B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111897815A (en) * 2020-07-15 2020-11-06 中国建设银行股份有限公司 Service processing method and device

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040044648A1 (en) * 2002-06-24 2004-03-04 Xmyphonic System As Method for data-centric collaboration
JP3913686B2 (en) * 2003-02-13 2007-05-09 株式会社クレオ Workflow route calculation system and route calculation method
US7337950B2 (en) * 2003-07-28 2008-03-04 Devault Ricky W Transaction workflow and data collection system
US8683027B2 (en) * 2011-06-08 2014-03-25 International Business Machines Corporation Utilization of uncertainty dependency relationships between items in a data stream
US9952899B2 (en) * 2014-10-09 2018-04-24 Google Llc Automatically generating execution sequences for workflows
JP7215710B2 (en) * 2018-10-10 2023-01-31 国立研究開発法人物質・材料研究機構 Prediction management system, prediction management method, prediction management device and prediction execution device
CN112069367A (en) * 2020-09-07 2020-12-11 上海金仕达软件科技有限公司 Task scheduling method and system
CN112416535B (en) * 2020-11-24 2023-12-22 中国工商银行股份有限公司 Distributed transaction processing method and system

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111897815A (en) * 2020-07-15 2020-11-06 中国建设银行股份有限公司 Service processing method and device

Also Published As

Publication number Publication date
CN114625509A (en) 2022-06-14

Similar Documents

Publication Publication Date Title
US11487536B2 (en) System for automating user-defined actions for applications executed using virtual machines in a guest system
US8966485B2 (en) Realizing jumps in an executing process instance
EP3931684B1 (en) Workflow engine tool
CN110888736A (en) Application management method and system based on container cloud platform and related components
Puttonen et al. Planning-based semantic web service composition in factory automation
CN113094125B (en) Business process processing method, device, server and storage medium
Zhang et al. A multi-level self-adaptation approach for microservice systems
CN109885580A (en) A kind of hot spot account batch updating method, apparatus, server and storage medium
CN114625509B (en) Workflow processing method and device
Cai et al. SMSS: Stateful Model Serving in Metaverse With Serverless Computing and GPU Sharing
CN113126961B (en) Pipeline processing method, device and storage medium
CN109669671B (en) Multi-level self-adaptive method based on micro-service
CN117350654A (en) Dynamic configuration method, system, electronic equipment and storage medium for auditor information
Cai et al. Deployment and verification of machine learning tool-chain based on kubernetes distributed clusters: This paper is submitted for possible publication in the special issue on high performance distributed computing
CN110782040A (en) Method, device, equipment and medium for training tasks of pitorch
Farhat et al. Safe Dynamic Reconfiguration of Concurrent Component-based Applications
CN114493493A (en) Decision engine and decision engine implementation method
CN114490694A (en) Business rule processing method and device, server and storage medium
US11907688B2 (en) System and method for a heterogenous software platform
CN114780175A (en) Configuration information generation method and device
CN107145372A (en) information generating method and device
Jacob et al. Simplifying the development and deployment of MapReduce algorithms
Donvir et al. Accelerating Product Innovation: Impact of Serverless Computing and Generative AI on Application Development
CN116450294A (en) Method and system for realizing management of cloud native application instance management architecture
CN118586375A (en) Text generation method, device and system, computing device and readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant