Service publishing method and device

Abstract

The invention provides a service publishing method and equipment, and the specific implementation scheme comprises the steps: obtaining a target task flow determined for a target scene task, responding to a running operation triggered for the target task flow, determining a to-be-executed task operator in the target task flow according to an execution sequence, and sending the to-be-executed task operator to a server; calling an input resource service associated with the to-be-executed task operator to execute the to-be-executed task operator to obtain a first execution result; determining a first target input data identifier and a resource service type corresponding to first target input data represented by the first target input data identifier according to configuration information of a downstream task operator connected with the to-be-executed task operator; and according to a resource service type corresponding to the first target input data, performing service release on the first target output data in the first execution result to convert the first target output data into a first resource service, the first resource service being used for executing a downstream task operator.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a service publishing method, computer equipment, storage medium, computer program product, and data processing system. Background Technology

[0002] To ensure efficient execution of business scenario tasks, these tasks are typically orchestrated into task flows comprising multiple operator nodes, and automated processing is achieved through the execution of these task flows. During the execution of the task flow, the input and output data of each operator node can flow in the form of service resources. Summary of the Invention

[0003] This invention provides a service publishing method, a computer device, a storage medium and a computer program product, and a data processing system.

[0004] According to one aspect of the present invention, a service publishing method is provided, comprising: obtaining a target task flow determined for a target scenario task, the target task flow including multiple task operators, an execution order among the multiple task operators, at least one input resource service associated with the multiple task operators, and configuration information of each task operator; responding to a run operation triggered for the target task flow, determining a task operator to be executed in the target task flow according to the execution order, and calling an input resource service associated with the task operator to be executed to execute the task operator to obtain a first execution result, the first execution result including at least one first output data; determining a first target input data identifier and a resource service type corresponding to the first target input data represented by the first target input data identifier according to the configuration information of a downstream task operator connected to the task operator to be executed, wherein the first target input data is input data received by the downstream task operator from the task operator to be executed; and publishing a service for the first target output data in the first execution result according to the resource service type corresponding to the first target input data, so as to convert the first target output data into a first resource service, wherein the first target output data is the first output data flowing from the task operator to the downstream task operator, and the first resource service is used to execute the downstream task operator.

[0005] According to another aspect of the present invention, a computer device is provided, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform a service publishing method as described above.

[0006] According to another aspect of the present invention, a computer-readable storage medium is provided having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the service publishing method as described above.

[0007] According to another aspect of the present invention, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the service publishing method as described above.

[0008] According to another aspect of the present invention, a data processing system is provided, comprising: a data orchestration module, configured to acquire a target task flow determined for a target scenario task, the target task flow including multiple task operators, an execution order among the multiple task operators, at least one input resource service associated with the multiple task operators, and configuration information for each task operator; in response to a run operation triggered for the target task flow, determining the task operators to be executed in the target task flow according to the execution order, and calling the input resource service associated with the task operators to be executed to execute the task operators to obtain a first execution result, the first execution result including at least one first output data; and according to the task operators to be executed... The configuration information of the connected downstream task operators determines the first target input data identifier and the resource service type corresponding to the first target input data represented by the first target input data identifier. The first target input data is the input data received by the downstream task operator from the task operator to be executed. The data management module, which is communicatively connected to the data orchestration module, is used to publish the first target output data in the first execution result according to the resource service type corresponding to the first target input data, so as to convert the first target output data into a first resource service. The first target output data is the first output data flowing from the task operator to be executed to the downstream task operator, and the first resource service is used to execute the downstream task operator. Attached Figure Description

[0009] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly described below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0010] Figure 1 This is a flowchart of a service publishing method according to an embodiment of the present invention;

[0011] Figure 2A This is a schematic diagram of the interactive interface according to an embodiment of the present invention;

[0012] Figure 2BThe diagram illustrates the first UI interaction interface of the first operator component, the second UI interaction interface of the second operator component, and the third UI interaction interface of the data resource component displayed in the main interface.

[0013] Figure 2C Schematic illustration based on Figure 2B A schematic diagram of the orchestration structure determined by multiple target resource components;

[0014] Figure 3 This is a block diagram of a data processing system according to an embodiment of the present invention;

[0015] Figure 4 This is a block diagram of a computer device suitable for implementing a service publishing method according to an embodiment of the present invention. Detailed Implementation

[0016] The technical solutions of the present invention will be clearly and completely described below with reference to the embodiments and accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention are within the scope of protection of the present invention.

[0017] It should be noted that the sequence numbers of each operation in the following methods are only for descriptive purposes and should not be considered as indicating the execution order of the operations. Unless explicitly stated otherwise, the method does not need to be executed in the exact order shown. Furthermore, in the description of this invention, terms such as "first," "second," etc. (if present) are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance.

[0018] In the technical solution of this invention, the collection, storage, use, processing, transmission, provision, disclosure, and application of data (including but not limited to user personal information) comply with the relevant laws and regulations of the relevant countries and regions, and do not violate public order and good morals. Furthermore, in the technical solution of this invention, authorization or consent from the data owner is obtained before acquiring or collecting any relevant data.

[0019] Figure 1 This is a flowchart of a service publishing method according to an embodiment of the present invention.

[0020] like Figure 1 As shown, the service publishing method 100 includes operations S110 to S140. The service publishing method of this embodiment can be executed by a computer device. For example, a data processing system is installed on the computer device. For instance, the computer device can be used to implement the service publishing method of this embodiment based on the data processing system.

[0021] In operation S110, the target task flow determined for the target scenario task is obtained. The target task flow includes multiple task operators, the execution order between the multiple task operators, at least one input resource service associated with the multiple task operators, and the configuration information of each task operator.

[0022] In operation S120, in response to the run operation triggered for the target task flow, the task operator to be executed in the target task flow is determined according to the execution order, and the input resource service associated with the task operator to be executed is called to execute the task operator to obtain a first execution result, the first execution result including at least one first output data.

[0023] In operation S130, based on the configuration information of the downstream task operator connected to the task operator to be executed, a first target input data identifier and the resource service type corresponding to the first target input data represented by the first target input data identifier are determined, wherein the first target input data is the input data received by the downstream task operator from the task operator to be executed.

[0024] In operation S140, according to the resource service type corresponding to the first target input data, the first target output data in the first execution result is published as a service to convert the first target output data into a first resource service. The first target output data is the first output data flowing from the task operator to the downstream task operator, and the first resource service is used to execute the downstream task operator.

[0025] According to embodiments of the present invention, a target task flow can be used to execute a target scenario task. The target task flow may, for example, be pre-stored by a computer device, and is generated by determining the configuration information of each target resource component and an orchestration structure containing multiple target resource components through configuration and orchestration operations triggered for multiple target resource components associated with the target scenario task, and based on the orchestration structure and the configuration information of each target resource component. Alternatively, the target task flow is generated by a computer device based on operations of configuring and orchestrating multiple target resource components associated with the target scenario task, determining the configuration information of each target resource component and an orchestration structure containing multiple target resource components, and based on the orchestration structure and the configuration information of each target resource component. In some embodiments, the target task flow may also be obtained by a computer device based on a user's import operation, and is generated by determining the configuration information of each target resource component and an orchestration structure containing multiple target resource components through configuration and orchestration operations triggered for multiple target resource components associated with the target scenario task, and based on the orchestration structure and the configuration information of each target resource component. Here, configuration information refers to the configuration parameters used to define the target resource components. This configuration information includes, for example, operator parameter configuration information, data resource parameter configuration information, and operator flow relationships. The orchestration structure can be used to indicate the execution order among multiple target resource components. Both configuration information and orchestration structure can influence the execution order and logic of task operators during the subsequent execution of the target task flow.

[0026] For example, the target task flow corresponding to the target scenario task can be obtained based on a data processing system. For instance, the configuration and orchestration operations triggered for multiple target resource components associated with the target scenario task can be performed in an interactive interface. This interactive interface can be an interface presented within the data processing system. In this interactive interface, the computer device can generate the target task flow in response to the configuration and orchestration operations triggered for multiple target resource components associated with the target scenario task.

[0027] For example, the user interface includes a resource component list and a main interface. The resource component list provides multiple operator components and multiple data resource components.

[0028] Each operator component can be an independent operator with a single business processing capability, or a scenario operator with scenario task processing capability. A scenario operator is obtained by orchestrating and encapsulating multiple independent operators. Each operator component corresponds to one operator task. The resource component list can include various types of operator components, such as data output, data transformation, data cleaning, data quality inspection, data repair, spatial analysis, model training, and graphics processing.

[0029] Each data resource component corresponds to a set of data resource services, and this set of data resource services is associated with a data resource. These data resource services and data resources can, for example, be pre-stored in the data processing system. Here, a data resource service refers to providing access to, management of, and interaction with data resources (such as data resources stored locally and / or data resources in external databases) in the form of a service. If a data resource component is connected to an operator component, the data resource component can provide the corresponding data resource services to the operator component, enabling the operator component to invoke the corresponding data resource services to execute the corresponding operator task.

[0030] The main interface is a visual interface for orchestrating and configuring resource components and target task flows. Users can drag multiple target resource components associated with the target scenario task from the resource component list to the main interface. Based on this drag-and-drop operation, the computer device displays multiple target resource components on the main interface. These multiple target resource components may include, for example, multiple operator components and at least one data resource component, or they may include, for example, only at least two operator components. Each operator component and each data resource component can be displayed as a UI on the main interface. The computer device can obtain the operator parameter configuration information of each operator component based on the user's configuration operations on that operator component. Furthermore, based on the user's orchestration operations on the multiple target resource components in the main interface, the computer device can determine the orchestration structure containing the multiple target resource components and the configuration information of each target resource component other than the operator parameter configuration information, and automatically generate the target task flow based on the orchestration structure and the configuration information of each target resource component.

[0031] In addition, the aforementioned interactive interface also includes import controls and run controls. The computer device can respond to the user's triggering operation on the import control, obtain the target task flow associated with the target scenario task, and display the target task flow on the main interface. When the target task flow is displayed on the main interface, the computer device can also respond to the user's triggering operation on the run control, calling the input resource service associated with the target task flow to execute the target task flow.

[0032] The following is for reference. Figures 2A to 2C The process of obtaining the target task flow is illustrated by an example.

[0033] First, the interactive interface is displayed, which includes a list of resource components and a main interface. The list of resource components includes multiple operator components and multiple data resource components, while the main interface is used to configure and orchestrate operator components and data resource components.

[0034] Figure 2A A schematic diagram of an interactive interface is provided. For example... Figure 2A As shown, the interactive interface may include a resource component list 21 and a main interface 22.

[0035] The resource component list 21 can be displayed, for example, at the edge of the interactive interface or on top of the main interface 22. The resource component list 21 includes multiple operator components and multiple data resource components. Each operator component can be an independent operator with a single business processing capability, or a scene operator with scene task processing capability. Independent operators and scene operators can be displayed separately (e.g., ...). Figure 2A The resource component list 21 can be displayed as "operator" and "scenario" respectively, or they can be displayed together. Each operator component corresponds to an operator task. Each data resource component corresponds to a set of data resource services, and a set of data resource services is associated with a data resource. The data resource can be used as input data for the operator component. In some embodiments, the resource component list 21 may also include an input box 211 and a search control 212. Users can enter a description of their desired resource component (e.g., an operator component or a data resource component) in the input box 211. After the user enters a description of their desired resource component in the input box 211, the computer device can perform subsequent operations in response to the user's operation on the search control 212 (e.g., clicking the search control 212). The resource component list 21 may also include a hidden control. The computer device can control the resource component list 21 to switch between a displayed state and a hidden state in response to the user's triggering operation on the hidden control, thereby improving the user experience.

[0036] The main interface 22 is a visual interface for orchestrating and configuring resource components and target task flows. Users can drag resource components (such as operator components and / or data resource components) from the resource component list 21 to the main interface 22. Based on the user's drag operation, the computer device displays the selected resource component in the main interface 22. Users can configure each operator component displayed in the main interface 22, and the computer device can obtain or change the operator parameter configuration information of the operator component in response to the user's configuration operation on the main interface 22. Users can also indicate the execution order and execution logic between two resource components (such as two operator components) by connecting any two resource components in the main interface 22, and configure the input / output data resource parameters of each of the two resource components. In response to the connection operation for the two resource components, the computer device can determine the input / output data resource parameters of each of the two resource components, display the connection line connecting the two resource components, and determine and store the execution order and execution logic of the two resource components based on the connection line. Additionally, the computer device can respond to a user's dragging operation on a resource component (such as an operator component and / or a data resource component) in the main interface 22, and move the position of the resource component in the main interface 22 according to the dragging operation. Furthermore, the computer device can also respond to a user's deletion operation on a resource component (such as an operator component and / or a data resource component) in the main interface 22, and delete the resource component from the main interface 22. If the resource component has a connection line with other resource components, the connection line is deleted simultaneously.

[0037] In some embodiments, the interactive interface may further include a display area 23 for displaying a thumbnail of the main interface 22. The display area 23 may be displayed, for example, at the edge of the interactive interface or above the main interface 22, but without overlapping with the location of the resource component list 21. In other embodiments, the display area 23 may also include a selection box 231. The computer device may, in response to a user's dragging operation on the selection box 231 within the display area 23, move the position of the main interface 22 displayed according to the dragging operation to adapt to the position of the selection box 231 shown in the display area 23.

[0038] In some embodiments, the interactive interface may further include a drop-down list option located on one side of the display area 23 for user selection. The computer device may, in response to a user's action on the drop-down list (e.g., clicking a drop-down option), display the names of at least one resource component located in the main interface 22 for user selection. After the user selects a resource component name from the displayed at least one resource component name, the computer device may, in response to the user's selection, locate the corresponding resource component in the main interface 22 and display a prompt.

[0039] In some embodiments, the interactive interface further includes an import control 241, a save control 242, and a run control 243. The computer device can, in response to a user's trigger operation on the import control 241, acquire the target task flow determined by the user for the target scenario task, and display the target task flow on the main interface 22. After the user completes the arrangement of the target task flow on the main interface 22, the computer device can also, in response to a user's trigger operation on the save control 242, store the target task flow. The computer device can also, in response to a user's trigger operation on the run control 243, invoke data resource services associated with the target task flow to execute the target task flow.

[0040] Next, in response to the operation of dragging multiple target resource components associated with the target scene task from the resource component list to the main interface, multiple target resource components are displayed on the main interface.

[0041] Users can drag multiple target resource components related to the target scenario task from the resource component list 21 to the main interface 22. The computer device responds to the user's dragging operation and displays the multiple target resource components on the main interface 22. These multiple target resource components may include, for example, at least one first operator component, at least one second operator component, and at least one data resource component, or they may include, for example, at least one first operator component and at least one second operator component. The first operator component refers to any operator component in the resource component list 21 other than the data output operator component, and the second operator component refers to the data output operator component. Each first operator component is used to perform operator tasks other than data storage based on input data. Each second operator component is used to store the data output by the first operator component connected to it. Each data resource component in the at least one data resource component corresponds to a set of input resource services, and each set of input resource services is associated with one input data. When multiple target resource components include at least one first operator component, at least one second operator component, and at least one data resource component, the at least one data resource component can provide at least one input data to the at least one first operator component. When multiple target resource components include at least one first operator component and at least one second operator component, the input data of each first operator component and each second operator component can be configured through configuration operations. For example, for the first operator component, the resource service address of the input resource service corresponding to the input data of the first operator component can be obtained by configuring the operator parameter configuration information of the first operator component, and then the input data of the first operator component can be obtained according to the resource service address of the input resource service.

[0042] Each target resource component is displayed as a UI interface in the main interface 22. That is, each target resource component displayed in the main interface 22 has at least one UI control that can respond to user actions. Users can view, configure, and orchestrate the target resource components based on the UI controls in the UI interface.

[0043] In this embodiment of the invention, the first operator component can be displayed as a first UI interaction interface on the main interface 22. The second operator component can be displayed as a second UI interaction interface on the main interface 22. The data resource component can be displayed as a third UI interaction interface on the main interface 22.

[0044] For example, such as Figure 2B As shown, the main interface 22 displays the UI interaction interfaces of multiple target resource components, such as the first UI interaction interface of the first operator component 10, the first UI interaction interface of the first operator component 20, the second UI interaction interface of the second operator component 30, the third UI interaction interface of data resource component A, and the third UI interaction interface of data resource component B.

[0045] The following section uses the first UI interaction interface of the first operator component 10, the second UI interaction interface of the second operator component 30, and the third UI interaction interface of the data resource component A as examples to introduce the first UI interaction interface, the second UI interaction interface, and the third UI interaction interface.

[0046] like Figure 2B As shown, the first UI interaction interface of the first operator component 10 may include, for example, a first region 2131 and a second region 2132.

[0047] The first area 2131 includes a configuration control, a first input connection control, and a first output connection control.

[0048] The configuration control is used to view or configure the operator parameter configuration information of the first operator component 10. The operator parameter configuration information is used to define the operator parameters of the first operator component 10. Here, operator parameters may include, for example, at least one input data resource parameter, at least one output data resource parameter, and other parameters. Operator parameters may be pre-set. Operator parameter configuration information may include, for example, operator parameter category, parameter value acquisition method, configuration information for parameter values, and resource service type corresponding to the parameter values. Operator parameter types may include, for example, service-oriented parameters, enumerated parameters, etc. Parameter value acquisition methods may include, for example, obtaining values ​​from the output of other nodes and obtaining values ​​by configuring fixed values. When the parameter value is obtained from the output of other nodes, the configuration information for the parameter value may include, for example, the component name of the resource component providing the parameter value, the output data identifier of the output data used as the parameter value in all output data of the resource component (such as other first operator components connected to the first operator component 10), or the data resource service identifier corresponding to the input data used as the parameter value provided by the resource component (such as a data resource component). When the parameter value is obtained by configuring a fixed value, the configuration information for the parameter value may include, for example, the resource service address of the input resource service used to obtain the parameter value, or the restriction parameters for the parameter value.

[0049] The first input connection control and the first output connection control of the first operator component 10 are respectively used to connect to the first output connection control and the first input connection control of other first operator components (such as the first operator component 20) to determine the operator flow relationship between the first operator component 10 and other first operator components. The operator flow relationship is used to characterize the execution order when there is no data resource flow relationship between the first operator component 10 and other first operator components (i.e., there is no data input / output relationship between the first operator component 10 and other first operator components). The first area 2131 also displays the component name of the first operator component 10, such as "first operator 10".

[0050] The second area 2132 displays at least one input data resource parameter and at least one output data resource parameter of the first operator component 10. Each input data resource parameter includes an input data identifier, an input data type, etc. The input data identifier represents the input data, and the input data type indicates the data type of the input data (e.g., vector, raster, etc.). For example, the input data identifier "input 11" represents input data 11, and the input data type "input type 11" indicates that the data type of input data 11 is input type 11. Each output data resource parameter includes an output data identifier, an output data type, etc. The output data identifier represents the output data, and the output data type indicates the data type of the output data (e.g., vector, raster, etc.). For example, the output data identifier "output 11" represents output data 11, and the output data type "output type 11" indicates that the data type of output data 11 is output type 11. In some embodiments, attribute identifiers can also be used to indicate the importance of each input data resource parameter and each output data resource parameter. For example, the attribute identifier "asterisk" can be used to identify the input data resource parameters and output data resource parameters necessary for the operation of the first operator component 10, so that the user can identify and select them. It should be understood that the attribute identifiers are not limited to the examples above, and can be set according to actual needs. This invention does not limit them.

[0051] The second region 2132 also includes a second input connection control corresponding to each input data resource parameter and a second output connection control corresponding to each output data resource parameter. Each second input connection control of the first operator component 10 can be connected to the second output connection control of other first operator components or to a data resource component, so that the first operator component 10 can receive data resources from other first operator components or data resource components. Each second output connection control of the first operator component 10 can be connected to the second input connection control of other first operator components or to a second operator component, so that the first operator component 10 can transfer the output data resource to the next first operator component that needs the data resource, or transfer it to the second operator component for data storage. Based on the second input connection control and the second output connection control, the first operator component 10 can interact with other operator components or data resource components, thereby establishing a data resource transfer relationship between target resource components.

[0052] Please continue to refer to this. Figure 2BAs shown, the second UI interface of the second operator component 30 includes, for example, a third area 2133 and an output configuration control 2134. The third area 2133 includes a third input connection control. This third input connection control connects the second operator component 30 to the second output connection control of the first operator component (such as the first operator component 20), enabling the second operator component 30 to receive output data from the first operator component. The output configuration control 2134 is used to configure the storage path of the output data. The third area 2133 also displays the component name of the second operator component 30, for example, the component name of the second operator component 30 is "Second Operator 30".

[0053] Please continue to refer to this. Figure 2B As shown, the third UI interaction interface of data resource component A may include, for example, a fourth area 2141 and a fifth area 2142. The fourth area 2141 displays the component name of data resource component A, for example, the component name of data resource component A is "Data Input A". The fifth area 2142 displays data resource service information associated with data resource component A, such as a data resource service identifier and a data resource service type. The data resource service identifier represents an input resource service, and the data resource service type indicates the type of input data associated with the input resource service (such as table, vector, raster, etc.). For example, the data resource service identifier "Resource A" represents input resource service A, and the data resource service type "Resource Type a" indicates that the data type of the input data associated with input resource service A is resource type a. The fifth area 2142 also includes a fourth output connection control and a viewing control. The fourth output connection control is used to connect data resource component A to the second input connection control of a first operator component (such as first operator component 10), so that the first operator component can receive input data from data resource component A. The view control is used to display the input data associated with data resource component A. When a user triggers the view control, the computer device can respond to the user's triggering action by displaying the data resource interface for the user to view.

[0054] Next, in response to the operation of configuring and orchestrating multiple target resource components in the main interface, the configuration information of each target resource component is determined, and the orchestration structure containing multiple target resource components is displayed in the main interface.

[0055] In this embodiment of the invention, the configuration information of the first operator component includes, for example, the configuration information of the first operator parameters, the configuration information of the first data resource parameters, and the operator flow relationship.

[0056] For example, a user can configure the first operator parameter configuration information of the first operator component by triggering the configuration control in the first area. The computer device can display a configuration interface in response to the user's triggering operation (e.g., a click operation) of the configuration control, allowing the user to configure the first operator parameter configuration information of the first operator component. After the user completes the configuration, the computer device can obtain and store the first operator parameter configuration information of the first operator component. The first operator parameter configuration information includes, but is not limited to, information such as the operator parameter category, the method of obtaining the parameter value, the configuration information for the parameter value, and the resource service type corresponding to the parameter value.

[0057] For example, a user can configure the operator flow relationship of a first operator component by connecting its first input connection control and first output connection control to the first input connection controls and first output connection controls of other first operator components. For instance, if there is no data resource flow relationship (i.e., data input / output relationship) between a first operator component and another first operator component, the user can connect the first output connection control of a first operator component to the first input connection control of another first operator component. The computer device can respond to this connection operation by establishing the operator flow relationship between the first operator component and another first operator component and displaying a first connection line between the first output connection control of the first operator component and the first input connection control of the other first operator component. The first connection line can, for example, be represented by a dashed line. The first connection line can indicate the operator flow relationship associated with the first operator component. This operator flow relationship characterizes the execution order when there is no data resource flow relationship between the first operator component and another first operator component. That is, after the first operator component finishes running, its output data is not used as input data for another first operator component, but the execution of the other first operator component continues.

[0058] For example, a user can configure the first data resource parameter configuration information of the first operator component by connecting the second input connection control and the second output connection control of the first operator component to the input connection controls and / or output connection controls of other target resource components, respectively. This first data resource parameter configuration information may include, but is not limited to, at least one input data resource parameter, at least one output data resource parameter, and data resource flow relationships of the first operator component. Each input data resource parameter includes an input data identifier and an input data type, and each output data resource parameter includes an output data identifier and an output data type.

[0059] For example, a user can connect at least one second output connection control of a first operator component to at least one second input connection control of another first operator component, so that at least one output data of the first operator component serves as input data of the other first operator component. A user can also connect at least one second output connection control of yet another first operator component to at least one second input connection control of the first operator component, so that at least one output data of yet another first operator component serves as input data of the first operator component. Alternatively, a user can connect a fourth output connection control of at least one data resource component to at least one second input connection control of the first operator component, so that at least one data resource component provides at least one input data to the first operator component. In response to the above connection operations, the computer device can determine the first data resource parameter configuration information of the first operator component and display a second connection line between at least one second output connection control of the first operator component and at least one second input connection control of another first operator component, or between at least one fourth output connection control of at least one data resource component and at least one second input connection control of the first operator component. The second connection line can indicate the data resource flow relationship associated with the first operator component. The second connection line is different from the first connection line, and the second connection line can be represented by, for example, a solid line.

[0060] It should be noted that when arranging the connection relationship between the first operator component and other target resource components through the second input connection control and the second output connection control, the user can determine which second input connection controls and which second output connection controls the first operator component needs to connect to other target resource components according to the actual business scenario task requirements. That is, the user can determine which input data resource parameters the first operator component needs to input and which output data resource parameters it needs to output. This allows for flexible configuration of the input / output data resource parameters of the first operator component.

[0061] In this embodiment of the invention, the configuration information of the second operator component includes, for example, the configuration information of the second operator parameters and the configuration information of the second data resource parameters.

[0062] For example, a user can configure the second operator parameter configuration information of the second operator component by triggering an output configuration control. For instance, a computer device can configure the second operator parameter configuration information of the second operator component in response to a user's triggering operation (e.g., an input operation) on the output configuration control. The second operator parameter configuration information may include, for example, a storage path.

[0063] For example, a user can configure the second data resource parameter configuration information of the second operator component by connecting the third input connection control of the second operator component to the second output connection control of the first operator component. For instance, a user can connect the second output connection control of the first operator component and the third input connection control of the second operator component to store the output data of the first operator component. Based on this connection operation, a computer device can determine the second data resource parameter configuration information of the second operator component and display a second connection line between the second output connection control of the first operator component and the third input connection control of the second operator component. This second connection line can indicate the data resource flow relationship between the first and second operator components. The second data resource parameter configuration information may include, for example, input data resource parameters and data resource flow relationships. The input data resource parameters include an input data identifier and an input data type. The input data resource parameters of the second operator component can be determined based on the output data resource parameters of the first operator component connected to the second operator component.

[0064] In this embodiment of the invention, the configuration information of the data resource component includes, for example, third data resource parameter configuration information.

[0065] For example, a user can configure the third data resource parameter configuration information of the data resource component by connecting the fourth output connection control of the data resource component to the second input connection control of the first operator component. This third data resource parameter configuration information may include, for example, the data resource flow relationship of the data resource component. In response to this connection operation, the computer device can determine the third data resource parameter configuration information of the data resource component and display a second connection line between the fourth output connection control of the data resource component and the second input connection control of the first operator component. This second connection line visually represents the data resource flow relationship associated with the data resource component.

[0066] In this embodiment of the invention, the computer device can respond to a user's orchestration operation on multiple target resource components by displaying an orchestration structure containing multiple target resource components on the main interface. This orchestration structure may, for example, indicate the position of each target resource component displayed on the main interface, the connection relationships between the multiple target resource components, and the connection method, etc. The connection method refers to whether any two target resource components are connected via a first connection line or a second connection line. Based on the above orchestration structure, the execution order between the target resource components and other configuration information of each target resource component, excluding operator parameter configuration information, can be determined.

[0067] For example, when the user follows Figure 2C Arranged in the manner shown Figure 2BWhen multiple target resource components are shown in the diagram, that is, when the user moves multiple target resource components to suitable positions in the main interface 22 and connects the multiple target resource components using the second connecting line, the computer device can display an arrangement structure containing multiple target resource components in the main interface 22 based on this arrangement operation. For example... Figure 2C As shown, the arrangement structure is as follows: the fourth output connection control of data resource component A is connected to a second input connection control (corresponding to input data identifier "input 11") of the first operator component 10 via a second connection line; the fourth output connection control of data resource component B is connected to another second input connection control (corresponding to input data identifier "input 12") of the first operator component 10 via a second connection line; a second output connection control (corresponding to output data identifier "output 11") of the first operator component 10 is connected to a second input connection control (corresponding to input data identifier "input 21") of the first operator component 20 via a second connection line; and the second output connection control (corresponding to output data identifier "output 21") of the first operator component 20 is connected to the third input connection control of the second operator component 30 via a second connection line. Based on this arrangement structure, data resource component A and data resource component B can provide input resource service A (i.e., the input resource service represented by data resource service identifier "Resource A") and input resource service B (i.e., the input resource service represented by data resource service identifier "Resource B") to the first operator component 10, respectively. Input resource service A is associated with input data 11 (i.e., the input data represented by input data identifier "Input 11"), and input resource service B is associated with input data 12 (i.e., the input data represented by input data identifier "Input 12"). Based on input data 11 and input data 12, the first operator component 10 can output output data 11 to the first operator component 20, serving as input data 21 for the first operator component 20. Based on input data 21, the first operator component 20 can output output data 21 to the second operator component 30, and the second operator component 30 can store the output data 21 to the storage path xxx.

[0068] In this embodiment of the invention, the execution order among data resource component A, data resource component B, first operator component 10, first operator component 20, and second operator component 30 can be determined according to the arrangement structure. Specifically, data resource components A and B flow to first operator component 10, then from first operator component 10 to first operator component 20, and finally from first operator component 20 to second operator component 30. Furthermore, according to this arrangement structure, the third data resource parameter configuration information corresponding to data resource components A and B, the first data resource parameter configuration information corresponding to first operator component 10 and first operator component 20, and the second data resource parameter configuration information corresponding to second operator component 30 can also be determined.

[0069] Next, based on the configuration information of each of the multiple target resource components and the orchestration structure containing multiple target resource components, the target task flow is generated.

[0070] In this embodiment of the invention, each first operator component and each second operator component among multiple target resource components can be defined as a task operator, and the configuration information of each task operator is determined according to the configuration information of the corresponding operator component. The execution order among multiple task operators can be determined according to the orchestration structure. Furthermore, if the multiple target resource components include a data resource component, the data resource component connected to the task operator can provide input resource services for that task operator, and these input resource services are associated with input data. If the multiple target resource components do not include a data resource component, the resource service address (if any) of the input resource service associated with the task operator can be obtained according to the configuration information of the task operator, and this resource service address is used to obtain the input data of the task operator.

[0071] For example, it can be Figure 2C The first operator component 10 shown is defined as task operator 10, the first operator component 20 is defined as task operator 20, and the second operator component 30 is defined as task operator 30. The execution order of task operators 10, 20, and 30 is from task operator 10 to task operator 20, and then from task operator 20 to task operator 30. Data resource components A and B connected to task operator 10 can provide input resource service A and input resource service B to task operator 10. Input resource service A is associated with input data 11, and input resource service B is associated with input data 12.

[0072] At this point, the target task flow associated with the target scenario task has been determined.

[0073] According to an embodiment of the present invention, by dragging multiple target resource components associated with the target scenario task from the resource component list to the main interface, and configuring and arranging the multiple target resource components in the main interface according to the requirements of the target scenario task, the target task flow is generated based on the configuration information of each target resource component and the arrangement structure containing multiple target resource components. This realizes the visual editing of the target task flow and improves the efficiency of obtaining the target task flow.

[0074] Return to reference Figure 1In operation S120, when a user triggers a run operation for the target task flow (such as the user clicking the run control on the main interface), the computer device can determine the task operator to be executed in the target task flow according to the execution order among the multiple task operators, and call the input resource service associated with the task operator to be executed to execute the task operator, thereby obtaining a first execution result. The first execution result includes at least one first output data.

[0075] In accordance with Figure 2C Taking the target task flow obtained through the orchestration method as an example, when the user clicks the run control 243 in the main interface 22 to run the target task flow, the computer device determines the task operator to be executed in the target task flow as task operator 10 based on the execution order among multiple task operators in the target task flow. When executing the task operator to be executed (i.e., task operator 10), the computer device can call the input resource service associated with the task operator to be executed (i.e., input resource service A from data resource component A and input resource service B from data resource component B) to obtain input data 11 and input data 12, and use input data 11 and input data 12 to execute the task operator to be executed, obtaining the first execution result. The first execution result includes, for example, two first output data, namely output data 11 and output data 12.

[0076] According to an embodiment of the present invention, during the execution of the target task process, the input and output data of each task operator are transferred in the form of service resources, which can improve data transfer efficiency. After obtaining the first execution result, the first execution result can be published as a service and stored for subsequent task operators to call.

[0077] The process of publishing the first execution result of the task operator as a service typically involves three steps: resource creation, parsing, and service publishing. Related technologies usually publish the first execution result as a full service, which leads to a lengthy parsing process, impacting the service publishing process, reducing efficiency, and consequently affecting the normal operation of the target task flow.

[0078] To address the aforementioned technical issues, in this embodiment of the invention, when publishing the first execution result as a service, a service publishing scheme for the first execution result is determined based on the operator type of the downstream task operator connected to the task operator to be executed. This enables targeted service publishing without having to publish the first execution result as a full service. This not only reduces resource consumption during the service publishing process but also improves service publishing efficiency, thereby improving task execution efficiency.

[0079] In one example, if the operator type of the downstream task operator connected to the task operator to be executed is a non-output operator type, the first target input data identifier and the resource service type corresponding to the first target input data represented by the first target input data identifier can be determined based on the configuration information of the downstream task operator. Then, according to the resource service type corresponding to the first target input data, the first target output data in the first execution result is published as a service to convert the first target output data into a first resource service, which can be used to execute the downstream task operator. Here, the first target input data refers to the input data received by the downstream task operator from the task operator to be executed, and the first target output data refers to the first output data flowing from the task operator to the downstream task operator, that is, the first target output data is the same as the first target input data.

[0080] In this embodiment of the invention, the operator type of a downstream task operator can be determined based on the configuration information of the downstream task operator connected to the task operator to be executed. For example, if the configuration information of the downstream task operator indicates that the downstream task operator is not connected to other task operators and the downstream task operator is used for data storage, then the operator type of the downstream task operator is an output operator type; otherwise, the operator type of the downstream task operator is a non-output operator type.

[0081] Continue using the above Figure 2C An example of the target task flow. First, based on the execution order of multiple task operators in the target task flow, the downstream task operator connected to the task operator to be executed (i.e., task operator 10) can be identified as task operator 20. Based on the configuration information of task operator 20, it can be determined that task operator 20 is a non-output operator type. Furthermore, based on the configuration information of task operator 20, the first target input data identifier can be identified as "input 21," and the resource service type corresponding to the first target input data (denoted as input data 21) represented by the first target input data identifier "input 21" can be determined. The first target input data (i.e., input data 21) is the input data received by the downstream task operator (i.e., task operator 20) from the task operator to be executed (i.e., task operator 10), and it is the same data as the first target output data. The first target output data refers to the first output data flowing from the task operator to be executed (i.e., task operator 10) to the downstream task operator (i.e., task operator 20), which is output data 11 represented by the output data identifier "output 11." Subsequently, when publishing the first execution result output by the task operator, the service can be published only for the first target output data (i.e., output data 11) in the first execution result, according to the resource service type corresponding to the first target input data (i.e., input data 21), so as to convert output data 11 into a first resource service and store it. The first resource service can then be used to execute downstream task operators.

[0082] In another example, if the downstream task operator connected to the task operator to be executed is of type output operator, the data type of each of the at least one first output data contained in the first execution result can be determined based on the configuration information of the task operator to be executed, and a first service publishing requirement can be determined based on the data type of each of the at least one first output data. The first service publishing requirement is used to characterize the type of resource service to be created when encapsulating each of the at least one first output data into a resource service. Then, service publishing is performed on the at least one first output data according to the first service publishing requirement.

[0083] In this embodiment of the invention, when the operator type of the downstream task operator connected to the task operator to be executed is an output operator type, a resource service type lookup table can be consulted based on the data type of at least one first output data contained in the first execution result to obtain the resource service type corresponding to the data type of each first output data, and a first service release requirement can be obtained based on these resource service types. The resource service type lookup table is pre-stored by the computer device. The resource service type lookup table stores the correspondence between data types and resource service types. Table 1 schematically shows the correspondence between some data types and resource service types. As shown in Table 1, for example, the resource service types corresponding to the data type "grid" include ZYFW_1, ZYFW_2, and ZYFW_3. The resource service types corresponding to the data type "vector" include ZYFW_1, ZYFW_2, ZYFW_3, ZYFW_4, ZYFW_5, ZYFW_6, and so on. It should be understood that the identifiers given in Table 1 are only used to distinguish different resource service types and do not represent the content and quantity of resource service types. The resource service type identifier can be set in any other way as needed in the embodiments of the present invention.

[0084]

[0085] Table 1

[0086] In some other embodiments, if the task operator to be executed is not connected to other task operators, the first execution result output by the task operator to be executed may not be published as a service. Furthermore, if there are still unexecuted task operators in the target task flow, after the task operator to be executed outputs its first execution result, these unexecuted task operators can continue to be executed according to the execution order among the multiple task operators in the target task flow until the target task flow is completed.

[0087] The process of publishing the first target output data as a service is similar to the process of publishing each of the first output data in at least one first output data as a service. The following explanation uses the first target output data as an example to illustrate service publishing.

[0088] For example, a service publishing task can be created and executed to publish the first target output data as a service. This service publishing task is used to encapsulate the first target output data into a first resource service according to the resource service type corresponding to the first target input data, and to create a target interface corresponding to the first resource service, where the target interface is used to implement the invocation of the first resource service.

[0089] Taking output data 11 as the first target output data as an example. For instance, a service publishing task can be created. This service publishing task can be: according to the resource service type corresponding to the first target input data (i.e., input data 21), encapsulate output data 11 into a first resource service, and create a target interface corresponding to the first resource service, so that the first resource service can be called through the target interface. After creating the service publishing task, it can be executed.

[0090] In some embodiments, during the execution of a service publishing task, the execution status of the service publishing task can be monitored in real time, and the running status of the task operator to be executed can be updated according to the execution status of the service publishing task. For example, the execution status of the service publishing task can be obtained periodically (e.g., every second, every minute, etc.). When it is determined that the execution status of the service publishing task is completed, the running status of the task operator to be executed can be updated to completed.

[0091] In this embodiment of the invention, if the execution status of the service publishing task is "execution completed," it indicates that the target output data has been successfully published as the first resource service and stored. That is, the conditions for running downstream task operators are now met, and the first resource service can be invoked to continue executing the downstream task operators.

[0092] For example, if the running status of the task operator to be executed is determined to be "completed", the downstream task operator can be continued to be executed by calling the first resource service through the target interface, thereby obtaining the second execution result. The second execution result may include at least one second output data.

[0093] Similar to the process of publishing the first execution result as a service, the service publishing process for the second execution result can be performed by obtaining the operator type of another downstream task operator connected to the downstream task operator based on its configuration information. Then, based on the operator type of that other downstream task operator, a second service publishing requirement for the second execution result is determined, and the second execution result is published as a service according to the second service publishing requirement.

[0094] If the operator type of another downstream task operator is a non-output operator type, the second target input data identifier and the resource service type corresponding to the second target input data represented by the second target input data identifier can be determined based on the configuration information of the other downstream task operator. The second target input data is the input data received by the other downstream task operator from the downstream task operator. Next, based on the resource service type corresponding to the second target input data, a second service publishing requirement is obtained. This second service publishing requirement can be described, for example, as follows: According to the resource service type corresponding to the second target input data, publish the second target output data in the second execution result to convert the second target output data into a second resource service. Here, the second target output data refers to the second output data flowing from one downstream task operator to another, and the second target output data is the same as the second target input data. Then, according to the second service publishing requirement, the second execution result is published as a service. For example, another service publishing task can be created, which encapsulates the second target output data into a second resource service according to the resource service type corresponding to the second target input data, and creates another target interface corresponding to the second resource service. This other target interface is used to implement the call to the second resource service. Next, execute another service publishing task.

[0095] If the operator type of another downstream task operator is an output operator type, the data type of each of the at least one second output data contained in the second execution result can be determined according to the configuration information of the downstream task operator, and a second service publishing requirement for the second execution result can be determined according to the data type of each of the at least one second output data. The second service publishing requirement characterizes the type of resource service to be created when encapsulating each of the at least one second output data into a resource service. This second service publishing requirement can be described, for example, as: publishing the at least one second output data contained in the second execution result according to its corresponding resource service type. The resource service type corresponding to each second output data can be determined by querying a resource service type lookup table based on the data type of the second output data. Then, the second execution result is published according to the second service publishing requirement. For example, another service publishing task can be created, which encapsulates each second output data into another second resource service according to the resource service type corresponding to each second output data, and creates another target interface corresponding to the other second resource service. This target interface is used to implement the call to the other second resource service. Afterwards, the other service publishing task is executed.

[0096] The following is a reference to the above. Figure 2CThe example of the target task flow is given, and the process of publishing the second execution result as a service is illustrated using task operator 20 as the downstream task operator.

[0097] For example, when executing a downstream task operator (i.e., task operator 20), the computer device can call a first resource service through the target interface to obtain first target output data (i.e., output data 11), and use output data 11 to execute task operator 20 to obtain a second execution result. The second execution result includes, for example, a second output data, i.e., output data 21. Next, based on the configuration information of the downstream task operator (i.e., task operator 30) connected to task operator 20, the operator type of task operator 30 can be determined to be an output operator type. Given that the operator type of task operator 30 is determined to be an output operator type, the data type of output data 21 can be determined to be output type 21 based on the configuration information of task operator 20. Next, based on the data type of output data 21, a resource service type lookup table is consulted to obtain the resource service type corresponding to the data type of output data 21. Further, based on the resource service type corresponding to the data type of output data 21, a second service publishing requirement can be determined. This second service publishing requirement can be described, for example, as: publishing output data 21 as a service according to the resource service type corresponding to the data type of output data 21. Next, based on the second service publishing requirement, output data 21 is published as another second resource service. For example, another service publishing task can be created, which encapsulates output data 21 into another second resource service according to the resource service type corresponding to the data type of output data 21, and creates another target interface corresponding to the other second resource service. This target interface is used to implement the call to the other second resource service. Then, the other service publishing task is executed.

[0098] Similarly, during the execution of another service deployment task, the execution status of that task can be periodically monitored, and the running status of task operator 20 can be updated accordingly. When it is determined that the execution status of another service deployment task is "execution completed," the running status of task operator 20 can be updated to "running completed." Furthermore, when it is determined that the running status of task operator 20 is "running completed," task operator 30 can continue to execute to store the output data 21 output by task operator 20. At this point, the target task process ends.

[0099] Figure 3 This is a block diagram of a data processing system according to an embodiment of the present invention.

[0100] like Figure 3 As shown, the data processing system 300 includes a data arrangement module 310 and a data processing module 320.

[0101] According to an embodiment of the present invention, the data orchestration module 310 can display an interactive interface for user interaction to obtain configuration information of multiple target resource components determined for a target scenario task, as well as an orchestration structure containing multiple target resource components, and generate a target task flow based on the configuration information of the multiple target resource components and the aforementioned orchestration structure. For example, the data orchestration module 310 can display an interactive interface including a resource component list and a main interface. The resource component list includes multiple operator components and multiple data resource components, and the main interface is used for orchestrating and configuring the operator components and data resource components. In response to an operation of dragging multiple target resource components associated with the target scenario task from the resource component list to the main interface, the data orchestration module 310 can display multiple target resource components on the main interface. The multiple target resource components may include, for example, at least one first operator component, at least one second operator component, and at least one data resource component, or the multiple target resource components may include at least one first operator component and at least one second operator component. The data orchestration module 310 can respond to operations that configure and orchestrate multiple target resource components in the main interface, determine the configuration information of each target resource component, and display an orchestration structure containing multiple target resource components in the main interface. The orchestration structure is used to indicate the execution order among the multiple target resource components. Based on the configuration information corresponding to each target resource component and the orchestration structure, a target task flow is generated. The target task flow includes multiple task operators, the execution order among the multiple task operators, at least one input resource service associated with the multiple task operators, and the configuration information of each task operator. After obtaining the target task flow, the data orchestration module 310 can also store the target task flow for subsequent use.

[0102] The data orchestration module 310 can respond to a run operation triggered for a target task flow, determine the task operator to be executed in the target task flow according to the execution order among multiple task operators, and call the input resource service associated with the task operator to execute the task operator to obtain a first execution result. The first execution result includes at least one first output data, and, based on the configuration information of the downstream task operator connected to the task operator to be executed, determines a first target input data identifier and the resource service type corresponding to the first target input data represented by the first target input data identifier. The first target input data is the input data received by the downstream task operator from the task operator to be executed.

[0103] The data management module 320 is communicatively connected to the data orchestration module 310. The data management module 320 is used to publish the first target output data in the first execution result as a service according to the resource service type corresponding to the first target input data, thereby converting the first target output data into a first resource service. The first target output data is the first output data flowing from the task operator to the downstream task operator, and the first resource service is used to execute the downstream task operator. The data management module 320 can also store the first resource service and other data resource services for subsequent use.

[0104] It should be noted that the implementation methods, technical problems solved, functions achieved, and technical effects of each module in the data processing system embodiments are the same as or similar to the implementation methods, technical problems solved, functions achieved, and technical effects of each corresponding step in the method embodiments, and will not be repeated here.

[0105] Figure 4 A block diagram of a computer device suitable for implementing a service publishing method according to an embodiment of the present invention is shown schematically.

[0106] like Figure 4 As shown, a computer device 400 according to an embodiment of the present invention includes a processor 401, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 402 or a program loaded from a storage portion 408 into a random access memory (RAM) 403. The processor 401 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 401 may also include onboard memory for caching purposes. The processor 401 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present invention.

[0107] RAM 403 stores various programs and data required for the operation of computer device 400. Processor 401, ROM 402, and RAM 403 are interconnected via bus 404. Processor 401 executes various operations of the method flow according to embodiments of the present invention by executing programs in ROM 402 and / or RAM 403. It should be noted that the programs may also be stored in one or more memories other than ROM 402 and RAM 403. Processor 401 may also execute various operations of the method flow according to embodiments of the present invention by executing programs stored in said one or more memories.

[0108] According to an embodiment of the present invention, the computer device 400 may further include an input / output (I / O) interface 405, which is also connected to a bus 404. The computer device 400 may also include one or more of the following components connected to the I / O interface 405: an input section 406 including a keyboard, mouse, etc.; an output section 407 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN card, modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the I / O interface 405 as needed. A removable medium 411, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 410 as needed so that computer programs read from it can be installed into the storage section 408 as needed.

[0109] The present invention also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the service publishing method according to embodiments of the present invention.

[0110] According to embodiments of the present invention, a computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of the present invention, a computer-readable storage medium may include ROM 402 and / or RAM 403 and / or one or more memories other than ROM 402 and RAM 403 described above.

[0111] Embodiments of the present invention also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to enable the computer system to implement the service publishing method provided by the embodiments of the present invention.

[0112] When the computer program is executed by the processor 401, it performs the functions defined in the system / apparatus of this embodiment of the invention. According to embodiments of the invention, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0113] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via communication section 409, and / or installed from removable medium 411. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0114] In such an embodiment, the computer program can be downloaded and installed from a network via communication section 409, and / or installed from removable medium 411. When the computer program is executed by processor 401, it performs the functions defined in the system of this embodiment of the invention. According to embodiments of the invention, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0115] According to embodiments of the present invention, program code for executing the computer programs provided in the embodiments of the present invention can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can be executed entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0116] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0117] Those skilled in the art will understand that the features described in the various embodiments of the present invention can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in the present invention. In particular, the features described in the various embodiments of the present invention can be combined and / or combined in various ways without departing from the spirit and teachings of the present invention. All such combinations and / or combinations fall within the scope of the present invention.

[0118] The embodiments of the present invention have been described above. However, these embodiments are merely illustrative and not intended to limit the scope of the invention. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of the invention, and all such substitutions and modifications should fall within the scope of the invention.

Claims

1. A service publishing method, comprising: Obtain the target task flow determined for the target scenario task. The target task flow includes multiple task operators, the execution order between the multiple task operators, at least one input resource service associated with the multiple task operators, and configuration information for each of the task operators. In response to a running operation triggered for the target task flow, the task operator to be executed in the target task flow is determined according to the execution order, and the input resource service associated with the task operator to be executed is invoked to execute the task operator to obtain a first execution result, the first execution result including at least one first output data; Based on the configuration information of the downstream task operator connected to the task operator to be executed, a first target input data identifier and the resource service type corresponding to the first target input data represented by the first target input data identifier are determined, wherein the first target input data is the input data received by the downstream task operator from the task operator to be executed; According to the resource service type corresponding to the first target input data, the first target output data in the first execution result is published as a service to convert the first target output data into a first resource service. The first target output data is the first output data flowing from the task operator to the downstream task operator, and the first resource service is used to execute the downstream task operator.

2. The method according to claim 1, further comprising: In response to determining that the operator type of the downstream task operator is an output operator type, the data type of at least one first output data is determined according to the configuration information of the task operator to be executed; Based on the data type of each of the at least one first output data, a first service publishing requirement is determined, wherein the first service publishing requirement is used to characterize the type of resource service to be created when each of the at least one first output data is encapsulated as a resource service. Based on the first service publishing requirement, at least one first output data is published as a service.

3. The method according to claim 2, wherein, Determining the first service publishing requirement based on the data type of each of at least one first output data includes: For each first output data, a preset resource service type lookup table is queried according to the data type of the first output data to obtain the resource service type corresponding to the data type of the first output data; wherein, the resource service type lookup table is used to store the correspondence between data types and resource service types; The first service publishing requirement is obtained based on the resource service type corresponding to the data type of each of the first output data.

4. The method according to any one of claims 1 to 3, wherein, The step of publishing the first target output data in the first execution result into a first resource service according to the resource service type corresponding to the first target input data includes: A service publishing task is created, which is used to encapsulate the first target output data into a first resource service according to the resource service type corresponding to the first target input data, and to create a target interface corresponding to the first resource service, which is used to implement the call to the first resource service; Perform the service publishing task.

5. The method according to claim 4, further comprising: Obtain the execution status of the service publishing task; In response to determining that the execution status of the service publishing task is "execution completed", the running status of the task operator to be executed is updated to "running completed".

6. The method according to claim 5, further comprising: In response to determining that the running status of the task operator to be executed is the running completed state, the first resource service is invoked to execute the downstream task operator to obtain the second execution result; Obtain the operator type of another downstream task operator connected to the downstream task operator, and determine the second service publishing requirement for the second execution result based on the operator type of the other downstream task operator; Based on the second service publishing requirement, the second execution result is published as a service.

7. The method according to claim 6, wherein, The second execution result includes at least one second output data, and determining the second service release requirement for the second execution result based on the operator type of the other downstream task operator includes: In response to determining that the operator type of the other downstream task operator is a non-output operator type, a second target input data identifier and the resource service type corresponding to the second target input data represented by the second target input data identifier are determined according to the configuration information of the other downstream task operator. The second target input data is the input data received by the other downstream task operator from the downstream task operator. Based on the resource service type corresponding to the second target input data, the second service publishing requirement is determined. The second service publishing requirement is to publish the second target output data in the second execution result according to the resource service type corresponding to the second target input data, so as to convert the second target output data into a second resource service. The second target output data is the second output data flowing from the downstream task operator to the other downstream task operator.

8. The method according to claim 6, wherein, The second execution result includes at least one second output data, and determining the second service release requirement for the second execution result based on the operator type of the other downstream task operator includes: In response to determining that the operator type of the other downstream task operator is an output operator type, the data type of at least one second output data is determined according to the configuration information of the downstream task operator; Based on the data type of each of the at least one second output data, a second service publishing requirement is determined, which is used to characterize the type of resource service to be created when each of the at least one second output data is encapsulated as a resource service.

9. The method according to any one of claims 1 to 8, wherein, The process of obtaining the target task determined for the target scenario task includes: The interactive interface includes a resource component list and a main interface. The resource component list includes multiple operator components and multiple data resource components. The main interface is used to arrange and configure operator components and data resource components. In response to the operation of dragging multiple target resource components associated with the target scene task from the resource component list to the main interface, multiple target resource components are displayed on the main interface; In response to the operation of configuring and orchestrating multiple target resource components in the main interface, the configuration information of each target resource component is determined, and an orchestration structure containing multiple target resource components is displayed in the main interface, the orchestration structure being used to indicate the execution order among the multiple target resource components; The target task flow is generated based on the configuration information of each of the multiple target resource components and the orchestration structure.

10. A computer device, comprising: One or more processors; Memory, used to store one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors perform the service publishing method according to any one of claims 1 to 9.

11. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the service publishing method according to any one of claims 1 to 9.

12. A computer program product comprising a computer program that, when executed by a processor, implements the service publishing method according to any one of claims 1 to 9.

13. A data processing system for performing the service publishing method as described in any one of claims 1 to 9, the data processing system comprising: The data orchestration module is used to obtain the target task flow determined for the target scenario task. The target task flow includes multiple task operators, the execution order between the multiple task operators, at least one input resource service associated with the multiple task operators, and configuration information of each task operator. In response to a run operation triggered for the target task flow, according to the execution order, a task operator to be executed in the target task flow is determined, and an input resource service associated with the task operator to be executed is invoked to execute the task operator to obtain a first execution result, the first execution result including at least one first output data; according to the configuration information of the downstream task operator connected to the task operator to be executed, a first target input data identifier and the resource service type corresponding to the first target input data represented by the first target input data identifier are determined, wherein the first target input data is input data received by the downstream task operator from the task operator to be executed; The data management module, which is communicatively connected to the data orchestration module, is used to publish the first target output data in the first execution result according to the resource service type corresponding to the first target input data, so as to convert the first target output data into a first resource service. The first target output data is the first output data flowing from the task operator to be executed to the downstream task operator, and the first resource service is used to execute the downstream task operator.

14. The system according to claim 13, wherein, The data orchestration module is also used for: The interactive interface includes a resource component list and a main interface. The resource component list includes multiple operator components and multiple data resource components. The main interface is used to arrange and configure operator components and data resource components. In response to the operation of dragging multiple target resource components associated with the target scene task from the resource component list to the main interface, multiple target resource components are displayed on the main interface; In response to the operation of configuring and orchestrating multiple target resource components in the main interface, the configuration information of each target resource component is determined, and an orchestration structure containing multiple target resource components is displayed in the main interface, the orchestration structure being used to indicate the execution order among the multiple target resource components; The target task flow is generated based on the configuration information of each of the multiple target resource components and the orchestration structure.

Images