CN116755685A - Configuration method, device and data query method of data interface - Google Patents

Abstract

The embodiment of the application provides a data interface configuration method, a data interface configuration device and a data query method, which can enable an developer to quickly configure and issue a data interface for querying target data only with basic development experience. The configuration method of the data interface comprises the following steps: responding to the creation operation of the data interface, and creating a corresponding data source for the data interface; responding to a first configuration operation for the data interface, and determining a database driver, a database connection and a query template corresponding to the data interface according to the first configuration operation, wherein the query template is a precompiled data source query instruction using a placeholder to replace a request parameter; responding to a second configuration operation for the data interface, creating unique interface information corresponding to the data interface according to the second configuration operation, and determining the mapping relation between the unique interface information and the database driver, the database connection and the query template; responsive to a docking operation for the data interface, the data interface is published to the business system to provide a data query.

Description

Configuration method, device and data query method of data interface

【Technical field】

The embodiments of the present application relate to the field of database technology, and in particular, to a data interface configuration method, device and data query method.

【Background technique】

At present, with the rapid development of big data technology, many enterprises and institutions are connecting their internal business systems with database products provided by various big data platforms, and using the data interfaces provided by them to integrate the data generated by the business systems. ,manage. However, when developing data interfaces for these database products, developers often need to have high development experience in Structured Query Language (SQL) and other programming languages, and the development of data interfaces takes a long time and costs a lot. higher.

[Content of the invention]

The embodiments of this application provide a data interface configuration method, data query method and device, which enable developers to quickly configure and publish user-oriented data interfaces only with basic development experience in structured query languages and programming languages. This allows users to easily query the required target data through the business system using the data interface, reducing the development time and cost of the data interface.

In a first aspect, embodiments of the present application provide a method for configuring a data interface. The method includes:

In response to the creation operation of the data interface, create a corresponding data source for the data interface;

In response to the first configuration operation for the data interface, determine the database driver, database connection and query template corresponding to the data interface according to the first configuration operation. The query template is a pre-compiled request parameter using placeholders. Data source query instructions;

In response to the second configuration operation for the data interface, create unique interface information corresponding to the data interface according to the second configuration operation, and determine whether the unique interface information is consistent with the database driver, the database connection, and the Query the mapping relationship between templates;

In response to the docking operation on the data interface, the data interface is published to the business system to provide data query.

In the embodiment of this application, after creating the data source connected to the data interface, the developer can directly specify the database driver, database connection and precompiled query template corresponding to the data interface through relevant operations, as well as establish the information and data interface. The mapping relationship between unique interface information can quickly complete the development of data interfaces. There is no need to design and program the underlying code architecture of the data interface, reducing development time and development costs.

Optionally, before the response is to the docking operation of the data interface and the data interface is released to the business system to provide data query, the method further includes:

In response to the pre-check configuration operation for the data interface, generate a required parameter rule according to the pre-check configuration operation, and connect the required parameter rule with the data interface. The required parameter rule is used To check whether the request parameters sent by the user to the data interface include all parameters that can query the target data.

In the embodiment of this application, the required parameter rules are formulated to check whether the request parameters filled in by the user when querying the target data include all the parameters necessary to locate the target data. If these parameters are not included, an error message will be returned to remind The filling in of user parameters is illegal, allowing users to discover problems with filling in request parameters and modify them.

Optionally, the data source is a relational database, and the response is to the first configuration operation of the data interface before determining the database driver, database connection and query template corresponding to the data interface according to the first configuration operation. , the method also includes:

In response to the template engine setting operation for the query template, determine the template engine that needs to be used to render the query template based on the relational database;

In response to an editing operation on the query template, generate a precompiled structured query language instruction, at least one placeholder, and a template engine instruction for describing a text rendering method of the structured query language instruction into a relational database-based The query template.

In the embodiment of this application, you can specify the template engine that needs to be used for the query template, and use the structured query language, the corresponding template engine instruction language, and at least one predetermined placeholder to write instructions for rendering the structured query language. Retrieve query templates of relational databases, allowing developers to customize configurations based on different data sources and user needs, enhancing the flexibility of data interface development and saving the development effort of separately configuring each user requirement. time.

Optionally, the data source is a non-relational database, and the response to the first configuration operation of the data interface determines the database driver, database connection and query template corresponding to the data interface according to the first configuration operation. Previously, the method also included:

In response to a template engine setting operation for the query template, determine the template engine that needs to be used to render the query template based on a non-relational database;

In response to an editing operation on the query template, a precompiled unstructured query language instruction, at least one placeholder, and a template engine instruction for describing a text rendering method of the unstructured query language instruction are generated into a non-structured query template based on the non-structured query language instruction. The query template for a relational database.

In the embodiment of this application, in order to adapt to data sources of non-relational database types, developers also need to use the data source query instruction language supported by non-relational databases, pre-specified placeholders, and corresponding templates for template rendering. The engine instructions are configured as non-relational query templates for rendering unstructured query language instructions just like when querying relational databases, so as to be compatible with queries to non-relational databases and adapt to users' more diverse query needs.

Optionally, before the response is to the docking operation of the data interface and the data interface is released to the business system to provide data query, the method further includes:

In response to the post-computing configuration operation of the data interface, a post-processor is connected to the data interface according to the post-computing configuration operation, and the post-processor is used to use conventional operators according to user needs. The target data is processed.

In the embodiment of this application, the data interface is connected to the corresponding post-processor to achieve the effect of using conventional operators to process the queried target data according to user needs, thereby improving the flexibility and customizability of the data interface.

In the second aspect, embodiments of the present application provide a data interface configuration device. The device includes:

A data source creation unit, used to respond to the creation operation of the data interface and create a corresponding data source for the data interface;

A configuration unit configured to respond to a first configuration operation for the data interface and determine the database driver, database connection and query template corresponding to the data interface according to the first configuration operation. The query template is replaced by a placeholder. Precompiled data source query instructions for request parameters;

The configuration unit is also configured to respond to a second configuration operation for the data interface, create unique interface information corresponding to the data interface according to the second configuration operation, and determine whether the unique interface information is consistent with the database driver. , the mapping relationship between the database connection and the query template;

The docking unit is configured to respond to the docking operation of the data interface and publish the data interface to the business system to provide data query.

Optionally, the device also includes:

A generating unit configured to respond to a pre-check configuration operation for the data interface, generate a required parameter rule according to the pre-check configuration operation, and bind the required parameter rule to the data interface, so The above required parameter rules are used to check whether the request parameters sent by the user to the data interface contain all parameters that can query the target data.

Optionally, the device also includes:

A determining unit configured to respond to a template engine setting operation for the query template and determine the template engine that needs to be used to render the query template based on the relational database;

The generating unit is also configured to respond to an editing operation on the query template, and generate a precompiled structured query language instruction, at least one placeholder, and a template used to describe the text rendering method of the structured query language instruction. The engine instructions are generated as the query template based on the relational database.

Optionally, the determining unit is also configured to determine the template engine that needs to be used to render the query template based on a non-relational database in response to a template engine setting operation for the query template;

The generating unit is also configured to respond to the editing operation of the query template and generate a precompiled unstructured query language instruction, at least one placeholder, and a text rendering method used to describe the unstructured query language instruction. The template engine instructions generate the query template based on the non-relational database

Optionally, the docking unit is also configured to respond to a post-computing configuration operation for the data interface, and dock a post-processor to the data interface according to the post-computing configuration operation. The post-processing The processor is used to process the target data using conventional operators according to the user's needs.

It should be understood that the second aspect of the embodiments of the present application is consistent with the technical solution of the first aspect of the embodiments of the present application, and the beneficial effects achieved by each aspect and corresponding feasible implementations are similar, and will not be described again.

In a third aspect, embodiments of the present application provide a data query method, which method includes:

Receive a query request sent by the business system, the query request including the unique interface information of the target data to be queried and the request parameters;

According to the mapping relationship between the preconfigured unique interface information and the query template, query the query template corresponding to the unique interface information, where the query template is a precompiled data source query instruction that uses placeholders to replace request parameters;

Import the request parameters and the query template into a template engine and render them into data source query instructions;

Query the target data from the data source according to the unique interface information and the data source query instruction;

Send the target data to the business system.

In the embodiment of this application, after receiving the query request issued by the business system, the corresponding query template is obtained according to the unique interface information in the query request, and the request parameters in the query request and the query template are sent to the template engine. Render an instruction that can be read by the database; then execute the instruction to obtain the target data from the database and send it to the business system, allowing users to easily query the target data from the database platform and greatly reducing the operational threshold for using the database.

Optionally, before querying the query template corresponding to the unique interface information according to the pre-configured correspondence between the unique interface information and the query template, the method further includes:

Obtain preconfigured required parameter rules, which are used to check whether the request parameters contain all parameters necessary to locate the target data from the data source;

Check the request parameters according to the required parameter rules;

If the request parameter check fails, an error message is output, and the error message is used to prompt the user that the filling in of the request parameter is illegal.

In the embodiment of this application, by checking whether the request parameters filled in by the user when querying the target data include all the parameters necessary to locate the target data, if these parameters are not included, an error message will be returned to remind the user that the parameter filling is illegal. This allows users to discover that the current query request cannot query the target data and modify it.

Optionally, the query request also includes post-calculation rules for processing the target data. The post-calculation rules include one or more operators. The target data is sent to the business system. include:

According to the post-calculation rules, use a post-processor to calculate the target data to obtain the target data calculation results;

Send the target data calculation result to the business system.

In the embodiment of this application, after the original target data in the data source is obtained, further calculation processing is performed on the queried target data by parsing the post-calculation rules contained in the query request, thereby directly outputting the results required by the user. , enhance the flexibility of data query.

Optionally, the data interface for receiving the query request and sending the target data is the only external interface.

In the embodiments of this application, data is received and sent through a unified external interface, thereby solving the problem that traditional database platforms need to open a dedicated data interface for each business system, and enhancing the convenience of data interface management.

[Picture description]

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of this specification. Those of ordinary skill in the art can also obtain other drawings based on these drawings without exerting creative efforts.

Figure 1 is a schematic flow chart of a target data query method provided by an embodiment of the present application;

Figure 2 is a schematic flowchart of a method for configuring required parameter rules in an embodiment of the present application;

Figure 3 is a schematic flowchart of a post-processor configuration method in an embodiment of the present application;

Figure 4 is a schematic flow chart of a query template configuration method based on a relational database in an embodiment of the present application;

Figure 5 is a schematic flowchart of a query template configuration method based on a non-relational database in an embodiment of the present application;

Figure 6 is a schematic structural diagram of a data interface configuration device in an embodiment of the present application;

Figure 7 is a schematic flow chart of a data query method provided by an embodiment of the present application;

Figure 8 is an operating logic diagram of a data interface provided by an embodiment of the present application.

【Detailed ways】

In order to better understand the technical solutions of this specification, the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

It should be clear that the described embodiments are only some of the embodiments of this specification, but not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without making creative efforts fall within the scope of protection of this specification.

The terminology used in the embodiments of the present application is for the purpose of describing specific embodiments only and is not intended to limit the specification. As used in the embodiments and the appended claims, the singular forms "a," "the" and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise.

At present, with the rapid development of big data technology, many enterprises and institutions are connecting their internal business systems with the database platforms provided by various big data platforms to integrate and manage various data generated in the business systems through the database platform. , Reduce the costs of data management and operation and maintenance for enterprises and institutions themselves.

The inventor of the present application found through research that when using the interfaces provided by these database platform products to query relevant business data, users often need to use SQL codes to write their own query instructions, or use professional database management tools to operate. The former requires users to have a certain SQL programming foundation, while the latter is often difficult for enterprises or institutions to afford due to the high price of management tools. Due to these shortcomings, the use threshold and limitations of this type of database platform are high, and it is unable to adapt to a variety of applications. oriented target data query requirements.

In view of this, embodiments of the present application provide a target data query method, which can import the user's query request and the corresponding query template into the template engine to generate a data source query instruction that can query the specified target data, allowing users to Users only need to have a basic understanding of structured query language to query business data in the cloud, reducing the cost and operation threshold of the database platform and meeting the query needs of various target data.

The technical solutions provided by the embodiments of the present application will be introduced below with reference to the accompanying drawings. Please refer to Figure 1. This embodiment of the present application provides a method for querying target data. The process of the method is described as follows:

Step 101: In response to the creation operation of the data interface, create a corresponding data source for the data interface.

Specifically, when creating the data interface required by the embodiment of this application, it is necessary to configure the data source corresponding to the current data interface, that is, the program basis for storing relevant business data to support data query services. Taking the relational database as an example, you should first create the data table used by the current data source (because of the storage structure limitations of the relational database, it is necessary to obtain the table name and column name to query the corresponding data table and data column). A one-step operation is generally implemented by accessing data and selecting the required data type, setting filter conditions such as date, filtering fields, and configuring user permissions. Then, establish a supporting data model based on the data table, configure developer permissions, data source name, and table name to complete the data source creation process.

Step 102: In response to the first configuration operation for the data interface, determine the database driver, database connection, and query template corresponding to the data interface according to the first configuration operation. The query template is a precompiled data source query instruction that uses placeholders to replace request parameters.

Specifically, the first configuration operation is used to configure the way the user connects to the target data source through the data interface, including a database driver used to parse and execute data query instructions, a database connection used to transmit the target data, and a database connection used to combine the user's The query request performs text rendering to derive a query template for the data query instructions.

It should be understood that the most common way to establish a database connection is to configure multiple continuously available connection objects, and directly allocate the corresponding connection object when a database connection needs to be called, so as to reduce the time-consuming creation and closing of the connection. These multiple connection objects together constitute the "connection pool" of the database - a dynamic mechanism responsible for allocating, managing and releasing database connections. It can retain a plurality of existing connection objects (such as 100) and allow query programs to Reuse one of the existing database connections.

Step 103: Respond to the second configuration operation of the data interface, create unique interface information corresponding to the data interface according to the second configuration operation, and determine the mapping relationship between the unique interface information and the database driver, database connection, and query template.

Specifically, the second configuration operation is mainly used to edit the connection details specified in the unique interface information. In the embodiment of this application, the unique interface information is mainly responsible for locating the data source according to the connection information recorded in the user to establish a connection when the user performs a query operation, thereby enabling the query command to input the data source and obtain the feedback target data result.

The specific configuration items of unique interface information include interface name and interface version number. The interface name is mainly responsible for recording information such as the data interface type and the connected business system, and is used to achieve unified management of the data interface, while the interface version number is used to carry the specific connection details of a single connection. By configuring the mapping relationship between the interface name and interface version number and the data source type, query template, user name, password, HOST information (IP address or domain name) and POST field (port information), the user can pass When querying the data interface, the relevant information is directly retrieved, the handshake process is executed, and the connection between the business system and a specific data source is established.

Step 104: In response to the docking operation of the data interface, publish the data interface to the business system to provide data query.

Specifically, the docking operation is mainly used to connect a certain data interface with the business system, that is, publish the developed data interface and connect the data interface to the corresponding business system to open the query of target data to the business system.

Before the data interface configuration is completed and released, more functions such as required parameter verification need to be added according to actual development needs to verify whether the query requests sent by users through the business system are legal.

Figure 2 is a configuration method of required parameter rules in an embodiment of the present application. As a possible implementation, before step 104, step 105 may be further performed.

Step 105: Respond to the pre-check configuration operation for the data interface, generate required parameter rules based on the pre-check configuration operation, and connect the required parameter rules with the data interface. The required parameter rules are used to check what the user sends to the data interface. Whether the request parameters contain all parameters that can query the target data.

In the embodiment of this application, the pre-check configuration operation of the data interface developer is mainly used to: configure a pre-processor to check the query request sent by the user, and determine whether all the parameters contained in it can support the user's query. operation, and the mechanism used to check the query request is the "required parameter rule".

Specifically, the items checked by this required parameter rule mainly include all parameters necessary to locate the target data in the data source. For example, in a relational database, the request parameters must generally include the table names and column names required to query the target data. , while in non-relational databases, required parameters vary according to different data source types, generally including database or collection name, query conditions, query projection, sorting rules, grouping rules, etc.; and the types of data sources that need to be queried are different. , the required parameter rules may also contain other required input parameters (such as row names, unique identification codes, factory dates, etc.) to support query operations on different data source types.

By adding this pre-processor, when the data interface receives a query request, it can be verified according to the required parameter rules, instead of returning an error message when the data source query command fails to render, or when the query using the rendered command fails. It is worth mentioning that in order to meet the needs of quick configuration, the specific actions of the pre-check configuration operation can include: customizing a new required parameter rule, or selecting a preset required parameter rule based on the specific type of data source and Custom modifications.

After configuring the pre-processor, a similar post-processor should be set up according to development needs to meet more complex user query needs.

Figure 3 is a configuration method of a post-processor in an embodiment of the present application. As a possible implementation, before step 104, step 106 may be further performed.

Step 106: In response to the post-computing configuration operation of the data interface, connect the post-processor to the data interface according to the post-computing configuration operation. The post-processor is used to process the target data using conventional operators according to the user's needs.

In the embodiment of this application, since the user may need to perform additional processing on the queried target data, the developer also needs to configure the post-processor corresponding to the data interface according to this requirement. By connecting the post-processor to the data interface, after the current data interface receives the query request, the additional post-calculation rules written in the query request can be parsed, and the target data obtained from the query can be calculated according to the operators in the rules. Special operations such as sum, difference, left or right shift, specific value, and byte count statistics allow the business system to receive the secondary processing results of the target data when receiving query results, which is what the user hopes to get. the result of. Similar to the pre-processor, in order to meet the purpose of rapid development, the specific actions of the post-processor configuration operation can include: customizing a new post-processor, or selecting a preset post-processor based on the general query requirements of the business system. processor and custom modifications.

In addition, when the pre-processor and post-processor are configured, developers also need to configure the query template used to render the data source query instructions to ensure the convenience of users querying the target data.

Figure 4 is a query template configuration method based on a relational database in an embodiment of the present application. As a possible implementation, before step 102, steps 107 to 108 may be further performed.

Step 107: In response to the template engine setting operation for the query template, determine the template engine that needs to be used to render the query template based on the relational database.

Step 108: In response to the editing operation of the query template, generate the precompiled structured query language instruction, at least one placeholder, and a template engine instruction used to describe the text rendering method of the structured query language instruction into a relational database-based Query template.

In the embodiment of this application, in order to enable the user to query the target data without inputting a complete query command, the developer needs to configure the query template available for this data source query operation in advance. Specifically, when the query database is a relational database, generating a query template first requires the developer to select the corresponding template engine according to the type of data source, design the abstract syntax tree of the data source query instructions, and use the corresponding structured query language Compile the abstract syntax tree into a formal data source query instruction, in which the specific variable content needs to be replaced by placeholders.

For example, when a user wants to query customer data named "XiaoMing" from a table in a relational database used to record customer information, the traditional method requires the user to enter a piece of content as "SELECT*FROM CustomerWHERE Name='XiaoMing'; "The complete query command means to find all the customer information named "XiaoMing" in the Customer table and return the corresponding information. In the embodiment of this application, the developer will write a precompiled statement with the content "SELECT*FROM Customer WHERE Name='{{Name}}';" in the template in advance, in which the placeholder "{{Name}} " is used to refer to specific customer name information, so that users only need to enter the required parameter "XiaoMing" to get the required SQL instructions after text rendering by the template engine.

On the other hand, in order to meet more diverse query needs, the query template in the embodiment of the present application may also include a general programming language that can be read and executed by the template engine (the programming language used may include C language, python, Assembly language, Java and other types, and there are differences according to the language libraries supported by different template engines. An introduction to the template engine will be given in detail below), which is used to inform the template engine how to combine the query template with the request parameters. Rendering is the template engine command above. In order to distinguish it from the query instructions in the template and avoid reading errors after importing the template engine, the template engine instructions can be distinguished by adding symbol qualifications in the form of "{% instruction content%}".

For example, in order to split the target data that several users want to query in a query request, you can use basic programming languages such as "{%for query object in query table%}" to execute loops. Each loop will follow the order. Extract one of the multiple request parameters of the query request and generate a query instruction with the query template to achieve the effect of "one query request corresponding to multiple query instructions" that cannot be achieved by a template that only contains precompiled query statements. In one embodiment, the specifically generated query template format is as follows:

{%for Name in NameList%}

#Execute the loop to tell the template engine how to extract the parameters for querying a single customer name (the address of a single data) from the name list (multiple request parameters) in the query request.

{"Name":"{{Name}}"};

#Specify the meaning of placeholders.

SELECT*FROM Customer WHERE Name＝'{{Name}}'

#Precompiled SQL statements.

{%if loop.last==false%}&{%endif%}

#When all request parameters are extracted, terminate the judgment.

{%endfor%}

#Jump out of the loop.

In addition, more complex query instruction text rendering effects can be achieved in templates through more complex instruction programming. When the query template required for this query has been edited in advance and retrieved when the user queries, the database query can be performed by processing the query template and request parameters into query instructions.

Before writing a query template, developers also need to configure the corresponding template engine for the data interface. As mentioned above, in the embodiment of the present application, the template engine is mainly used for text rendering of the query template to output specific query instructions that can query relevant data in the database. In general application scenarios, the essence of a template engine is a language processing tool produced to separate the user interface from business data. It can compare input parameters with text templates with some declaration, syntax or format restrictions. Splicing (during the splicing process, the placeholders declared in advance in the text template are replaced by parameters of the corresponding type), outputting a piece of text with a specific format. Currently, commonly used template engines on the market include Thymeleaf, Jap, etc., and the embodiment of this application selects one of the engines with relatively excellent performance: "JinJa2" for text rendering; this template engine is often used to render specific code segments in python programs. However, it also works stably when rendering code instructions written in other programming languages, and supports template engine instructions written in C language, Java and other programming languages. Therefore, JinJa2 can be applied in the process of query template generation instructions. However, since other template engines can also be used to achieve similar effects when performing text rendering on query templates, there is no restriction on the type of template engine here.

Once the template engine corresponding to the data interface is determined, the query template based on the relational database supported by the template engine can be configured according to the above method. In addition, when the data source corresponding to the query template is a non-relational database, the structured query language instructions obviously cannot query it. Therefore, developers need to reprogram the corresponding query template using the unstructured query language format.

Figure 5 is a query template configuration method based on a non-relational database. As a possible implementation, before step 102, steps 109 to 110 may be further performed.

Step 109: In response to the template engine setting operation for the query template, determine the template engine that needs to be used to render the query template based on the non-relational database.

Step 110: In response to the editing operation on the query template, generate the precompiled unstructured query language instruction, at least one placeholder, and a template engine instruction for describing a text rendering method of the unstructured query language instruction into a non-relational based Query template for type database.

In the embodiment of the present application, the query template based on the non-relational database also needs to be generated through the editing operation of the query template, but its database type is more complex than the relational database, and the gap between different databases is larger (such as MongoDB, Non-relational databases such as Cassandra, Redis, Neo4j, Amazon DynamoDB, Couchbase, HBase, and Riak have very different data storage structures and query methods, so the query templates need to be configured one by one. Specifically, because the data interface adapts to many types of data sources, the types of database drivers supported by different non-relational databases are also different, which leads to the format or format of the corresponding query instructions when the data source types for querying the target data are different. Code details also need to be adjusted accordingly. The following are different examples of several non-relational database query instructions:

(1) MongoDB query instructions and Couchbase query instructions

MongoDB's query language is based on JavaScript, and the commands used are find(), count(), distinct(), etc. The query syntax is relatively simple. The query language used by Couchbase is based on N1QL, which is also a SQL-like language that can implement various SQL operations, such as SELECT, JOIN, GROUP BY, etc., and has rich query functions and flexibility.

(2) Cassandra’s query instructions and ScyllaDB’s query instructions

Cassandra uses the CQL language for querying. CQL is somewhat similar to SQL syntax, but has some differences. For example, it does not support JOIN operations. ScyllaDB also uses the CQL language for querying, but it makes some improvements to CQL, supports more syntax, such as JOIN operations, and introduces index-like data structures to improve query efficiency.

(3) Amazon DynamoDB query instructions and Apache HBase query instructions

Amazon DynamoDB's query instructions use the API in the AWS SDK instead of separate query instructions. Developers can select the corresponding API for query operations as needed. Apache HBase's query instructions use HBaseAPI, and Hadoop's API can also be used to perform query operations, which can implement various operations of SQL-like statements.

Therefore, developers write a set of dedicated query templates for each type of database based on all non-relational database types that the data interface can support, which can adapt to users' needs for querying different non-relational databases.

Referring to Figure 6, based on the same inventive concept, an embodiment of the present application also provides a data interface configuration device. The device includes: a data source creation unit 201, a configuration unit 202, and a docking unit 203.

in:

The data source creation unit 201 is used to respond to the creation operation of the data interface and create a corresponding data source for the data interface;

The configuration unit 202 is configured to respond to the first configuration operation of the data interface and determine the database driver, database connection and query template corresponding to the data interface according to the first configuration operation. The query template is a precompiled data source that uses placeholders to replace request parameters. query instructions;

The configuration unit 202 is also configured to respond to the second configuration operation for the data interface, create unique interface information corresponding to the data interface according to the second configuration operation, and determine the mapping relationship between the unique interface information and the database driver, database connection, and query template. ;

The docking unit 203 is used to respond to the docking operation of the data interface and publish the data interface to the business system to provide data query.

Optionally, the device also includes:

The generation unit is used to respond to the pre-check configuration operation of the data interface, generate required parameter rules based on the pre-check configuration operation, and bind the required parameter rules to the data interface. The required parameter rules are used to check the user sent Whether the request parameters to the data interface contain all parameters that can query the target data.

Optionally, the device also includes:

The determination unit is used to respond to the template engine setting operation for the query template and determine the template engine that needs to be used to render the query template based on the relational database;

The generation unit is also configured to respond to an editing operation on the query template and generate the precompiled structured query language instruction, at least one placeholder, and a template engine instruction used to describe a text rendering method of the structured query language instruction into a relation-based Query template for type database.

Optionally, the determining unit is also used to: respond to the template engine setting operation for the query template, and determine the template engine that needs to be used to render the query template based on the non-relational database;

The generation unit is also configured to respond to the editing operation of the query template and generate the precompiled unstructured query language instruction, at least one placeholder, and a template engine instruction used to describe the text rendering method of the unstructured query language instruction into Query template based on non-relational database

Optionally, the docking unit 203 is also used to respond to the post-computing configuration operation of the data interface, and dock the post-processor to the data interface according to the post-computing configuration operation. The post-processor is used to use conventional operations according to the needs of the user. character to process the target data.

Please refer to Figure 7. Based on the same inventive concept, the embodiment of the present application also provides a data query method. The process of the method is as follows:

Step 301: Receive a query request sent by the business system. The query request includes unique interface information and request parameters of the target data to be queried.

Step 302: Query the query template corresponding to the unique interface information according to the preconfigured mapping relationship between the unique interface information and the query template. The query template is a precompiled data source query instruction that uses placeholders to replace request parameters.

Step 303: Import the request parameters and query template into the template engine and render them into data source query instructions.

Step 304: Query the target data from the data source according to the unique interface information and data source query instructions.

Step 305: Send target data to the business system.

In the embodiment of this application, the corresponding query template can be quickly found through the correspondence between the unique interface information and the query template pre-configured by the developer, and imported into the pre-specified template engine together with the request parameters input by the user to generate data The source query command is used together with the unique interface information to query the target data.

As a possible implementation, before step 302, steps 306 to

Step 306: Obtain preconfigured required parameter rules. The required parameter rules are used to check whether the request parameters contain all parameters necessary to locate the target data from the data source.

Step 307: Check the request parameters according to the required parameter rules.

Step 308: If the request parameter check fails, an error message is output. The error message is used to prompt the user that the filling in of the request parameters is illegal.

In the embodiment of this application, before querying the target data according to the query request input by the user, it is also necessary to use the pre-used required parameter rules to verify the query request. If the verification fails, the user is prompted to fill in the parameters in an incorrect type. Correct, needs to be rescreened and corrected.

As a possible implementation, step 305 can be specifically implemented through sub-steps 3051 to 3052.

Step 3051: According to the post-calculation rules, use the post-processor to calculate the target data and obtain the target data calculation result.

Step 3052: Send the target data calculation result to the business system.

In the embodiment of this application, when the business system sends the target data, it can also call the corresponding operator according to the post-calculation rules additionally filled in the user's query request, and then process the original target data twice to obtain the processing results required by the user. and pass the result back to the user.

In addition, in traditional database query technology, the database platform allocates an exclusive data interface for each connected business system. The disadvantage of this method is that it requires a lot of extra effort when sorting and deleting the data interface. Administrative costs. In the embodiment of this application, the interface for receiving the query request and sending the target data is the only external interface, and the way of distinguishing the query for different data is related to the unique interface information.

Specifically, the interface name determines the data interface provided to the business system, and its interface version number carries the connection details of the business system when accessing the data interface. This allows only one new configuration to be configured when data needs to be updated. The interface version number can be quickly updated without the need to build a new data interface and reconnect to the business system. For the detailed steps of establishing a connection between the business system and each database, after extracting the preconfigured content based on the unique interface information, it is handed over to the subsequent gateway and database connection pool for execution. Through this method, it can effectively reduce the development difficulty of the database platform while reducing the cost of data interface management.

It is worth noting that the data interface quickly developed through the data interface configuration method provided in the embodiment of this application has its operating logic and specific implementation effect when the user queries through the above data query method, as shown in Figure 8.

The above are only preferred embodiments of this specification and are not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification shall be included in this specification. within the scope of protection.

Claims (10)

1. A method for configuring a data interface, the method comprising:

responding to the creation operation of a data interface, and creating a corresponding data source for the data interface;

responding to a first configuration operation of the data interface, and determining a database driver, a database connection and a query template corresponding to the data interface according to the first configuration operation, wherein the query template is a pre-compiled data source query instruction using a placeholder to replace a request parameter;

responding to a second configuration operation of the data interface, creating unique interface information corresponding to the data interface according to the second configuration operation, and determining a mapping relation among the unique interface information, the database driver, the database connection and the query template;

And responding to the docking operation of the data interface, and issuing the data interface to a service system to provide data inquiry.

2. The method of claim 1, wherein in response to a docking operation for the data interface, prior to publishing the data interface to a business system to provide a data query, the method further comprises:

and responding to the pre-checking configuration operation of the data interface, generating a rule of necessary parameters according to the pre-checking configuration operation, and binding the rule of necessary parameters with the data interface, wherein the rule of necessary parameters is used for checking whether all parameters capable of inquiring target data are contained in request parameters sent to the data interface by a user.

3. The method of claim 1, wherein the data source is a relational database, and wherein the responding is responsive to a first configuration operation of the data interface, and wherein prior to determining the database driver, database connection, and query template corresponding to the data interface according to the first configuration operation, the method further comprises:

determining a template engine to be used for rendering the query template based on a relational database in response to a template engine setting operation for the query template;

In response to an editing operation on the query template, a precompiled structured query language instruction, at least one placeholder, and template engine instructions for describing a text rendering manner of the structured query language instruction are generated as the query template based on a relational database.

4. The method of claim 1, wherein the data source is a non-relational database, the responding is responsive to a first configuration operation of the data interface, and the method further comprises, prior to determining a database driver, a database connection, and a query template corresponding to the data interface according to the first configuration operation:

determining a template engine to be used for rendering the query template based on a non-relational database in response to a template engine setting operation for the query template;

in response to an editing operation on the query template, a precompiled unstructured query language instruction, at least one placeholder, and a template engine instruction for describing a text rendering manner of the unstructured query language instruction are generated as the query template based on a non-relational database.

5. The method of claim 2, wherein the responding to the binding operation for the data interface, prior to binding the data interface with the business system, further comprises:

And responding to the post-calculation configuration operation of the data interface, binding a post-processor to the data interface according to the post-calculation configuration operation, wherein the post-processor is used for processing the target data according to the requirement of a user by using a conventional operator.

6. A device for configuring a data interface, the device comprising:

a data source creation unit, configured to create a corresponding data source for a data interface in response to a creation operation for the data interface;

the configuration unit is used for responding to a first configuration operation of the data interface, determining a database driver, a database connection and a query template corresponding to the data interface according to the first configuration operation, wherein the query template is a pre-compiled data source query instruction using a placeholder to replace a request parameter;

the configuration unit is further used for responding to a second configuration operation of the data interface, creating unique interface information corresponding to the data interface according to the second configuration operation, and determining a mapping relation among the unique interface information, the database driver, the database connection and the query template;

And the binding unit is used for responding to the binding operation of the data interface and binding the data interface with the service system.

7. A method of querying data, the method comprising:

receiving a query request sent by a service system, wherein the query request comprises unique interface information of target data to be queried and request parameters;

inquiring the inquiry template corresponding to the unique interface information according to the mapping relation between the pre-configured unique interface information and the inquiry template, wherein the inquiry template is a pre-compiled data source inquiry instruction using a placeholder to replace a request parameter;

importing the request parameters and the query templates into a template engine, and rendering the request parameters and the query templates into data source query instructions;

inquiring the target data from a data source according to the unique interface information and the data source inquiry instruction;

and sending the target data to the service system.

8. The method according to claim 7, wherein before the query template corresponding to the unique interface information is queried according to the corresponding relationship between the pre-configured unique interface information and the query template, the method further comprises:

Acquiring a pre-configured rule of necessary parameters, wherein the rule of necessary parameters is used for checking whether all parameters necessary for locating the target data from the data source are contained in the request parameters;

checking the request parameters according to the rule of the necessary parameters;

if the request parameters are not checked, outputting error information, wherein the error information is used for prompting a user that filling of the request parameters is illegal.

9. The method of claim 7, wherein the query request further includes post-computation rules for processing the target data, the post-computation rules including one or more operators, the sending the target data to the business system comprising:

calculating the target data by using a post processor according to the post calculation rule to obtain a target data calculation result;

and sending the target data calculation result to the service system.

10. The method of claim 7, wherein the data interface receiving the query request and transmitting the target data is a unique external interface.