WO2018228034A1 - Procédé et dispositif de génération d'une demande de recherche élastique - Google Patents

Procédé et dispositif de génération d'une demande de recherche élastique Download PDF

Info

Publication number
WO2018228034A1
WO2018228034A1 PCT/CN2018/082283 CN2018082283W WO2018228034A1 WO 2018228034 A1 WO2018228034 A1 WO 2018228034A1 CN 2018082283 W CN2018082283 W CN 2018082283W WO 2018228034 A1 WO2018228034 A1 WO 2018228034A1
Authority
WO
WIPO (PCT)
Prior art keywords
query
keyword
elastic search
request
executable file
Prior art date
Application number
PCT/CN2018/082283
Other languages
English (en)
Chinese (zh)
Inventor
王英杰
Original Assignee
北京京东尚科信息技术有限公司
北京京东世纪贸易有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京京东尚科信息技术有限公司, 北京京东世纪贸易有限公司 filed Critical 北京京东尚科信息技术有限公司
Publication of WO2018228034A1 publication Critical patent/WO2018228034A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2452—Query translation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2453—Query optimisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0623—Item investigation

Definitions

  • 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.
  • ElasticSearch 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • configuring the parameter in the data query request by the object relationship mapping framework 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.
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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 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.
  • 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.
  • FIG. 1 is an exemplary system architecture diagram to which the present application can be applied;
  • FIG. 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
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • object relational mapping such as Object Relational Mapping, ORM
  • 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.
  • 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 scope is an order table (eg, the keyword is t_order)
  • 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').
  • SQL Structured Query Language
  • the query keyword and query condition can be generated as: "select*from t_order where created>'2017-01-01')".
  • 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 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.
  • ORM Object Relational Mapping
  • 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.
  • the electronic device uses the injection tool of the relational database (such as sqlMap in the SQL database) to configure parameters as:
  • select id 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.
  • 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.
  • 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.
  • 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.
  • an object tag such as the command select as a select tag
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.).
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • JSON JavaScript Object Notation
  • Step 204 Generate an elastic search request by replacing the executable file object after the grammar keyword.
  • 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.
  • 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).
  • 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.
  • TCP or HTTP a transmission protocol
  • 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.
  • 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 object
  • 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.
  • the present application provides an embodiment of an apparatus for generating an elastic search request.
  • 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.
  • the request generation module 404 can be configured to generate an elastic search request for the executable file object after the replacement grammar keyword.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 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.
  • 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.
  • RAM random access memory
  • ROM read only memory
  • 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.
  • 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.
  • the computer program can be downloaded and installed from the network via the communication portion 509, and/or installed from the removable medium 511.
  • CPU central processing unit
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 can 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Computational Linguistics (AREA)
  • Databases & Information Systems (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne un procédé et un dispositif de génération d'une demande de recherche élastique. Le procédé comporte les étapes consistant: en réaction à la détection d'une opération de demande d'interrogation de données de recherche élastique, à configurer des paramètres dans une demande d'interrogation de données au moyen d'un environnement-cadre de mappage de relations d'objets pour générer une instruction de langage d'interrogation structuré (201); à convertir l'instruction de langage d'interrogation structuré en un objet de fichier exécutable selon une relation de mappage entre des commandes de langage d'interrogation structuré et des objets de fichiers exécutables (202); à remplacer un mot-clé de syntaxe dans l'objet de fichier exécutable par un mot-clé de syntaxe dans une syntaxe de recherche élastique sur la base d'une règle de conversion prédéfinie (203); et à générer une demande de recherche élastique à partir de l'objet de fichier exécutable soumis au remplacement de mot-clé de syntaxe (204). Selon le procédé, l'efficacité d'une recherche élastique peut être améliorée.
PCT/CN2018/082283 2017-06-15 2018-04-09 Procédé et dispositif de génération d'une demande de recherche élastique WO2018228034A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710451970.7 2017-06-15
CN201710451970.7A CN109145014A (zh) 2017-06-15 2017-06-15 生成弹性搜索请求的方法和装置

Publications (1)

Publication Number Publication Date
WO2018228034A1 true WO2018228034A1 (fr) 2018-12-20

Family

ID=64659423

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/082283 WO2018228034A1 (fr) 2017-06-15 2018-04-09 Procédé et dispositif de génération d'une demande de recherche élastique

Country Status (2)

Country Link
CN (1) CN109145014A (fr)
WO (1) WO2018228034A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112988132A (zh) * 2021-02-25 2021-06-18 平安科技（深圳）有限公司 数据接口的自动生成方法、装置、计算机设备及存储介质

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110888876A (zh) * 2019-10-31 2020-03-17 平安科技（深圳）有限公司 生成数据库脚本的方法、装置、存储介质及计算机设备
CN111026931A (zh) * 2019-12-09 2020-04-17 中国建设银行股份有限公司 一种数据查询方法、装置、设备及介质
CN111460241B (zh) * 2020-04-26 2024-01-23 甬矽电子(宁波)股份有限公司 一种数据查询方法、装置、电子设备及存储介质
CN111522840B (zh) * 2020-04-27 2023-08-11 平安科技（深圳）有限公司 标签的配置方法、装置、设备及计算机可读存储介质
CN112765200A (zh) * 2021-01-18 2021-05-07 武汉悦学帮网络技术有限公司 一种基于Elasticsearch的数据查询方法及装置
CN113111356A (zh) * 2021-03-09 2021-07-13 深圳市教育信息技术中心(深圳市教育装备中心) 数据加密方法、装置、设备和介质
CN114168565B (zh) * 2021-12-10 2022-07-08 北京宇信科技集团股份有限公司 业务规则模型的回溯测试方法、装置、系统及决策引擎

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103399887A (zh) * 2013-07-19 2013-11-20 蓝盾信息安全技术股份有限公司 一种海量日志的查询与统计分析系统
CN105224633A (zh) * 2015-09-24 2016-01-06 北京锐安科技有限公司 基于SQL语言的solr查询方法及装置
CN106528797A (zh) * 2016-11-10 2017-03-22 上海轻维软件有限公司 基于Elasticsearch的DSL查询方法
CN106649630A (zh) * 2016-12-07 2017-05-10 乐视控股（北京）有限公司 数据查询方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102004634A (zh) * 2009-09-01 2011-04-06 上海杉达学院 分层的业务管理系统
CN102932474B (zh) * 2012-11-14 2015-06-17 北京星网锐捷网络技术有限公司 报文解析方法、设备及系统
CN104317964A (zh) * 2014-11-14 2015-01-28 中国建设银行股份有限公司 一种基于iBatis的对象关系映射方法及系统
CN104881490B (zh) * 2015-06-10 2019-11-22 中科宇图天下科技有限公司 一种web表单数据存取方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103399887A (zh) * 2013-07-19 2013-11-20 蓝盾信息安全技术股份有限公司 一种海量日志的查询与统计分析系统
CN105224633A (zh) * 2015-09-24 2016-01-06 北京锐安科技有限公司 基于SQL语言的solr查询方法及装置
CN106528797A (zh) * 2016-11-10 2017-03-22 上海轻维软件有限公司 基于Elasticsearch的DSL查询方法
CN106649630A (zh) * 2016-12-07 2017-05-10 乐视控股（北京）有限公司 数据查询方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112988132A (zh) * 2021-02-25 2021-06-18 平安科技（深圳）有限公司 数据接口的自动生成方法、装置、计算机设备及存储介质
CN112988132B (zh) * 2021-02-25 2021-12-21 平安科技（深圳）有限公司 数据接口的自动生成方法、装置、计算机设备及存储介质

Also Published As

Publication number Publication date
CN109145014A (zh) 2019-01-04

Similar Documents

Publication Publication Date Title
WO2018228034A1 (fr) Procédé et dispositif de génération d'une demande de recherche élastique
CN110019350B (zh) 基于配置信息的数据查询方法和装置
JP7146963B2 (ja) アプレットの実行方法、装置、電子機器及び記憶媒体
US10318595B2 (en) Analytics based on pipes programming model
US9940396B1 (en) Mining potential user actions from a web page
US11561972B2 (en) Query conversion for querying disparate data sources
US9600567B2 (en) Local context search results improvements
TWI526028B (zh) A way to implement network access and a web server
US11223686B2 (en) Transport channel via web socket for OData
JP2009530738A (ja) サービスシーケンス内の変換のための宣言
US20200278969A1 (en) Unified metrics computation platform
CN110109983B (zh) 一种操作Redis数据库的方法和装置
CN108959294B (zh) 一种访问搜索引擎的方法和装置
CN110806967A (zh) 一种单元测试方法和装置
US10599728B1 (en) Metadata agent for query management
CN113515285A (zh) 生成实时计算逻辑数据的方法和装置
Li et al. A fast big data collection system using MapReduce framework
CN113779018A (zh) 一种数据处理方法和装置
US20120030273A1 (en) Saving multiple data items using partial-order planning
US11038765B2 (en) Cloud software defined networking application programming interface converter
CN114268558B (zh) 监控图的生成方法、装置、设备、介质
US20210342400A1 (en) Information search method and apparatus
US10496455B1 (en) Enabling synchronous editable signals in process modeling
CN112181937B (zh) 一种结转数据的方法和装置
CN110807089B (zh) 一种问答方法、装置及电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18818216

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC , EPO FORM 1205A DATED 20.03.2020.

122 Ep: pct application non-entry in european phase

Ref document number: 18818216

Country of ref document: EP

Kind code of ref document: A1