API-based query system and method

Abstract

The invention discloses an API-based query method, and the method comprises the steps: accessing a query statement input by a user through a receiving module in a database interface mode, and sendingthe query statement input by the user to a control module; analyzing a query statement input by a user through a control module, compiling and customizing a corresponding execution plan, receiving thequery statement input by the user through a compiling process, analyzing a JS code, and generating a final ES query statement after compiling; and calling an actuator according to the final ES querystatement through an execution process to obtain a return result. According to the method, interface iteration zero development is realized, and the development speed is greatly increased; interface projects only need to be installed and deployed for the first time, and later project iteration does not need to be published again; QDL is replaced with DQL query to complete ES query; the interface configuration and the smoking test are integrated, so that the interface test time is reduced; the interface smoking test can be published only after passing, so that the interface correctness is improved; interfaces are managed in a centralized manner and are convenient to search and use; and the unified interface can return to the JSON format conveniently.

Description

technical field [0001] The present disclosure relates to the technical field of big data, in particular to an API-based query system and method. Background technique [0002] Currently, there are two common ways to query elasticsearch: [0003] One is to directly write QDL query statements; [0004] The second is to use the client tools provided by elasticsearch to generate QDL query statements by writing code; [0005] When providing a large number of external API interfaces or interface changes, there are several big problems in using the above two methods: [0006] 1. Code development needs to be carried out through programming languages, and related queries are scattered among various modules, which is not convenient for unified maintenance, and will be released and launched frequently; [0007] 2. When there is a problem, it cannot be updated in time, and the request parameters of the interface, the returned result, or the processing logic change cannot be updated in...

AI Technical Summary

Problems solved by technology

[0006] 1. Code development needs to be carried out through programming languages, and related queries are scattered among various modules, which is not convenient for unified maintenance, and will be released and launched frequently;

[0007] 2. When there is a problem, it cannot be updated in time, and the request parameters of the interface, the returned result, or the processing logic change cannot be updated in time;

[0008] 3. It is impossible to dynamically add new query services;

[0009] 4. When the same query interface has a small part of the new business requirements, it cannot be compatible. It is necessary to re-modify the original interface or add a new interface

[0010] In actual work, a department is responsible for the query of elasticsearch. APIs are provided according to business needs. It is not obvious to use the above methods in a timely manner for business needs. However, when dealing with the needs of multiple business development lines, the above two The problem is particularly difficult to solve, taking up a lot of manpower and time

Images