Data type matching method and device, electronic equipment and storage medium

Abstract

Embodiments of the present disclosure provide a data type matching method and device, electronic equipment and a storage medium. The method comprises: for a current data processing node, obtaining input data of the current data processing node, and determining a data type of the input data; in a case where the data type of the input data exists in pre-stored type corresponding information, querying a data type of output data corresponding to the data type of the input data based on the type corresponding information; and configuring a data type of the current data processing node based on the data type of the input data and the data type of the output data corresponding to the data type of the input data. The technical solution of the present embodiment achieves the effect of automatic configuration of the data type of the data processing node, simplifies the configuration process of the data type, and improves the configuration efficiency of the data type.

Description

Technical Field

[0001] This disclosure relates to data processing technology, and more particularly to a data type matching method, apparatus, electronic device, and storage medium. Background Technology

[0002] In a data processing workflow that includes multiple data processing stages, each stage can be considered a data processing node in the data flow, and the nodes are connected through data transmission. For data flow between nodes, data transmission between the upstream data processing node and the downstream data processing node can only occur when the data type of the output data of the upstream data processing node matches the data type of the input data of the downstream data processing node.

[0003] In existing technologies, for every two data processing nodes in a data stream, when the data types between these two nodes need to be matched, the user needs to manually configure the data types of these two data processing nodes. When there are multiple data processing nodes in the data stream, the user needs to repeatedly perform data type configuration operations. Furthermore, different types of data processing nodes have different type-related settings, which results in the data type configuration process consuming a lot of manual and time costs, reducing data transmission efficiency, and consequently affecting the user experience. Summary of the Invention

[0004] This disclosure provides a data type matching method, apparatus, electronic device, and storage medium to achieve automated configuration of data types in data processing nodes, simplifying the data type configuration process, improving data type configuration efficiency, thereby improving data stream transmission efficiency and enhancing the user experience.

[0005] In a first aspect, embodiments of this disclosure provide a data type matching method, the method comprising:

[0006] For the current data processing node, obtain the input data of the current data processing node and determine the data type of the input data;

[0007] If the data type of the input data exists in the pre-stored type correspondence information, the data type of the output data corresponding to the data type of the input data is queried based on the type correspondence information, wherein the type correspondence information is used to indicate the correspondence between the data types of the input data and the data types of the output data supported by the current data processing node;

[0008] The data type of the current data processing node is configured based on the data type of the input data and the data type of the output data corresponding to the data type of the input data.

[0009] Secondly, embodiments of this disclosure also provide a data type matching apparatus, the apparatus comprising:

[0010] The input data type acquisition module is used to acquire the input data of the current data processing node and determine the data type of the input data;

[0011] The output data type determination module is used to query the data type of the output data corresponding to the data type of the input data based on the type correspondence information when the data type of the input data exists in the pre-stored type correspondence information, wherein the type correspondence information is used to indicate the correspondence between the data types of the input data and the data types of the output data supported by the current data processing node;

[0012] The node data type configuration module is used to configure the data type of the current data processing node based on the data type of the input data and the data type of the output data corresponding to the data type of the input data.

[0013] Thirdly, embodiments of this disclosure also provide an electronic device, the electronic device comprising:

[0014] One or more processors;

[0015] Storage device for storing one or more programs.

[0016] When the one or more programs are executed by the one or more processors, the one or more processors implement the data type matching method as described in any of the embodiments of this disclosure.

[0017] Fourthly, embodiments of this disclosure also provide a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform the data type matching method as described in any of the embodiments of this disclosure.

[0018] The technical solution of this disclosure, for the current data processing node, obtains the input data of the current data processing node, determines the data type of the input data, and further, if the data type of the input data exists in the pre-stored type correspondence information, queries the data type of the output data corresponding to the data type of the input data based on the type correspondence information. Finally, based on the data type of the input data and the data type of the output data corresponding to the data type of the input data, the data type of the current data processing node is configured. This solves the problems in the prior art where users need to manually configure the data type of the data processing node, and the configuration operation needs to be repeatedly performed, resulting in a large amount of labor and time costs in the data type configuration process, reducing data transmission efficiency. It achieves the effect of automated configuration of data type of data processing node, simplifies the data type configuration process, improves the data type configuration efficiency, and thus improves the data flow transmission efficiency and enhances the user experience. Attached Figure Description

[0019] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0020] Figure 1 A flowchart illustrating a data type matching method provided in an embodiment of this disclosure;

[0021] Figure 2 This is a flowchart illustrating another data type matching method provided in an embodiment of this disclosure;

[0022] Figure 3 This is a flowchart illustrating another data type matching method provided in an embodiment of this disclosure;

[0023] Figure 4 This is a flowchart illustrating another data type matching method provided in an embodiment of this disclosure;

[0024] Figure 5 This is a schematic diagram of the structure of a data type matching device provided in an embodiment of the present disclosure;

[0025] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0026] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0027] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0028] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0029] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0030] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0031] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0032] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0033] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0034] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0035] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0036] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0037] Before introducing this technical solution, an exemplary application scenario can be provided. The technical solution of this disclosure embodiment can be applied to any data stream transmission scenario including multiple data processing nodes. For example, during data transmission, multiple data processing stages may be included. After digitally describing the data processing process, each data processing stage can be considered a data processing node. The data flow between any two data processing nodes generally falls into two categories: weakly typed, where the data type between the two data processing nodes is not specifically defined; weakly typed data stream transmission is simple to operate but has relatively few operational details and limited applicability. Strongly typed data stream transmission requires the data types between the two data processing nodes to match; while strongly typed data stream transmission has more operational details, it is more complex in terms of user interaction. Furthermore, when the data type matching between the two data processing nodes fails, the user needs to manually configure the data types of the two data processing nodes. When there are multiple data processing nodes in the data stream, the user needs to repeatedly perform data type configuration operations. Moreover, different types of data processing nodes have different type-related settings, resulting in a significant increase in manual and time costs for data type configuration, thus reducing data transmission efficiency. Based on this, the data type of the input data of the current data processing node can be determined on a strongly typed node data stream, and if the data type of the input data exists in the type correspondence information corresponding to the current data processing node, the data type of the current data processing node can be configured based on the data type of the input data and the corresponding data type of the output data. This can achieve the effect of automatic adaptation of the data type of the current data processing node, improve the configuration efficiency of the data type, and thus improve the data transmission efficiency.

[0038] Figure 1 This is a flowchart illustrating a data type matching method provided in an embodiment of the present disclosure. This embodiment is applicable to the situation where the data type of each data processing node is automatically configured in a data processing process including multiple data processing nodes. The method can be executed by a data type matching device, which can be implemented in software and / or hardware, or optionally by an electronic device, such as a mobile terminal, a PC, or a server.

[0039] like Figure 1 As shown, the method in this embodiment may specifically include:

[0040] S110. For the current data processing node, obtain the input data of the current data processing node and determine the data type of the input data.

[0041] In this embodiment, the digital carrier of the data processing flow is the data stream. It can be understood that the data stream can at least reflect each data processing stage in the data processing flow, as well as the relationships between these stages. Each data processing stage included in the data stream can be considered a data processing node. It should be noted that the data stream can be executed on a single terminal device. In this case, the current data processing node can be any data processing module within that terminal device used to execute the data stream. Alternatively, the data stream can be executed in a distributed system comprising multiple terminal devices. In this case, the current data processing node can be any terminal device in the distributed system, or any data processing module within any terminal device used to execute the data stream. This embodiment does not specifically limit the scope of the data stream execution.

[0042] In this embodiment, the input data of the current data processing node can be data input to the current data processing node for data processing. The data type can be an expression representing data attributes. The data type of the input data is the expression representing the attributes of the input data. The data type can define the operations performed on the corresponding data, the data itself, its meaning, and the way the data of that type is stored. For example, the data type can be a one-dimensional vector, a multi-dimensional vector, a function, or a string, etc.

[0043] In practical applications, for a data stream that includes multiple data processing nodes, any one of the data processing nodes in the data stream can be taken as the current processing node. When data input to the current processing node is detected, the input data input to the current data node can be obtained. Furthermore, the input data can be analyzed to determine the data type of the input data.

[0044] It should be noted that the data type of the input data of the current data processing node can be one or more types. Regardless of whether it is one or more types, it can be processed using the technical solutions provided in the embodiments of this disclosure.

[0045] S120. If the data type of the input data exists in the pre-stored type correspondence information, query the data type of the output data corresponding to the data type of the input data based on the type correspondence information.

[0046] The type correspondence information is used to indicate the correspondence between the data types of input data and the data types of output data supported by the current data processing node. In this embodiment, the type correspondence information can be information representing the mapping relationship between the data types of input data and the data types of output data. In practical applications, for each data processing node in the data stream, the data types of input data that can be input into the current data processing node can be predetermined. Based on the data type of the input data and the data processing algorithm pre-deployed in the current data processing node for processing the input data, at least one data type of output data corresponding to the data type of the input data is determined, and the data type of the input data is associated with its corresponding data type of output data to establish a mapping relationship between the data types of input data and the data types of output data. Thus, based on this mapping relationship, type correspondence information corresponding to the current data processing node is generated and stored in the current data processing node.

[0047] In this embodiment, the output data can be data output from the current data processing node to the next data processing node. The data type of the output data can be an expression representing the data attributes of the output data.

[0048] In practical applications, for the current data processing node, after determining the data type of the input data to the current data processing node, the type correspondence information pre-stored in the current data processing node can be traversed to determine whether the data type of the input data exists in the type correspondence information. If the data type of the input data exists in the type correspondence information, the type correspondence information can be traversed and queried to determine the data type of the output data corresponding to the data type of the input data.

[0049] Optionally, querying the data type of the output data corresponding to the data type of the input data based on the type correspondence information includes: querying the type correspondence information according to the data type of the input data and a preset information query order; and taking the first data type of the output data corresponding to the data type of the input data as the data type of the output data corresponding to the data type of the input data.

[0050] In this embodiment, the information query order can be pre-set, used to query the data type of the output data according to the type of information. The information query order can be arbitrary; optionally, it can be random query, or it can be sequential query, etc.

[0051] In practical applications, when querying the data type of output data corresponding to the data type of input data based on type correspondence information, the type correspondence information can be traversed and queried according to a pre-set information query order based on the data type of input data. The first data type of output data found that corresponds to the data type of input data—that is, the first data type of output data found in the information query order that corresponds to the data type of input data—is selected as the data type of output data corresponding to the data type of input data. The advantage of this setup is that it reduces the data type query time, improves query efficiency, and consequently, improves the overall data type matching efficiency.

[0052] For example, the data type of the input data of the current data processing node is data type A1. In the type correspondence information pre-stored in the current data processing node, the data types of the output data corresponding to data type A1 include data type B2, data type B3, and data type B4. Furthermore, the order of these three data types in the type correspondence information is data type B2, data type B3, and data type B4. The information query order can be sequential. Then, the first data type of the output data corresponding to data type A1 found according to the information query order is data type B2. At this time, data type B2 can be used as the data type of the output data corresponding to data type A1.

[0053] S130. Configure the data type of the current data processing node based on the data type of the input data and the data type of the output data corresponding to the data type of the input data.

[0054] In this embodiment, after determining the data type of the input data and the data type of the output data corresponding to the data type of the input data, the data type of the current data processing node can be configured according to these two data types.

[0055] In practical applications, after determining the data types of the input data and the corresponding data types of the output data, the applicable data types of the input data and the corresponding data types of the output data of the current data processing node can be configured according to the determined data types of the input data and the corresponding data types of the output data to obtain the applicable data type combination corresponding to the current data processing node. Then, the current data processing node can execute the data processing process and the data stream transmission process according to the configured data type combination.

[0056] In practical applications, when querying the data type of the input data input to the current data processing node based on the pre-stored type correspondence information in the current data processing node, there may be cases where the data type of the input data is not found in the type correspondence information. In this case, the upstream data processing node corresponding to the current data processing node can be notified so that the data type can be processed based on the upstream data processing node.

[0057] Based on this, in addition to the above technical solutions, the method further includes: generating a matching failure notification when the data type of the input data is not found in the pre-stored type correspondence information, and feeding the matching failure notification back to the upstream data processing node.

[0058] In this embodiment, the upstream data processing node can be a data processing node that has a data flow transmission relationship with the current data processing node, or it can be understood as the input data of the current data processing node being the output data of the upstream data processing node. The matching failure notification can be a prompt indicating that data transmission between the current data processing node and the upstream data processing node cannot be achieved, or it can be understood as a prompt indicating that the data type of the input data of the current data processing node and the data type of the output data of the upstream data processing node have failed to match.

[0059] In practical applications, after determining the data type of the input data at the current data processing node, the type-correspondence information pre-stored in the current data processing node can be traversed and queried to determine if the data type exists in the type-correspondence information. If the data type does not exist, a matching failure notification is generated and sent to the upstream data processing node connected to the current data processing node. When the upstream data processing node receives the matching failure notification, it re-traverses the pre-stored type-correspondence information to determine if there are other output data types that correspond to the input data type of the upstream data processing node. If so, the data type of the upstream data processing node is reconfigured; otherwise, a node for data type conversion can be added between the upstream and current data processing nodes. This enables data transmission between the upstream and current data processing nodes. The advantage of this setup is that it allows the upstream data processing node to promptly understand the data type matching status between data processing nodes, thus enabling timely responses to data type matching failures and improving data type matching efficiency.

[0060] The technical solution of this disclosure, for the current data processing node, obtains the input data of the current data processing node, determines the data type of the input data, and further, if the data type of the input data exists in the pre-stored type correspondence information, queries the data type of the output data corresponding to the data type of the input data based on the type correspondence information. Finally, based on the data type of the input data and the data type of the output data corresponding to the data type of the input data, the data type of the current data processing node is configured. This solves the problems in the prior art where users need to manually configure the data type of the data processing node, and the configuration operation needs to be repeatedly performed, resulting in a large amount of labor and time costs in the data type configuration process, reducing data transmission efficiency. It achieves the effect of automated configuration of data type of data processing node, simplifies the data type configuration process, improves the data type configuration efficiency, and thus improves the data flow transmission efficiency and enhances the user experience.

[0061] Figure 2This is a flowchart illustrating another data type matching method provided in this embodiment. Based on the above embodiments, this embodiment addresses the issue of data type mismatch between the current data processing node and the downstream data processing node when data type matching fails. It allows for data type adaptation between the current data processing node and the downstream data processing node based on a type conversion node. Detailed implementation methods can be found in the description of this embodiment. Technical features that are the same as or similar to those in the foregoing embodiments will not be repeated here.

[0062] like Figure 2 As shown, the method in this embodiment may specifically include:

[0063] S210. For the current data processing node, obtain the input data of the current data processing node and determine the data type of the input data.

[0064] S220. If the data type of the input data exists in the pre-stored type correspondence information, query the data type of the output data corresponding to the data type of the input data based on the type correspondence information.

[0065] S230. Configure the data type of the current data processing node based on the data type of the input data and the data type of the output data corresponding to the data type of the input data.

[0066] S240. Upon receiving a matching failure notification from a downstream data processing node, add a type conversion node between the downstream data processing node and the current data processing node.

[0067] In this embodiment, the downstream data processing node can be a data processing node that has a data flow transmission relationship with the current data processing node, or it can be understood as the output data of the current data processing node being the input data of the downstream data processing node. The matching failure notification can be a prompt indicating that data transmission between the current data processing node and the downstream data processing node cannot be achieved, or it can be understood as a prompt indicating that the data type of the output data of the current data processing node and the data type of the input data of the downstream data processing node have failed to match. The type conversion node can be a node used to implement data type conversion. In practical applications, the type conversion node can set a specific conversion type and perform data type conversion according to the corresponding conversion rules; that is, given the data type to be converted and the converted data type, data type conversion is performed according to the conversion rules. For example, if the data type to be converted is data type B5 and the converted data type is data type C3, then the type conversion node can convert data type B5 to data type C3. The type conversion node can be any node capable of implementing data type conversion. Optionally, the type conversion node can include a node with the data type conversion function Cast. The Cast function is used to explicitly convert an expression of one data type to another data type. In practical applications, if it is determined that there is a mismatch between the data type of the output data of the current data processing node and the data type of the input data of the downstream data processing node, the data type of the output data of the current data processing node and the data type of the input data of the downstream data processing node can be processed according to the type conversion node.

[0068] In practical applications, after configuring the data type of the current data processing node according to the data type of the input data and the corresponding data type of the output data, the current data processing node will input the output data to the downstream data processing node connected to it as input data. When the downstream data processing node receives the input data, it can determine the data type of the input data and, based on the data type of the input data, it iterates through the data type correspondence information pre-stored in the downstream data processing node to determine whether the data type of the input data currently being input to the downstream data processing node exists in the data type correspondence information. If the data type of the input data does not exist in the data type correspondence information, it means that the current data processing node and the downstream data node cannot be connected. At this time, a matching failure notification can be generated and sent to the current data processing node. When the current data processing node receives the matching failure notification sent by the downstream data processing node, a type conversion node can be added between the current data processing node and the downstream data processing node to process the data type of the output data of the current data processing node and the data type of the input data of the downstream data processing node based on the type conversion node.

[0069] In practical applications, there are at least two scenarios where a type conversion node can be added between the current data processing node and the downstream data processing node. These two scenarios will be explained below.

[0070] The first scenario could be: adding a type conversion node between the downstream data processing node and the current data processing node, including: adding a type conversion node between the downstream data processing node and the current data processing node when there is no other output data type corresponding to the input data type in the type correspondence information.

[0071] In this embodiment, the data types of other output data can be data types other than the data types of the input data of the current data processing node, excluding the data types of the already determined output data. For example, continuing with the previous example, the data types of the output data corresponding to data type A1 include data types B2, B3, and B4. If the data type of the already determined output data is data type B2, then the data types of the other output data are data types B3 and B4.

[0072] In practical applications, when the current data processing node receives a matching failure notification from the downstream data processing node, it can re-traverse the pre-stored type correspondence information in the current data processing node to determine if there are other output data data types besides the already determined output data data types that correspond to the input data data type. If no other output data data types correspond to the input data data type, meaning that the input data data type of the current data processing node corresponds to only one output data data type, then a type conversion node can be added between the current data processing node and the downstream data processing node. The advantage of this setup is that it enhances the possibility of data type matching between the current data processing node and the downstream data processing node without adding a type conversion node, potentially simplifying the data type matching process and reducing interaction complexity.

[0073] The second scenario could be: adding a type conversion node between the downstream data processing node and the current data processing node, including: displaying the type conversion node connected between the downstream data processing node and the current data processing node; and receiving data type configuration operations input to the type conversion node.

[0074] The data type configuration operation includes configuring the data type to be converted and / or the converted data type of the type conversion node. The data type to be converted of the type conversion node is the data type of the output data of the current data processing node, and the converted data type of the type conversion node is the data type of the input data supported by the downstream data processing node.

[0075] In this embodiment, the data type configuration operation can be an operation that configures the data type according to data transmission requirements. In practical applications, before configuring the data type of the type conversion node, the data type of the output data of the current data processing node and the data type of the input data that the downstream data processing node connected to the current data processing node can support can be determined first. Then, the type conversion node can be configured according to the data type of the output data of the current data processing node and the data type of the input data that the downstream data processing node can support.

[0076] In practical applications, when the current data processing node receives a matching failure notification from the downstream data processing node, it can directly display the type conversion node connecting the current data processing node and the downstream data processing node, instead of querying the type correspondence information stored in the current data processing node for the data type of other output data that corresponds to the data type of the input data. Furthermore, it can configure the data type of the type conversion node based on the data type configuration operation.

[0077] Optionally, displaying a type conversion node connected between the downstream data processing node and the current data processing node includes: displaying a type conversion node connected between the downstream data processing node and the current data processing node in response to a node type configuration trigger operation input for the current data processing node.

[0078] In this embodiment, a control for triggering the configuration node type can be developed in advance, or a piece of program code for triggering the configuration node type can be preset. When the user triggers the control, or the program code is received, the node type configuration trigger operation can be responded to, thereby displaying the type conversion node connected between the current data processing node and the downstream data processing node.

[0079] In practical applications, when the current data processing node receives a matching failure notification from the downstream data processing node, a trigger operation can be configured based on the node type input of the current data processing node. Upon detecting this node type configuration trigger operation, a response can be initiated, displaying the type conversion node connected to both the downstream and current data processing nodes. The advantages of this setup are: it eliminates the step of re-traversing type correspondence information, directly adding a type conversion node between the downstream and current data processing nodes, simplifying the addition process, improving type conversion efficiency, meeting user needs for data type conversion, and enhancing the user experience of the data type matching tool.

[0080] Furthermore, based on the pre-determined data type of the output data of the current data processing node and the data type of the input data supported by the downstream data processing node, the data type to be converted and / or the converted data type of the type conversion node are configured. According to the data type configuration operation for the input data of the type conversion node, the data type to be converted of the type conversion node is configured as the data type of the output data of the current data processing node. Simultaneously, the converted data type of the type conversion node is configured as the data type of the input data supported by the downstream data processing node, thus completing the process of adding a type conversion node between the downstream data processing node and the current data processing node. The advantage of this setup is that it eliminates the need to iterate and query the type correspondence information again, improving the efficiency of data type configuration, and consequently, improving the data transmission efficiency between data processing nodes.

[0081] S250. Based on the type conversion node, convert the data type of the output data of the current data processing node to the data type of the input data supported by the downstream data processing node.

[0082] In this embodiment, after adding a type conversion node between the downstream data processing node and the current data processing node, the data type of the output data of the current data processing node can be converted to the data type of the input data supported by the downstream data processing node based on the data type configuration information in the type conversion node.

[0083] In practical applications, after obtaining the type conversion node, the data type of the output data of the current data processing node can be converted to the data type of the input data supported by the downstream data processing node according to the data type to be converted and the data type after conversion set in the type conversion node, thereby realizing the data transmission between the current data processing node and the downstream data processing node.

[0084] For example, continuing with the previous example, the data type of the output data of the current data processing node is data type B2, and the data type of the input data supported by the downstream data processing node configured in the type conversion node is data type C3. Then, based on the type conversion node, the data type of the output data of the current data processing node can be converted from data type B2 to data type C3.

[0085] For example, the conversion logic of a type conversion node can correspond to at least three conversion scenarios, which will be explained below:

[0086] The first conversion scenario can be as follows: If the data type of the output data of the current data processing node is a one-dimensional vector, and the data type of the input data supported by the downstream data processing node is a multi-dimensional vector, then the one-dimensional vector can be copied according to the dimension of the multi-dimensional vector so that the components of each dimension in the multi-dimensional vector are consistent with the one-dimensional vector, thereby obtaining a multi-dimensional vector that includes multiple one-dimensional vectors, and the number of one-dimensional vectors is consistent with the dimension of the multi-dimensional vector.

[0087] The second conversion scenario is as follows: If the output data of the current data processing node is a multi-dimensional vector, and the input data supported by the downstream data processing node is a vector of other dimensions (one-dimensional or higher-dimensional vectors), to convert the multi-dimensional vector to a one-dimensional vector, the first few vector values ​​of the multi-dimensional vector can be removed. To convert the multi-dimensional vector to a higher-dimensional vector, preset vector values ​​can be added to the multi-dimensional vector to make the dimension of the added multi-dimensional vector consistent with the dimension of the higher-dimensional vector. The preset vector values ​​can be any value, and optionally, can be 0.

[0088] The third conversion scenario is as follows: If the output data of the current data processing node is a vector of other dimensions, and the input data supported by the downstream data processing node is a color RGBA vector, then a transparency A component can be added to the vector of other dimensions, and the transparency A component can be set to a preset transparency. The preset transparency can be any value, optionally 1.

[0089] The technical solution of this disclosure involves obtaining the input data of the current data processing node, determining the data type of the input data, and then, if the data type of the input data exists in the pre-stored type correspondence information, querying the data type of the output data corresponding to the data type of the input data based on the type correspondence information. Based on the data type of the input data and the corresponding data type of the output data, the data type of the current data processing node is configured. Furthermore, upon receiving a matching failure notification from a downstream data processing node, a type conversion node is added between the downstream data processing node and the current data processing node. Finally, based on the type conversion node, the data type of the output data of the current data processing node is converted to the data type of the input data supported by the downstream data processing node. This solves the problems in the prior art where users need to manually configure the data type of the data processing node, and the configuration operation needs to be repeatedly performed, resulting in a large amount of labor and time costs in the data type configuration process and reduced data transmission efficiency. It achieves the effect of matching the data types of any two interconnected data processing nodes even if their data types do not match by adding a type conversion node, simplifying the data type matching process, improving the data type matching efficiency, and thus improving the data flow transmission efficiency. At the same time, it meets the personalized needs of users and improves the user experience.

[0090] Figure 3 This is a flowchart illustrating another data type matching method provided in this embodiment. Based on the above embodiments, when data type matching between the current data processing node and the downstream data processing node fails, the data type of the current data processing node can be updated based on the type correspondence information of the current data processing node, so as to re-attempt data type matching with the downstream data processing node based on the updated data type. Detailed implementation can be found in the description of this embodiment. Technical features that are the same as or similar to those in the foregoing embodiments will not be repeated here.

[0091] like Figure 3 As shown, the method in this embodiment may specifically include:

[0092] S310. For the current data processing node, obtain the input data of the current data processing node and determine the data type of the input data.

[0093] S320. If the data type of the input data exists in the pre-stored type correspondence information, query the data type of the output data corresponding to the data type of the input data based on the type correspondence information.

[0094] S330. Configure the data type of the current data processing node based on the data type of the input data and the data type of the output data corresponding to the data type of the input data.

[0095] S340. If a matching failure notification is received from a downstream data processing node and there is another output data type that corresponds to the data type of the input data in the type correspondence information, the data type of the output data corresponding to the data type of the input data is switched based on the type correspondence information.

[0096] In practical applications, for downstream data processing nodes, the input data of the downstream data processing node is obtained, and the data type of the input data is determined. Based on the data type of the input data, the type-correspondence information pre-stored in the downstream data processing node is traversed and queried to determine if the data type of the input data exists in the type-correspondence information of the downstream data processing node. If not, a matching failure notification is generated and sent to the current data processing node connected to the downstream data processing node. Furthermore, when the current data processing node receives the matching failure notification from the downstream data processing node, it can again traverse the pre-stored type-correspondence information in the current data processing node to determine if there are other output data data types besides the already determined output data data type that correspond to the data type of the input data. If so, the data type of the output data corresponding to the input data data type can be switched according to the other output data data types that correspond to the input data data type, thereby changing the data type of the output data corresponding to the input data data type to the other output data data types included in the type-correspondence information that correspond to the input data data type.

[0097] For example, continuing with the previous example, the data types of the output data corresponding to data type A1 include data type B2, data type B3, and data type B4. If the data type of the output data is determined to be data type B2, then the data types of the other output data are data type B3 and data type B4. At this time, the data type of the output data can be switched from data type B2 to data type B3 or data type B4 based on the type correspondence information.

[0098] It should be noted that when querying the data type of other output data corresponding to the data type of the input data based on the pre-stored type correspondence information, the query can also be performed in the type correspondence information according to the preset information query order. The first data type of the other output data corresponding to the data type of the input data will be used as the data type of the other output data corresponding to the data type of the input data. Optionally, the information query order can be random query or sequential query, etc.

[0099] S350: Based on the data type of the input data and the data type of the output data after switching, update the configuration of the data type of the current data processing node.

[0100] In practical applications, after switching the data type of the output data corresponding to the data type of the input data based on the type correspondence information, the data type of the current data processing node can be updated to the data type of the input data and the data type of the switched output data to obtain a new data type combination corresponding to the current data processing node. Then, the current data processing node can continue to execute the data transmission process according to the updated data type combination.

[0101] Furthermore, after updating the data type configuration of the current data processing node, the data type of the updated output data can be re-matched with the data type of the input data of the downstream data processing node. If the match is successful, the data type matching and data transmission process between subsequent data processing nodes can continue. If the match fails, a matching failure notification is generated again and sent to the current data processing node so that when the current data processing node receives the matching failure notification, the data type conversion process can be executed again.

[0102] The technical solution of this disclosure involves obtaining the input data of the current data processing node, determining the data type of the input data, and then, if the data type of the input data exists in the pre-stored type correspondence information, querying the data type of the output data corresponding to the data type of the input data based on the type correspondence information. Subsequently, the data type of the current data processing node is configured based on the data type of the input data and the data type of the output data corresponding to the data type of the input data. Furthermore, if a matching failure notification is received from a downstream data processing node and other data types of output data corresponding to the data type of the input data exist in the type correspondence information, the data type of the input data is switched based on the type correspondence information. The corresponding output data data type is then determined. Finally, based on the input data data type and the switched output data data type, the configuration of the data type for the current data processing node is updated. This solves the problems in existing technologies where users need to manually configure the data type of data processing nodes and repeatedly perform configuration operations, resulting in significant labor and time costs and reduced data transmission efficiency. The new technology enables the reconfiguration of the data type of any two interconnected data processing nodes based on their type correspondence information, even when their data types do not match. This improves the intelligence of the data type configuration process and enhances the possibility of data type matching between data processing nodes.

[0103] Figure 4 This is a flowchart illustrating another data type matching method provided in this embodiment. Based on the above embodiments, the technical solution of this embodiment can pre-determine the data types of input data supported by the current data processing node and the corresponding data types of output data. Then, based on the correspondence between the data types of input data and output data, type correspondence information is established to configure the data types of the current data processing node. Detailed implementation methods can be found in the description of this embodiment. Technical features that are the same as or similar to those in the foregoing embodiments will not be repeated here.

[0104] like Figure 4 As shown, the method in this embodiment may specifically include:

[0105] S410. For the current data processing node, obtain the input data of the current data processing node and determine the data type of the input data.

[0106] S420. Obtain the data types of input data supported by the current data processing node.

[0107] In this embodiment, the supported input data data types can be those that the data processing node can execute data processing procedures for; that is, the data data data types that the data processing node can process. Accordingly, the input data data data types supported by the current data processing node are those that the current data processing node can process.

[0108] In practical applications, for the current data processing node, we can first obtain the data types of input data supported by the current data processing node, and then determine the data type of output data corresponding to the data type of input data based on the obtained data type of input data and the current data processing node.

[0109] It should be noted that the current data processing node supports one or more types of input data. Regardless of whether it is one or more, it can be processed based on the technical solution provided in the embodiments of this disclosure.

[0110] It should be noted that the data type of input data supported by the current data processing node can be obtained based on the data type information corresponding to the data processing node that is pre-stored. This data type information can be information that developers set in advance during the development phase; or, it can be obtained by receiving the setting operation input by the user during the application phase regarding the data type of input data supported by the current data processing node, so as to determine the data type of input data supported by the current data processing node based on the setting operation; or, it can be obtained in other ways, which are not specifically limited in this embodiment.

[0111] S430. Based on the data type of the input data and at least one data processing method corresponding to the current data processing node, determine the data type of the output data corresponding to the input data.

[0112] In this embodiment, the data processing method can be a method that is pre-deployed in the current data processing node to process the input data of the current data processing node.

[0113] In practical applications, after determining the data types of input data supported by the current data processing node, at least one data processing method pre-deployed in the current data processing node can be determined. Furthermore, for each data processing method, the input data can be processed according to the data processing method to obtain output data, and the data type of the output data can be determined. After all the data processing methods corresponding to the current data processing node have processed the input data, the data types of the obtained output data can be statistically analyzed, thereby determining the data type of the output data corresponding to the data type of the input data.

[0114] It should be noted that the number of output data types corresponding to the data types of the input data and the number of data processing methods corresponding to the current data processing node can be in a one-to-one correspondence, that is, for each data processing method, there is a corresponding data type of output data; or, they can not be in a one-to-one correspondence, that is, the data types of the output data obtained by processing the input data based on multiple different data processing methods can be the same.

[0115] S440. Establish type correspondence information based on the correspondence between the data types of input data and the data types of output data, and store the type correspondence information.

[0116] In practical applications, after determining the data types of input data supported by the current data processing node, and the corresponding data types of output data, type correspondence information can be established based on the correspondence between the data types of input data and the corresponding data types of output data, and this type correspondence information can be stored in the current data processing node.

[0117] S450. If the data type of the input data exists in the pre-stored type correspondence information, query the data type of the output data corresponding to the data type of the input data based on the type correspondence information.

[0118] S460. Configure the data type of the current data processing node based on the data type of the input data and the data type of the output data corresponding to the data type of the input data.

[0119] The technical solution of this disclosure, for the current data processing node, obtains the input data of the current data processing node, determines the data type of the input data, then obtains the data types of the input data supported by the current data processing node, then determines the data type of the output data corresponding to the input data based on the data type of the input data and at least one data processing method corresponding to the current data processing node, establishes type correspondence information based on the correspondence between the data types of the input data and the data types of the output data, and stores the type correspondence information. Further, if the data type of the input data exists in the pre-stored type correspondence information, the data type of the output data corresponding to the data type of the input data is queried based on the type correspondence information. Finally, the data type of the current data processing node is configured based on the data type of the input data and the data type of the output data corresponding to the data type of the input data. This solves the problems in the prior art where users need to manually configure the data type of the data processing node, and the configuration operation needs to be repeatedly performed, resulting in a large amount of labor and time costs in the data type configuration process, reducing data transmission efficiency. It achieves the effect of automatically configuring the data type of the data processing node through pre-determined type correspondence information, shortens the data type configuration time, improves the data type configuration efficiency, and thus improves the user experience.

[0120] Figure 5 This is a schematic diagram of the structure of a data type matching device provided in an embodiment of the present disclosure, as shown below. Figure 5 As shown, the device includes: an input data type acquisition module 510, an output data type determination module 520, and a node data type configuration module 530.

[0121] The input data type acquisition module 510 is used to acquire the input data of the current data processing node and determine the data type of the input data.

[0122] The output data type determination module 520 is used to query the data type of the output data corresponding to the data type of the input data based on the type correspondence information when the data type of the input data exists in the pre-stored type correspondence information, wherein the type correspondence information is used to indicate the correspondence between the data types of the input data and the data types of the output data supported by the current data processing node;

[0123] The node data type configuration module 530 is used to configure the data type of the current data processing node based on the data type of the input data and the data type of the output data corresponding to the data type of the input data.

[0124] Optionally, the output data type determination module 520 includes: an information query unit and an output data type determination unit.

[0125] The information query unit is used to query the information corresponding to the type according to the data type of the input data and the preset information query order;

[0126] The output data type determination unit is used to take the first data type of the output data that corresponds to the data type of the input data as the data type of the output data corresponding to the data type of the input data.

[0127] Optionally, the device further includes: a type conversion node adding module and a data type conversion module.

[0128] A type conversion node adding module is used to add a type conversion node between the downstream data processing node and the current data processing node when a matching failure notification is received from the downstream data processing node.

[0129] The data type conversion module is used to convert the data type of the output data of the current data processing node into the data type of the input data supported by the downstream data processing node based on the type conversion node.

[0130] Optionally, the type conversion node adding module includes: type conversion node adding unit.

[0131] A type conversion node adding unit is used to add a type conversion node between the downstream data processing node and the current data processing node when there is no other output data data type corresponding to the data type of the input data in the type correspondence information.

[0132] Optionally, the type conversion node adding module also includes: a type conversion node display unit and a data type configuration operation receiving unit.

[0133] A type conversion node display unit is used to display type conversion nodes connected between the downstream data processing node and the current data processing node;

[0134] A data type configuration operation receiving unit is configured to receive a data type configuration operation input for the type conversion node, wherein the type configuration operation includes a configuration operation for the data type to be converted and / or the converted data type of the type conversion node, the data type to be converted of the type conversion node is the data type of the output data of the current data processing node, and the converted data type of the type conversion node is the data type of the input data supported by the downstream data processing node.

[0135] Optionally, a type conversion node display unit is specifically used to display the type conversion node connected between the downstream data processing node and the current data processing node in response to a node type configuration trigger operation input for the current data processing node.

[0136] Optionally, the device further includes a matching failure notification generation module.

[0137] The matching failure notification generation module is used to generate a matching failure notification when the data type of the input data does not exist in the pre-stored type correspondence information, and to feed the matching failure notification back to the upstream data processing node.

[0138] Optionally, the device further includes: a data type switching module and a data type configuration update module.

[0139] The data type switching module is used to switch the data type of the output data corresponding to the data type of the input data based on the type correspondence information when a matching failure notification is received from a downstream data processing node and there is another data type of output data corresponding to the data type of the input data in the type correspondence information.

[0140] The data type configuration update module is used to update the data type configuration of the current data processing node based on the data type of the input data and the data type of the output data after the switch.

[0141] Optionally, the device further includes: a data type acquisition module, a data type determination module, and a type correspondence information establishment module.

[0142] The data type acquisition module is used to acquire the data type of the input data supported by the current data processing node before querying the data type of the output data corresponding to the data type of the input data based on the type correspondence information.

[0143] The data type determination module is used to determine the data type of the output data corresponding to the input data based on the data type of the input data and at least one data processing method corresponding to the current data processing node;

[0144] The type correspondence information establishment module is used to establish type correspondence information based on the correspondence between the data type of the input data and the data type of the output data, and to store the type correspondence information.

[0145] The technical solution of this disclosure, for the current data processing node, obtains the input data of the current data processing node, determines the data type of the input data, and further, if the data type of the input data exists in the pre-stored type correspondence information, queries the data type of the output data corresponding to the data type of the input data based on the type correspondence information. Finally, based on the data type of the input data and the data type of the output data corresponding to the data type of the input data, the data type of the current data processing node is configured. This solves the problems in the prior art where users need to manually configure the data type of the data processing node, and the configuration operation needs to be repeatedly performed, resulting in a large amount of labor and time costs in the data type configuration process, reducing data transmission efficiency. It achieves the effect of automated configuration of data type of data processing node, simplifies the data type configuration process, improves the data type configuration efficiency, and thus improves the data flow transmission efficiency and enhances the user experience.

[0146] The data type matching apparatus provided in this disclosure can execute the data type matching method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects of the method execution.

[0147] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of this disclosure.

[0148] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Reference is made below. Figure 6 It illustrates an electronic device suitable for implementing embodiments of the present disclosure (e.g., Figure 6The diagram below shows the structure of the terminal device or server 600. The terminal device in this embodiment may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), and vehicle terminals (e.g., vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0149] like Figure 6 As shown, electronic device 600 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 608 into random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of electronic device 600. The processing unit 601, ROM 602, and RAM 603 are interconnected via bus 604. An edit / output (I / O) interface 605 is also connected to bus 604.

[0150] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0151] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 609, or installed from a storage device 608, or installed from a ROM 602. When the computer program is executed by the processing device 601, it performs the functions defined in the methods of embodiments of this disclosure.

[0152] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0153] The electronic device provided in this embodiment and the data type matching method provided in the above embodiments belong to the same inventive concept. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0154] This disclosure provides a computer storage medium storing a computer program that, when executed by a processor, implements the data type matching method provided in the above embodiments.

[0155] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0156] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0157] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0158] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: acquire input data of the current data processing node and determine the data type of the input data for the current data processing node;

[0159] If the data type of the input data exists in the pre-stored type correspondence information, the data type of the output data corresponding to the data type of the input data is queried based on the type correspondence information, wherein the type correspondence information is used to indicate the correspondence between the data types of the input data and the data types of the output data supported by the current data processing node;

[0160] The data type of the current data processing node is configured based on the data type of the input data and the data type of the output data corresponding to the data type of the input data.

[0161] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0162] 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 this disclosure. 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 the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can 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.

[0163] The units described in the embodiments of this disclosure can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0164] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0165] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0166] According to one or more embodiments of this disclosure, [Example 1] provides a data type matching method, the method comprising:

[0167] For the current data processing node, obtain the input data of the current data processing node and determine the data type of the input data;

[0168] If the data type of the input data exists in the pre-stored type correspondence information, the data type of the output data corresponding to the data type of the input data is queried based on the type correspondence information, wherein the type correspondence information is used to indicate the correspondence between the data types of the input data and the data types of the output data supported by the current data processing node;

[0169] The data type of the current data processing node is configured based on the data type of the input data and the data type of the output data corresponding to the data type of the input data.

[0170] According to one or more embodiments of this disclosure, Example 2 provides the method of Example 1, which further includes:

[0171] Optionally, the information corresponding to the type can be queried according to the data type of the input data and the preset information query order;

[0172] The first data type of the output data that corresponds to the data type of the input data is used as the data type of the output data corresponding to the data type of the input data.

[0173] According to one or more embodiments of this disclosure, Example 3 provides the method of Example 1, which further includes:

[0174] Optionally, upon receiving a matching failure notification from a downstream data processing node, a type conversion node is added between the downstream data processing node and the current data processing node.

[0175] Based on the type conversion node, the data type of the output data of the current data processing node is converted into the data type of the input data supported by the downstream data processing node.

[0176] According to one or more embodiments of this disclosure, Example 4 provides the method of Example 3, which further includes:

[0177] Optionally, if there is no other output data data type corresponding to the data type of the input data in the type correspondence information, a type conversion node is added between the downstream data processing node and the current data processing node.

[0178] According to one or more embodiments of this disclosure, Example 5 provides the method of Example 3, which further includes:

[0179] Optionally, a type conversion node connected between the downstream data processing node and the current data processing node may be displayed;

[0180] The system receives a data type configuration operation input to the type conversion node, wherein the type configuration operation includes a configuration operation for the data type to be converted and / or the converted data type of the type conversion node, the data type to be converted of the type conversion node is the data type of the output data of the current data processing node, and the converted data type of the type conversion node is the data type of the input data supported by the downstream data processing node.

[0181] According to one or more embodiments of this disclosure, Example Six provides the method of Example Five, which further includes:

[0182] Optionally, in response to a node type configuration trigger operation input for the current data processing node, a type conversion node connected between the downstream data processing node and the current data processing node is displayed.

[0183] According to one or more embodiments of this disclosure, Example 7 provides the method of Example 1, which further includes:

[0184] Optionally, if the data type of the input data is not found in the pre-stored type correspondence information, a matching failure notification is generated and the matching failure notification is fed back to the upstream data processing node.

[0185] According to one or more embodiments of this disclosure, Example 8 provides the method of Example 1, which further includes:

[0186] Optionally, if a matching failure notification is received from a downstream data processing node and there is another data type of output data in the type correspondence information that corresponds to the data type of the input data, the data type of the output data corresponding to the data type of the input data is switched based on the type correspondence information.

[0187] Based on the data type of the input data and the data type of the output data after the switch, update the configuration of the data type of the current data processing node.

[0188] According to one or more embodiments of this disclosure, [Example Nine] provides the method of Example One, which, before querying the data type of the output data corresponding to the data type of the input data based on the type correspondence information, further includes:

[0189] Optionally, the data types of input data supported by the current data processing node can be obtained;

[0190] Based on the data type of the input data and at least one data processing method corresponding to the current data processing node, determine the data type of the output data corresponding to the input data;

[0191] Type correspondence information is established based on the correspondence between the data types of the input data and the data types of the output data, and the type correspondence information is stored.

[0192] According to one or more embodiments of this disclosure, [Example 10] provides a data type matching apparatus, the apparatus comprising:

[0193] The input data type acquisition module is used to acquire the input data of the current data processing node and determine the data type of the input data;

[0194] The output data type determination module is used to query the data type of the output data corresponding to the data type of the input data based on the type correspondence information when the data type of the input data exists in the pre-stored type correspondence information, wherein the type correspondence information is used to indicate the correspondence between the data types of the input data and the data types of the output data supported by the current data processing node;

[0195] The node data type configuration module is used to configure the data type of the current data processing node based on the data type of the input data and the data type of the output data corresponding to the data type of the input data.

[0196] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0197] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0198] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A data type matching method, characterized in that, This is applied to a data stream processing system, which includes multiple data processing nodes. The data stream is used to characterize each data processing stage in the data processing flow and the data transmission relationship between each data processing stage. The data type matching method includes: For the current data processing node, obtain the input data of the current data processing node, and determine the data type of the input data, wherein the current data processing node is one of a plurality of data processing nodes; Based on the data processing algorithms pre-deployed in the current data processing node for processing input data, determine the mapping relationship between the data types of input data and the data types of output data supported by the current data processing node, and establish and store type correspondence information. If the data type of the input data exists in the pre-stored type correspondence information, query the data type of the output data corresponding to the data type of the input data based on the type correspondence information; Based on the data type of the input data and the data type of the output data corresponding to the data type of the input data, the receivable data type of the current data processing node is configured as the data type of the input data, and the output data type of the current data processing node is configured as the data type of the output data. The configured current data processing node is used to receive data from the upstream data processing node based on the configured receivable data type, and to transmit data to the downstream data processing node based on the configured output data type.

2. The data type matching method according to claim 1, characterized in that, The step of querying the data type of the output data corresponding to the data type of the input data based on the type correspondence information includes: The information corresponding to the type is queried according to the data type of the input data and the preset information query order; The first data type of the output data that corresponds to the data type of the input data is used as the data type of the output data corresponding to the data type of the input data.

3. The data type matching method according to claim 1, characterized in that, Also includes: Upon receiving a matching failure notification from a downstream data processing node, a type conversion node is added between the downstream data processing node and the current data processing node. Based on the type conversion node, the data type of the output data of the current data processing node is converted into the data type of the input data supported by the downstream data processing node.

4. The data type matching method according to claim 3, characterized in that, Adding a type conversion node between the downstream data processing node and the current data processing node includes: If there is no other output data data type corresponding to the data type of the input data in the type correspondence information, a type conversion node is added between the downstream data processing node and the current data processing node.

5. The data type matching method according to claim 3, characterized in that, Adding a type conversion node between the downstream data processing node and the current data processing node includes: Display the type conversion node that connects the downstream data processing node and the current data processing node; The system receives a data type configuration operation input to the type conversion node, wherein the type configuration operation includes a configuration operation for the data type to be converted and / or the converted data type of the type conversion node, the data type to be converted of the type conversion node is the data type of the output data of the current data processing node, and the converted data type of the type conversion node is the data type of the input data supported by the downstream data processing node.

6. The data type matching method according to claim 5, characterized in that, The display connects the type conversion node between the downstream data processing node and the current data processing node, including: In response to a node type configuration trigger operation input for the current data processing node, a type conversion node connected between the downstream data processing node and the current data processing node is displayed.

7. The data type matching method according to claim 1, characterized in that, Also includes: If the data type of the input data is not found in the pre-stored type correspondence information, a matching failure notification is generated and the matching failure notification is fed back to the upstream data processing node.

8. The data type matching method according to claim 1, characterized in that, Also includes: If a matching failure notification is received from a downstream data processing node and there is another data type of output data in the type correspondence information that corresponds to the data type of the input data, the data type of the output data corresponding to the data type of the input data is switched based on the type correspondence information. Based on the data type of the input data and the data type of the output data after the switch, update the configuration of the data type of the current data processing node.

9. The data type matching method according to claim 1, characterized in that, Before querying the data type of the output data corresponding to the data type of the input data based on the type correspondence information, the method further includes: Obtain the data types of input data supported by the current data processing node; Based on the data type of the input data and at least one data processing method corresponding to the data processing node, determine the data type of the output data corresponding to the input data; Type correspondence information is established based on the correspondence between the data types of the input data and the data types of the output data, and the type correspondence information is stored.

10. A data type matching device, characterized in that, An apparatus for use in a data stream processing system, the data stream processing system comprising multiple data processing nodes, wherein the data stream is used to characterize the various data processing stages in the data processing flow and the data transmission relationships between the various data processing stages; the apparatus includes: The mapping relationship establishment module is used to determine the mapping relationship between the data types of input data and the data types of output data supported by the current data processing node based on the data processing algorithms pre-deployed in the current data processing node for processing input data, and to establish and store type correspondence information. The input data type acquisition module is used to acquire the input data of the current data processing node and determine the data type of the input data, wherein the current data processing node is one of the plurality of data processing nodes; The output data type determination module is used to query the data type of the output data corresponding to the data type of the input data based on the type correspondence information when the data type of the input data exists in the pre-stored type correspondence information. The node data type configuration module is used to configure the receivable data type of the current data processing node as the data type of the input data and the data type of the output data corresponding to the data type of the input data, and to configure the output data type of the current data processing node as the data type of the output data. The configured current data processing node is used to receive data from upstream data processing nodes based on the configured receivable data type and to transmit data to downstream data processing nodes based on the configured output data type.

11. An electronic device, characterized in that, The electronic device includes: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the data type matching method as described in any one of claims 1-9.

12. A storage medium containing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to perform the data type matching method as described in any one of claims 1-9.

Images