Data processing method and apparatus and related device

Abstract

A data processing method and a computing device. By means of constructed relationship records and change information inputted by a user, affected points can be automatically queried, thereby improving efficiency and convenience. In addition, the affected points further comprise interfaces. Therefore, the solution can identify the impact of change information on interfaces, making inspection results more complete and accurate.

Description

A data processing method, device and related equipment

[0001] The present application claims priority to the Chinese patent application No. 202410543736.7, filed on April 30, 2024, with the State Intellectual Property Office of China, and the Chinese patent application No. 202410543736.7 has the title of “Change analysis method, device, computing device cluster and storage medium”, the content of which is incorporated herein by reference in its entirety.

[0002] The present application claims priority to the Chinese patent application No. 202411036984.9, filed on July 30, 2024, with the State Intellectual Property Office of China, and the Chinese patent application No. 202411036984.9 has the title of “A data processing method, device and related equipment”, the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present application relates to the field of data processing, and more particularly, to a data processing method, device and related equipment. BACKGROUND

[0004] Iterative updating of software systems is inevitable and very frequent in the software life cycle. When the software is changed, the source code and the database of the system software are changed accordingly. Each version change, especially the transactional business system of large enterprises mainly using relational databases, is accompanied by inevitable database changes (for example, deleting tables, deleting fields in tables, etc.). Through the change operation of the related table structure of the relational database, the specific business logic is adapted.

[0005] In a complex business scenario (for example, a cloud system), there may be a very long influence chain in the database, because the interfaces also call fields on each other. When a database needs to be changed due to business demands (for example, tables and fields in the database need to be deleted or changed), designers and developers cannot quickly analyze which external interfaces and tables will be affected after the change. At this time, manual full-scale analysis of the code based on historical experience is required, which is not only inefficient but also has low accuracy.

[0006] Therefore, a data processing method is needed to improve the analysis efficiency and ensure the accuracy of the analysis results. SUMMARY

[0007] The present application provides a data processing method, which can efficiently query the influence points and ensure the accuracy of the query results by constructing relationship records.

[0008] In a first aspect, a data processing method is provided, which can be performed by a computing device (e.g., a server) or a component (e.g., a chip or a circuit) of the computing device.

[0009] For example, the method can be applied to a data processing platform, which is communicatively connected to a business processing platform including at least one table and at least one interface.

[0010] The method includes receiving change information input by a user, the change information including a target field to be changed, the target field being a field in the at least one table; and displaying an analysis result to the user, the analysis result being generated according to the change information and a relationship record, the relationship record being used to indicate the at least one table, at least one field included in each of the at least one table, and at least one interface related to each of the at least one table, at least one field corresponding to each of the at least one interface, wherein the analysis result includes at least one impact point, each of the at least one impact point including a table and / or an interface affected in a case where the target field is changed, and at least one field corresponding to the table and / or the interface affected in the case where the target field is changed being the same as the target field.

[0011] In the embodiments of the present application, the "related" in the "at least one interface related to each of the at least one table" can be understood as that at least one field included in a certain table in the at least one table and at least one field corresponding to a certain interface in the at least one interface overlap.

[0012] In the embodiments of the present application, the "corresponding" in the "at least one field corresponding to each of the at least one interface" can be understood as that an input parameter of the interface uses a certain field or an output parameter of the interface uses a certain field.

[0013] In a possible implementation, the change information can include the target field and a table corresponding to the target field, wherein the at least one table includes the table corresponding to the target field. For example, the table corresponding to the target field can be understood as a table in which the target field is located.

[0014] In the present application, by constructing the relationship record and the change information input by the user, each impact point can be automatically queried, thereby being more efficient and convenient. In addition, the impact point in the present application also includes an interface, so that the influence of the change information on the interface can be identified in the scheme of the present application, and the result of the investigation is more complete and accurate.

[0015] In a possible implementation manner of the first aspect, the relationship record is further used to indicate a dependency relationship between the plurality of interfaces and / or a dependency relationship between the at least one interface and the at least one table, and the analysis result further includes at least one influence chain, the at least one influence chain including a relationship between a plurality of influence points.

[0016] In the embodiments of the present application, the at least one influence chain including a relationship between a plurality of influence points can also be understood as the at least one influence chain being used to indicate a relationship between a plurality of influence points. For example, the at least one influence chain can be used to indicate that there is a dependency relationship between some influence points, or there is no dependency relationship between some influence points.

[0017] Based on the above technical solution, in the present application, the relationship between the influence points can be obtained based on the dependency relationship in the relationship record, so as to output the at least one influence chain to the user. Since the at least one influence chain can indicate the relationship between the plurality of influence points, the analysis result is more clear, and the user experience is better.

[0018] In a possible implementation manner of the first aspect, the change information further includes a target table to be changed and a table change type, and each influence point further includes a table and / or an interface affected in a case where the target table is changed, and the at least one table includes the target table.

[0019] In a possible implementation manner, in a case where the table change type is deleting a table, at least one field corresponding to the table and / or the interface affected in the case where the target table is changed is the same as at least one field included in the target table.

[0020] In a possible implementation manner, in a case where the table change type is changing a table index, at least one field corresponding to the table and / or the interface affected in the case where the target table is changed includes a table index to be changed in the target table, and the table change type is used to indicate the table index to be changed in the target table.

[0021] In a possible implementation manner, in a case where the table change type is changing a table primary key, at least one field corresponding to the table and / or the interface affected in the case where the target table is changed includes a table primary key to be changed in the target table, and the table change type is used to indicate the table primary key to be changed in the target table.

[0022] In a possible implementation manner, in a case where the table change type is changing a table name, the interface affected in the case where the target table is changed has a direct dependency relationship with the target table.

[0023] With reference to the first aspect, in a possible implementation manner, the change information further comprises a field change type, and the analysis result further comprises an optimization suggestion of the field change, the optimization suggestion of the field change being used to indicate an optimization suggestion for the at least one impact point in a case where the target field is changed in the field change type.

[0024] With reference to the first aspect, in a possible implementation manner, the optimization suggestion of the field change is generated according to the field change type, the at least one impact point, and a knowledge base, the knowledge base storing optimization suggestions corresponding to a plurality of field change types respectively.

[0025] For example, in a case where the field change type is changing a field length, the optimization suggestion is that the length of the field to be changed in each impact point is changed accordingly; in a case where the field change type is deleting a field, the optimization suggestion is that the field to be changed in each impact point is deleted; and in a case where the field change type is changing a field data type, the optimization suggestion is that the data type of the field to be changed in each impact point is changed accordingly.

[0026] In the embodiment of the present application, if the change information input by the user initially comprises the target field, after the at least one impact point is obtained, if the user wants to obtain the optimization suggestion of each of the at least one impact point, the user can further input the field change type (equivalent to that the change information comprises the target field and the field change type, or the change information comprises the target field, the table corresponding to the target field, and the field change type) to obtain the optimization suggestion of the field change for each of the impact points.

[0027] With reference to the first aspect, in a possible implementation manner, the field change type comprises at least one of the following: changing a field name, changing a field data type, changing a field length, changing a field format, changing a field enumeration value, and deleting a field.

[0028] For example, the changing of the field data type can be understood as changing the field data type from a string type to an integer type.

[0029] For example, the changing of the field format can be understood as changing the original time format (which can be understood as being controlled by a field) of 2024-05-17 15:28:30 to 15:28:30 2024-05-17, or changing the time format to 2024 / 05 / 17 15:28:30.

[0030] For example, the "change field enumeration value" can include addition and deletion. For example, when selecting an address, a province is selected, the province is a field in the system (for example, in a table), and the content stored in the field is an enumeration value. For example, the field of the current province has a total of 31 enumeration values, which are the names of various provinces. Assuming that a province or municipality is added, there is an additional enumeration value. Assuming that a municipality is merged into a province, an enumeration value is deleted.

[0031] In a possible implementation of the first aspect, in a case where the change information includes a target table to be changed and a table change type, the analysis result further includes an optimization suggestion for the table change, the optimization suggestion for the table change being used to indicate an optimization suggestion for at least one influence point in a case where the target table is changed in the table change type.

[0032] In a possible implementation of the first aspect, the optimization suggestion for the table change is generated according to the table change type, the at least one influence point, and a knowledge base, and the knowledge base stores a plurality of optimization suggestions corresponding to a plurality of table change types respectively.

[0033] For example, in a case where the table change type is deletion of a table, the optimization suggestion is that a structured query language (SQL) statement related to the target table in each influence point can need to be adjusted. In a case where the table change type is change of a table index, the optimization suggestion is that a SQL statement related to a table index to be changed of the target table in each influence point can need to be adjusted. In a case where the table change type is change of a table primary key, the optimization suggestion is that a SQL statement related to a table primary key to be changed of the target table in each influence point can need to be adjusted. In a case where the table change type is change of a table name, the optimization suggestion is that a SQL statement related to a table name to be changed of the target table in each influence point can need to be adjusted.

[0034] In a possible implementation of the first aspect, the optimization suggestion is generated according to the field change type, the at least one influence point, and a knowledge base, or the optimization suggestion is generated according to the table change type, the at least one influence point, and the knowledge base, and the knowledge base stores a plurality of optimization suggestions corresponding to a plurality of field change types respectively and a plurality of optimization suggestions corresponding to a plurality of table change types respectively.

[0035] With reference to the first aspect, in a possible implementation manner, the method further includes: obtaining data information, the data information including at least two of the following: a respective name of each of the at least one table, at least one field included in each table, a type and a length of each field in each table, a respective address of at least one interface corresponding to the table, at least one field corresponding to each of the at least one interface, a type and a length of the field corresponding to each of the at least one interface, an interface type to which the field corresponding to each of the at least one interface belongs, a dependency relationship between the interfaces, and a dependency relationship between the at least one interface and the at least one table; and generating the relationship record according to the data information.

[0036] In the present application, the interface type to which the field corresponding to each of the interfaces belongs can be understood as whether the field corresponding to the interface is an input parameter or an output parameter.

[0037] Based on the technical solution described above, in the present application, data can be collected by, for example, a data model service (DMS) platform, an application programming interface Designer (API Designer) platform, and an application performance management (APM) platform, so as to construct the relationship record.

[0038] With reference to the first aspect, in a possible implementation manner, the method can also be executed by an infrastructure providing cloud services. The infrastructure includes at least one cloud data center, each of the at least one cloud data center including at least one server, the at least one server storing the relationship record.

[0039] The second aspect provides a data processing method, which can be executed by, for example, a computing device (for example, a server) or a component (for example, a chip or a circuit) of the computing device.

[0040] For example, the method can be applied to a data processing platform, the data processing platform being in communication connection with a business processing platform, the business processing platform including at least one table and at least one interface.

[0041] The method comprises: receiving user input change information, the change information comprising a target table to be changed and a table change type, the at least one table comprising the target table; and displaying an analysis result to the user, the analysis result being generated according to the change information and a relationship record, the relationship record being used to indicate the at least one table, at least one field included in each of the at least one table, and at least one interface related to each of the at least one table, at least one field corresponding to each of the at least one interface, wherein the analysis result comprises at least one impact point, each of the at least one impact point comprising a table and / or an interface affected in a case where the target table is changed (i.e., in a case where the target table is changed in the table change type), the at least one table comprising the target table to be changed.

[0042] With reference to the second aspect, in a possible implementation, the relationship record is further used to indicate a dependency relationship between the plurality of interfaces and / or a dependency relationship between the at least one interface and the at least one table, and the analysis result further comprises at least one impact chain, the at least one impact chain comprising a relationship between the plurality of impact points.

[0043] With reference to the second aspect, in a possible implementation, in a case where the table change type is deleting a table, the at least one field corresponding to the table and / or the interface affected in the case where the target table is changed is the same as at least one field included in the target table.

[0044] With reference to the second aspect, in a possible implementation, in a case where the table change type is changing a table index, the at least one field corresponding to the table and / or the interface affected in the case where the target table is changed comprises a table index to be changed in the target table, and the table change type is used to indicate the table index to be changed in the target table.

[0045] With reference to the second aspect, in a possible implementation, in a case where the table change type is changing a table primary key, the at least one field corresponding to the table and / or the interface affected in the case where the target table is changed comprises a table primary key to be changed in the target table, and the table change type is used to indicate the table primary key to be changed in the target table.

[0046] With reference to the second aspect, in a possible implementation, in a case where the table change type is changing a table name, the interface related to the target table in the case where the target table is changed is directly dependent.

[0047] With reference to the second aspect, in a possible implementation, the analysis result further comprises an optimization suggestion for the table change, the optimization suggestion for the table change being used to indicate an optimization suggestion for the at least one impact point in the case where the target table is changed in the table change type.

[0048] With reference to the second aspect, in a possible implementation manner, the optimization suggestion of the table change is generated according to the table change type, the at least one influence point, and a knowledge base, where the knowledge base stores optimization suggestions corresponding to a plurality of table change types respectively.

[0049] With reference to the second aspect, in a possible implementation manner, the change information further includes a target field to be changed, and at least one field corresponding to the table and / or the interface affected in the case where the target field is changed is the same as the target field, where the at least one table includes the target field to be changed.

[0050] With reference to the second aspect, in a possible implementation manner, the change information further includes a field change type of the target field to be changed, and the analysis result further includes an optimization suggestion of the field change, where the optimization suggestion of the field change is used to indicate an optimization suggestion for the at least one influence point in the case where the target field is changed in the field change type.

[0051] With reference to the second aspect, in a possible implementation manner, the optimization suggestion of the field change is generated according to the field change type, the at least one influence point, and a knowledge base, where the knowledge base stores optimization suggestions corresponding to a plurality of field change types respectively.

[0052] With reference to the second aspect, in a possible implementation manner, the field change type includes at least one of the following: changing a field name, changing a field data type, changing a field length, changing a field format, changing a field enumeration value, and deleting a field.

[0053] In the third aspect, the present application provides a data processing apparatus, which is used to execute the method in the first aspect or the second aspect. Specifically, the apparatus can include units and / or modules for executing the method, such as an input module and a display module.

[0054] For example, the computing device can be a server, a server cluster, or an infrastructure providing cloud services in a cloud service system.

[0055] In the fourth aspect, the present application provides a computing device, which includes at least one processor configured to execute computer programs or instructions stored in a memory to execute the method in the first aspect or the second aspect. Optionally, the device further includes the memory configured to store the computer programs or instructions. Optionally, the device further includes a communication interface through which the processor reads the computer programs or instructions stored in the memory.

[0056] In an implementation manner, the computing device is a device for implementing the functions of the above method in a chip.

[0057] In another implementation, the computing device is a chip, a chip system, or a circuit for implementing the functions of the above method in a chip.

[0058] In a fifth aspect, the present application provides a processor, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method of the first aspect or the second aspect.

[0059] In the implementation, the processor can be one or more chips, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a flip-flop, and various logic circuits. The input signal received by the input circuit can be received and input by, for example but not limited to, a transceiver, the output signal output by the output circuit can be output to and transmitted by, for example but not limited to, a transmitter, and the input circuit and the output circuit can be the same circuit that is used as the input circuit and the output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0060] For the sending and obtaining / receiving operations of the processor, if there is no special description, or if it does not conflict with the actual role or internal logic in the related description, it can be understood as the processor output and receive, input, and the like, or as the sending and receiving operations performed by the radio frequency circuit and the antenna, and the present application does not limit this.

[0061] In a sixth aspect, a processing device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory, and can receive a signal through a transceiver and transmit a signal through a transmitter to execute the method of the first aspect or the second aspect.

[0062] Optionally, the processor is one or more, and the memory is one or more.

[0063] Optionally, the memory can be integrated with the processor, or the memory and the processor can be separately arranged.

[0064] In the implementation, the memory can be a non-transitory memory, for example, a read only memory (ROM), which can be integrated with the processor on the same chip, or can be separately arranged on different chips. The embodiments of the present application do not limit the type of memory and the arrangement of the memory and the processor.

[0065] It should be understood that the relevant data interaction process, for example, sending the first information can be a process of outputting the first information from the processor, and receiving the capability information can be a process of receiving the input capability information by the processor. Specifically, the data output by the processor can be output to the transmitter, and the input data received by the processor can come from the transceiver. Among them, the transmitter and the transceiver can be collectively referred to as a transceiver.

[0066] The processing device in the sixth aspect described above can be one or more chips. The processor in the processing device can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading software codes stored in a memory, which can be integrated in the processor or exist independently outside the processor.

[0067] In a seventh aspect, a computing cluster is provided, including at least one computing device, each computing device including a processor and a memory; the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing cluster performs the method described in any possible implementation manner of the first aspect or the second aspect.

[0068] Optionally, the processor can be a general-purpose processor, which can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading software codes stored in a memory, which can be integrated in the processor or exist independently outside the processor.

[0069] In an eighth aspect, a computer readable storage medium is provided, which stores program codes for execution by a device, and the program codes include codes for executing the method of the first aspect or the second aspect.

[0070] In a ninth aspect, a computer program product including instructions is provided, which, when executed on a computer, causes the computer to execute the method of the first aspect or the second aspect.

[0071] In a tenth aspect, a chip system is provided, including a processor, configured to call and run a computer program from a memory, so that a device installed with the chip system executes the method of the first aspect or the second aspect.

[0072] In an eleventh aspect, a data processing system is provided, the data processing system comprising a data processing platform and a business processing platform, the data processing platform being communicatively coupled to the business processing platform, the business processing platform comprising at least one table and at least one interface, the data processing platform being configured to perform the method of the first aspect or the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0073] FIG. 1 is a schematic diagram of a system architecture to which embodiments of the present application are applicable.

[0074] FIG. 2 is a schematic flowchart of a data processing method 200 according to an embodiment of the present application.

[0075] FIG. 3 is a schematic diagram of a page of a data model service platform according to an embodiment of the present application.

[0076] FIG. 4 is a schematic diagram of a page for parsing an interface definition to obtain parameters used by the interface according to an embodiment of the present application.

[0077] FIG. 5 is a schematic diagram of a page of an interface call chain according to an embodiment of the present application.

[0078] FIG. 6 is another schematic diagram of a data processing method according to an embodiment of the present application.

[0079] FIG. 7 is a schematic diagram of an order placement process according to an embodiment of the present application.

[0080] FIG. 8 is a schematic diagram of a page for querying an impact point according to an embodiment of the present application.

[0081] FIG. 9 is a schematic diagram of a page for optimization suggestions for an impact point according to an embodiment of the present application.

[0082] FIG. 10 is a schematic diagram of a cloud service system architecture according to an embodiment of the present application.

[0083] FIG. 11 is a schematic block diagram of a computing device 1100 according to an embodiment of the present application.

[0084] FIG. 12 is a schematic block diagram of a computing device 1200 according to an embodiment of the present application.

[0085] FIG. 13 is a schematic diagram of an architecture of a computing device cluster according to an embodiment of the present application.

[0086] FIG. 14 is a schematic diagram of a connection between a computing device 1300A and a computing device 1300B via a network according to an embodiment of the present application. DETAILED DESCRIPTION

[0087] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0088] The technical solutions in the present application will be described below with reference to the drawings.

[0089] In order to facilitate the understanding of the technical solutions of the present application, the individual professional terms involved in the present application will be introduced first. It should be noted that the introduction of these terms is for better understanding of the technical solutions, and should not cause any limitation on the solutions of the present application.

[0090] 1. Data standard: for example, it can be understood as a normative constraint that guarantees the consistency and accuracy of internal and external use and exchange of data. For example, "data standard" can be used to regulate the definition and use of tables and fields.

[0091] 2. Model asset: for example, it can be understood as a design output containing the domain model, physical model, logical model, data standard, etc. in the software system. Among them, the "domain model" describes the business entities involved in the business and the relationship between them. Therefore, it can help the demand analysis personnel and users (or user representatives) to understand the actual business, so as to become an important tool for communication between demand analysis personnel and users, a common understanding concept, and a language for communication with each other, and thus can also be understood as a conceptual model. The "logical model" is to materialize the conceptual model, to realize the things described in the conceptual model, and to need which specific functions and to process which specific information. The "physical model" is to realize the above-mentioned logical model on the specific physical medium. For example: the database uses SQL server, so that specific SQL scripts can be written to establish the database on the database server.

[0092] 3. Interface: for example, it can be understood as an entrance for providing services and a channel for data transmission. "Interface" provides a standardized way so that different objects can operate and communicate with each other in the same way. By implementing the same interface, different objects can be type-converted to realize communication. In interface design, input parameters and output parameters jointly define the function and interaction mode of the interface. "Input parameters (also referred to as input parameters for short)" are data provided to the interface when the interface is called. These parameters can be various types of data such as strings, numbers, booleans, etc., used to describe the specific content or conditions of the request. Output parameters (also referred to as output parameters for short) are data returned to the calling party after the interface processes the request. These data usually include the results of request processing, status information and other possible related information.

[0093] A field is a specific data item that constitutes an interface input parameter and an interface output parameter. One parameter (an input parameter or an output parameter) can be composed of one or more fields. For example, an input parameter of a user login interface can include two fields of "username" and "password", and an output parameter can include fields of "user ID", "name", "permission level", and the like. In an interface document, all input and output parameters are usually listed in detail, including their field names, data types, descriptions, whether they are required, and the like.

[0094] 4. Call chain: Exemplarily, in the process of completing a service call of a system, call information (for example, time, interface, result, and the like) between services is dotted into a log, and then all the dotted data is connected into a tree chain to generate a call chain. The tracking system analyzes and processes the log information generated in the process, restores the complete call process of the execution of a service end to end, performs statistical analysis according to different dimensions, thereby identifying abnormal service calls, can quickly analyze and delimit the abnormal service, and can analyze the performance bottleneck of the system according to data statistics. For example, the call chain can be used to indicate the dependency relationship between interfaces or between an interface and an executed SQL.

[0095] Iterative updating of a software system is inevitable and very frequent in the software life cycle. When the software is changed, the source code and the database of the system software are changed accordingly. Each version change, especially the transactional business system of a large enterprise mainly using a relational database, is inevitably accompanied by database changes (for example, deleting a table, deleting a field in a table, and the like). The related table structure of the relational database is modified by adding, deleting, and the like to adapt to specific business logic. In a complex business scenario (for example, a cloud system), there can be a very long influence chain in the database, because the fields between interfaces also call each other. When a model is changed due to business demands (for example, a table or a field in the database needs to be deleted or changed), designers and developers cannot quickly analyze which external interfaces and which tables will be affected after the database is changed. At this time, manual full-scale analysis and code checking based on historical experience are required, which is not only low in efficiency but also low in accuracy. Therefore, a data processing method is needed to improve the analysis efficiency and ensure the accuracy of the analysis result.

[0096] In view of this, the present application provides a data processing method. Through the constructed relationship record and the user input change information, each affected point can be automatically queried, thereby being more efficient and convenient. In addition, the affected point of the present application can also include an interface, so that the influence of the change information on the interface can be identified in the scheme of the present application, and the checking result is more complete and accurate.

[0097] FIG. 1 is a schematic diagram of a system architecture to which the present application is applicable. As shown in FIG. 1, the system architecture includes a business processing platform 110 and a data processing platform 120, wherein the data processing platform 120 is communicatively connected with the business processing platform 110. As shown in FIG. 1, the business processing platform 110 includes design state data 111 and running state data 112, and the data processing platform 120 includes a page query and result display module 121, an analysis module 122, and a knowledge management module 123. The business processing platform includes at least one table and at least one interface.

[0098] The page query and result display module 121 is configured to receive the change information input by the user and display the analysis result to the user.

[0099] In a possible implementation of the present application, the change information includes a target field. The at least one table includes the target field.

[0100] In another possible implementation, the change information can also include the target field and a table corresponding to the target field, and the at least one table includes the table corresponding to the target field. The table corresponding to the target field can be understood as the table in which the target field is located.

[0101] In a possible implementation, the change information further includes a field change type.

[0102] In yet another possible implementation, the change information can also include a target table and a table change type, and the at least one table includes the target table.

[0103] For example, the field change type includes at least one of the following: changing a field name, changing a field data type, changing a field length, changing a field format, changing a field enumeration value, and deleting a field. For example, in this implementation, the analysis result displayed to the user includes at least one impact point, and each of the at least one impact point includes a table and / or an interface affected by the case where the target field is changed in the field change type. The at least one field corresponding to the table and / or the interface affected by the case where the target field is changed is the same as the target field. For example, if the impact point is a table, the table includes the target field that needs to be changed. For another example, if the impact point is an interface, the field corresponding to the interface includes the target field that needs to be changed.

[0104] For example, the table change type includes deleting a table, changing a table name, changing a table index, and changing a table primary key. For example, in this implementation, the analysis result displayed to the user includes at least one impact point, and each of the at least one impact point includes a table and / or an interface affected by the case where the target table is changed in the table change type.

[0105] In an embodiment of the present application, the analysis module 122 is configured to analyze the impact point of the change information. For example, by collecting the design state data 111 and the running state data 112, the analysis module 122 can generate a relationship record. Based on the change information input by the user and the relationship record, the analysis module 122 can generate at least one impact point.

[0106] In an embodiment of the present application, the relationship record is configured to indicate at least one table, at least one field included in each of the at least one table, and at least one interface related to each of the at least one table, at least one field corresponding to each of the at least one interface. Further, the relationship record is also configured to indicate a dependency relationship between the plurality of interfaces and / or a dependency relationship between the at least one interface and the at least one table.

[0107] Further, the analysis module 122 in an embodiment of the present application can also query information from the knowledge management module 123 and provide optimization suggestions. The knowledge management module 123 includes a knowledge base that stores a plurality of field change types each corresponding to an optimization suggestion and a plurality of table change types each corresponding to an optimization suggestion. For example, the optimization suggestion is an optimization suggestion for the impact point in the case that the target field is changed in the field change type. For another example, the optimization suggestion is an optimization suggestion for the impact point in the case that the target table is changed in the table change type.

[0108] In an embodiment of the present application, for example, the design state data 111 can include data standards, model assets, interface definitions, and other pre-designed or defined data formats, interface specifications. For example, the running state data 112 can include interface call chain analysis and SQL parsing. The running state data 112 can be understood as data generated when the user performs business access each time.

[0109] FIG. 2 is a schematic flowchart of a data processing method 200 provided by the present application. As shown in FIG. 2, for example, the method 200 is applied to a data processing platform, the data processing platform is in communication connection with a business processing platform, the business processing platform includes at least one table and at least one interface, and the method 200 includes the following steps:

[0110] 210, receiving change information input by a user.

[0111] In a possible implementation manner, for example, the change information includes a target field. It can also be understood that the change information is configured to indicate the target field. The at least one table includes the target field.

[0112] In another possible implementation, for example, the change information includes a target field and a table corresponding to the target field, and the at least one table includes the table corresponding to the target field. It can also be understood that the change information is used to indicate the target field and the table corresponding to the target field. In the embodiments of the present application, the "table corresponding to the target field" can be understood as the table in which the target field is located.

[0113] In a possible implementation, for example, the change information can further include a field change type. It can also be understood that the change information can indicate the field change type. At this time, the change information includes the target field and the change type of the target field, or the change information includes the target field, the table corresponding to the target field, and the change type of the target field.

[0114] In another possible implementation, for example, the change information includes a target table and a table change type, and the at least one table includes the target table. It can also be understood that the change information is used to indicate the target table and the table change type.

[0115] It can also be understood that the embodiments of the present application mainly relate to two cases of "field change" and "table change", and the two change cases will be introduced below.

[0116] For example, the "table" in the embodiments of the present application can be understood as a table in a database, and the "field" in the present application can be understood as a field included in the table and / or a field used by an interface.

[0117] The "field change type" in the embodiments of the present application includes one or more of the following: changing a field name, changing a field data type, changing a field length, changing a field format, changing a field enumeration value, and deleting a field.

[0118] For example, the "changing a field data type" can be understood as changing the field type from "string type" to "integer type".

[0119] For example, the "changing a field format" is that the original time format (which can be understood as being controlled by a field) is "2024-05-17 15:28:30", the changed format is "15:28:30 2024-05-17", or the changed time format is 2024 / 05 / 17 15:28:30.

[0120] For example, the "change field enumeration value" can include adding a field enumeration value and deleting a field enumeration value. For example, when selecting an address, a province is selected, and the province can be a field in the system (for example, in a table). The content stored in this field is an enumeration value. For example, the current province field has a total of 31 enumeration values, which are the names of each province. Assuming that a province or municipality is added, there is an additional enumeration value. Assuming that a municipality is merged into a province, an enumeration value is deleted.

[0121] The "table change type" in the embodiments of the present application includes one or more of the following: deleting a table, changing a table name, changing a table index, and changing a table primary key.

[0122] In a possible implementation, the method 200 further includes obtaining data information. For example, the data information can be obtained according to data standards, model assets, interfaces, and a calling chain. For example, the data information can specifically include at least one of the following: a name corresponding to each of at least one table, at least one field included in each table, a type and a length of each field in each table, an address corresponding to at least one interface related to each table, at least one field corresponding to each of the at least one interface, an interface type and a length to which a field corresponding to each interface belongs, and a dependency relationship between the interfaces.

[0123] In addition, the obtained at least one interface, at least one field corresponding to each interface, and the name of each field corresponding to each interface can be matched with the obtained at least one database, a name corresponding to each of the at least one database, a name corresponding to each of at least one table included in each database, at least one field included in each table, and the name of each field in each table, thereby obtaining a dependency relationship between the at least one interface and the at least one table, and a corresponding relationship between the at least one interface and the at least one field. It can also be understood that, in the present application, the "dependency relationship between the at least one interface and the at least one table" can be obtained based on matching the collected data information.

[0124] In a possible implementation, a relationship record can be generated according to the obtained data information. The relationship record is used to indicate at least one table, at least one field included in each of the at least one table, and at least one interface related to the table and at least one field corresponding to each of the at least one interface.

[0125] In the present application, the "related" in the "at least one interface related to the table" can be understood as that at least one field included in a certain table of the at least one table and at least one field corresponding to a certain interface of the at least one interface overlap.

[0126] In the embodiments of the present application, the "correspondence" in "at least one field corresponding to each interface" can be understood as that an input parameter of the interface uses a certain field, or an output parameter of the interface uses a certain field.

[0127] Further, the relationship record can also be used to indicate the dependency relationship between the interfaces and / or the dependency relationship between the at least one interface and the at least one table.

[0128] For example, information of each table in a database (DB) can be collected on a data model service (DMS) platform, and each table includes at least one field. For example, data of the fields in the data model is obtained and parsed on the DMS platform, and the data includes the data type and length of each field in the table. Specifically, the design state data can be obtained through a timing task, and the data model in the system is updated. For example, the DMS platform query interface is called every 4 hours to obtain the updated design state data. It should be understood that the data model to be obtained should be configured in the system in advance, including the table name, timing duration and other data, so as to clearly know which data needs to be obtained.

[0129] As shown in FIG. 3, the database #1 includes one table, and the table name of the table is t_partner. The table includes five fields, which are "BPID", the field length is 500; "PARTNER_NAME", the field length is 32; "RECORD_TYPE", the field length is 500; "BEID", the field length is 32; and "PARTNERSHIP_STATUS", the field length is 500. As can be seen from FIG. 3, the field type corresponding to each field is "varchar". Based on FIG. 3, the following table 1 can be obtained.

[0130] Table 1

[0131] For example, the interface definition can be obtained in an application programming interface designer (API designer) platform, and the interface definition yaml file is parsed to obtain the output parameter (i.e., field) and input parameter (i.e., field) of the interface, and the type and length of the field. By comparing and matching each field with the field in the data model obtained from the DMS, it can be determined which tables the interface has a relationship with, and thus the dependency relationship between the interface and the table can be determined. As shown in FIG. 4, the parameters used by the interface (i.e., which fields are used by the interface) are obtained by parsing the interface definition.

[0132] For example, the system obtains the call chain information of the interface configured by the business side by calling the application performance management (APM) query call chain information through a timing task. For example, by specifying the call chain starting point interface, the call chain data of the interface is parsed to obtain the downstream interfaces dependent on the interface, i.e., which interfaces are called by the interface, and which interfaces are called by the downstream interfaces, and the input and output parameter fields of the interfaces are found through the uniform resource locator (URL) of each interface, as shown in FIG. 5. Based on FIGS. 3 and 4, the information of the interface can be obtained, as shown in Table 2 below.

[0133] Table 2

[0134] For example, based on the obtained data information (for example, Table 1 and Table 2), the relationship record in the present application can be obtained, as shown in Table 3 below. It should be understood that the column of “dependency relationship” in Table 3 is optional.

[0135] Table 3

[0136] The “field change” and “table change” in the embodiments of the present application will be introduced below in combination with Table 3.

[0137] Case 1: Field change

[0138] In a possible implementation, the method 200 further includes: the target field in the change information can be found in the relationship record to determine at least one impact point. The impact point includes a table and / or an interface. For example, each of the at least one impact point indicates the table and / or the interface affected in the case where the target field is changed. The table and / or the interface affected in the case where the target field is changed corresponds to at least one field which is the same as the target field.

[0139] Further, when the dependency between the interfaces and / or the dependency between the at least one interface and the at least one table is included in the relationship record (for example, the column of "Dependency" in Table 3), the multiple impact points (i.e., in the case of multiple impact points) can be generated based on the dependency to form the at least one impact chain. Some of the multiple impact chains include multiple impact points, and some of the multiple impact chains can include only one impact point; or each of the at least one impact chain can include only one impact point; or each of the at least one impact chain can include multiple impact points. The at least one impact chain is generated based on the dependency between the multiple interfaces and / or the dependency between the at least one interface and the at least one table, and the at least one impact chain includes the relationship between the multiple impact points. It can also be understood that the at least one impact chain is used to indicate the relationship between the multiple impact points. For example, the at least one impact chain can be used to indicate that some impact points have a dependent relationship, and / or some impact points do not have a dependent relationship.

[0140] As an example, assume that the change information input by the user includes: the target field "BEID", and the length of the field "BEID" is expanded. As can be seen from Table 3, the table t_partner in identification #1 includes the field "BEID", and in addition, the table t_order in identification #3 also includes the field "BEID", so the field "BEID" is directly related to identification #1 and identification #3.

[0141] Further, as can be seen from Table 3, the interface in identification #2 depends on the table t_partner in identification #1 (for example, this can be because the interface in identification #2 includes the field BEID in the output parameter, and BEID is attributed to identification #1 in business, so identification #2 depends on identification #1), and it can be found that the interface in identification #2 includes the field "BEID" in the output parameter; the interface in identification #5 includes the field "BEID" in the output parameter, and identification #5 depends on identification #2. In addition, although the interface in identification #4 depends on the table t_order in identification #3, the field "BEID" is not included in the input parameter and the output parameter of the interface in identification #4, which indicates that the interface corresponding to identification #4 is not an impact point.

[0142] Based on the above analysis, it can be seen that there are four impact points, respectively: identification #1, identification #2, identification #3, and identification #5. Further, if referring to the "dependency relationship" in Table 3, the above four impact points can be divided into two impact chains: the first impact chain is: identification #5→identification #2→identification #1, from which it can be seen that identification #5 depends on identification #2, and identification #2 depends on identification #1; the second impact chain is: identification #3.

[0143] Case two: table change

[0144] Method 1: delete table

[0145] In the case of the table change type being delete table, for example, the target table in the change information can be found in the relationship record to determine at least one impact point. The impact point includes a table and / or an interface. For example, each of the at least one impact point includes a table and / or an interface that is affected in the case of the table change type change, wherein the affected table and / or interface corresponds to at least one field that is the same as at least one field included in the target table that needs to be changed. In this change method, for example, the SQL statement corresponding to the affected table and / or interface can need to be adjusted.

[0146] As an example, assume that the change information input by the user includes: the target table is t_partner, and the target table t_partner is deleted. From Table 3 above, it can be seen that the target table t_partner includes the following fields: BPINFOID, BPID, CORPNAME, BPSTATUS, BECODE, and BEID. When t_partner is deleted, these fields will be deleted, so other tables that include at least one of these fields can be affected, and each interface that includes at least one of these fields can also be affected. Therefore, identification #2, identification #3, and identification #5 will be affected. That is, there are three impact points, respectively: identification #2, identification #3, and identification #5. Further, if referring to the "dependency relationship" in Table 3, the above three impact points can be divided into two impact chains: the first impact chain is: identification #5→identification #2, from which it can be seen that identification #5 depends on identification #2; the second impact chain is: identification #3.

[0147] Method 2: change table index

[0148] In the case of the table change type being change table index, the table change type can indicate the index in the target table that needs to be changed. For example, the target table and the index in the target table that needs to be changed in the change information can be found in the relationship record to determine at least one impact point. The impact point includes a table and / or an interface. For example, each of the at least one impact point indicates the table and / or the interface that is affected in the case of the target table being changed in the table change type, and the at least one field corresponding to the affected table and / or the interface includes the index in the target table that needs to be changed. In this change mode, for example, the SQL statement corresponding to the affected table and / or the interface can need to be adjusted.

[0149] As an example, it is assumed that the change information input by the user includes: the target table is t_partner, and the index BPID is deleted. It can be seen from Table 3 that there are two impact points, which are: identification #2 and identification #5. Further, if the two impact points are represented as an impact chain: identification #5→identification #2, by referring to the “dependency relationship” in Table 3.

[0150] Mode 3: Change table primary key

[0151] In the case of the table change type being change table primary key, the table change type can indicate the primary key in the target table that needs to be changed. For example, the target table and the primary key in the target table that needs to be changed in the change information can be found in the relationship record to determine at least one impact point. The impact point includes a table and / or an interface. For example, each of the at least one impact point indicates the table and / or the interface that is affected in the case of the target table being changed in the table change type, and the at least one field corresponding to the affected table and / or the interface includes the primary key in the target table that needs to be changed. In this change mode, for example, the SQL statement corresponding to the affected table and / or the interface can need to be adjusted.

[0152] As an example, it is assumed that the change information input by the user includes: the target table is t_partner, and the primary key BPINFOID is changed. It can be seen from Table 3 that there is one impact point: identification #2.

[0153] Mode 4: Change table name

[0154] In the case of the table change type being change table name, each impact point is an interface, and the affected interface has a direct dependency relationship with the target table. For example, the interface directly dependent on the target table can be found in the relationship record to determine the affected table and / or the interface. In this change mode, for example, the SQL statement corresponding to the affected table and / or the interface can need to be adjusted.

[0155] In the present application, "directly dependent" can be understood as the affected interface directly depends on the target table that needs to be changed. For example, in the impact chain 5→2→1 shown in the above example, the identifier #2 directly depends on the identifier #1, the identifier #5 directly depends on the identifier #2, and the identifier #5 indirectly depends on the identifier #1.

[0156] As an example, it is assumed that the change information input by the user includes: the target table is t_partner, and the table name is changed. It can be seen from the above table 3 that there is one impact point: identifier #2.

[0157] Further, in the embodiments of the present application, the knowledge management module includes a knowledge base management page. For example, the user can input, through the page, the optimization suggestion of the field change of each impact point corresponding to each field change type in the knowledge base in advance, wherein the optimization suggestion of the field change is used to indicate the optimization suggestion for at least one impact point in the case that the target field in the target table is changed in the field change type. For another example, the user can input, through the page, the optimization suggestion of the table change of each impact point corresponding to each table change type in the knowledge base in advance, and the optimization suggestion of the table change is used to indicate the optimization suggestion for at least one impact point in the case that the target table is changed in the table change type.

[0158] In the embodiments of the present application, for the "field change" in the first case, if the change information input by the user at the beginning includes the target field in the target table, after at least one impact point is obtained, if the user still wants to obtain the optimization suggestion of each impact point, at this time, the user can also input the "field change type" (equivalent to the change information including the target field and the field change type, or the change information including the target field, the table corresponding to the target field, and the field change type) to obtain the optimization suggestion of the field change of each impact point. It can also be understood that, in the embodiments of the present application, for the field change, the user can first input the target field, or the user can first input the target field and the target table, and then input the field change type.

[0159] Specifically, the "optimization suggestion of the field change" can be understood as the change operation performed by at least one impact point in the case that the target field is changed in the field change type.

[0160] For example, the knowledge base stores a plurality of field change types each corresponding to an optimization suggestion. Exemplarily, in the case of the field change type being changing the length of a field, the optimization suggestion is to change the length of the field to be changed in each of the impact points; in the case of the field change type being deleting a field, the optimization suggestion is to delete the field to be changed in each of the impact points; in the case of the field change type being changing the data type of a field, the optimization suggestion is to change the data type of the field to be changed in each of the impact points.

[0161] Specifically, the "optimization suggestion for table change" can be understood as a change operation performed by at least one impact point in the case of the target table being changed in the table change type.

[0162] For example, the knowledge base stores a plurality of table change types each corresponding to an optimization suggestion. Exemplarily, in the case of the table change type being deleting a table, the optimization suggestion is that the SQL related to the target table in each of the impact points can need to be adjusted; in the case of the table change type being changing the index of a table, the optimization suggestion is that the SQL related to the changed index of the target table in each of the impact points can need to be adjusted; in the case of the table change type being changing the primary key of a table, the optimization suggestion is that the SQL related to the changed primary key of the target table in each of the impact points can need to be adjusted. In the case of the table change type being changing the name of a table, the optimization suggestion is that the SQL related to the changed name of the target table in each of the impact points can need to be adjusted.

[0163] FIG. 6 is another flowchart of the data processing method according to the present application. As shown in FIG. 6, data can be collected from the DMS platform, the API Designer and the APM platform, and then a relationship record can be generated based on the collected data. Then, based on the relationship record and the change information input by the user, an impact point can be generated. Further, the knowledge management module can be queried based on the generated impact point, and an optimization suggestion can be provided.

[0164] 220, display the analysis result to the user, the analysis result including at least one impact point.

[0165] In the embodiment of the present application, in the case of field change, each of the at least one impact point includes a table and / or an interface affected in the case of the target field being changed. The table and / or the interface affected in the case of the target field being changed correspond to at least one field which is the same as the target field.

[0166] In the embodiment of the present application, in the case of table change, each of the at least one impact point includes a table and / or an interface affected in the case of the target table being changed.

[0167] For example, in the case that the table change type is a delete table, the at least one field corresponding to the affected table and / or interface in the case that the target table is changed is the same as at least one field included in the target table.

[0168] For example, in the case that the table change type is a change table index, the at least one field corresponding to the affected table and / or interface in the case that the target table is changed includes a table index that needs to be changed in the target table, wherein the table change type is used to indicate the table index that needs to be changed in the target table.

[0169] For example, in the case that the table change type is a change table primary key, the at least one field corresponding to the affected table and / or interface in the case that the target table is changed includes a table primary key that needs to be changed in the target table, wherein the table change type is used to indicate the table primary key that needs to be changed in the target table.

[0170] For example, in the case that the table change type is a change table primary key, the at least one field corresponding to the affected table and / or interface in the case that the target table is changed includes a table primary key that needs to be changed in the target table, wherein the table change type is used to indicate the table primary key that needs to be changed in the target table.

[0171] In a possible implementation, the analysis result further includes at least one influence chain. In the case that there are multiple influence points, some of the multiple influence chains include multiple influence points, and the other influence chains can only include one influence point; or each of the at least one influence chain only includes one influence point; or each of the at least one influence chain includes multiple influence points. The at least one influence chain is generated according to the dependency relationship between the multiple interfaces and / or the dependency relationship between the at least one interface and the at least one table, and the at least one influence chain is used to indicate the relationship between the multiple influence points.

[0172] In a possible implementation, in the case that the change information includes a field change type, the analysis result further includes an optimization suggestion of the field change, and the optimization suggestion of the field change is used to indicate a change operation performed for the at least one influence point in the case that a target field in the target table is changed in the field change type; or, in the case that the change information includes a target table and a table change type, the analysis result further includes an optimization suggestion of the table change, and the optimization suggestion of the table change is used to indicate a change operation performed for the at least one influence point in the case that the target table is changed in the table change type.

[0173] As mentioned above, since the knowledge base stores the optimization suggestions corresponding to different change types respectively, based on the obtained at least one impact point, the change information input by the user, the knowledge base, the optimization suggestion of each impact point can be obtained. For example, based on the obtained at least one impact point, the field change type, the knowledge base, the optimization suggestion of the field change of each impact point can be obtained. For example, based on the obtained at least one impact point, the table change type, the knowledge base, the optimization suggestion of the table change of each impact point can be obtained.

[0174] In the embodiments of the present application, when providing the optimization suggestion, the artificial intelligence (AI) mode can be adopted (for example, the AI suggestion analysis module can be included), for example, the AI can provide the optimization suggestion more accurately and flexibly based on the change type, the at least one impact point and the knowledge base. For example, it is assumed that the change information is to expand the length of the field "BEID" from 32 bits to 64 bits. It is assumed that the original field "BEID" in the interface of the impact point #5 is 128 bits, so the field "BEID" of the impact point does not need to be expanded any more, and the original field length can be maintained.

[0175] The technical scheme of the field change type of the present application will be introduced below taking the "order placement process" as an example. After the customer places an order, the order service needs to query the BEID field of the partner database; then, it is stored in the service database, and at the same time, the field needs to be pushed to the billing service, the cost is generated through billing, and the field is saved; in addition, the fee deduction service needs to pull the cost for fee deduction, and the BEID field is saved in the deduction record. Further, the billing service can also be notified to bill according to the BEID, and the billing service saves the field. The data transmission between services is carried out through API. As shown in FIG. 7. It is assumed that the "BEID field" of the "t_partner table" in the "partner database" needs to be changed, and the length of the "BEID field" is expanded from 32 bits to 64 bits. By inputting the table name "t_partner", the field name "BEID", the change type "field length expansion", the impact chain queried is: 1→2→3→4→5→6. For example, the query page can be as shown in FIG. 8. Further, the optimization suggestion of the field change of each impact point can also be queried, as shown in FIG. 9. For example, the analysis result of DB5 is that the field length of the table in the database is 32, and the new length cannot be stored, and the optimization suggestion of the field change is that the length of the BEID field in DB5 needs to be expanded, as shown in (a) of FIG. 9; for another example, the analysis result of interface 4 is that the field length of the original interface is 32, and the new length cannot be stored, and the optimization suggestion of the field change is that the length of the BEID field in interface 4 needs to be expanded, as shown in (b) of FIG. 9.

[0176] Based on the technical scheme, the relationship record and the change information input by the user are constructed, and each affected point can be automatically queried, so that the method is more efficient and convenient. In addition, the interface is also included in the affected point, so that the influence of the change information on the interface can be identified, and the troubleshooting result is more complete and accurate.

[0177] FIG. 10 is a schematic diagram of a cloud service scenario used in the present application. As shown in FIG. 10, the cloud scenario can include a cloud management platform 1010, an Internet 1020, and a client 1030. As shown in FIG. 10, the cloud management platform 1010 is used to manage the infrastructure that provides a plurality of cloud services. The infrastructure includes a plurality of cloud data centers, each of which includes a plurality of servers, and each of the servers includes a cloud service resource, which provides a corresponding cloud service for a tenant. In an embodiment of the present application, the cloud service resource can be a cloud database.

[0178] The cloud management platform 1010 can be located in a cloud data center, which can provide an access interface (such as an interface or an application program interface (API)). The tenant can remotely access the access interface to register a cloud account and a password on the cloud management platform 1010 by operating the client 1030, and log in to the cloud management platform 1010. After the cloud management platform 1010 authenticates the cloud account and the password successfully, the tenant can further select and purchase a virtual machine of a specific specification (processor, memory, disk) on the cloud management platform 1010 by paying a fee. After the payment and purchase are successful, the cloud management platform 1010 provides a remote login account and password of the purchased virtual machine, and the client 1030 can remotely log in to the virtual machine, and install and run the application of the tenant in the virtual machine. Therefore, the tenant can create, manage, log in to, and operate the virtual machine in the cloud data center through the cloud management platform 1010.

[0179] The functions of the cloud management platform 1010 include but are not limited to a tenant console, a computing management service, a network management service, a storage management service, an authentication service, and an image management service. The tenant console provides an interface or an API to interact with the tenant, the computing management service is used to manage servers running virtual machines and containers and bare metal servers, the network management service is used to manage network services (such as gateways, firewalls, etc.), the storage management service is used to manage storage services (such as data bucket services), the authentication service is used to manage the account and password of the tenant, and the image management service is used to manage virtual machine images. The tenant uses the client 1030 to log in to the cloud management platform 1010 through the Internet 1020 to manage the rented cloud services.

[0180] In the present application, for example, each step of the method 200 described above can be performed by the infrastructure in the cloud service system. For example, the technical scheme of the present application can be published in the form of a cloud service.

[0181] It can be understood that the term "and / or" in this document merely describes an associated relationship for associated objects, and indicates that there can be three relationships, for example, A and / or B can indicate that A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this document generally indicates that the front and rear associated objects are in an "or" relationship.

[0182] Those skilled in the art can understand that the units and algorithm steps of each example described in combination with the embodiments disclosed in this document can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is realized in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0183] The embodiments of the present application can divide the functional modules of the computing device according to the above-mentioned method examples, for example, each functional module can be divided according to each function, or two or more functions can be integrated in one processing module. The above-mentioned integrated module can be realized in the form of hardware or software functional module. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical functional division. When actually implemented, there can be another division method. The following will be described taking the example of dividing each functional module according to each function.

[0184] FIG. 11 is a schematic block diagram of a computing device 1100 provided by an embodiment of the present application. As shown in the figure, the computing device 1100 can include an input module 1110, a display module 1120. Optionally, it further includes an acquisition module 1130 and a generation module 1140.

[0185] Each of the above-mentioned modules is respectively used to execute each step of the above-mentioned method, which will not be described here.

[0186] It should also be understood that the computing device 1100 herein is embodied in the form of functional units. The term "unit" herein can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combination logic circuit and / or other suitable components supporting the described functions.

[0187] The computing device 1100 of each of the above solutions has a function of implementing the corresponding steps of the above method 200. The function can be implemented by hardware, or implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, an input module, a display module, etc. can be replaced by a processor to perform the receiving operation and the related processing operation in each method embodiment. In addition, the input module or the display module can also be a processing circuit.

[0188] It should be noted that the computing device in FIG. 11 can be a computing device (for example, a server for providing cloud services) in the foregoing method embodiments, or a chip or chip system corresponding to the computing device, for example: a system on chip (SoC). The processing module is a processor or microprocessor or integrated circuit integrated on the chip. Herein, no limitation is made.

[0189] FIG. 12 is a schematic block diagram of another computing device 1200 provided by an embodiment of the present application. As shown in the figure, the device 1200 includes at least one processor 1220. The processor 1220 is coupled with a memory, and is configured to execute instructions stored in the memory to send and / or receive signals. Optionally, the device 1200 further includes a memory 1230 for storing instructions. Optionally, the device 1200 further includes a transceiver 1210, and the processor 1220 controls the transceiver 1210 to send and / or receive signals.

[0190] It should be understood that the processor 1220 and the memory 1230 described above can be combined into one processing device, and the processor 1220 is configured to execute program codes stored in the memory 1230 to implement the above functions. In specific implementation, the memory 1230 can be integrated in the processor 1220, or independent of the processor 1220.

[0191] It should also be understood that the transceiver 1210 can include a transceiver (or receiver) and a transmitter (or transmitter). The transceiver can further include an antenna, and the number of antennas can be one or more. The transceiver 1210 can be a communication interface or interface circuit.

[0192] The bus 1240 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, or the like. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one line is shown in FIG. 12, but it does not mean that there is only one bus or only one type of bus. The bus 1240 can include a path for transmitting information between various components (for example, the memory 1230, the processor 1220, the transceiver 1210) of the computing device 1200.

[0193] The memory 1230 stores executable program code, and the processor 1220 executes the executable program code to respectively implement the functions of the aforementioned input module and display module, thereby implementing the data processing method in the embodiments of the present application. That is, the memory 1230 stores instructions for executing the data processing method. For example, the processor 1220 is configured to execute the computer program or instructions stored in the memory 1230 to implement the steps in the method 200 described above.

[0194] FIG. 13 is a schematic diagram of an architecture of a computing device cluster according to an embodiment of the present application. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a desktop computer, a notebook computer, or a terminal device such as a smart phone. As shown in FIG. 13, the computing device cluster includes at least one computing device 1300. The memory 1330 in one or more computing devices 1300 in the computing device cluster can store the same instructions for performing the actions performed in the method 200 described above.

[0195] In some possible implementations, the memory 1330 of one or more computing devices 1300 in the computing device cluster can also respectively store partial instructions for performing the actions performed in the method 200 described above. In other words, the combination of one or more computing devices 1300 can collectively execute the instructions for performing the actions performed in the method 200 described above.

[0196] It should be noted that the memories 1330 in different computing devices 1300 in the computing device cluster can store different instructions, respectively, for performing part of the functions of the computing device 1300. That is, the instructions stored in the memories 1330 in different computing devices 1300 can implement the functions of one or more of the aforementioned input module and display module.

[0197] Alternatively, the memories 1330 in different computing devices 1300 in the computing device cluster can store different instructions for performing the functions of the computing devices corresponding to the communication devices 1100-1200 described above, respectively. That is, the memories 1330 in different computing devices 1300 store instructions that can implement the functions of one or more of the input modules, display modules, etc.

[0198] In some possible implementations, one or more computing devices in the computing device cluster can be connected through a network. The network can be a wide area network, a local area network, or the like. FIG. 14 shows one possible implementation. As shown in FIG. 14, two computing devices 1300A and 1300B are connected through a network. Specifically, the communication interfaces in the respective computing devices are connected to the network.

[0199] It should be understood that the functions of the computing device 1300A shown in FIG. 14 can also be performed by multiple computing devices 1300. Similarly, the functions of the computing device 1300B can also be performed by multiple computing devices 1300.

[0200] The manner in which the computing device cluster shown in FIG. 14 is connected can be such that, given that the data processing method provided in the present application requires a large amount of data to be collected and analyzed, the functions implemented by the obtaining module and the generating module are performed by the computing device 1300A.

[0201] In the present embodiment, a computer program product containing instructions is also provided. The computer program product can be a software or program product containing instructions that can be run on the computing device cluster or stored in any available medium. When run by the computing device cluster, the computer program product causes the computing device cluster to perform the method provided above, or causes the computing device cluster to implement the functions of the apparatus provided above.

[0202] In the present embodiment, a computer readable storage medium is also provided. The computer readable storage medium can be any available medium that can be stored by the computing device or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk), etc. The computer readable storage medium contains instructions that, when executed on the computing device, cause the computing device to perform the method provided above.

[0203] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0204] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0205] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0206] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0207] In addition, each functional unit in each embodiment of the present application can be integrated into a processing module, or each unit can exist physically, or two or more units can be integrated into one unit.

[0208] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that contribute to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0209] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A data processing method, characterized by, The method is applied to a data processing platform, the data processing platform is in communication connection with a business processing platform, the business processing platform comprises at least one table and at least one interface, and the method comprises: receiving user inputted change information, the change information comprising a target field to be changed, the target field being a field in the at least one table; displaying an analysis result to the user, the analysis result being generated according to the change information and a relationship record, the relationship record being used to indicate the at least one table, at least one field included in each table of the at least one table, and at least one field corresponding to each interface of the at least one interface related to the each table, wherein the analysis result comprises at least one impact point, each impact point of the at least one impact point comprising a table and / or an interface affected in the case that the target field is changed, wherein at least one field corresponding to the affected table and / or the affected interface in the case that the target field is changed is the same as the target field.

2. The method of claim 1, wherein, The relationship record is also used to indicate a dependency relationship between a plurality of interfaces and / or a dependency relationship between the at least one interface and the at least one table, and the analysis result further comprises at least one impact chain, the at least one impact chain comprising a relationship between a plurality of impact points.

3. The method according to any one of claims 1 or 2, characterized in that, The change information further comprises a target table to be changed and a table change type, each impact point further comprises a table and / or an interface affected in the case that the target table is changed, and the at least one table comprises the target table, wherein, in the case that the table change type is deleting a table, at least one field corresponding to the affected table and / or the affected interface in the case that the target table is changed is the same as at least one field included in the target table; in the case that the table change type is changing a table index, at least one field corresponding to the affected table and / or the affected interface in the case that the target table is changed comprises a table index to be changed in the target table, wherein the table change type is used to indicate the table index to be changed in the target table; in the case that the table change type is changing a table primary key, at least one field corresponding to the affected table and / or the affected interface in the case that the target table is changed comprises a table primary key to be changed in the target table, wherein the table change type is used to indicate the table primary key to be changed in the target table; in the case that the table change type is changing a table name, the affected interface in the case that the target table is changed has a direct dependency relationship with the target table.

4. The method according to claim 1 or 2, characterized in that, The change information further comprises a field change type of the target field to be changed, and the analysis result further comprises an optimization suggestion of field change, the optimization suggestion of field change being used to indicate an optimization suggestion for the at least one impact point in the case that the target field is changed in the field change type.

5. The method of claim 4, wherein, The field change type includes at least one of changing a field name, changing a field data type, changing a field length, changing a field format, changing a field enumeration value, and deleting a field.

6. The method of claim 3, wherein, In a case where the change information includes the target table to be changed and a table change type, the analysis result further includes an optimization suggestion for table change, which is used to indicate an optimization suggestion for the at least one influence point in a case where the target table is changed in the table change type.

7. The method according to claim 5 or 6, characterized in that, The optimization suggestion for the field change is generated according to the field change type, the at least one influence point, and a knowledge base, or the optimization suggestion for the table change is generated according to the table change type, the at least one influence point, and the knowledge base, wherein the knowledge base stores a plurality of optimization suggestions corresponding to the respective field change types and a plurality of optimization suggestions corresponding to the respective table change types.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: obtaining data information, the data information including at least two of the following: a respective name of each of the at least one table, at least one field included in each of the tables, a type and a length of each field in each of the tables, a respective address of at least one interface related to the tables, at least one field corresponding to each of the at least one interface, a type and a length of the field corresponding to each of the interfaces, an interface type to which the field corresponding to each of the interfaces belongs, a dependency relationship between the interfaces, and a dependency relationship between the at least one interface and the at least one table; generating the relationship record according to the data information.

9. A data processing apparatus, characterized by, The data processing device is applied to a data processing platform, the data processing platform is in communication connection with a business processing platform, the business processing platform includes at least one table and at least one interface, and the data processing device includes an input module and a display module. The input module is configured to receive change information input by a user, the change information including a target field to be changed, the target field being a field in the at least one table. The display module is configured to display an analysis result to the user, the analysis result being generated according to the change information and a relationship record, the relationship record being used to indicate the at least one table, at least one field included in each of the at least one table, and at least one interface related to each of the tables, and at least one field corresponding to each of the at least one interface, wherein the analysis result includes at least one influence point, each of the at least one influence point including a table and / or an interface affected in a case where the target field is changed, and at least one field corresponding to the table and / or the interface affected in the case where the target field is changed being the same as the target field.

10. The data processing apparatus according to claim 9, characterized by The relationship record is further used to indicate a dependency relationship between the interfaces and / or a dependency relationship between the at least one interface and the at least one table, and the analysis result further includes at least one influence chain, the at least one influence chain including a relationship between a plurality of influence points.

11. The data processing apparatus according to claim 9 or 10, characterized by The change information further comprises a target table to be changed and a table change type, each of the influence points further comprises a table and / or an interface affected in the case that the target table is changed, and the at least one table comprises the target table, wherein In the case that the table change type is deleting a table, at least one field corresponding to the affected table and / or interface in the case that the target table is changed is the same as at least one field included in the target table; In the case that the table change type is changing a table index, at least one field corresponding to the affected table and / or interface in the case that the target table is changed comprises a table index to be changed in the target table, wherein the table change type is used to indicate the table index to be changed in the target table; In the case that the table change type is changing a table primary key, at least one field corresponding to the affected table and / or interface in the case that the target table is changed comprises a table primary key to be changed in the target table, wherein the table change type is used to indicate the table primary key to be changed in the target table; In the case that the table change type is changing a table name, the affected interface in the case that the target table is changed is directly dependent on the target table.

12. The data processing apparatus according to claim 9 or 10, wherein The change information further comprises a field change type of the target field to be changed, and the analysis result further comprises an optimization suggestion of field change, which is used to indicate an optimization suggestion for the at least one influence point in the case that the target field is changed in the field change type.

13. The data processing apparatus according to claim 12, characterized in that, The field change type comprises at least one of changing a field name, changing a field data type, changing a field length, changing a field format, changing a field enumeration value, and deleting a field.

14. The data processing apparatus according to claim 11, wherein, In the case that the change information comprises the target table to be changed and the table change type, the analysis result further comprises an optimization suggestion of table change, which is used to indicate an optimization suggestion for the at least one influence point in the case that the target table is changed in the table change type.

15. The data processing apparatus according to claim 13 or 14, characterized by The optimization suggestion of field change is generated according to the field change type, the at least one influence point, and a knowledge base, or the optimization suggestion of table change is generated according to the table change type, the at least one influence point, and the knowledge base, wherein the knowledge base stores a plurality of optimization suggestions corresponding to the field change type respectively and a plurality of optimization suggestions corresponding to the table change type respectively.

16. The data processing apparatus according to any one of claims 9 to 15, characterized in that, The data processing apparatus further comprises an obtaining module and a generating module, The acquisition module is configured to acquire data information, the data information including at least two of the following: a respective name of each table in the at least one table, at least one field included in each table, a type and a length of each field in each table, a respective address of each of at least one interface related to the table, at least one field corresponding to each of the at least one interface, a type and a length of the field corresponding to each of the at least one interface, an interface type to which the field corresponding to each of the at least one interface belongs, a dependency relationship between the interfaces, and a dependency relationship between the at least one interface and the at least one table. The generation module is configured to generate the relationship record according to the data information.

17. A cluster of computing devices, characterized in that, at least one computing device, each computing device including a processor and a memory; the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device to cause the cluster of computing devices to perform the method of any one of claims 1-8.

18. A computer program product comprising instructions, characterized in that, the instructions, when executed by the cluster of computing devices, cause the cluster of computing devices to perform the method of any one of claims 1-8.

19. A computer-readable storage medium, characterized in that, computer program instructions, the cluster of computing devices, when executing the computer program instructions, performing the method of any one of claims 1-8.

Images