Data processing method, device, electronic device and computer-readable storage medium

Abstract

The present disclosure provides a data processing method, apparatus, electronic device, and computer-readable storage medium, relating to the field of data processing, and more particularly, to the field of data retrieval. A specific implementation scheme comprises: receiving a retrieval request, wherein the retrieval request carries a retrieval starting condition and a retrieval scenario tag; determining, based on the retrieval starting condition and the retrieval scenario tag, a retrieval link from the starting data corresponding to the retrieval starting condition to the target data corresponding to the retrieval scenario tag; and performing a search based on the retrieval link to obtain a retrieval result. Through the above-described processing, the technical effects of reducing retrieval costs and improving retrieval efficiency can be achieved.

Description

Technical Field

[0001] The present disclosure relates to the field of data processing technology, in particular to the field of data retrieval, and specifically to a data processing method, device, electronic device, and computer-readable storage medium. Background Art

[0002] In related technologies, data retrieval is usually performed using either data user development or data middle platform development. However, when using the data user development method, data users need to understand the meaning of the data tables and the relationship between them before developing and calculating, which is very costly and difficult to modify the code when the data changes. The data middle platform is a sedimentation of the business and data of existing or newly built information systems. It is an intermediate and supporting platform for realizing data empowerment of new businesses and new applications, and is used to provide data services for the business. However, the data middle platform development method is only suitable for clear business scenarios. The data middle platform is developed according to business needs and cannot fully understand the meaning of the data. It is not suitable for data retrieval in a large number of business scenarios. Summary of the Invention

[0003] The present disclosure provides a method, apparatus, device, and storage medium for data processing.

[0004] According to one aspect of the present disclosure, a data processing method is provided, comprising: receiving a retrieval request, wherein the retrieval request carries a retrieval starting condition and a retrieval scenario tag; determining a retrieval link from starting data corresponding to the retrieval starting condition to target data corresponding to the retrieval scenario tag based on the retrieval starting condition and the retrieval scenario tag; performing a retrieval based on the retrieval link to obtain a retrieval result.

[0005] Optionally, based on the retrieval starting conditions and the retrieval scenario label, a retrieval link is determined from the starting data corresponding to the retrieval starting conditions to the target data corresponding to the retrieval scenario, including: obtaining a standard data relationship between the associated starting data and the target data, wherein the standard data relationship is a relationship between predetermined fields and predetermined fields; based on the standard data relationship, determining a retrieval link between the starting data and the target data.

[0006] Optionally, based on the retrieval starting conditions and the retrieval scenario label, the retrieval link from the starting data corresponding to the retrieval starting conditions to the target data corresponding to the retrieval scenario label is determined, including: obtaining the standard data relationship and extended data relationship of the associated starting data and target data, wherein the standard data relationship is the relationship between predetermined fields and predetermined fields, and the extended data relationship is the relationship between predetermined fields and business customized fields; based on the standard data relationship and the extended data relationship, the retrieval link between the starting data and the target data is determined.

[0007] Optionally, performing a search based on the search link to obtain a search result includes: assembling a search statement based on the search link; and performing a search using the search statement to obtain a search result.

[0008] According to another aspect of the present disclosure, a data processing device is provided, including: a first receiving module for receiving a retrieval request, wherein the retrieval request carries a retrieval starting condition and a retrieval scenario label; a first determining module for determining, based on the retrieval starting condition and the retrieval scenario label, a retrieval link from the starting data corresponding to the retrieval starting condition to the target data corresponding to the retrieval scenario label; and a first retrieval module for performing a search based on the retrieval link to obtain a retrieval result.

[0009] Optionally, the first determination module includes: a first acquisition unit, used to obtain a standard data relationship associating the starting data and the target data, wherein the standard data relationship is a relationship between predetermined fields and predetermined fields; a first determination unit, used to determine a retrieval link between the starting data and the target data based on the standard data relationship.

[0010] Optionally, the first determination module includes: a second acquisition unit, used to obtain the standard data relationship and extended data relationship of the associated starting data and target data, wherein the standard data relationship is the relationship between predetermined fields and predetermined fields, and the extended data relationship is the relationship between predetermined fields and business customized fields; the second determination unit, used to determine the retrieval link between the starting data and the target data based on the standard data relationship and the extended data relationship.

[0011] Optionally, the first retrieval module includes: an assembling unit, configured to assemble a retrieval statement based on a retrieval link; and a retrieval unit, configured to perform retrieval using the retrieval statement to obtain a retrieval result.

[0012] According to another aspect of the present disclosure, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the above methods.

[0013] According to yet another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable a computer to execute any one of the above methods.

[0014] According to yet another aspect of the present disclosure, a computer program product is provided, including a computer program, which implements any of the above methods when executed by a processor.

[0015] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings are provided to facilitate a better understanding of the present invention and do not constitute a limitation of the present disclosure.

[0017] Figure 1 is a flow chart of a data processing method provided according to an embodiment of the present disclosure;

[0018] Figure 2 is a schematic diagram of a data processing method provided according to an optional embodiment of the present disclosure;

[0019] Figure 3 is a flow chart of the data processing method according to an optional embodiment of the present disclosure;

[0020] Figure 4 is a structural block diagram of a data processing device provided according to an embodiment of the present disclosure;

[0021] Figure 5 The present invention is a block diagram of an electronic device for implementing the data processing method according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0022] The following description of exemplary embodiments of the present disclosure is made in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding. These details should be considered as merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0023] Terminology

[0024] Data relationship: different fields in different business tables have the same business meaning, so the two tables can be connected based on this field. The data in the tables involved in the association link formed in this way have a data relationship. This association link is the link mentioned in the embodiment of the present disclosure.

[0025] Search ID (SID for short): When the data standard relationship clearly exists and various IDs can be associated through a minimum dimension ID, all IDs in these relationships can be used as SIDs.

[0026] A software development kit (SDK) refers to a collection of development tools used by software engineers to build application software for specific software packages, software frameworks, hardware platforms, operating systems, etc.

[0027] JavaScript Object Notation (JSON) is a lightweight data exchange format that is easy for humans to read and write, and easy for machines to parse and generate, and effectively improves network transmission efficiency.

[0028] Structured Query Language (SQL) is a special-purpose programming language, a database query and programming language used to access data and query, update, and manage relational database systems.

[0029] Join, used in SQL to combine rows from two or more tables.

[0030] In an embodiment of the present disclosure, a data processing method is provided. Figure 1 is a flow chart of a data processing method according to an embodiment of the present disclosure, such as Figure 1 As shown, the flowchart includes the following steps:

[0031] Step S102: receiving a search request, wherein the search request carries a search starting condition and a search scenario tag;

[0032] Step S104, based on the retrieval starting condition and the retrieval scenario tag, determining a retrieval link from the starting data corresponding to the retrieval starting condition to the target data corresponding to the retrieval scenario tag;

[0033] Step S106: perform a search based on the search link to obtain a search result.

[0034] Through the above processing, the search starting data can be filtered out based on the search starting conditions, and the search target data can be determined based on the search scenario tags. Based on the search starting conditions and the search scenario tags, it can be ensured that the corresponding search link can be quickly and accurately determined even in a large number of business scenarios, and then the search can be performed according to the search link to obtain the search results. Because the search process is based on the data relationship, and the data relationship is a configured link determined based on the link starting field and the end field, the link contains the connection fields of the first table to be searched and subsequent tables. That is, the search path between different fields can be determined based on the configured link, so the search can be directly carried out along the link until the required field and the link end field are retrieved. In other words, the data user does not need to clearly understand the meaning of the data table or the relationship between the data tables, and there is no problem of difficulty in modifying the development code when the data changes. Moreover, as subsequent data relationships are continuously obtained, the query scope will also be larger, greatly reducing the cost of data retrieval and improving retrieval efficiency. At the same time, because the above solution can quickly and accurately determine the target data relationship in a large number of business scenarios, the above solution is also applicable to a large number of application scenarios for business promotion, solving the problems of high customization cost, high docking cost and low retrieval efficiency of data retrieval in a large number of business scenarios.

[0035] As an optional embodiment, based on the retrieval starting conditions and the retrieval scenario labels, a variety of methods can be used to determine the retrieval link between the starting data corresponding to the retrieval starting conditions and the target data corresponding to the retrieval scenario labels. For example, the following method can be used: obtaining a standard data relationship between the associated starting data and the target data, wherein the standard data relationship is a relationship between predetermined fields and predetermined fields; and determining the retrieval link between the starting data and the target data based on the standard data relationship. By obtaining the standard data relationship between the associated starting data and the target data, since the standard data relationship is a relationship between predetermined fields and predetermined fields determined based on predetermined standards, the relationship is definite and accurate, and therefore a very clear data relationship can be obtained. At the same time, since the standard data relationship can be directly obtained, there is no need to recalculate the relationship between the fields each time a retrieval is performed, nor is there a need to understand the meaning of each field. This greatly reduces the cost of retrieving data and improves retrieval efficiency.

[0036] As an optional embodiment, based on the retrieval starting condition and the retrieval scenario label, a retrieval link between the starting data corresponding to the retrieval starting condition and the target data corresponding to the retrieval scenario label can be determined in a variety of ways. For example, the following method can be used: obtaining a standard data relationship and an extended data relationship that associate the starting data and the target data, wherein the standard data relationship is the relationship between a predetermined field and a predetermined field, and the extended data relationship is the relationship between a predetermined field and a business-customized field; and determining the retrieval link between the starting data and the target data based on the standard data relationship and the extended data relationship. By obtaining the standard data relationship and the extended relationship that associate the starting data and the target data, a very clear data relationship can be obtained without clarifying the specific meaning of each field. In particular, the extended data relationship can link the predetermined field with the business-customized field. By constructing and entering the extended data relationship, the user's operation of configuring the retrieval path according to the business scenario is greatly simplified. At the same time, the above solution can be applied to different business scenarios by simply changing the corresponding extended data relationship. Thus, the required data can still be quickly and accurately retrieved based on the relationship between the fields in different and a large number of business scenarios, reducing the problems of high customization cost, high connection cost and low retrieval efficiency of data retrieval in a large number of business scenarios.

[0037] It should be noted that the above-mentioned method of determining the retrieval link between the starting data and the target data based on the standard data relationship and / or extended data relationship between the starting data and the target data is only used as a preferred means, that is, when there is a standard data relationship and / or extended data relationship, the retrieval process can be greatly shortened, but the standard data relationship or the extended data relationship is not necessary. When there is no standard data relationship or extended data relationship between the starting data and the target data, the optional embodiment of the present disclosure can still gradually complete the retrieval according to other data relationships.

[0038] It should be noted that the search links may differ in different business scenarios. The search links corresponding to the business scenarios can be configured by the system or by the user. For example, in situations with multiple application scenarios and a high degree of scenario reuse, users can greatly reduce repetitive operations and save complex search costs by configuring the search links themselves. In addition, the above-mentioned satisfaction of various search requirements in different business scenarios can be for business scenarios with high reuse of a certain application scenario, or for situations where the application scope is expanded to a large number of complex business scenarios. For example, when faced with a large number of business scenarios, since different business scenarios may use different data, the data sources are numerous and the relationships are complex, making it difficult for users to clearly understand the meaning of each data field. However, according to the above method, users only need to modify or improve the extended relationship data table when expanding new business scenarios to configure a complete search link according to the search needs, thereby quickly and accurately completing data retrieval, greatly eliminating the heavy and complex use costs of related technical solutions where users need to first understand the data meaning before conducting data development. In practical applications, especially for new business expansion and application scenarios of a large number of different business expansions, the above method can demonstrate good applicability, convenience, and scalability.

[0039] As an optional embodiment, a search can be performed based on a search link to obtain search results in a variety of ways. For example, the following methods can be used: assemble a search statement based on the search link; use the search statement to perform a search and obtain a search result. When searching based on a search link, the search conditions entered can determine the search conditions for the first table in the search link, and in subsequent link searches, the result set of the previous search is used as the search condition. In this way, each table is searched, so that the entire data retrieval process can be carried out in an orderly manner. After the search is completed, the method of result aggregation can also be determined based on the input aggregation conditions. For example, assuming that the search result has multiple values, depending on the different input aggregation conditions, the final result returned can be to return all data; to aggregate by dimension and return the first value of each dimension; to take only the latest data; or to aggregate all data into one and return it. By returning results in this way, different forms of search results can be provided according to different user search requirements, improving the flexibility of data retrieval and further providing users with higher-quality personalized data retrieval services.

[0040] It should be noted that the specific configuration of the above-mentioned search links depends on the actual search conditions and search scenarios. For example, multiple search links can be configured based on the search scenario, or multiple starting data can be selected as the search starting point based on the search conditions, thereby naturally achieving many-to-many data retrieval. The above-mentioned search scenarios are merely illustrative. Other search link configurations and actual usage scenarios are also within the scope of the embodiments of this disclosure and will not be further illustrated here.

[0041] Based on the above embodiments and optional embodiments, an optional implementation is provided, which is described below.

[0042] Long-link data retrieval is a technical solution used in situations where data relationships are clear and multi-table joint retrieval is used. In actual application scenarios in the field of performance research and development, in order to adapt to different requirements, data users need to understand the business significance of various data tables, the relationship between data, and develop data retrieval code on their own to obtain correct data. This solution has problems such as high customization costs, high docking costs, and low retrieval efficiency when promoting a large number of businesses. The optional implementation method disclosed in this disclosure is suitable for situations where data relationships are clear and there are many business customized retrieval scenarios, which can greatly reduce retrieval costs and improve efficiency.

[0043] The current solutions for long-link data retrieval are as follows:

[0044] (1) User development: In this solution, the data user bears the cost of use. The data user needs to understand the meaning of the data table and the relationship between the data tables, and obtain the data results he needs by developing data calculation code.

[0045] (2) Data middle platform development. The data middle platform in this solution is responsible for data collection, governance, and dimensional modeling. When the business has needs, the middle platform will submit requirements to the middle platform, which will then develop and provide data provision methods such as interfaces or SDKs.

[0046] However, the above solution also has disadvantages:

[0047] In the application scenario of solution (1), when querying data from different business parties, users need to understand the relationships between different tables and write complex JOIN SQL statements. The more tables there are, the more complex the SQL statements become. In some cases, it is difficult for ordinary search users to clearly understand the relationships between business data and cannot complete joint table searches. Therefore, solution (1) is very costly for data users, and the data calculation and maintenance costs are high. When the original data changes, users need to spend time and energy to modify the code to obtain what they need.

[0048] Solution (2) is suitable for scenarios with clear business scenarios and the ability to clearly divide and model data domains. However, it is not applicable to data from a large number of business scenarios. The data middle platform cannot fully understand the meaning of the data and cannot quickly provide business needs.

[0049] In response to the above problems, an optional implementation method of the present disclosure proposes a long-link data retrieval solution. This long-link data retrieval solution is based on the basic data retrieval capability, and it has a very clear premise, namely, clear data relationships. In an optional implementation method of the present disclosure, data association relationships are described by links, and the retrieval paths of different fields between different tables are also determined by links. Among them, the important components of the optional implementation method of the present disclosure are data association relationships and data retrieval links. The data association relationships and data retrieval links are introduced separately below.

[0050] (1) Data Relationship

[0051] If different fields in different business tables have the same business meaning, then the above-mentioned different business tables can be connected using the fields with the same business meaning, and the data in the connected business tables will have a data relationship.

[0052] Data relationships in the system are divided into two categories: standard relationships and extended relationships. Standard relationships are explicitly defined by the various modules or platforms that comprise the system. They have uniform definitions and standard naming within the system. These relationships can be stored uniformly in a single data relationship table (typically, data IDs are sufficient). Extended relationships are extended by various custom service providers. Each custom service provider has its own data ID, and each type of data is associated with one or more fields in the standard data relationship table. For example, the following table assumes that a system has the following relationship table, named CICD_BASIC_INFO.

[0053] Column Name type describe id Bigint(11) Auto-increment id AGILE_MODULE_NAME varchar(255) Module Name AGILE_WORKSPACE_ID varchar(255) Space ID AGILE_PIPELINE_ID varchar(255) Pipeline id AGILE_PIPELINE_BUILD_ID varchar(255) Pipeline build id AGILE_PIPELINE_JOB_CONF_ID varchar(255) Job ID AGILE_PIPELINE_JOB_BUILD_ID varchar(255) Job build id COMMIT_ID varchar(255) Commit id timestamp datetime Data time

[0054] Table 1 Standard relationship table

[0055] Custom service A is associated with the system through its AGILE_PIPELINE_JOB_BUILD_ID. Therefore, the extended relationship table is designed to automatically record this information during data entry. As shown in the following table, assume that the extended relationship table is named EXTEND_CICD_BASIC_INFO.

[0056]

[0057] Table 2 Extended relationship table

[0058] Through two relational tables, all standard data and business-customized data in a system can be linked together.

[0059] (2) Retrieval link

[0060] After connecting different business tables using fields with the same business significance, a connection relationship between different business tables can be obtained, that is, an association link, which is also referred to as a retrieval link in an optional embodiment of the present disclosure.

[0061] For example, all IDs in the above standard relational table can be used as search IDs, and AGILE_PIPELINE_JOB_BUILD_ID in the above standard relational table is assumed to be the ID with the smallest granularity.

[0062] In a search link configuration, you need to clearly specify the search link's start ID, end ID, the standard relationship table name used (this solution can be used in scenarios with multiple relationships), and the relationship filtering conditions (such as taking the most recent one or selecting according to other rules).

[0063] Now assume that the starting ID of a search link is COMMIT_ID and the ending ID is AGILE_PIPELINE_BUILD_ID, and the associated search is configured in the following JSON:

[0064]

[0065]

[0066] In actual applications, it is not possible to directly obtain AGILE_PIPELINE_BUILD_ID through COMMIT_ID in the association table. An intermediate ID is required for transfer. That is, all AGILE_PIPELINE_JOB_BUILD_IDs are obtained in the CICD_BASIC_INFO table through COMMIT_ID, and then AGILE_PIPELINE_JOB_BUILD_ID is used to reversely query AGILE_PIPELINE_BUILD_ID to indirectly establish the relationship.

[0067] Therefore, by using the standard relationship table, you can obtain the relationship between the start ID and the end ID through simple calculation and transformation, and by using the extended relationship table, you can obtain the relationship between the standard relationship table and the custom table through the standard relationship field.

[0068] In actual applications, multiple tables are typically queried, and different tables may use different relationships, meaning that multiple search links are used in a single search. Businesses need to register scenarios in the system. Each scenario has a scenario tag that uniquely represents the configuration. Within a scenario configuration, businesses primarily need to identify the required data tables and fields. Figure 2 is a schematic diagram of a data processing method provided according to an optional embodiment of the present disclosure, such as Figure 2 The specific retrieval process is as follows:

[0069] (1) Parse the search request and obtain the scene label;

[0070] (2) Obtain search configuration based on the tag and parse the circled data table and field name;

[0071] (3) Assemble the retrieval task and enter the concurrent processing thread pool;

[0072] (4) Determine whether the data table is a system standard table;

[0073] (5) If it is a system standard table, scan the CICD_BASIC_INFO table to obtain the start ID and end ID; if it is not a system standard table, scan the EXTEND_CICD_BASIC_INFO table to obtain the standard field name associated with the standard table as the end ID;

[0074] (6) Obtain the system configuration retrieval link and assemble the retrieval statement;

[0075] (7) Get all thread search results;

[0076] (8) The aggregation results are returned.

[0077] Figure 3 is a flow chart of a data processing method provided according to another optional embodiment of the present disclosure, such as Figure 3 The specific usage process is as follows:

[0078] (1) Search input: input the starting point of the search link, search conditions, etc.

[0079] (2) Establish data association relationships: Establish standard association relationships in the system and automatically generate extended association relationship tables through data entry specifications;

[0080] (3) Configure the retrieval link:,determine a unique link by retrieving the start ID and end ID;

[0081] (4) Registering business scenarios: The business party registers its own scenarios in the system, focusing on identifying the required tables and fields. Each business table includes search fields, table names, and table types;

[0082] (5) Searching based on search conditions: The search process starts with link search. After obtaining the value of the dimension field, the fields in the scenario configuration are searched in the business table. The search conditions in the search input can be used to determine the search conditions for the first table in the search link. The search conditions for subsequent links are based on the result set of the previous SQL statement until the target field is found.

[0083] (6) Result aggregation: When the search results contain multiple values, different result aggregation methods are implemented according to different aggregation conditions. For example, all data can be returned, data can be aggregated according to data dimensions and the first value of each dimension can be returned, only the latest data can be taken, or all data can be aggregated into one;

[0084] (7) Output the search results.

[0085] Through the above-mentioned retrieval configuration service, the following technical effects can be achieved:

[0086] (1) Through the process of introducing linked data, links are deposited during the process of introducing business data, or the business person in charge who is familiar with the data relationship configures the link relationship for use by search users. In the case of a link relationship, the search user can use only the fields at the beginning and end of the link to determine a link and use the link to perform cross-table search, thereby solving the problem of joint query difficulties between different source data with clear data relationships;

[0087] (2) It can provide the function of scenario configuration. For retrieval with a high degree of reuse, a set of scenario templates is provided. Business parties can define the tables and fields to be retrieved, as well as the end point of the link through scenario configuration. When searching, they only need to provide the scenario template to be used, the starting point of the link, and the corresponding search conditions to complete a long link search. In different scenarios, only different scenario templates need to be configured, which greatly reduces repetitive operations and saves the cost of complex searches.

[0088] (3) As data relationships accumulate, more data will be connected, and the scope of joint table queries will be larger.

[0089] In an embodiment of the present disclosure, a data processing device is further provided. Figure 4 is a structural block diagram of a data processing device provided according to an embodiment of the present disclosure, such as Figure 4 As shown, the device includes: a first receiving module 41, a first determining module 42 and a first searching module 43. The device is described below.

[0090] The first receiving module 41 is used to receive a retrieval request, wherein the retrieval request carries a retrieval starting condition and a retrieval scenario tag; the first determining module 42 is connected to the above-mentioned first receiving module 41, and is used to determine, based on the retrieval starting condition and the retrieval scenario tag, a retrieval link from the starting data corresponding to the retrieval starting condition to the target data corresponding to the retrieval scenario tag; the first retrieval module 43 is connected to the above-mentioned first determining module 42, and is used to perform a search based on the retrieval link to obtain a retrieval result.

[0091] As an optional embodiment, the first determination module includes: a first acquisition unit, used to obtain a standard data relationship associating the starting data and the target data, wherein the standard data relationship is a relationship between predetermined fields and predetermined fields; a first determination unit, used to determine a retrieval link between the starting data and the target data based on the standard data relationship.

[0092] As an optional embodiment, the first determination module includes: a second acquisition unit, used to obtain the standard data relationship and extended data relationship of the associated starting data and target data, wherein the standard data relationship is the relationship between predetermined fields and predetermined fields, and the extended data relationship is the relationship between predetermined fields and business customized fields; the second determination unit is used to determine the retrieval link between the starting data and the target data based on the standard data relationship and the extended data relationship.

[0093] As an optional embodiment, the first search module includes: an assembling unit, configured to assemble a search statement based on a search link; and a retrieval unit, configured to perform a search using the search statement to obtain a search result.

[0094] In the technical solutions disclosed herein, the acquisition, storage, and application of user personal information involved comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0095] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0096] Figure 5 A schematic block diagram of an example electronic device 500 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are provided as examples only and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0097] like Figure 5 As shown, the device 500 includes a computing unit 501, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 502 or a computer program loaded from a storage unit 508 into a random access memory (RAM) 503. Various programs and data required for the operation of the device 500 can also be stored in the RAM 503. The computing unit 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0098] Various components in device 500 are connected to I / O interface 505, including: an input unit 506, such as a keyboard, mouse, etc.; an output unit 507, such as various types of displays, speakers, etc.; a storage unit 508, such as a magnetic disk, optical disk, etc.; and a communication unit 509, such as a network card, modem, wireless communication transceiver, etc. The communication unit 509 allows device 500 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0099] The computing unit 501 can be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 501 performs the various methods and processes described above, such as the data processing method. For example, in some embodiments, the data processing method can be implemented as a computer software program that is tangibly contained in a machine-readable medium, such as the storage unit 508. In some embodiments, part or all of the computer program can be loaded and / or installed on the device 500 via the ROM 502 and / or the communication unit 509. When the computer program is loaded into the RAM 503 and executed by the computing unit 501, one or more steps of the data processing method described above can be performed. Alternatively, in other embodiments, the computing unit 501 can be configured to perform the data processing method by any other appropriate means (e.g., by means of firmware).

[0100] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0101] The program code for implementing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when the program code is executed by the processor or controller, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

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

[0103] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0104] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.

[0105] A computer system may include a client and a server. The client and server are generally remote from each other and typically interact through a communication network. The client-server relationship arises through computer programs running on the respective computers and having a client-server relationship with each other. The server may be a cloud server, a server in a distributed system, or a server integrated with a blockchain.

[0106] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this disclosure can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved. This is not a limitation herein.

[0107] The above specific embodiments do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure shall be included within the scope of protection of this disclosure.

Claims

1. A data processing method, comprising: Receiving a search request, wherein the search request carries a search starting condition and a search scenario tag; Based on the retrieval starting condition and the retrieval scenario label, determining a retrieval link from the starting data corresponding to the retrieval starting condition to the target data corresponding to the retrieval scenario label, wherein the retrieval link is used to represent a connection relationship between different business tables; Performing a search based on the search link to obtain a search result; The search results are aggregated according to an aggregation method, and the aggregated search results are returned, wherein the aggregation method is determined according to the input aggregation condition.

2. The method according to claim 1, wherein Determining, based on the retrieval starting condition and the retrieval scenario tag, a retrieval link from the starting data corresponding to the retrieval starting condition to the target data corresponding to the retrieval scenario tag, comprising: Acquire a standard data relationship associating the starting data with the target data, wherein the standard data relationship is a relationship between predetermined fields; Based on the standard data relationship, a retrieval link between the starting data and the target data is determined.

3. The method according to claim 1, wherein Determining, based on the retrieval starting condition and the retrieval scenario tag, a retrieval link from the starting data corresponding to the retrieval starting condition to the target data corresponding to the retrieval scenario tag, comprising: Acquire a standard data relationship and an extended data relationship that associate the starting data with the target data, wherein the standard data relationship is a relationship between predetermined fields, and the extended data relationship is a relationship between a predetermined field and a business customized field; Based on the standard data relationship and the extended data relationship, a retrieval link between the starting data and the target data is determined.

4. The method according to any one of claims 1 to 3, wherein The searching based on the search link to obtain the search results includes: Assembling a search statement based on the search link; The search statement is used to perform a search to obtain a search result.

5. A data processing device comprising: A first receiving module is configured to receive a search request, wherein the search request carries a search starting condition and a search scenario tag; a first determining module, configured to determine, based on the retrieval starting condition and the retrieval scenario tag, a retrieval link from the starting data corresponding to the retrieval starting condition to the target data corresponding to the retrieval scenario tag, wherein the retrieval link is used to represent a connection relationship between different business tables; A first retrieval module, configured to perform a search based on the retrieval link to obtain a retrieval result; The data processing device is further configured to aggregate the search results according to an aggregation method and return the aggregated search results, wherein the aggregation method is determined according to an input aggregation condition.

6. The device according to claim 5, wherein The first determining module includes: a first acquiring unit, configured to acquire a standard data relationship associating the starting data with the target data, wherein the standard data relationship is a relationship between predetermined fields; The first determining unit is configured to determine a retrieval link between the starting data and the target data based on the standard data relationship.

7. The device according to claim 5, wherein The first determining module includes: a second acquiring unit, configured to acquire a standard data relationship and an extended data relationship associating the starting data with the search target data, wherein the standard data relationship is a relationship between predetermined fields and predetermined fields, and the extended data relationship is a relationship between a predetermined field and a business customized field; The second determining unit is configured to determine a retrieval link between the starting data and the target data based on the standard data relationship and the extended data relationship.

8. The device according to any one of claims 5 to 7, wherein The first retrieval module includes: an assembling unit, configured to assemble a search statement based on the search link; The retrieval unit is used to perform retrieval using the retrieval statement to obtain retrieval results.

9. An electronic device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 4.

10. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1 to 4.

11. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 4.

Images