WO2018228034A1

WO2018228034A1 - Method and device for generating elastic search request

Info

Publication number: WO2018228034A1
Application number: PCT/CN2018/082283
Authority: WO
Inventors: 王英杰
Original assignee: 北京京东尚科信息技术有限公司; 北京京东世纪贸易有限公司
Priority date: 2017-06-15
Filing date: 2018-04-09
Publication date: 2018-12-20
Also published as: CN109145014A

Abstract

A method and device for generating an elastic search request. The method comprises: in response to detection of a data query request operation of elastic search, configuring parameters in a data query request by means of an object relation mapping framework to generate a structured query language statement (201); converting the structured query language statement into an executable file object according to a mapping relation between structured query language commands and executable file objects (202); replacing a syntax keyword in the executable file object with a syntax keyword in an elastic search syntax based on a preset conversion rule (203); and generating an elastic search request from the executable file object subjected to syntax keyword replacement (204). According to the method, the effectiveness of elastic search can be improved.

Description

Method and apparatus for generating an elastic search request

Cross-reference to related applications

This patent application claims to be submitted on June 15, 2017, the application number is 201710451970.7, the applicant is Beijing Jingdong Century Trading Co., Ltd. and Beijing Jingdong Shangke Information Technology Co., Ltd., and the invention is entitled "Method and Device for Generating Elastic Search Request" Priority of the Chinese Patent Application, the entire contents of which is hereby incorporated by reference.

Technical field

The present application relates to the field of computer technologies, and in particular, to the field of Internet technologies, and in particular, to a method and apparatus for generating an elastic search request.

Background technique

ElasticSearch, referred to as ES, is based on the full-text search engine Lucene, which provides a full-text search engine with distributed multi-user capabilities, which is designed for real-time search in the field of big data cloud computing. However, ES has its own specific grammar, and people who use it need to understand its grammatical structure to be able to control it. It is quite different from the SQL grammar of web developers who are more familiar with relational databases in data retrieval, which leads to increased learning costs for developers. Therefore, the existing ES is less effective.

Summary of the invention

The purpose of the present application is to propose an improved method and apparatus for generating an elastic search request to solve the technical problems mentioned in the background section above.

In a first aspect, an embodiment of the present application provides a method for generating an elastic search request, where the method includes: in response to detecting a data query request operation of an elastic search, configuring a parameter in a data query request by using an object relationship mapping framework to generate a structure. The query language statement; according to the mapping relationship between the structured query language command and the executable file object, converting the structured query language statement into an executable file object; replacing the syntax keyword in the executable file object according to a preset conversion rule The grammar keyword in the grammar is searched for; the executable file object after the grammar keyword is replaced to generate an elastic search request.

In some embodiments, the converting the structured query language statement into the executable file object according to the mapping relationship between the structured query language command and the executable file object includes: detecting a query condition in the data query request, wherein the query is The condition includes querying the keyword and the condition value; the query keyword and the condition value of the above query condition are respectively used as labels and attributes of the executable file object to convert the above structured query language statement into an executable file object.

In some embodiments, the query keyword and the condition value of the query condition are delivered in the form of a key-value pair, wherein the key-value pair key is a query keyword, and the value is a condition value corresponding to the query keyword.

In some embodiments, in response to detecting the data query request operation of the elastic search, configuring the parameter in the data query request by the object relationship mapping framework, generating the structured query language statement comprises: responding to the data query request detecting the elastic search The operation, according to the data query request operation, detects the query keyword of the data query request; when there are multiple query keywords, the query keywords are spliced by a preset syntax to generate a structured query language statement.

In some embodiments, the structured query language statement includes a search table name and a query keyword, wherein the search table name of the structured query language statement is consistent with the elastic search index name, and the query keyword of the structured query language statement is The query keywords of the Elastic Search Language statement are consistent.

In a second aspect, the present application further provides an apparatus for generating an elastic search request, the apparatus comprising: a statement generation module configured to configure a data query request through an object relationship mapping framework in response to detecting a data query request operation of the elastic search The parameter in the structure generates a structured query language statement; the conversion module is configured to convert the structured query language statement into an executable file object according to a mapping relationship between the structured query language command and the executable file object; replacing the module, configuring For replacing a grammar keyword in an executable file object with a grammar keyword in an elastic search grammar according to a preset conversion rule; a request generation module configured to generate an elastic search request for the executable file object after replacing the grammar keyword .

In some embodiments, the foregoing conversion module includes: a detecting unit configured to detect a query condition in the data query request, wherein the query condition includes a query keyword and a condition value; and a converting unit configured to use the query condition The query keyword and the condition value are respectively used as labels and attributes of the executable file object to convert the above structured query language statement into an executable file object.

In some embodiments, the statement generation module is further configured to: in response to detecting the data query request operation of the elastic search, detecting a query keyword of the data query request according to the data query request; when there are multiple query keywords The above query keywords are spliced by a preset grammar.

The method and apparatus for generating an elastic search request provided by the present application, in response to detecting a data query request operation of the elastic search, configuring parameters in the data query request through the object relationship mapping framework, generating a structured query language statement, and then according to the structured query The mapping relationship between the language command and the executable file object, converting the above structured query language statement into an executable file object, and then replacing the syntax key in the executable file object with the syntax in the elastic search syntax according to a preset conversion rule The keyword then generates an elastic search request by replacing the executable object with the grammar keyword. Since the elastic search request is generated by automatically performing grammar conversion on the basis of the existing file object, the effectiveness of the elastic search can be improved.

DRAWINGS

Other features, objects, and advantages of the present application will become more apparent from the detailed description of the accompanying drawings.

1 is an exemplary system architecture diagram to which the present application can be applied;

2 is a flow diagram of one embodiment of a method of generating an elastic search request in accordance with the present application;

3a and 3b are schematic diagrams of application scenarios of an embodiment of a method for generating an elastic search request according to the present application;

4 is a schematic structural diagram of an embodiment of an apparatus for generating an elastic search request according to the present application;

FIG. 5 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server of an embodiment of the present application.

detailed description

The present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention, rather than the invention. It is also to be noted that, for the convenience of description, only the parts related to the related invention are shown in the drawings.

It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. The present application will be described in detail below with reference to the accompanying drawings.

FIG. 1 illustrates an exemplary system architecture 100 of an embodiment of a method of generating an elastic search request to which the present application may be applied.

As shown in FIG. 1, system architecture 100 can include

terminal devices

101, 102, network 103, and server 104. The network 103 is used to provide a medium for communication links between the

terminal devices

101, 102 and the server 104. Network 103 may include various types of connections, such as wired, wireless communication links, fiber optic cables, and the like.

The user can interact with the server 104 over the network 103 using the

terminal devices

101, 102 to receive or transmit messages and the like. Various communication client applications, such as a browser application, a shopping application, a search application, an instant communication tool, and the like, can be installed on the

terminal devices

101 and 102.

The

terminal devices

101, 102 may be various electronic devices having communication functions including, but not limited to, smartphones, tablets, e-book readers, laptop portable computers, desktop computers, and the like.

The server 104 may be a server that provides various services, such as a background server that supports browser applications on the

terminal devices

101, 102, shopping applications, and the like. The server 104 may analyze the received data such as the query or the unlock request, and the like, and feed back the processing result (for example, the queried item payment status information) to the

terminal devices

101 and 102.

Generally, the method for generating an elastic search request provided by the embodiment of the present application is applicable to the

terminal devices

101 and 102. Accordingly, the device for generating an elastic search request provided by the embodiment of the present application is disposed in the

terminal devices

101 and 102. The server 104 can provide elastic search support, and the

terminal devices

101, 102 can receive the user's search request operation and generate an elastic search request to the server 104 to retrieve data from the server 104.

It should be understood that the number of terminal devices, networks, and servers in Figure 1 is merely illustrative. Depending on the implementation needs, there can be any number of terminal devices, networks, and servers.

With continued reference to FIG. 2, FIG. 2 illustrates one embodiment of a method of generating an elastic search request of the present application. The method for generating an elastic search request includes the following steps:

Step 201: In response to detecting the data query request operation of the elastic search, configuring the parameter in the data query request by the object relationship mapping framework to generate a structured query language statement.

In this embodiment, the electronic device (for example, the

terminal device

101, 102 shown in FIG. 1) on which the method for generating the elastic search request is run may detect the data query request operation of the user, and when detecting the elastic search server When performing a data query request operation for data query, the parameters in the data query request may be first configured by an object relational mapping (such as Object Relational Mapping, ORM) framework to generate a structured query language statement.

Generally, a user can input or select a keyword through a browser page to perform a data query request operation. These keywords can often generate query statements through object mapping. For example, when the browser page displays the order inquiry page, the user selects the start time as January 01, 2017, and the electronic device can generate a query according to the query condition.

In practice, the electronic device may first determine that the query scope is an order table (eg, the keyword is t_order), and then determine that the query keyword includes an order time (eg, the keyword is created).

The query condition is the order time after January 01, 2017 (eg created> '2017-01-01'). Taking SQL (Structured Query Language) as an example, the query keyword and query condition can be generated as: "select*from t_order where created>'2017-01-01')".

It will be appreciated that in some implementations, there may be multiple query keywords. For example, when the browser page displays the order inquiry page, the user selects the start time as January 01, 2017, and selects the restriction condition to pay successfully. At this time, in response to detecting the data query request operation of the elastic search, the electronic device may first detect the query keyword of the data query request according to the data query request, and when there are multiple query keywords, the preset syntax is The query keyword is spliced. The predetermined syntax here may be, for example, the conjunctions "and", "or", "not", and the like. The electronic device may first determine that the query scope is an order table (for example, the keyword is t_order), and then determine that the query keyword includes an order time (such as a keyword created) and a payment status (such as a keyword status), and the query condition is an order. The time is after January 01, 2017 (eg created> '2017-01-01') and the payment status is successful (eg status=1). Taking SQL (Structured Query Language) as an example, the query keyword and query condition can be generated as follows: "select*from t_order where created>'2017-01-01'and status=1)".

In this embodiment, the electronic device may pre-store an Object Relational Mapping (ORM) framework for managing a mapping relationship between a relational database operation statement (such as a SQL query statement) and a Java object, and the java program is used. The executable object in the map is mapped to a relational database. The above electronic device may configure the parameter in the data query request as a structured query language statement according to the object relationship mapping framework. For example, in the foregoing example, the electronic device uses the injection tool of the relational database (such as sqlMap in the SQL database) to configure parameters as:

<select id (select SQL database) = "get Order By Condition", parameterClass (parameter type) = "java.util.HashMap", resultClass (result type) = "java.util.HashMap"> ;

The structured query language statement after the configuration parameters can be as follows: select*from t_order where created>'2017-01-01'and status=1</select>;

Among them, select id, select is semi-automatic ORM framework ibatis ORM framework selection syntax, id is the unique identifier of the SQL database (such as database name t_order, etc.), parameterClass is the dynamic parameter in the SQL query statement, resultClass is the SQL query statement The return value, parameterClass and resultClass are the fixed attributes of the object tag.

In some optional implementations of this embodiment, the structured query language statement includes a search table name and a query keyword, wherein the search table name of the structured query language statement is consistent with the elastic search index name, and the query of the structured query language statement The keyword matches the query keyword of the Elastic Search Language statement. In order to ensure that the elastic search request is generated, it is not necessary to convert the retrieval table name and the query keyword, thereby improving the retrieval efficiency.

Step 202: Convert the structured query language statement into an executable file object according to a mapping relationship between the structured query language command and the executable file object.

In this embodiment, the electronic device (for example, the

terminal device

101, 102 shown in FIG. 1) on which the method for generating the elastic search request is run may further according to the mapping relationship between the structured query language command and the executable file object. The commands and parameters in a structured query language statement are converted into tags or attributes of executable file objects such as Java objects.

Specifically, the electronic device may first map the structured query language statement to an execution client object of the executable file, such as an sqlMapClient object, where the electronic device may use a command in the structured query language statement. As an object tag, such as the command select as a select tag; then, through the executable client object of the executable file, the electronic device can obtain the attribute of the object tag, such as the id attribute of the selecet tag, and the attribute value can be the SQL database to be queried. And the electronic device may convert the structured query language statement corresponding to the attribute of the object tag to a mapping declaration object (such as a MappedStatement object).

In some optional implementation manners of the embodiment, the electronic device may further detect a query condition in the data query request, where the query condition may include a query keyword and a condition value. Then, the electronic device may respectively use the query keyword and the condition value in the query conditions as labels and attributes of the executable file object to convert the structured query language statement into an executable file object. Optionally, for the query condition of the structured query language statement, the electronic device may save the key-value in the form of a key-value by using a mapping object, where the key-value pair key may be The query keyword, the value (value) can be the condition value corresponding to the query keyword. For example, for the query condition "payment status is payment success (such as status=1)", when stored in the form of a key-value pair, the "key" can be the payment status (or status, etc.) of the query keyword, and the "value" can be the condition value. The payment was successful (or a value of 1, etc.).

Through this step, the electronic device can complete the acquisition of the structured query language statement by the executable file.

Step 203: Replace the syntax key in the executable file object with the syntax key in the flexible search syntax based on the preset conversion rule.

In this embodiment, the electronic device (for example, the

terminal device

101, 102 shown in FIG. 1) on which the method for generating the elastic search request is run may further store a preset conversion rule in advance, further in the executable file object. The grammar keyword is replaced with a grammar keyword in the elastic search grammar.

Here, the preset conversion rule may include, but is not limited to, a correspondence relationship between a grammar keyword in the structured query language and a grammar keyword in the elastic search grammar. The grammar keyword may include a command keyword (such as a command keyword select of a selection command), a connection keyword (such as a connection keyword indicating a connection relationship "and", and the like). For example, the syntax keywords "select, where, and, or" in SQL correspond to the grammar keywords "query, bool, must, match" in the elastic search grammar, and so on.

For example, if the SQL statement is converted into a JSON (JavaScript Object Notation) string by a Java object, the above electronic device can parse the SQL statement into a java object "QueryAction"; and then use the "QueryAction" method to convert the SQL statement to satisfy the ES syntax. Json string.

Step 204: Generate an elastic search request by replacing the executable file object after the grammar keyword.

In this embodiment, the electronic device (for example, the

terminal device

101, 102 shown in FIG. 1) on which the method for generating the elastic search request is run may further generate an elastic search request by the executable file object after replacing the grammar keyword. For example, the foregoing electronic device may first create an ES client object (such as HttpClient), and then generate an ES request according to a URL (Uniform Resource Locator) of the ES server. The generated ES request may be sent to the ES server through a transmission protocol such as TCP (Transmission Control Protocol) or HTTP (HyperText Transfer Protocol).

As an application scenario, the method for generating an elastic search request in this embodiment may be applied to, for example, a shopping application client. The backend server that provides support for the shopping application client can be an ES server. The shopping application client and the ES server can communicate through a transmission protocol such as TCP or HTTP. As shown in FIG. 3a, the shopping application client runs on the terminal 300, and selects the "My Order" option in the pop-up option of the pull-up option box of the tag 301, the shopping application client. The end switch displays the order inquiry page shown in Figure 3b. The order inquiry page shown in Figure 3b shows the partial query keywords "all", "order time", etc. of the order inquiry. Assume that the user selects the query keyword "order time" and selects the order time limit in the drop-down menu 302 given to perform the order inquiry. After detecting the query operation performed by the user through the terminal 300, the terminal 300 may first configure a parameter in the data query request through an object relationship mapping framework (such as an ORM framework) to generate a structured query language (such as SQL) statement; then, the terminal 300 may The structured query language statement is converted into an executable file object (such as a Json string) according to a mapping relationship between a structured query language (such as SQL) command and an executable file object (such as a Java object); then, the terminal 300 can be based on a preset The conversion rule replaces the syntax key in the executable file object with the syntax key in the elastic search syntax; then, the terminal 300 may generate an ES request by the executable file object after the replacement syntax keyword, and send the ES request to The ES server performs data query. After receiving the order information fed back by the ES server, the terminal device can further display through the page of the shopping application running on the terminal device.

The method for generating an elastic search request in this embodiment can improve the effectiveness of the elastic search by automatically generating a flexible search request by performing an automatic conversion of the executable file object based on the prior art.

With further reference to FIG. 4, as an implementation of the method for generating an elastic search request corresponding to the embodiment shown in FIG. 2, the present application provides an embodiment of an apparatus for generating an elastic search request.

As shown in FIG. 4, the apparatus 400 for generating an elastic search request of the present embodiment includes: a statement generation module 401, a conversion module 402, a replacement module 403, and a request generation module 404. The statement generation module 401 can be configured to generate a structured query language statement by configuring a parameter in the data query request by the object relationship mapping framework in response to detecting the data query request operation of the elastic search; the conversion module 402 can be configured to be configured according to The structured query language command is converted into an executable file object by a mapping relationship between the structured query language command and the executable file object; the replacement module 403 can be configured to use the syntax key in the executable file object according to the preset conversion rule. Replaced with a grammar keyword in the elastic search grammar; the request generation module 404 can be configured to generate an elastic search request for the executable file object after the replacement grammar keyword.

In some optional implementation manners of the embodiment, the converting module 402 may further include: a detecting unit (not shown), configured to detect a query condition in the data query request, where the query condition includes a query keyword And a condition value; a conversion unit (not shown), configured to use the query keyword and the condition value of the above query condition as labels and attributes of the executable file object, respectively, to convert the structured query language statement into an executable file File object. In some implementations, the query keyword and the condition value of the query condition are delivered in the form of a key-value pair, wherein the key-value pair key is a query keyword, and the value is a condition value corresponding to the query keyword.

In some optional implementation manners of the embodiment, the statement generating module 401 may be further configured to: in response to detecting the data query request operation of the elastic search, detecting a query keyword of the data query request according to the data query request operation; When there are multiple query keywords, the above query keywords are spliced by a preset grammar.

In some optional implementation manners of the embodiment, the structured query language statement generated by the statement generation module 401 may include a retrieval table name and a query keyword, wherein the retrieval table name is consistent with the elastic search index name, and the structured query language statement is The query keyword is consistent with the query keyword of the Elastic Search Language statement.

Those skilled in the art will appreciate that the apparatus 400 for generating an elastic search request further includes some other well-known structures, such as a processor, a memory, etc., in order to unnecessarily obscure the embodiments of the present disclosure, these well-known structures are not shown in FIG. Out.

Referring now to Figure 5, there is shown a block diagram of a computer system 500 suitable for use in implementing a terminal device/server of an embodiment of the present application. The terminal device/server shown in FIG. 5 is merely an example, and should not impose any limitation on the function and scope of use of the embodiments of the present application.

As shown in FIG. 5, computer system 500 includes a central processing unit (CPU) 501 that can be loaded into a program in random access memory (RAM) 503 according to a program stored in read only memory (ROM) 502 or from storage portion 508. And perform various appropriate actions and processes. In the RAM 503, various programs and data required for the operation of the system 500 are also stored. The CPU 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504. An input/output (I/O) interface 505 is also coupled to bus 504.

The following components are connected to the I/O interface 505: an input portion 506 including a keyboard, a touch screen, a microphone or a scanner, etc.; an output portion 507 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc.; storage including a hard disk or the like Portion 508; and a communication portion 509 including a network interface card such as a LAN card, modem, or the like. The communication section 509 performs communication processing via a network such as the Internet. Driver 510 is also coupled to I/O interface 505 as needed. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory or the like is mounted on the drive 510 as needed so that a computer program read therefrom is installed into the storage portion 508 as needed.

In particular, the processes described above with reference to the flowcharts may be implemented as a computer software program in accordance with an embodiment of the present disclosure. For example, an embodiment of the present disclosure includes a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for executing the method illustrated in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network via the communication portion 509, and/or installed from the removable medium 511. When the computer program is executed by the central processing unit (CPU) 501, the above-described functions defined in the method of the present application are performed. It should be noted that the non-transitory computer readable medium described herein may be a non-transitory computer readable signal medium or a non-transitory computer readable storage medium or any combination of the two. The non-transitory computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of non-transitory computer readable storage media may include, but are not limited to, electrical connections having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read only memory (ROM), Erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the foregoing. In the present application, a non-transitory computer readable storage medium can be any tangible medium that can contain or store a program, which can be used by or in connection with an instruction execution system, apparatus, or device. In the present application, a computer readable signal medium may include a data signal that is propagated in the baseband or as part of a carrier, carrying computer readable program code. Such propagated data signals can take a variety of forms including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the foregoing. The computer readable signal medium can also be any computer readable medium other than a computer readable storage medium, which can transmit, propagate, or transport a program for use by or in connection with the instruction execution system, apparatus, or device. . Program code embodied on a computer readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality and operation of possible implementations of systems, methods and computer program products in accordance with various embodiments of the present application. In this regard, each block of the flowchart or block diagram can represent a module, a program segment, or a portion of code that includes one or more of the logic functions for implementing the specified. Executable instructions. It should also be noted that in some alternative implementations, the functions noted in the blocks may also occur in a different order than that illustrated in the drawings. For example, two successively represented blocks may in fact be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts, can be implemented in a dedicated hardware-based system that performs the specified function or operation. Or it can be implemented by a combination of dedicated hardware and computer instructions.

The modules involved in the embodiments of the present application may be implemented by software or by hardware. The described modules may also be provided in the processor, for example, as a processor including a statement generation module, a conversion module, a replacement module, and a request generation module. The names of these modules do not constitute a limitation on the unit itself under certain circumstances. For example, the statement generation module may also be described as "configured to respond to data query request operations that detect elastic search, through object relationships. The mapping framework configures the parameters in the data query request to generate a module for the structured query language statement.

The above description is only a preferred embodiment of the present application and a description of the principles of the applied technology. It should be understood by those skilled in the art that the scope of the invention referred to in the present application is not limited to the specific combination of the above technical features, and should also be covered by the above technical features or without departing from the above inventive concept. Other technical solutions formed by arbitrarily combining the equivalent features. For example, the above features are combined with the technical features disclosed in the present application, but are not limited to the technical features having similar functions.

Claims

A method for generating an elastic search request, the method comprising:

In response to detecting the data query request operation of the elastic search, configuring the parameter in the data query request through the object relationship mapping framework to generate a structured query language statement;

Converting the structured query language statement into an executable file object according to a mapping relationship between the structured query language command and the executable file object;

Replace the grammar keyword in the executable file object with the grammar keyword in the elastic search grammar according to the default conversion rule;

An elastic search request is generated from the executable object after replacing the grammar keyword.
The method according to claim 1, wherein the converting the structured query language statement into an executable file object according to a mapping relationship between the structured query language command and the executable file object comprises:

Detecting a query condition in the data query request, wherein the query condition includes a query keyword and a condition value;

The query key and the condition value of the query condition are respectively used as tags and attributes of the executable file object to convert the structured query language statement into an executable file object.
The method according to claim 2, wherein the query keyword and the condition value of the query condition are transmitted in the form of a key value pair, wherein the key value centering key is a query key, and the value is a query key The condition value corresponding to the word.
The method according to claim 1, wherein in response to detecting the data query request operation of the elastic search, configuring the parameter in the data query request by the object relationship mapping framework, and generating the structured query language statement comprises:

Responsive to detecting a data query request operation of the elastic search, detecting a query keyword of the data query request according to the data query request operation;

When there are multiple query keywords, the query keywords are spliced by a preset grammar to generate a structured query language statement.
The method of claim 1, wherein the structured query language statement comprises a retrieval table name and a query key, wherein the retrieval table name of the structured query language statement is consistent with an elastic search index name, The query keyword of the structured query language statement is consistent with the query keyword of the elastic search language statement.
An apparatus for generating an elastic search request, the apparatus comprising:

a statement generation module configured to, in response to detecting a data query request operation of the elastic search, configuring a parameter in the data query request through the object relationship mapping framework to generate a structured query language statement;

a conversion module configured to convert the structured query language statement into an executable file object according to a mapping relationship between the structured query language command and the executable file object;

a replacement module configured to replace a syntax keyword in an executable file object with a syntax keyword in an elastic search syntax according to a preset conversion rule;

The request generation module is configured to generate an elastic search request for the executable file object after replacing the syntax keyword.
The apparatus according to claim 6, wherein the conversion module comprises:

a detecting unit, configured to detect a query condition in the data query request, where the query condition includes a query keyword and a condition value;

And a conversion unit configured to use the query keyword and the condition value of the query condition as labels and attributes of the executable file object, respectively, to convert the structured query language statement into an executable file object.
The apparatus according to claim 7, wherein the query keyword and the condition value of the query condition are transmitted in the form of a key value pair, wherein the key value centering key is a query key, and the value is a query key. The condition value corresponding to the word.
The apparatus according to claim 6, wherein the statement generation module is further configured to:

Responsive to detecting a data query request operation of the elastic search, detecting a query keyword of the data query request according to the data query request operation;

When there are multiple query keywords, the query keywords are spliced by a preset grammar.
The apparatus according to claim 6, wherein the structured query language statement comprises a retrieval table name and a query key, wherein the retrieval table name of the structured query language statement is consistent with the elastic search index name, The query keyword of the structured query language statement is consistent with the query keyword of the elastic search language statement.
A computing device comprising:

One or more processors;

a storage device for storing one or more programs;

The one or more programs are executed by the one or more processors such that the one or more processors implement the method of any of claims 1-5.
A non-transitory computer readable storage medium having stored thereon a computer program, characterized in that the program, when executed by a processor, implements the method of any of claims 1-5.