Data processing method, server and storage medium

Abstract

An embodiment of the present invention provides a data processing method, a server and a storage medium, the method comprising: receiving a data storage request; the data storage request carries at least one type of identification and configuration information; constructing a first tag based on the at least one type of identification; assigning a first index value to the first tag; associating the first tag and the first index value and storing them in a first data table, and associating the first index value and the configuration information carried in the data storage request and storing them in a second data table; the configuration information is used to configure a big data engine.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a data processing method, a server and a storage medium. Background Art

[0002] With the development of computer technology, more and more technologies (such as big data, etc.) are applied in the financial field, and the traditional financial industry is gradually transforming into financial technology. However, due to the security and real-time requirements of the financial industry, financial technology also puts forward higher requirements on technology. In the field of financial technology, when performing multi-layer hierarchical configuration of the big data engine, there are configuration information at different levels. In the related technology, at least two association tables are used to associate the configuration items and corresponding configuration parameters corresponding to all levels, but there is a large amount of duplicate data between at least two association tables, such as configuration items and / or configuration parameters, resulting in memory waste. Summary of the invention

[0003] In view of this, an embodiment of the present invention provides a data processing method, a server and a storage medium to solve the technical problem in the related art that when storing multiple levels of configuration information through at least two association tables, memory is wasted due to a large number of repeated configuration items.

[0004] To achieve the above object, the technical solution of the present invention is achieved as follows:

[0005] An embodiment of the present invention provides a data processing method, including:

[0006] Receive a data storage request; the data storage request carries at least one type of identification and configuration information;

[0007] Based on the at least one type of identification, construct a first label;

[0008] Assigning a first index value to the first tag;

[0009] The first tag and the first index value are associated and stored in a first data table, and the first index value and the configuration information carried in the data storage request are associated and stored in a second data table; the configuration information is used to configure the big data engine.

[0010] In the above solution, the at least one type of identification includes at least one of the following:

[0011] User identification;

[0012] Application identification;

[0013] Category identification of big data engines;

[0014] The version identifier of the big data engine.

[0015] In the above solution, constructing a first label based on the at least one type of identification includes:

[0016] Based on the setting correspondence between at least two types of setting identifiers and setting label construction methods, determining the setting label construction methods corresponding to at least two types of identifiers carried in the data storage request;

[0017] According to the determined setting label construction method, a first label corresponding to the at least two types of identifications is constructed.

[0018] In the above scheme, the method further includes:

[0019] receiving an update request; the update request is used to request to update the first tag and / or the configuration information;

[0020] Based on the first index value, the first tag is updated in the first data table and / or the configuration information is updated in the second data table.

[0021] In the above scheme, the method further includes:

[0022] Receiving a query request for configuration information; the query request carries at least one type of identification;

[0023] constructing at least one second tag based on at least one type of identification in the query request;

[0024] Finding in the first data table a first index value corresponding to a tag matching each second tag in the at least one second tag;

[0025] Acquire configuration information corresponding to each determined first index value from the second data table;

[0026] Based on the acquired configuration information, a query result regarding the query request is output.

[0027] In the above solution, constructing at least one second tag based on at least one type of identifier in the query request includes:

[0028] constructing a third tag based on the user identifier and the application identifier in the query request, and constructing a fourth tag based on the category identifier and the version identifier of the big data engine in the query request;

[0029] Combining the third label and the fourth label to obtain a second label of the first priority;

[0030] Using a first set character to replace the user identifier and the application identifier in the second tag of the first priority to obtain a second tag of the second priority;

[0031] A second set character is used to replace the user identifier in the second label of the first priority to obtain a second label of a third priority; wherein the first priority is higher than the second priority; and the second priority is higher than the third priority.

[0032] In the above solution, the configuration information includes at least one configuration item and a corresponding configuration parameter; and outputting a query result about the query request based on the acquired configuration information includes:

[0033] Based on the configuration items included in the configuration information corresponding to each second tag and based on the priority corresponding to each second tag, determining the second configuration parameter corresponding to each configuration item from the first configuration parameters included in the acquired configuration information;

[0034] Output each configuration item and the corresponding second configuration parameter.

[0035] The embodiment of the present invention further provides a server, including:

[0036] A receiving unit, configured to receive a data storage request; the data storage request carries at least one type of identification and configuration information;

[0037] A construction unit, configured to construct a first label based on the at least one type of identification;

[0038] an allocating unit, configured to allocate a first index value to the first tag;

[0039] A storage unit is used to associate and store the first tag and the first index value in a first data table, and associate and store the first index value and the configuration information carried in the data storage request in a second data table; the configuration information is used to configure a big data engine.

[0040] An embodiment of the present invention further provides a server, comprising: a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is used to execute the steps of the above-mentioned data processing method when running the computer program.

[0041] An embodiment of the present invention further provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the above data processing method are implemented.

[0042] In an embodiment of the present invention, a first index value is assigned to a first tag carried in a received data storage request, the first tag and the first index value are associated and stored in a first data table, and the first index value and the configuration information carried in the data storage request are associated and stored in a second data table. Thus, by storing the configuration information of the big data engine through a first data table (i.e., an association table) and a second data table, there is no need to set up multiple association tables, which can reduce the memory resources occupied by the association table, and there is no repeated associated data in the association table. Compared with the configuration information storage method in the related art, the present invention has only one association table, and there are no repeated associated configuration items and / or configuration parameters in the association table, which can avoid wasting system resources due to a large amount of repeated associated data; the first data table and the second data table are associated through index values, which can reduce the complexity of processing the configuration information of the big data engine and improve processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 A schematic diagram of the implementation flow of the data processing method provided in an embodiment of the present invention;

[0044] Figure 2 A schematic diagram of an implementation flow of querying configuration information in a data processing method provided in an embodiment of the present invention;

[0045] Figure 3 A schematic diagram of the implementation flow of querying configuration information in a data processing method provided by an application embodiment of the present invention;

[0046] Figure 4 A schematic diagram of the structure of a server provided in an embodiment of the present invention;

[0047] Figure 5 A schematic diagram of the hardware composition structure of a server provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0048] When performing multi-level configuration of a big data engine, there are configuration information at different levels. In the related technology, a configuration table is used to store configuration items and the configuration parameters corresponding to the configuration items, and at least two association tables are used to associate the configuration items and the corresponding configuration parameters corresponding to all levels. The configuration items and the corresponding configuration parameters corresponding to all levels are associated. However, the number of association tables increases with the increase in the number of configuration levels. For example, for a three-layer configuration structure, at least two association tables need to be set; for a five-layer configuration structure, at least four association tables need to be set; for a ten-layer configuration structure, at least nine association tables need to be set. When there are many configuration levels, the following problems arise:

[0049] 1. Occupies more system resources: Too many associations in the association table occupy a large storage space, and a large amount of duplicate data leads to a waste of resources;

[0050] 2. Complex management: Too many relationships make the storage, update, and query of the configuration information of the big data engine too complicated;

[0051] 3. Poor scalability: When increasing the level or expanding the number of configuration items at a certain level, it is necessary to build new associations in all association tables, and dynamic expansion cannot be achieved.

[0052] For example, when performing three-level configuration of the big data engine at "user level-engine level-application level", it is necessary to save user-level configuration information, engine-level configuration information and application-level configuration information. The user-level configuration information includes at least user identification, engine information, configuration items and corresponding configuration parameters, and may also include application identification; the engine-level configuration information includes at least engine information, configuration items and corresponding configuration parameters; the application-level configuration information includes at least application identification, engine information, configuration items and corresponding configuration parameters.

[0053] In the related art, it is necessary to configure a configuration table to store engine-level configuration information, and configure at least two association tables, one of which is used to store the correspondence between user identification, engine information, configuration items and configuration parameters, and the other is used to store the correspondence between engine information, application identification, configuration items and configuration parameters. Therefore, there may be a large number of repeated configuration items and / or configuration parameters in the same association table or between different association tables.

[0054] In order to solve the above technical problems, in an embodiment of the present invention, a data storage request is received; the data storage request carries a first tag and configuration information; a first index value is assigned to the first tag; the first tag and the first index value are associated and stored in a first data table, and the first index value and the configuration information included in the data storage request are associated and stored in a second data table; the configuration information is used to configure a big data engine. Thus, by storing the configuration information of the big data engine through a first data table (i.e., an association table) and a second data table, there is no need to set up multiple association tables, which can reduce the memory resources occupied by the association table, and there is no duplicate association data in the association table, which can avoid wasting system resources with a large amount of duplicate association data; the first data table and the second data table are associated through index values, which can reduce the complexity of processing the configuration information of the big data engine and improve processing efficiency.

[0055] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0056] Figure 1The following is a schematic diagram of the implementation process of the data processing method provided by the embodiment of the present invention, wherein the execution subject of the process is a server, such as a server corresponding to a big data platform. Figure 1 As shown, the data processing method includes:

[0057] Step 101: Receive a data storage request; the data storage request carries at least one type of identification and configuration information; wherein the configuration information is used to configure a big data engine.

[0058] The server receives a data storage request sent by the terminal; the data storage request is used to request storage configuration information. The data storage request carries at least one type of identification and configuration information; the configuration information is used to configure the big data engine when calling the big data engine to perform a data processing task. Among them, the data processing request can be sent in a scenario where the terminal initializes the big data engine or the first application, or it can be sent in a scenario where the user personalizes the big data engine. The first application is an application that needs to call the big data engine to perform a data processing task.

[0059] Exemplarily, in a scenario where a user initializes a big data engine through a set interactive interface, the trigger terminal sends a first data storage request to the server. The configuration information carried in the first data storage request is the engine-level configuration information corresponding to the big data engine. At least one type of identifier carried in the first data storage request is used to construct the first tag at the engine level. The engine-level configuration information represents the configuration information used by the big data engine when no user and application are specified. In actual application, the engine-level configuration information is the default configuration information.

[0060] Exemplarily, in a scenario where a user initializes the first application through a setting operation, the terminal installed with the first application sends a second data storage request to the server, and the configuration information carried in the second data storage request is the application-level configuration information corresponding to the big data engine. At least one type of identifier carried in the second data storage request is used to construct an application-level first tag. The application-level configuration information represents the configuration information used by the corresponding application when calling the big data engine to perform a data processing task when no user is specified. In actual application, the application-level configuration information is also the default configuration information.

[0061] Exemplarily, in a scenario where a user performs personalized configuration on a big data engine through a set interactive interface, the trigger terminal sends a third data storage request to the server, and the configuration information carried in the third data storage request is the user-level configuration information corresponding to the big data engine, and at least one type of identifier carried in the third data storage request is used to construct a user-level first label. User-level configuration information refers to the user's personalized configuration information for the big data engine, and represents the configuration information used when the user triggers an application to call the big data engine to perform a data processing task during the use of an application. It should be noted that the categories of identifiers included in the engine-level first label, the application-level first label, and the user-level first label are at least partially different. In some embodiments, the at least one type of identifier includes at least one of the following:

[0062] User identification;

[0063] Application identification;

[0064] Category identification of big data engines;

[0065] The version identifier of the big data engine.

[0066] Here, the user identifier represents the user identity, and the application identifier represents the application type. At least one type of identifier is different in the first tags of different levels.

[0067] In this embodiment, the levels to which the first tags belong are distinguished by using different types of identifiers, so that the configuration information corresponding to the first tags of different levels can be stored conveniently.

[0068] In actual application, the first tag at the engine level includes the category identifier of the big data engine and the version identifier of the big data engine. The first tag at the application level includes the application identifier, the category identifier of the big data engine and the version identifier of the big data engine. The first tag at the user level includes the user identifier, the application identifier, the category identifier of the big data engine and the version identifier of the big data engine.

[0069] In actual applications, the configuration information includes configuration items and configuration parameters corresponding to the configuration items. The configuration parameters corresponding to at least one configuration item in the configuration information corresponding to the first tags of different levels are different. The configuration items include the maximum usage threshold of memory, the maximum number of concurrent connections, etc.

[0070] Step 102: construct a first label based on the at least one type of identification.

[0071] Considering that in the stage of storing configuration information, the first tag and the configuration information are one-to-one corresponding, and the first tag can only be a tag of one setting level, for example, the first tag is an engine-level tag, an application-level tag, or a user-level tag, therefore, the server determines the corresponding setting tag construction method based on the category and quantity of the acquired identifiers, and uses the determined setting tag construction method to construct the corresponding first tag.

[0072] When the server obtains a type of identifier, the server determines the type of identifier as the first label.

[0073] When the server obtains at least two types of identifiers, it arranges the identifiers of different types according to a set arrangement order to obtain corresponding second tags.

[0074] In the case where at least two types of identifiers are carried in the data storage request, in order to unify the format of the first tag and thus facilitate the management of the first tag and the corresponding configuration information, in some embodiments, constructing the first tag based on the at least one type of identifier includes:

[0075] Based on the setting correspondence between at least two types of setting identifiers and setting label construction methods, determining the setting label construction methods corresponding to at least two types of identifiers carried in the data storage request;

[0076] According to the determined setting label construction method, a first label corresponding to the at least two types of identifications is constructed.

[0077] Here, the setting label construction method represents the arrangement format of different types of labels, setting connectors and setting separators, the setting connector is used to connect different types of identifiers, and the setting separator is used to separate two identifiers connected by the setting connector. The database stores the setting correspondence between at least two types of setting identifiers and the setting label construction method; the database can be a local database or a non-local database, for example, a cloud database.

[0078] An electronic device carries at least two types of identifiers in a data storage request. In this case, based on the setting correspondence between at least two types of setting identifier categories and setting label construction methods stored in a database, the setting label construction methods corresponding to the at least two types of identifiers obtained are determined; the at least two types of identifiers obtained are arranged according to the arrangement format represented by the determined setting label construction method to obtain at least two types of identifiers after sorting; a setting connector represented by the determined setting label construction method is used to connect every two types of identifiers in the at least two types of identifiers after sorting, and a setting separator is used to separate the two identifiers connected by the setting connector, thereby obtaining a first label.

[0079] It should be noted that, in some embodiments, at least two types of identifiers may be arranged in a set sorting order, and adjacent identifiers may be connected using a set connector to obtain a first label. Of course, the first label may also be set by the user, that is, the data storage request received by the server carries the first label and configuration information.

[0080] Step 103: assign a first index value to the first tag.

[0081] When receiving a data storage request, the server assigns a corresponding first index value to the first tag carried in the received data storage request. Different first tags correspond to different first index values. In actual application, the first index values ​​assigned by the server to different first tags constitute a set of continuous numbers.

[0082] Step 104: The first tag and the first index value are associated and stored in a first data table, and the first index value and the configuration information carried in the data storage request are associated and stored in a second data table; the configuration information is used to configure the big data engine.

[0083] Here, the server stores a first data table and a second data table set according to the setting table structure. The first data table is used to store tags and index values, and the second data table is used to store index values ​​and configuration information corresponding to the tags. The first data table and the second data table are associated through the index values ​​of the tags.

[0084] When the server assigns the first index value to the first tag, the server associates and stores the first tag and the first index value assigned to the first tag in a first data table, and associates and stores the first index value assigned to the first tag and the configuration information carried in the data storage request in a second data table.

[0085] In actual application, the first data table includes at least a first setting field and a second setting field. The first setting field is used to write the index value of the label; the second setting field is used to write the specific content of the label, and the field name of the second field can be label_key_value. Of course, the first data table can also include a third setting field and a fourth setting field. The third setting field is used to write the time when the first data table is created; the fourth setting field is used to write the time when the first data table is updated. The second data table includes a fifth setting field and a sixth setting field. The fifth setting field is used to write the index value of the label, and the sixth setting field is used to write configuration information.

[0086] In actual applications, the format of the field value of the second field is (label_key, label_stringvalue). label_key represents the labelKey corresponding to the label, that is, the key of the label; label_stringvalue represents the StringValue corresponding to the label, that is, the key value of the label, which is used to identify the specific content of the label.

[0087] Exemplarily, the label_key of the first label can be Combine_UserCreator_EngineType. When user A configures the big data engine A with version number A under application A, the label_stringvalue of the first label corresponds to "userA-creatorA, engineA-A". userA represents the user ID, creatorA represents the application ID, engineA represents the category ID of the big data engine, and A represents the version ID of the big data engine.

[0088] In this embodiment, a data storage request is received; the data storage request carries a first tag and configuration information; a first index value is assigned to the first tag; the first tag and the first index value are associated and stored in a first data table, and the first index value and the configuration information included in the data storage request are associated and stored in a second data table; the configuration information is used to configure the big data engine. Thus, by storing the configuration information of the big data engine through a first data table (i.e., an association table) and a second data table (configuration table), there is no need to set up multiple association tables, the memory resources occupied by the association table can be reduced, there is no duplicate association data in the association table, and a large amount of duplicate association data can be avoided from wasting system resources; the first data table and the second data table are associated through the index value, which can reduce the complexity of processing the configuration information of the big data engine and improve the processing efficiency.

[0089] Considering that in the application scenario of multi-level configuration of the big data engine, some levels of configuration information cannot be modified, such as default configuration information, and some levels of configuration information are allowed to be modified, such as personalized configuration information. In order to better meet the user's needs for modifying configuration information, in some embodiments, on the basis of associating the first tag and the first index value and storing them in the first data table, and associating the first index value corresponding to the first tag and the configuration information and storing them in the second data table, the method further includes:

[0090] receiving an update request; the update request is used to request to update the first tag and / or the configuration information;

[0091] Based on the first index value, the first tag is updated in the first data table and / or the configuration information is updated in the second data table.

[0092] Here, when the user wants to update the configuration information of a certain level, he can modify the configuration information of the big data engine through the set interactive interface and trigger the terminal to send an update request to the server to request to update the first tag and / or configuration information in the first data table.

[0093] Exemplarily, in a scenario where a user modifies the personalized configuration of the big data engine through a set interactive interface, the terminal is triggered to send an update request to the server.

[0094] When receiving the update request, the server updates the first tag in the first data table and / or updates the configuration information in the second data table based on the update request and the first index value in the first data table. The specific implementation process is as follows:

[0095] When receiving the update request, the server searches the first data table for a first tag that matches the first tag carried in the update request to obtain a search result.

[0096] When the search result indicates that no matching first tag is found, the first tag carried in the update request is not stored in the first data table, and the update request is used to request an update of the first tag in the first data table and the configuration information in the second data table. At this time, the server assigns a first index value to the first tag carried in the update request, and associates and stores the first tag carried in the update request and the first index value assigned to the first tag in the first data table, thereby updating the first tag in the first data table.

[0097] When the search result indicates that a matching first tag has been found, the update request is used to request an update of the configuration information in the second data table. The server determines the first index value corresponding to the first tag carried in the update request from the first data table, and searches for the first index value that matches the determined first index value from the second data table, and replaces the configuration information corresponding to the matching first index value in the second data table with the configuration information carried in the update request.

[0098] It should be noted that, when the user name of the user is changed, the update request is used to update the first tag in the first data table.

[0099] Exemplarily, when a user's username changes, the update request sent by the user triggering the terminal carries the first tag before the change and the first tag after the change. Upon receiving the update request, the server searches the first data table for a first tag that matches the first tag before the change carried in the update request, and replaces the found first tag with the first tag after the change carried in the update request.

[0100] Exemplarily, when the user's username changes and the user has obtained the first index value corresponding to the first label before the change, the update request sent by the user triggering the terminal carries the first index value and the changed first label. When the server receives the update request, it searches the first data table for a first index value that matches the first index value carried in the update request, and when a matching first index value is found, based on the found matching first index value, it replaces the first label corresponding to the matching first index value in the first data table with the changed first label carried in the update request.

[0101] In this embodiment, the configuration information of the big data engine is stored through a first data table (i.e., an association table) and a second data table (configuration table). There is no duplicate association relationship. When the configuration information of the big data engine needs to be updated, the user only needs to update the first tag in the first data table and / or the configuration information in the second data table, which can improve data update efficiency.

[0102] Considering that in the scenario where the user updates the first tag in the first data table or the configuration information in the second data table, or in the scenario where the big data engine is called to perform a data processing task, it is necessary to query the configuration information of the big data engine, such as Figure 2 As shown, in some embodiments, the method further includes:

[0103] Step 201: receiving a query request for configuration information; the query request carries at least one type of identification;

[0104] Step 202: construct at least one second tag based on at least one type of identification in the query request;

[0105] Step 203: searching the first data table for a first index value corresponding to a tag matching each second tag in the at least one second tag;

[0106] Step 204: Acquire configuration information corresponding to each determined first index value from the second data table;

[0107] Step 205: Based on the acquired configuration information, output the query result regarding the query request.

[0108] Here, when the server receives the query request for configuration information sent by the terminal, based on at least one type of identifier in the query request, the server constructs at least one second tag using a corresponding set tag construction method. The implementation process of constructing at least one second tag using a corresponding set tag construction method is as follows:

[0109] When the query request carries only one type of identifier, the server determines the type of identifier as the second label.

[0110] When the query request carries at least two types of identifiers, the server determines the corresponding set label construction method from the database based on the category to which each acquired identifier belongs, and based on the first set correspondence relationship and the second set correspondence relationship stored in the database, and uses the set label construction method to construct at least one second label corresponding to the acquired at least two types of identifiers. The first set correspondence relationship represents the set correspondence relationship between labels of different set levels and label categories; the second set correspondence relationship represents the set correspondence relationship between labels of different set levels and set label construction methods. In actual application, when the query request carries at least two types of identifiers, the server can construct second labels of different levels. For example, when the big data engine is configured at the user level, engine level, and application level, the set label construction method includes a method for constructing a user-level label, a method for constructing an engine-level label, and a method for constructing an application-level label; when the query request carries the category identifier of the big data engine and the version identifier of the big data engine, the server can construct an engine-level second label based on the method for constructing the engine-level label; when the query request carries the application identifier, the category identifier of the big data engine, and the version identifier of the big data engine, the server can construct an engine-level second label and an application-level second label based on the method for constructing the engine-level label and the method for constructing the application-level label; when the query request carries the user identifier, the application identifier, the category identifier of the big data engine, and the version identifier of the big data engine, the server can construct a user-level second label, an engine-level second label, and an application-level second label.

[0111] Exemplarily, when the big data engine is configured at the user level, engine level, and application level, since only the user-level configuration information is modifiable, in an application scenario where the user wants to update the user-level configuration information, the user can enter or input the user name, application ID, category ID, and version ID of the big data engine in the interactive interface for querying the configuration information of the big data engine in the terminal, and trigger the terminal to send a query request to the server, where the query request carries the user ID, application ID, category ID of the big data engine, and version ID of the big data engine. When the server receives the query request sent by the terminal, it can construct a second user-level tag, a second engine-level tag, and a second application-level tag based on the user ID, application ID, category ID of the big data engine, and version ID of the big data engine carried in the query request, using the corresponding set tag construction method.

[0112] When the second tag is constructed, the first index value corresponding to the tag matching the second tag is searched in the first data table to obtain the first index value corresponding to each second tag; the configuration information corresponding to each first index value is obtained from the second data table to obtain the configuration information corresponding to each second tag.

[0113] When the number of constructed second tags is one, the configuration information corresponding to the second tag is determined as the query result of the query request, and the configuration information corresponding to the first tag is output.

[0114] When the number of constructed second tags is at least two, based on the set priority corresponding to each second tag and the configuration information corresponding to each second tag, a query result regarding the query request is determined and the query result is output.

[0115] In actual application, the configuration information includes configuration items and configuration parameters corresponding to the configuration items. When two second tags of different levels are constructed, the server can use the configuration information corresponding to the second tag with a higher priority to replace the configuration parameters corresponding to the same configuration items in the configuration information corresponding to the second tag with a lower priority, and output the replaced configuration information. When at least three second tags of different levels are constructed, the configuration information corresponding to the second tag with the highest priority is used to replace the configuration information corresponding to the second tag with the second highest priority in descending order of priority to obtain a processing result, and the configuration information corresponding to the second tag with the next highest priority is replaced based on the processing result, and so on, until the configuration information corresponding to the second tag with the lowest priority is replaced.

[0116] In actual application, outputting the query result about the query request means sending the query result to the terminal that sent the query request. In the application scenario where the user needs to update the user-level configuration information, the terminal displays the query result when receiving the query result about the query request sent by the server, so as to modify the user-level configuration information based on the query result; in the scenario where the user operates an application and triggers the application to call the big data engine to perform data processing tasks, the terminal configures the called big data engine using the configuration information in the query result when receiving the query result about the query request sent by the server, and performs the corresponding data processing tasks through the big data engine.

[0117] In this embodiment, a second tag is constructed by using an identifier carried in a query request for configuration information, a first index value corresponding to a match with the constructed second tag is found from the first data table, and then configuration information corresponding to the found first index value is obtained from the second data table. Thus, the server can find the corresponding configuration information through the index value corresponding to the second tag, without having to query the configuration information through multiple association relationships, thereby reducing the time consumed in querying the configuration information and improving the efficiency of querying the configuration information.

[0118] Considering that the configuration items contained in the configuration information corresponding to the tags at different levels are not exactly the same, in order to obtain the configuration information that matches the usage habits or operation requirements of the calling object of the big data engine, it is necessary to construct the second tags at different levels based on the query request, so as to query the configuration information corresponding to the second tags at different levels from the second data table, wherein the calling object includes a user or an application. In some embodiments, in step 202, the at least one second tag is constructed based on at least one type of identification in the query request, including:

[0119] constructing a third tag based on the user identifier and the application identifier in the query request, and constructing a fourth tag based on the category identifier and the version identifier of the big data engine in the query request;

[0120] Combining the third label and the fourth label to obtain a second label of the first priority;

[0121] Using a first set character to replace the user identifier and the application identifier in the second label of the first priority to obtain a second label of the second priority;

[0122] The user identifier in the second tag of the first priority is replaced by a second set character to obtain a second tag of a third priority; wherein,

[0123] The first priority is higher than the second priority; the second priority is higher than the third priority.

[0124] Here, the query request carries a user ID, an application ID, a category ID of the big data engine, and a version ID of the big data engine.

[0125] The server determines the arrangement order of the user identifier and the application identifier carried in the query request according to the set priorities corresponding to the user identifier and the application identifier respectively, arranges the user identifier and the application identifier according to the determined arrangement order, and obtains a third tag.

[0126] The server determines the arrangement order of the category identifier and version identifier of the big data engine carried in the query request according to the set priorities corresponding to the category identifier and version identifier of the big data engine, arranges the category identifier and version identifier of the big data engine according to the determined arrangement order, and obtains a fourth label.

[0127] When the third tag and the fourth tag are determined, the third tag and the fourth tag are combined according to the set rule to obtain the second tag of the first priority, that is, the second tag of the user level. For example, when the third tag is userA-creatorA and the fourth tag is engineA-A, the second tag of the first priority is "userA-creatorA, engineA-A".

[0128] When the second tag of the first priority is determined, the first setting character is used to replace the user identifier and the application identifier in the second tag of the first priority to obtain the second tag of the second priority; and the second setting character is used to replace the user identifier in the second tag of the first priority to obtain the second tag of the third priority. The first setting character and the second setting character both represent null values, and the first setting character and the second setting character can be the same or different. In actual application, the first setting character and the second setting character are both "*".

[0129] For example, when the second tag of the first priority is "userA-creatorA, engineA-A", the second tag of the second priority is engineA-A, and the second tag of the third priority is =<creatorA,engineA-A> .

[0130] In actual application, the format of the label is (label_key, label_stringvalue). It should be noted that the labels in the embodiments of the present invention involve four entity classes: generic label (GenericLabel), user-application label (UserCreatorLabel), engine category label (EngineTypeLabel), and combination label (CombineLabel); UserCreatorLabel, EngineTypeLabel, and CombineLabel all inherit the properties of GenericLabel. Among them,

[0131] The fields and methods contained in GenericLabel, UserCreatorLabel, EngineTypeLabel, and CombineLabel are explained as follows:

[0132] (1) The fields and methods contained in GenericLabel are explained as follows:

[0133] The first field, labelKey: a fixed string constant, is used to identify the label type to which the value belongs;

[0134] The second field labelValue: The label corresponds to the stored map data, the type is Map<String,String> , the map stores the key-value pair information corresponding to the label, and the corresponding value needs to be initialized when the entity class is constructed;

[0135] The third field value_separator: value connection separator, used to connect the value values ​​in the map;

[0136] The fourth field stringValue: is used to store the result of connecting the value in the map through value_separator, and is also the core value stored in the database.

[0137] getStringValue(): The core method for constructing StringValue. It connects stringValue according to value_separator and labelValue. The construction order is parsed based on the custom annotation ValueSerialNum in the set method of labelKey in the inherited class. Parsing process: Get all methods of the inherited class through class.getDeclaredMethods-->Filter the methods through method.isAnnotationPresent(ValueSerialNum.class) of each method to get the annotated methods--->Get the corresponding value in the annotation ValueSerialNum of the annotated method-->Sort the keys in labelValue according to the priority identified by the value of ValueSerialNum to determine the order of labelValue's keys. The advantage of this design is that you only need to design the sorting method at the top level, and set the order of keys in the inherited class by introducing annotations, which greatly reduces the code implementation content of the inherited class. The traditional method requires setting additional variables through the inherited class for custom key order, and then re-implementing the getStringValue method for sorting.

[0138] setStringValue(): The core method for constructing StringValue. The processing logic is similar to getStringValue and will not be repeated here.

[0139] (2) The fields and methods contained in UserCreatorLabel are explained as follows:

[0140] labelKey: Override field, fixed string constant "userCreator", mainly used to identify the Label type to which the labelValue belongs;

[0141] labelValue: Overrides the field. The label corresponds to the stored map data. The type is Map<String,String> The key-value pairs stored in the map include two types, namely <'user',value> and <'creator',value>. The corresponding values ​​need to be initialized when the entity class is constructed;

[0142] setUser(): method for setting the label user, annotated with ValueSerialNum(0), indicating the highest priority, used for label key priority parsing in GenericLabel;

[0143] setCreator(): This method sets the application to which the label belongs. It is annotated with ValueSerialNum(1), indicating secondary priority. It is used for label key priority parsing in GenericLabel.

[0144] default_user: represents the value of user when no user is specified.

[0145] (3) The main fields and methods of EngineTypeLabel are explained as follows:

[0146] labelKey: Override field, fixed string constant "engineType", mainly used to identify the Label type to which the labelValue belongs;

[0147] labelValue: Overrides the field. The label corresponds to the stored map data. The type is Map<String,String> The key-value pairs stored in the map include two types, namely <'engineType',value> and <'version',value>. The corresponding values ​​need to be initialized when the entity class is constructed;

[0148] setEngine: method for setting the tag engine, annotated with ValueSerialNum(0), indicating the highest priority;

[0149] setType: This method is used to set the version of the tag engine. It is annotated with ValueSerialNum(1), indicating a lower priority.

[0150] (4) CombineLabel is used to combine and convert UserCreatorLabel and EngineTypeLabel. It is the label actually used for storage. The core classes and methods are as follows:

[0151] labelKey: a composite LabelKey, the content must be the result of sorting the labelKeys of the combined labels according to certain rules.

[0152] labelValue: map data, used to store the labels of the combined records;

[0153] COMBINED_LABEL_KEY_PREFIX: labelKey prefix, used to identify the label type

[0154] LABEL_KEY_JOIN_SYMBOL: labelKey separator, used to construct and parse the labelKey of CombineLabel;

[0155] LABEL_VALUE_JOIN_SYMBOL: labelValue separator, used to construct and parse the labelValue of CombineLabel;

[0156] getStringValue(): The core method for constructing StringValue; the steps of this method are as follows: parse the labelKey priority and sort it --> sort the labelValue in the same order --> combine labelValue according to the value of LABEL_VALUE_JOIN_SYMBOL --> return StringValue.

[0157] The following is a detailed description of the implementation process of the server constructing second tags of different levels based on the user identifier, application identifier, category identifier and version identifier of the big data engine carried in the query request with reference to a specific example:

[0158] In the scenario of three-level configuration of the big data engine, the priorities are from high to low: user level, engine level, and application level.

[0159] When the query request carries userA, applicationA, engine typeA and versionA, the server constructs the second tag as follows:

[0160] The server obtains the setting parameters, which include the value connection separator (value_separator), the prefix of the combined label, the first separator corresponding to the labelKey of the combined label, the second separator corresponding to the labelValue of the combined label, and the setting character. In actual application, value_separator = "-"; the prefix of the combined label COMBINED_LABEL_KEY_PREFIX = "Combined"; the first separator corresponding to the labelKey of the combined label LABEL_KEY_JOIN_SYMBOL = "_"; the second separator corresponding to the labelValue of the combined label LABEL_VALUE_JOIN_SYMBOL = ","; the setting character is "*", that is, default_user = "*".

[0161] The server constructs UserCreatorLabel based on the user ID, application ID and value connection separator in the query request; constructs EngineTypeLabel based on the category ID, version ID of the big data engine in the query request and value connection separator in the setting parameter; and combines the constructed UserCreatorLabel and the constructed EngineTypeLabel based on the first separator and the second separator in the setting parameter to obtain the second label of the first priority.

[0162] The server constructs the UserCreatorLabel based on the user ID and application ID in the query request as follows:

[0163] Create a new UserCreatorLabel object, call the setUser() method to set the value of 'user' to userA, and get the key-value pair <'user',userA>; call the setUser() method to set the value of 'creator' to creatorA, and get the key-value pair <'creator',creatorA>. In other words, UserCreatorLabel includes two key-value pairs: <'user',userA> and <'creator',creatorA>.

[0164] The server calls the getStringValue method of UserCreatorLabel and constructs the StringValue of UserCreatorLabel based on the value concatenation separator (value_separator) included in the setting parameters. Since the priority of 'user' is higher than the priority of 'creator', when the value concatenation separator is "-", the StringValue of UserCreatorLabel is userA-creatorA.

[0165] That is to say, the labelKey of the constructed UserCreatorLabel is userCreator; the labelValue of the constructed UserCreatorLabel includes: <'user',userA> and <'creator',creatorA>; and the StringValue of the constructed UserCreatorLabel is userA-creatorA.

[0166] The server constructs EngineTypeLabel based on the category identifier and version identifier of the big data engine in the query request:

[0167] The server creates a new EngineTypeLabel object, calls the setUser() method to set the value of 'engineType' to engineA, and obtains the key-value pair <'engineType',engineA>; calls the setUser() method to set the value of 'version' to A, and obtains the key-value pair <'version',A>. In other words, EngineTypeLabel includes two key-value pairs: <'engineType',engineA> and <'version',A>.

[0168] The server calls the getStringValue method of EngineTypeLabel and constructs the StringValue of EngineTypeLabel based on the value concatenation separator (value_separator) included in the setting parameters. Since the priority of 'engineType' is higher than the priority of 'version', when the value concatenation separator is "-", the stringValue of EngineTypeLabel is engineA-A.

[0169] The server combines the constructed UserCreatorLabel and the constructed EngineTypeLabel to obtain the second label of the first priority. The implementation process is as follows:

[0170] In the case of the constructed UserCreatorLabel and EngineTypeLabel, the server creates a new CombineLabel object, obtains the labelKey of UserCreatorLabel from the constructed UserCreatorLabel to obtain userCreator; obtains the labelKey of EngineTypeLabel from the constructed EngineTypeLabel to obtain engineType; obtains the first separator corresponding to the labelKey of the combined label from the setting parameters; constructs the labelKey of the second label of the first priority based on the constructed labelKey of UserCreatorLabel, the constructed labelKey of EngineTypeLabel and the first separator corresponding to the labelKey of the combined label; the labelKey of the second label of the first priority = Combined_UserCreator_EngineType. In the process of constructing the combined label, the constructed UserCreatorLabel and EngineTypeLabel are used as the input parameters of the combined label. That is to say, the server passes the constructed labelKey of UserCreatorLabel and the constructed labelKey of EngineTypeLabel into the newly created CombineLabel object, and according to the priority of UserCreatorLabel and EngineTypeLabel, connects the prefix of the combined label, the labelKey of UserCreatorLabel and the labelKey of EngineTypeLabel respectively through the first separator corresponding to the labelKey of the combined label to obtain the labelKey of the second label with the first priority.

[0171] The server obtains the stringValue of UserCreatorLabel from the constructed UserCreatorLabel to obtain userA-creatorA; obtains the stringValue of EngineTypeLabel from the constructed EngineTypeLabel to obtain engineA-A, and separates the stringValue of UserCreatorLabel and the stringValue of EngineTypeLabel according to the priority of UserCreatorLabel and EngineTypeLabel by the second separator corresponding to the labelValue of the combined label to obtain the stringValue of the second label of the first priority =<userA-creatorA,engineA-A> .

[0172] In actual applications, the labelKey of the second label of the first priority constructed is Combined_UserCreator_EngineType; the labelValue of the second label of the first priority constructed includes:<user-creator,userA-creatorA> and<engineType-version,engineA-A> ; The stringValue of the second tag of the first priority constructed is<userA-creatorA,engineA-A> .

[0173] When the server determines the second tag of the first priority, it replaces the user identifier and application identifier obtained from the query request with the set character "*", and constructs the second tag of the second priority based on the replaced user identifier, the replaced application identifier, the category identifier and the version identifier of the big data engine; it replaces the user identifier obtained from the query request with the set identifier "*", and constructs the second tag of the third priority based on the replaced user identifier, the application identifier, the category identifier and the version identifier of the big data engine. Among them, the method of constructing the second tag of the second priority or the third priority is similar to the method of constructing the second tag of the first priority mentioned above. Please refer to the relevant description above and it will not be repeated here.

[0174] In some embodiments, here, considering that the labelKey of the second label of the first priority, the second priority and the third priority is unchanged, and the StringValue of the combined label is obtained by combining the StringValue in UserCreatorLabel and the StringValue in EngineTypeLabel, the server can keep the labelKey of the second label of the first priority unchanged, replace the user identifier and the application label in the StringValue of the second label of the first priority with the set character "*", and obtain the second label of the second priority, and replace the user identifier in the StringValue of the second label of the first priority with the set character "*", and obtain the third label of the second priority. For example, in the case where the labelKey of the second label of the first priority is Combined_UserCreator_EngineType, and the StringValue of the second label of the first priority is<userA-creatorA,engineA-A> In this case, the StringValue of the second tag of the second priority level is StringValue=<*-*,engineA-A>, and the StringValue of the second tag of the third priority level is StringValue=<*-creatorA,engineA-A>.

[0175] Considering that the configuration items contained in the configuration information corresponding to the tags at different levels are not completely the same, in order to obtain the configuration information that matches the usage habits or operation requirements of the calling object of the big data engine, in some embodiments, the query result about the query request is output based on the acquired configuration information in step 205, including:

[0176] Based on the configuration items included in the configuration information corresponding to each second tag and based on the priority corresponding to each second tag, determining the second configuration parameter corresponding to each configuration item from the first configuration parameters included in the acquired configuration information;

[0177] Output each configuration item and the corresponding second configuration parameter.

[0178] Here, when the configuration items included in the configuration information corresponding to all second tags are the same, the server determines the first configuration parameter corresponding to each configuration item in the configuration information corresponding to the second tag of the first priority as the second configuration parameter corresponding to the corresponding configuration item, and outputs the configuration information corresponding to the second tag of the first priority.

[0179] In the case where the configuration items included in the configuration information corresponding to the second tag of the first priority are not completely the same as the configuration items included in the configuration information corresponding to the second tag of the second priority, the configuration parameters of the corresponding configuration items in the configuration information corresponding to the second tag of the second priority are replaced based on the configuration information corresponding to the second tag of the first priority to obtain the first configuration information. Replacing the configuration information refers to replacing configuration parameters corresponding to the same configuration items.

[0180] When the configuration items included in the configuration information corresponding to the second tag of the second priority are exactly the same as the configuration items included in the configuration information corresponding to the second tag of the third priority, the first configuration parameter corresponding to each configuration item in the first configuration information is determined as the second configuration parameter corresponding to the corresponding configuration item; and the first configuration information is output.

[0181] When the configuration items included in the configuration information corresponding to the second tag of the second priority are not completely the same as the configuration items included in the configuration information corresponding to the second tag of the third priority, the configuration parameters corresponding to the corresponding configuration items in the configuration information corresponding to the second tag of the third priority are replaced based on the first configuration information to obtain the second configuration information, and the second configuration information is output.

[0182] In actual application, the number of configuration items included in the user-level configuration information is the least. The configuration items included in the engine-level configuration information and the configuration items included in the application-level configuration information can be completely the same or partially the same.

[0183] Since the configuration information of the big data engine corresponding to different users and different applications is different, in this embodiment, based on the configuration items included in the configuration information corresponding to each second tag and based on the priority corresponding to each second tag, the second configuration parameter corresponding to each configuration item is determined from the first configuration parameter included in the acquired configuration information; each configuration item and the corresponding second configuration parameter are output, thereby outputting configuration information that matches the usage habits or operating requirements of the calling object of the big data engine.

[0184] Figure 3 The following is a schematic diagram showing the implementation flow of querying configuration information in the data processing method provided by the application embodiment of the present invention. Figure 3 As shown, the method for querying configuration information includes:

[0185] Step 301: Receive a query request for configuration information, where the query request carries a user identifier, an application identifier, a category identifier of a big data engine, and a version identifier of the big data engine.

[0186] Step 302: construct a user-application tag based on the user identifier and the application identifier, and construct an engine category tag based on the category identifier of the big data engine and the version identifier.

[0187] Here, the server constructs UserCreatorLabel based on the user ID and application ID, and constructs EngineTypeLabel based on the category ID and version ID of the big data engine. For the specific implementation process, please refer to the relevant description of constructing the third label and the fourth label above, which will not be repeated here.

[0188] Step 303: Combine the constructed user-application label and engine category label to obtain a combined label.

[0189] Here, the server combines UserCreatorLabel and EngineTypeLabel to obtain a combined label. For the specific implementation method, please refer to the above description of combining the third label and the fourth label to obtain the second label of the first priority, which is not repeated here.

[0190] Step 304: Find the first index value corresponding to the tag matching the combined tag in the first data table.

[0191] Among them, step 304 is similar to step 203. Please refer to the relevant description in step 203 for the specific implementation process, which will not be repeated here.

[0192] Step 305: Obtain configuration information corresponding to the determined first index value from the second data table.

[0193] Among them, step 305 is similar to step 204. For the specific implementation process, please refer to the relevant description in step 204, which will not be repeated here.

[0194] Step 306: Determine whether the priority of the combined tag is the lowest priority.

[0195] The server determines whether the priority of the combined tag is the lowest priority and obtains a determination result. If the determination result indicates that the priority of the combined tag is not the lowest priority, step 307 is executed; if the determination result indicates that the priority of the combined tag is the lowest priority, step 308 is executed.

[0196] Step 307: Use set characters to replace the user ID and the application ID, or use set characters to replace the user ID.

[0197] It should be noted that when step 307 is executed for the first time, the user identifier and application identifier obtained from the query request are replaced with the set character "*", and steps 302 to 306 are executed again.

[0198] When the judgment result obtained by executing step 306 again indicates that the priority of the combined tag is not the lowest priority, when executing step 307 again, the user identifier obtained from the query request is replaced with the set character "*", and steps 302 to 306 are executed again.

[0199] It should be noted that in this application embodiment, the big data engine is configured at three levels: user level, engine level, and application level, with the priority being user level, engine level, and application level in descending order. The server executes steps 302 to 303 for the first time, and the resulting combined tag is a user-level combined tag. The server executes steps 302 to 303 for the second time, and the resulting combined tag is an engine-level combined tag. The server executes steps 302 to 303 for the third time, and the resulting combined tag is an application-level combined tag.

[0200] Step 308: Based on the acquired configuration information, output the query result regarding the query request.

[0201] Among them, the implementation process request of step 308 refers to the above. When the second tag of the first priority, the second tag of the second priority and the second tag of the third priority are constructed, the implementation process of outputting the query result of the query request based on the configuration information corresponding to the second tags of these three priorities is not repeated here.

[0202] To implement the method of the embodiment of the present application, the embodiment of the present application also provides a server, such as Figure 4 As shown, the server includes:

[0203] A receiving unit 41 is configured to receive a data storage request; the data storage request carries at least one type of identification and configuration information;

[0204] A construction unit 42, configured to construct the first label based on the at least one type of identification;

[0205] An allocating unit 43, configured to allocate a first index value to the first tag;

[0206] The storage unit 44 is used to associate and store the first tag and the first index value in a first data table, and associate and store the first index value and the configuration information carried in the data storage request in a second data table; the configuration information is used to configure the big data engine.

[0207] In some embodiments, the at least one type of identification includes at least one of the following:

[0208] User identification;

[0209] Application identification;

[0210] Category identification of big data engines;

[0211] The version identifier of the big data engine.

[0212] In some embodiments, the construction unit 42 is specifically used to:

[0213] Based on the setting correspondence between at least two types of setting identifiers and setting label construction methods, determining the setting label construction methods corresponding to at least two types of identifiers carried in the data storage request;

[0214] According to the determined setting label construction method, a first label corresponding to the at least two types of identifications is constructed.

[0215] In some embodiments, the receiving unit 41 is further used to receive an update request; the update request is used to request to update the first tag and / or the configuration information; the server further includes:

[0216] An updating unit is configured to update the first tag in the first data table and / or update the configuration information in the second data table based on the first index value.

[0217] In some embodiments, the receiving unit 41 is further used to receive a query request for configuration information; the query request carries at least one type of identification; the server further includes:

[0218] A construction unit, configured to construct at least one second tag based on at least one type of identification in the query request;

[0219] A query unit, configured to search the first data table for a first index value corresponding to a tag matching each second tag in the at least one second tag;

[0220] A determining unit, configured to obtain, from the second data table, configuration information corresponding to each determined first index value;

[0221] The output unit is used to output the query result about the query request based on the acquired configuration information.

[0222] In some embodiments, the construction unit is used to:

[0223] constructing a third tag based on the user identifier and the application identifier in the query request, and constructing a fourth tag based on the category identifier and the version identifier of the big data engine in the query request;

[0224] Combining the third label and the fourth label to obtain a second label of the first priority;

[0225] Using a first set character to replace the user identifier and the application identifier in the second tag of the first priority to obtain a second tag of the second priority;

[0226] A second set character is used to replace the user identifier in the second label of the first priority to obtain a second label of a third priority; wherein the first priority is higher than the second priority; and the second priority is higher than the third priority.

[0227] In some embodiments, the configuration information includes at least one configuration item and a corresponding configuration parameter; the output unit is used to:

[0228] Based on the configuration items included in the configuration information corresponding to each second tag and based on the priority corresponding to each second tag, determining the second configuration parameter corresponding to each configuration item from the first configuration parameters included in the acquired configuration information;

[0229] Output each configuration item and the corresponding second configuration parameter.

[0230] In actual application, each unit included in the server can be implemented by a processor in the server, such as a central processing unit (CPU), a digital signal processor (DSP), a microcontroller unit (MCU) or a programmable gate array (FPGA).

[0231] It should be noted that: when the server provided in the above embodiment performs data processing, only the division of the above program modules is used as an example. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the server provided in the above embodiment and the data processing method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0232] Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiment of the present application, the embodiment of the present application also provides a server. Figure 5 FIG. 1 is a schematic diagram of the hardware structure of the server according to an embodiment of the present invention. Figure 5 As shown, the server 5 includes:

[0233] Communication interface 51, capable of exchanging information with other devices such as network devices;

[0234] The processor 52 is connected to the communication interface 51 to implement information exchange with other devices and is used to execute the method provided by one or more of the above technical solutions when running a computer program. The computer program is stored in the memory 53.

[0235] Of course, in actual application, the various components in the server 5 are coupled together through the bus system 54. It can be understood that the bus system 54 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 54 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Figure 5 Various buses are labeled as bus system 54 .

[0236] The memory 53 in the embodiment of the present application is used to store various types of data to support the operation of the server 5. Examples of such data include: any computer program used to operate on the server 5.

[0237] It can be understood that the memory 53 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAM bus random access memory (DRRAM, Direct Rambus Random Access Memory).The memory 53 described in the embodiments of the present application is intended to include but is not limited to these and any other suitable types of memory.

[0238] The method disclosed in the above embodiment of the present application can be applied to the processor 52, or implemented by the processor 52. The processor 52 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 52 or the instruction in the form of software. The above processor 52 can be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 52 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiment of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 53, and the processor 52 reads the program in the memory 53 and completes the steps of the above method in combination with its hardware.

[0239] Optionally, when the processor 52 executes the program, it implements the corresponding processes implemented by the terminal in each method of the embodiments of the present application, which will not be described here for the sake of brevity.

[0240] In an exemplary embodiment, the present application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, for example, including a first memory 53 storing a computer program, and the computer program can be executed by a processor 52 of the terminal to complete the steps of the aforementioned method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface storage, optical disk, or CD-ROM.

[0241] In the several embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0242] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0243] In addition, all functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0244] A person skilled in the art can understand that: all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), disks or optical disks, etc. Various media that can store program codes.

[0245] It should be noted that the technical solutions described in the embodiments of the present invention can be arbitrarily combined without conflict.

[0246] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A data processing method, characterized in that: include: receiving a data storage request; The data storage request carries at least one type of identification and configuration information; Based on the at least one type of identification, construct a first label; Assigning a first index value to the first tag; The first tag and the first index value are associated and stored in a first data table, and the first index value and the configuration information carried in the data storage request are associated and stored in a second data table; The configuration information is used to configure the big data engine; The constructing a first label based on the at least one type of identification includes: Based on the setting correspondence between at least two types of setting identifiers and setting label construction methods, determining the setting label construction methods corresponding to at least two types of identifiers carried in the data storage request; According to the determined setting label construction method, a first label corresponding to the at least two types of identifications is constructed.

2. The method according to claim 1, characterized in that The at least one type of identification includes at least one of the following: User identification; Application identification; Category identification of big data engines; The version identifier of the big data engine.

3. The method according to claim 1, characterized in that The method further comprises: receiving an update request; the update request is used to request to update the first tag and / or the configuration information; Based on the first index value, the first tag is updated in the first data table and / or the configuration information is updated in the second data table.

4. The method according to claim 2, characterized in that The method further comprises: Receiving a query request for configuration information; the query request carries at least one type of identification; constructing at least one second tag based on at least one type of identification in the query request; Finding in the first data table a first index value corresponding to a tag matching each second tag in the at least one second tag; Acquire configuration information corresponding to each determined first index value from the second data table; Based on the acquired configuration information, a query result regarding the query request is output.

5. The method according to claim 4, characterized in that The constructing at least one second tag based on at least one type of identification in the query request includes: constructing a third tag based on the user identifier and the application identifier in the query request, and constructing a fourth tag based on the category identifier and the version identifier of the big data engine in the query request; Combining the third label and the fourth label to obtain a second label of the first priority; Using a first set character to replace the user identifier and the application identifier in the second label of the first priority to obtain a second label of the second priority; The user identifier in the second tag of the first priority is replaced by a second set character to obtain a second tag of a third priority; wherein, The first priority is higher than the second priority; the second priority is higher than the third priority.

6. The method according to claim 5, characterized in that The configuration information includes at least one configuration item and a corresponding configuration parameter; and outputting a query result about the query request based on the acquired configuration information includes: Based on the configuration items included in the configuration information corresponding to each second tag and based on the priority corresponding to each second tag, determining the second configuration parameter corresponding to each configuration item from the first configuration parameters included in the acquired configuration information; Output each configuration item and the corresponding second configuration parameter.

7. A server, characterized in that: include: A receiving unit, configured to receive a data storage request; The data storage request carries at least one type of identification and configuration information; A construction unit, configured to construct a first label based on the at least one type of identification; an allocating unit, configured to allocate a first index value to the first tag; A storage unit, used to associate and store the first tag and the first index value in a first data table, and associate and store the first index value and the configuration information carried in the data storage request in a second data table; the configuration information is used to configure a big data engine; The building blocks are specifically used for: Based on the setting correspondence between at least two types of setting identifiers and setting label construction methods, determining the setting label construction methods corresponding to at least two types of identifiers carried in the data storage request; According to the determined setting label construction method, a first label corresponding to the at least two types of identifications is constructed.

8. A server, characterized in that: include: a processor and a memory for storing a computer program capable of being executed on the processor, Wherein, when the processor is used to run the computer program, it executes the steps of the method described in any one of claims 1 to 6.

9. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images