Dynamic Configuration Method for Return Content of Document Database and Related Devices

Abstract

The present application discloses a method for dynamically configuring the returned content of a document-based database and related devices. The method includes an application program dynamically reading a content configuration file during program operation, wherein each of the content configuration files has a unique identifier, and the content configuration file is used to describe and constrain target fields; after translating the content configuration file, converting it into the query language of the corresponding document-based database; and performing a query operation in the document-based database according to the query language. The present application solves the technical problem that the application program needs to be frequently iterated for different business scenarios. Through the present application, by configuring a translation and conversion module, the configuration content is dynamically parsed during program execution and translated into the target database query language.

Description

Technical Field

[0001] This application relates to the field of computer software, and more particularly, to a method for dynamically configuring the returned content of a document-based database and related devices. Background Art

[0002] Usually, when using a document-based database, the data content stored in a single document is relatively large and complex. In actual use, an application only needs some of the data. When filtering the content of a single document, it is usually written in the application in the form of hard coding.

[0003] Due to the existence of a large number of document filtering codes in the application, and these codes cannot be adjusted after the application is released. For frequently changing business scenarios, it is necessary to frequently iterate the version of the application.

[0004] In view of the problem that the application needs to be frequently iterated for different business scenarios in the related art, no effective solution has been proposed yet. Summary of the Invention

[0005] The main purpose of this application is to provide a method for dynamically configuring the returned content of a document-based database and related devices to solve the problem that the application needs to be frequently iterated for different business scenarios.

[0006] To achieve the above object, according to one aspect of this application, a method for dynamically configuring the returned content of a document-based database is provided.

[0007] The method for dynamically configuring the returned content of a document-based database according to this application includes: the application dynamically reads a content configuration file during program operation, where each content configuration file has a unique identifier, and the content configuration file is used to describe and constrain target fields; after translating the content configuration file, it is converted into the query language corresponding to the document-based database; according to the query language, a query operation is performed in the document-based database.

[0008] Further, the application dynamically reads the content configuration file during program operation, including: the application reads and / or modifies the content configuration file through the unique identifier.

[0009] Further, the step of translating the content configuration file and converting it into the query language corresponding to the document-based database includes: after translating the pre-unified content configuration file, it is converted into the query language corresponding to the software of different databases.

[0010] Further, the application program dynamically reads a content configuration file during program operation. Each content configuration file has a unique identifier. The content configuration file is used to describe and constrain target fields, including: if the data required during program operation is an object type field, the first preset value in JSON Schema is set to constrain the data attribute set; after translating the content configuration file, it is converted into the query language of the corresponding document database, including: if the object type field of the data contains M attributes and N attribute fields are to be returned, the JSON Schema is set to the first preset statement and the content configuration file is translated to obtain the first preset query statement of elastic search, where M > N, and M and N are integers.

[0011] Further, the application program dynamically reads a content configuration file during program operation. Each content configuration file has a unique identifier. The content configuration file is used to describe and constrain target fields, including: if the data required during program operation is an array type field, the second preset value in JSON Schema is set to constrain the data quantity; after translating the content configuration file, it is converted into the query language of the corresponding document database, including: if the array type field of the data contains L data and O data are to be returned, the JSON Schema is set to the second preset statement and the content configuration file is translated to obtain the second preset query statement of elasticsearch, where L > O, and L and O are integers.

[0012] Further, if the data required during program operation is an object type field, the first preset value in JSON Schema is set to constrain the data attribute set, and it further includes: if the data object type field required during program operation is nested in multiple application layer objects, the preset format of JSON Schema is set to constrain each layer; after translating the content configuration file, it is converted into the query language of the corresponding document database, and it further includes: for the case where the data object type field is nested in multiple application layer objects, the configuration content is parsed and translated layer by layer and then converted into the query language of the corresponding document database.

[0013] Further, converting the content configuration file into the query language of the corresponding document database after translation includes: obtaining a translation conversion result after translating the content configuration file; caching the translation conversion result, and for the same content configuration file with unchanged content, directly obtaining the cached result of the translation conversion result.

[0014] To achieve the above object, according to another aspect of the present application, there is provided an apparatus for dynamically configuring the returned content of a document-based database.

[0015] The apparatus for dynamically configuring the returned content of a document-based database according to the present application includes: a reading module, configured to dynamically read a content configuration file during program operation, wherein each of the content configuration files has a unique identifier, and the content configuration file is used to describe and constrain target fields; a conversion module, configured to convert the content configuration file into a query language corresponding to the document-based database after translation; and a query module, configured to perform a query operation in the document-based database according to the query language.

[0016] To achieve the above object, according to another aspect of the present application, there is also provided a storage medium in which a computer program is stored, wherein the computer program is configured to execute the steps in any one of the above method embodiments during operation.

[0017] To achieve the above object, according to still another aspect of the present application, there is also provided an electronic device including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0018] In the embodiments of the present application, by adopting the method that an application program dynamically reads a content configuration file during program operation, and converting the content configuration file into a query language corresponding to the document-based database after translation, the purpose of performing a query operation in the document-based database according to the query language is achieved, thereby realizing the technical effect of reducing the redundancy of application program code and being able to timely adjust the program functions according to different customers and different scenarios, and further solving the technical problem of frequent iteration of application programs for different business scenarios. The present application adopts a dynamic configuration method to configure corresponding content when the program starts. In the application program, a configuration translation and conversion module is used to dynamically parse the configuration content during program execution and translate it into a target database query language. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings constituting a part of the present application are used to provide a further understanding of the present application, making other features, objects, and advantages of the present application more obvious. The schematic embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation of the present application. In the drawings:

[0020] Figure 1 is a schematic hardware structure diagram of a method for dynamically configuring the returned content of a document-based database according to an embodiment of the present application;

[0021] Figure 2Schematic structural diagram of a device for dynamically configuring the content returned by a document database according to an embodiment of the present application;

[0022] Figure 3 Schematic flowchart of a method for dynamically configuring the content returned by a document database according to an embodiment of the present application;

[0023] Figure 4 Schematic flowchart of a method for dynamically configuring the content returned by a document database according to an embodiment of the present application. Detailed implementation manners

[0024] In order to enable those skilled in the art of the present technology to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily need to be used to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so as to describe the embodiments of the present application here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device including a series of steps or units does not necessarily have to be limited to those clearly listed steps or units, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0026] In the present application, the orientation or positional relationship indicated by the terms "upper", "lower", "left", "right", "front", "rear", "top", "bottom", "inner", "outer", "middle", "vertical", "horizontal", "lateral", "longitudinal", etc. is based on the orientation or positional relationship shown in the accompanying drawings. These terms are mainly used to better describe the present application and its embodiments, and are not used to limit that the indicated devices, elements or components must have a specific orientation, or be constructed and operated in a specific orientation.

[0027] Moreover, in addition to being able to represent an orientation or positional relationship, some of the above terms may also be used to represent other meanings. For example, the term "upper" may also be used to represent a certain attachment relationship or connection relationship in some cases. For those of ordinary skill in the art, the specific meanings of these terms in the present application can be understood according to specific circumstances.

[0028] In addition, the terms "installed", "set up", "provided with", "connected", "linked", and "socketed" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral structure; it can be a mechanical connection or an electrical connection; it can be a direct connection, or an indirect connection through an intermediate medium, or an internal connection between two devices, components, or parts. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0029] It should be noted that, without conflict, the embodiments in this application and the features in the embodiments can be combined with each other. The following will describe this application in detail with reference to the drawings and in conjunction with the embodiments.

[0030] As Figure 1 shown, the schematic diagram of the hardware structure of the method for dynamically configuring the returned content of the document-type database in the embodiment of this application, including: application program 100, background server 200, and database 300. The application program 100 can configure the corresponding content in a dynamically configurable manner when the program starts. Through the configuration translation and conversion module in the application program, the configuration content is dynamically parsed and translated into the target database query language during the program execution, which can not only reduce the redundancy of the application program code, but also timely adjust the program functions for different customers and different scenarios. The database 300 is the document-type database. The background server 200 receives the request of the application program 100 and returns data.

[0031] As Figure 2 shown, the method includes the following steps S201 to S203:

[0032] Step S201, the application program dynamically reads the content configuration file during the program operation, where each content configuration file has a unique identifier, and the content configuration file is used to describe and constrain the target fields;

[0033] Step S202, after translating the content configuration file, convert it into the query language of the corresponding document-type database;

[0034] Step S203, perform a query operation in the document-type database according to the query language.

[0035] From the above description, it can be seen that this application achieves the following technical effects:

[0036] By adopting the method that the application program dynamically reads the content configuration file during program operation, after translating the content configuration file, it is converted into the query language of the corresponding document database, achieving the purpose of performing query operations in the document database according to the query language, thereby realizing the technical effect of reducing the redundancy of application program code and being able to timely adjust the program functions for different customers and different scenarios, and further solving the technical problem of frequently iterating the application program for different business scenarios. Through the dynamic configuration method adopted in this application, corresponding content can be configured when the program starts. In the application program, through the configuration translation and conversion module, the configuration content is dynamically parsed during program execution and translated into the target database query language.

[0037] In step S201 above, the program runs in the application program, and the application program dynamically reads the content configuration file during program operation.

[0038] As an optional implementation manner, dynamically reading the content configuration file means reading the content configuration file according to different business scenarios.

[0039] As a preferred implementation manner, each content configuration file has a unique identifier. Through the unique identifier, the application program can access the content configuration file.

[0040] As a preferred implementation manner, the content configuration file is used to describe and constrain the target fields.

[0041] In step S202 above, based on the above content configuration file, after translating the content configuration file, it is converted into the query language of the corresponding document database.

[0042] As an optional implementation manner, it can be converted into multiple different query languages of the document database.

[0043] As a preferred implementation manner, the query content of the document database is used to meet the data requirements in the application scenarios required by the application program.

[0044] In step S203 above, according to the obtained query language, query operations are performed in the document database. The obtained query results will be returned to the application program.

[0045] As an optional implementation manner, according to the obtained query language, query operations on the field attributes of the target data group are performed in the document database.

[0046] As a preferred implementation manner, according to the obtained query language, query operations on the number of target data fields are performed in the document database.

[0047] As a preference in this embodiment, when the application program runs, it dynamically reads the content configuration file, including: the application program reads and / or modifies the content configuration file through the unique identifier.

[0048] Specifically, the function of configuration management refers to reading and modifying the configuration when the program runs. This function is implemented on the application program.

[0049] As a preference in this embodiment, after translating the content configuration file, it is converted into the query language of the corresponding document-based database, including: after translating the pre-unified content configuration file, it is converted into the query language corresponding to different database software.

[0050] Specifically, when implementing, the unified configuration translation is converted into the query language corresponding to different database software. This function is implemented on the application program.

[0051] As a preference in this embodiment, when the application program runs, it dynamically reads the content configuration file. Among them, each content configuration file has a unique identifier, and the content configuration file is used to describe and constrain the target field, including: if the data required when the program runs is an object type field, then the first preset value in JSON Schema is set to constrain the data attribute set; after translating the content configuration file, it is converted into the query language of the corresponding document-based database, including: if the object type field of the data contains M attributes and N attribute fields to be returned, then the JSON Schema is set to the first preset statement and the content configuration file is translated to obtain the first preset query statement of elastic search, where M > N, and M and N are integers.

[0052] Specifically, when implementing, the configuration content is described in the JSON Schema format. Each configuration has a unique identifier, and the application program reads and modifies the configuration through the unique identifier. The configuration content is mainly the description and constraint of the target field.

[0053] For the object type field, the properties value in JSON Schema is set to constrain its attribute set.

[0054] For example, if object a has three attributes b, c, and d, and only fields b and c are to be returned, then the JSON Schema is set to

[0055] {"type": "object", "properties": {"b": {"type": "string"}, "c": {"type": "string"}}} gives the translated Elasticsearch query statement as {"_source": ["b", "c"]}.

[0056] Preferably in this embodiment, the application reads the content configuration file dynamically during program operation. Each content configuration file has a unique identifier, and the content configuration file is used to describe and constrain target fields, including: if the data required during program operation is an array type field, then a second preset value in JSON Schema is set to constrain the data quantity; after translating the content configuration file, it is converted into the query language of the corresponding document database, including: if there are L pieces of data in the array type field of the data and O pieces of data are to be returned, then the JSON Schema is set to the second preset statement and the content configuration file is translated to obtain the second preset query statement of Elasticsearch, where L > O, and L and O are integers.

[0057] In specific implementation, for an array type field, its quantity is constrained by setting the maxItems value in JSON Schema.

[0058] For example, if the value a[1, 2, 3, 4, 5, 6] only wants to return 5 pieces of data at most, then the JSON Schema can be set to {"type": "array", "maxItems": 5}, and the translated Elasticsearch query statement is obtained.

[0059] When there are multiple levels of object nesting in an object type field, it can also be constrained layer by layer through the JSON Schema format.

[0060] Preferably in this embodiment, if the data required during program operation is an object type field, then a first preset value in JSON Schema is set to constrain the data attribute set, and it also includes: if the data object type field required during program operation is nested in multiple application layer objects, then the preset format of JSON Schema is set to constrain each layer; after translating the content configuration file, it is converted into the query language of the corresponding document database, and it also includes: for the case where the data object type field is nested in multiple application layer objects, the configuration content is parsed and translated layer by layer and then converted into the query language of the corresponding document database.

[0061] During specific implementation, the configuration content will be persistently stored in the database and edited through the external interface provided by the management module. When the application runs, the configuration is read from the internal interface provided by the management module through a unique identifier, then the configuration content is translated into the target database query language by the translation and conversion module, and finally the query is executed.

[0062] As a preference in this embodiment, after translating the content configuration file, converting it into the query language of the corresponding document-based database includes: obtaining the translation and conversion result after translating the content configuration file; caching the translation and conversion result, and in the case of the same content configuration file with unchanged content, directly obtaining the cached result of the translation and conversion result.

[0063] During specific implementation, when the translation and conversion module performs translation and conversion, it parses and translates the configuration content layer by layer. The translation and conversion module caches the translation and conversion result internally, and in the case of the same configuration with unchanged content, obtains its cached result.

[0064] It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0065] According to an embodiment of the present application, there is also provided a device for dynamically configuring the return content of a document-based database for implementing the above method, as Figure 3 shown, the device includes:

[0066] A reading module 301, configured to dynamically read a content configuration file during program operation, where each content configuration file has a unique identifier, and the content configuration file is used to describe and constrain target fields;

[0067] A conversion module 302, configured to convert the content configuration file into the query language of the corresponding document-based database after translation;

[0068] A query module 303, configured to execute a query operation in the document-based database according to the query language.

[0069] In the reading module 301 in the embodiment of the present application, a program runs in the application, and the application dynamically reads a content configuration file during program operation.

[0070] As an optional implementation manner, dynamically reading a content configuration file means reading the content configuration file according to different business scenarios.

[0071] As a preferred embodiment, each of the content profiles has a unique identifier. Through the unique identifier, the application can access the content profile.

[0072] As a preferred embodiment, the content profile is used to describe and constrain target fields.

[0073] In the conversion module 302 in the embodiments of the present application, based on the above content profile, after translating the content profile, it is converted into a query language of a corresponding document-type database.

[0074] As an alternative embodiment, it can be converted into query languages of multiple different document-type databases.

[0075] As a preferred embodiment, the query content of the document-type database is used to meet the data requirements in the application scenarios required by the application.

[0076] In the query module 303 in the embodiments of the present application, according to the obtained query language, a query operation is performed in the document-type database. The obtained query result is returned to the application.

[0077] As an alternative embodiment, according to the obtained query language, a query operation on the field attributes of the target data group is performed in the document-type database.

[0078] As a preferred embodiment, according to the obtained query language, a query operation on the number of target data fields is performed in the document-type database.

[0079] Obviously, those skilled in the art should understand that the above-mentioned modules or steps of the present application can be implemented by a general-purpose computing device. They can be concentrated on a single computing device or distributed on a network composed of multiple computing devices. Optionally, they can be implemented by program codes executable by the computing device, so that they can be stored in the storage device and executed by the computing device, or they can be separately made into individual integrated circuit modules, or multiple of them can be made into a single integrated circuit module to implement. In this way, the present application is not limited to any specific combination of hardware and software.

[0080] In order to better understand the above method flow, the above technical solutions will be explained below in conjunction with preferred embodiments, but are not used to limit the technical solutions of the embodiments of the present invention.

[0081] The method for dynamically configuring the content returned by the document-type database in the embodiments of the present application ensures the flexibility of the application, reduces code redundancy and its version iteration.

[0082] Such asFigure 4 As shown in the figure, it is a schematic flowchart of the method for dynamically configuring the returned content of the document-type database in the embodiment of the present application, specifically including the following steps:

[0083] Step S401, configure content management.

[0084] The configured content is described in JSON Schema format. Each configuration has a unique identifier, and the application reads and modifies the configuration through the unique identifier. The configured content mainly describes and constrains the target fields.

[0085] Step S402, translate and convert the configured content.

[0086] For object-type fields, by setting the properties value in JSON Schema, its property set is constrained. For example, if object a has three properties b, c, and d, and only fields b and c are desired to be returned, the JSON Schema is set to

[0087] {"type":"object","properties":{"b":{"type":"string"},"c":{"type":"string"}}} and its translated elastic search query statement is {"_source":["b","c"]}.

[0088] For array-type fields, by setting the maxItems value in JSON Schema, its quantity is constrained. For example, if the numerical value a[1,2,3,4,5,6] only wants to return at most 5 data, the JSON Schema can be set to {"type":"array","maxItems":5} to obtain the translated elastic search query statement.

[0089] When there are multiple levels of object nesting in object-type fields, they can also be constrained layer by layer through the JSON Schema format.

[0090] The configured content will be persistently stored in the database and edited through the external interface provided by the management module. When the application runs, it reads the configuration from the internal interface provided by the management module through the unique identifier, then translates and converts the configured content into the target database query language through the translation and conversion module, and finally executes the query.

[0091] When the translation and conversion module performs translation and conversion, it parses and translates and converts the configured content layer by layer. The translation and conversion module caches the translation and conversion results internally. For the same configuration and unchanged content, it takes the cached results.

[0092] Step S403, database query.

[0093] The content is configured in a conventional format, and the content returned by the database can be dynamically changed, realizing the database query.

[0094] The above are only the preferred embodiments of the present application and are not used to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the protection scope of the present application.

Claims

1. A method for dynamically configuring the return content of a document-based database, characterized in that, it includes: The application dynamically reads the content configuration file during program operation. Each of the content configuration files has a unique identifier, and the content configuration file is used to describe and constrain the target fields; The application dynamically reads the content configuration file during program operation, including: the application reads and / or modifies the content configuration file through the unique identifier; After translating the content configuration file, it is converted into the query language of the corresponding document-based database; The step of converting the content configuration file into the query language of the corresponding document-based database after translation includes: After translating the content configuration file with a pre-unified specification, it is converted into the query language corresponding to the software of different databases; According to the query language, perform a query operation in the document-based database; The application dynamically reads the content configuration file during program operation. Each of the content configuration files has a unique identifier, and the content configuration file is used to describe and constrain the target fields, including: If the data required during program operation is an object type field, set the first preset value in JSON Schema to constrain the data attribute set; The step of converting the content configuration file into the query language of the corresponding document-based database after translation includes: If the object type field of the data contains M attributes and N attribute fields to be returned, set the JSON Schema to the first preset statement and translate the content configuration file to obtain the first preset query statement of elastic search, where M > N, and M and N are integers; The application dynamically reads the content configuration file during program operation. Each of the content configuration files has a unique identifier, and the content configuration file is used to describe and constrain the target fields, including: If the data required during program operation is an array type field, set the second preset value in JSON Schema to constrain the data quantity; The step of converting the content configuration file into the query language of the corresponding document-based database after translation includes: If the array type field of the data contains L pieces of data and O pieces of data to be returned, set the JSON Schema to the second preset statement and translate the content configuration file to obtain the second preset query statement of elastic search, where L > O, and L and O are integers.

2. The method according to claim 1, characterized in that, If the data required during program operation is an object type field, setting the first preset value in JSON Schema to constrain the data attribute set further includes: If the data object type field required during program operation is nested in multiple application layer objects, set the preset format of JSON Schema to constrain each layer; After translating the content profile, converting it into the query language of the corresponding document-type database further includes: For the case where the data object type field is nested in multiple application layer objects, the configuration content is parsed and translated layer by layer and then converted into the query language of the corresponding document-type database.

3. The method according to claim 1, characterized in that the converting the content profile into the query language of the corresponding document-type database after translation includes: obtaining a translation conversion result after translating the content profile; caching the translation conversion result, and directly obtaining the cached result of the translation conversion result in the case of the same content profile and unchanged content.

4. A device for dynamically configuring the content returned by a document-type database, characterized in that it includes: a reading module, configured to dynamically read a content profile during program operation of an application. Each of the content profiles has a unique identifier, and the content profile is used to describe and constrain target fields; the application dynamically reads the content profile during program operation, including: the application reads and / or modifies the content profile through the unique identifier; a conversion module, configured to convert the content profile into the query language of the corresponding document-type database after translation; the converting the content profile into the query language of the corresponding document-type database after translation includes: translating the content profile with a pre-unified specification and converting it into the query language corresponding to the software of different databases; a query module, configured to perform a query operation in the document-type database according to the query language; the application dynamically reads the content profile during program operation. Each of the content profiles has a unique identifier, and the content profile is used to describe and constrain target fields, including: if the data required during program operation is an object type field, a first preset value in JSON Schema is set to constrain the data attribute set; the converting the content profile into the query language of the corresponding document-type database after translation includes: if the object type field of the data contains M attributes and N attribute fields to be returned, setting the JSON Schema to a first preset statement and translating the content profile to obtain a first preset query statement of elastic search, where M > N, and M and N are integers; the application dynamically reads the content profile during program operation. Each of the content profiles has a unique identifier, and the content profile is used to describe and constrain target fields, including: if the data required during program operation is an array type field, a second preset value in JSON Schema is set to constrain the data quantity; the converting the content profile into the query language of the corresponding document-type database after translation includes: If there are L pieces of data contained in the array type field of the said data and O pieces of data to be returned, then set the JSONSchema to the second preset statement and translate the said content profile to obtain the second preset query statement of elastic search, where L > O, and L and O are integers.

5. A computer-readable storage medium, characterized in that, a computer program is stored in the computer-readable storage medium, wherein the computer program is set to execute the method described in any one of claims 1 to 3 when running.

6. An electronic device, comprising a memory and a processor, characterized in that, a computer program is stored in the memory, and the processor is set to run the computer program to execute the method described in any one of claims 1 to 3.

Images