CN112463735A - Method for splitting large-volume JSON file and requesting according to needs - Google Patents
Method for splitting large-volume JSON file and requesting according to needs Download PDFInfo
- Publication number
- CN112463735A CN112463735A CN202011349468.3A CN202011349468A CN112463735A CN 112463735 A CN112463735 A CN 112463735A CN 202011349468 A CN202011349468 A CN 202011349468A CN 112463735 A CN112463735 A CN 112463735A
- Authority
- CN
- China
- Prior art keywords
- volume
- json
- layer
- json file
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/13—File access structures, e.g. distributed indices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method for splitting a large-volume JSON file and requesting the file as required, which comprises the following steps: the development end sends the large-volume JSON file which needs to be stored in a split mode and a predefined splitting rule to the server end; the server traverses the large-volume JSON file according to a predefined rule, generates a new small-volume JSON file from the traversed node content meeting the requirement, and replaces the corresponding node content with a corresponding identifier in the large-volume JSON file; the user end requests the required content according to the requirement. Has the advantages that: according to the method, on the basis of not damaging the original data structure of the JSON file with the large volume, the JSON file with the large volume is split into the plurality of related JSON files with the small volume and stored in the server side, so that each user side needing to use the JSON files can request the needed JSON file as required conveniently, and the efficiency and experience of requesting the needed JSON file by the user side are improved.
Description
Technical Field
The invention belongs to the technical field of information processing, and particularly relates to a method for splitting a large-volume JSON file and requesting the file as required.
Background
A JSON (JavaScript Object Notation) format file is a lightweight data exchange format file, and is widely applied to a front end, a back end, a client end, and the like because of its characteristics of simple format, support of multiple development languages, small size, and the like.
In the development process, related information such as resources, data and the like is configured in a JSON file and stored in a server. When the method is used, the JSON file of the server is pulled, and corresponding functions are performed according to the JSON content.
In the process of implementing the invention, the inventor finds that the prior art has at least the following problems:
as version iteration and development time of a project increase, the project will become larger and the volume of the configured JSON file is also increasing, thereby causing the following problems:
(1) when a user side requests a page of the JSON file from a server side, the request time is long and a large amount of bandwidth and time are consumed in the request process because the JSON file is large in size; in addition, due to objective reasons such as network fluctuation, the JSON file request often fails, thereby reducing the user experience of the user terminal.
(2) In addition, after the complete JSON file is requested from the server to the client, the client usually only needs to use a small number of fields in the JSON file, and for a large number of fields in the JSON file, the client has no actual use value, and the client also occupies the storage resources.
In order to solve the above problems, the prior art adopts the following two methods:
(1) in the process of developing and configuring the JSON file, resources are put into different JSON files, so that a plurality of JSON files with smaller volumes are formed.
(2) And circulating the whole large-volume JSON file, setting a length condition, and when the length is reached, placing the file content of the length into a new JSON file so as to form a plurality of small-volume JSON files.
In the two ways of splitting the large-volume JSON file into the small-volume JSON files, when a user side uses the small-volume JSON files, the relevance among the small-volume JSON files is often inconvenient to understand, and the integral data structure of the original large-volume JSON file is easy to damage.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a method for splitting a large-volume JSON file and requesting the file as required, which can effectively solve the problems.
The technical scheme adopted by the invention is as follows:
the invention provides a method for splitting a large-volume JSON file and requesting the file as required, which comprises the following steps:
step 1, a development end sends a large-volume JSON file which needs to be stored in a split mode and a predefined splitting rule to a server end; the splitting rule comprises a volume minimum threshold M1 of the small-volume JSON file and a layer number maximum threshold M2 allowed by the small-volume JSON file;
step 2, the structure form of the large-volume JSON file is as follows: the key-value pair formed by multilayer nesting; wherein, the key K is positioned in the root directory0Is a main key, the key K0All descendant nodes and leaf nodes of the key K0Value V of0；
The key K0The method comprises the steps that a plurality of sub nodes located in a layer 1 directory are provided, and each sub node is a layer 1 key or a layer 1 value; all descendant nodes and leaf nodes of each layer 1 key are value values of the layer 1 key;
for each layer 1 key, there are multiple children located in the layer 2 directory, each child being a layer 2 key or a layer 2 value; all descendant nodes and leaf nodes of each 2 nd-layer key are value values of the 2 nd-layer key;
and so on, forming a multi-layer nested large-volume JSON file structure; wherein, the nodes corresponding to the value values of each layer without sub-nodes are leaf nodes; for the nodes corresponding to the key keys of each layer with the sub-nodes, the nodes are connection nodes;
step 3, the large-volume JSON file has n layers from top to bottom, namely a 1 st layer, a 2 nd layer and an nth layer; all nodes of the nth layer are leaf nodes; nodes from level 2 to level n, including leaf nodes and/or junction nodes;
the server firstly traverses all leaf nodes of the large-volume JSON file, and each traversed leaf node is represented as a leaf node C0Judging the leavesNode C0Whether the volume of the corresponding value is larger than a volume minimum threshold value M1, and if so, executing the step 4; if not, continuing to perform traversal operation on the next leaf node;
step 4, leaf node C0The corresponding value generates a new small-volume JSON file D0And then a new small-volume JSON file D for unique identification is generated0Identifier T of0New small-sized JSON file D0Using an identifier T0Naming; then, in the large-volume JSON file, the leaf node C is connected0Identifier T for corresponding value0Replacement;
the process is continuously circulated until all leaf nodes C in the JSON file with large volume are finished0Thus obtaining a large-volume JSON file after one-time processing;
step 5, the server performs secondary traversal on the primarily processed large-volume JSON file, wherein the traversal mode is as follows:
the server traverses each connection node of the n-1 th layer of the once-processed large-volume JSON file, and represents each traversed connection node of the n-1 th layer as a connection node C of the n-1 th layern-1Judging the n-1 th layer connection node Cn-1If the volume of all the descendant nodes is larger than the volume minimum threshold value M1, if so, executing step 6; if not, executing step 7; after traversing all the connection nodes of the (n-1) th layer, executing the step 8;
step 6, connecting the n-1 st layer with the node Cn-1All the descendant nodes are guaranteed to be unchanged in the connection structure between the descendants, and a new JSON file D with small volume is generatedn-1And then a new small-volume JSON file D for unique identification is generatedn-1Identifier T ofn-1New small-sized JSON file Dn-1Using an identifier Tn-1Naming; then, in the once processed large-volume JSON file, the n-1 layer connection node C is connected withn-1All descendant nodes of (1) use identifier Tn-1Replacement; then returning to step 5 to continue to connect the nodes C to other n-1 layern-1Traversing;
step 7, further judging the n-1 st layer connection node Cn-1Whether the number of layers of the current descendant nodes reaches the maximum threshold value M2 of the number of layers, if not, returning to the step 5, and continuing to connect the nodes C of the other (n-1) th layern-1Traversing; if yes, returning to the step 6;
and 8, the server performs three times of traversal on the large-volume JSON file after the secondary processing by adopting the methods from the step 5 to the step 7, namely: traversing each connecting node of the (n-2) th layer of the secondarily processed JSON file, and continuously circulating in such a way until the traversal of each connecting node of the 2 nd layer is completed; at the moment, the original JSON file with large volume is changed into a JSON index file with small volume by adopting an identifier replacement mode, and a JSON file group formed by a plurality of related new JSON files with small volume is obtained at the same time; moreover, the file structure of the JSON index file is the same as that of the original large-volume JSON file; the IP address of the JSON index file is the same as that of the original large-volume JSON file;
step 9, the user side sends a request message for acquiring the JSON file corresponding to the IP address to the server side; the server locates the JSON index file through the IP address and sends the JSON index file to the user side;
step 10, a user side receives a complete JSON index file with small volume, analyzes and reads the content of the JSON index file, and sends a request for obtaining the content of a first target identifier to a server side when specific content corresponding to the first target identifier needs to be read;
step 11, the server searches a JSON file group formed by the small-volume JSON files according to the first target identifier to obtain corresponding small-volume JSON files, and sends the small-volume JSON files to the user side;
step 12, after receiving the small-volume JSON file, the user side analyzes and reads the small-volume JSON file, and if the small-volume JSON file still has a certain second target identifier needing to be read, the user side obtains the small-volume JSON file corresponding to the second target identifier from the server side; the method is repeated, and the effect that the user side requests the content of the JSON file according to the requirement is achieved.
Preferably, in step 4, a new small-volume JSON file D for uniquely identifying is generated0Identifier T of0As a new small-sized JSON file D0MD5 value of (a).
The method for splitting the large-volume JSON file and requesting the large-volume JSON file according to the requirement, provided by the invention, has the following advantages:
on the basis of not damaging the original data structure of the JSON file with the large volume, the JSON file with the large volume is split into a plurality of related JSON files with small volume and stored in a server, so that each user side needing to use the JSON files can conveniently request the needed JSON file as required, and the efficiency and experience of requesting the needed JSON file by the user side are improved.
Drawings
Fig. 1 is a schematic flow diagram of a method for splitting a large-volume JSON file and requesting the JSON file as needed according to the present invention.
Detailed Description
In order to make the technical problems, technical solutions and advantageous effects solved by the present invention more clearly apparent, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The invention provides a method for splitting a large-volume JSON file and requesting the JSON file as required, which splits the large-volume JSON file into a plurality of related small-volume JSON files on the basis of not damaging the data structure of the original large-volume JSON file and stores the small-volume JSON files in a server, so that each user side needing to use the JSON files can request the required JSON file as required conveniently, and the efficiency and experience of requesting the required JSON file by the user side are improved. Referring to fig. 1, the method for splitting and requesting a large-volume JSON file on demand includes the following steps:
step 1, a development end sends a large-volume JSON file which needs to be stored in a split mode and a predefined splitting rule to a server end; the splitting rule comprises a volume minimum threshold M1 of the small-volume JSON file and a layer number maximum threshold M2 allowed by the small-volume JSON file;
step 2, the structure form of the large-volume JSON file is as follows: the key-value pair formed by multilayer nesting; wherein, the key K is positioned in the root directory0Is a main key, the key K0All descendant nodes and leaf nodes of the key K0Value V of0；
The key K0The method comprises the steps that a plurality of sub nodes located in a layer 1 directory are provided, and each sub node is a layer 1 key or a layer 1 value; all descendant nodes and leaf nodes of each layer 1 key are value values of the layer 1 key;
for each layer 1 key, there are multiple children located in the layer 2 directory, each child being a layer 2 key or a layer 2 value; all descendant nodes and leaf nodes of each 2 nd-layer key are value values of the 2 nd-layer key;
and so on, forming a multi-layer nested large-volume JSON file structure; wherein, the nodes corresponding to the value values of each layer without sub-nodes are leaf nodes; for the nodes corresponding to the key keys of each layer with the sub-nodes, the nodes are connection nodes;
step 3, the large-volume JSON file has n layers from top to bottom, namely a 1 st layer, a 2 nd layer and an nth layer; all nodes of the nth layer are leaf nodes; nodes from level 2 to level n, including leaf nodes and/or junction nodes;
the server firstly traverses all leaf nodes of the large-volume JSON file, and each traversed leaf node is represented as a leaf node C0Judging leaf node C0Whether the volume of the corresponding value is larger than a volume minimum threshold value M1, and if so, executing the step 4; if not, continuing to perform traversal operation on the next leaf node;
step 4, leaf node C0The corresponding value generates a new small-volume JSON file D0And then a new small-volume JSON file D for unique identification is generated0Identifier T of0New small-sized JSON fileD0Using an identifier T0Naming; then, in the large-volume JSON file, the leaf node C is connected0Identifier T for corresponding value0Replacement;
the process is continuously circulated until all leaf nodes C in the JSON file with large volume are finished0Thus obtaining a large-volume JSON file after one-time processing;
in practical application, a new small-volume JSON file D for unique identification is generated0Identifier T of0As a new small-sized JSON file D0MD5 value of (a).
Step 5, the server performs secondary traversal on the primarily processed large-volume JSON file, wherein the traversal mode is as follows:
the server traverses each connection node of the n-1 th layer of the once-processed large-volume JSON file, and represents each traversed connection node of the n-1 th layer as a connection node C of the n-1 th layern-1Judging the n-1 th layer connection node Cn-1If the volume of all the descendant nodes is larger than the volume minimum threshold value M1, if so, executing step 6; if not, executing step 7; after traversing all the connection nodes of the (n-1) th layer, executing the step 8;
step 6, connecting the n-1 st layer with the node Cn-1All the descendant nodes are guaranteed to be unchanged in the connection structure between the descendants, and a new JSON file D with small volume is generatedn-1And then a new small-volume JSON file D for unique identification is generatedn-1Identifier T ofn-1New small-sized JSON file Dn-1Using an identifier Tn-1Naming; then, in the once processed large-volume JSON file, the n-1 layer connection node C is connected withn-1All descendant nodes of (1) use identifier Tn-1Replacement; then returning to step 5 to continue to connect the nodes C to other n-1 layern-1Traversing;
step 7, further judging the n-1 st layer connection node Cn-1Whether the number of the layers of the current descendant nodes reaches the maximum threshold value M2 of the number of the layers, if not, returning to the step 5, and continuing to connect other n-1-th layer junctionsPoint Cn-1Traversing; if yes, returning to the step 6;
and 8, the server performs three times of traversal on the large-volume JSON file after the secondary processing by adopting the methods from the step 5 to the step 7, namely: traversing each connecting node of the (n-2) th layer of the secondarily processed JSON file, and continuously circulating in such a way until the traversal of each connecting node of the 2 nd layer is completed; at the moment, the original JSON file with large volume is changed into a JSON index file with small volume by adopting an identifier replacement mode, and a JSON file group formed by a plurality of related new JSON files with small volume is obtained at the same time; moreover, the file structure of the JSON index file is the same as that of the original large-volume JSON file; the IP address of the JSON index file is the same as that of the original large-volume JSON file;
step 9, the user side sends a request message for acquiring the JSON file corresponding to the IP address to the server side; the server locates the JSON index file through the IP address and sends the JSON index file to the user side;
step 10, a user side receives a complete JSON index file with small volume, analyzes and reads the content of the JSON index file, and sends a request for obtaining the content of a first target identifier to a server side when specific content corresponding to the first target identifier needs to be read;
step 11, the server searches a JSON file group formed by the small-volume JSON files according to the first target identifier to obtain corresponding small-volume JSON files, and sends the small-volume JSON files to the user side;
step 12, after receiving the small-volume JSON file, the user side analyzes and reads the small-volume JSON file, and if the small-volume JSON file still has a certain second target identifier needing to be read, the user side obtains the small-volume JSON file corresponding to the second target identifier from the server side; the method is repeated, and the effect that the user side requests the content of the JSON file according to the requirement is achieved.
Experiments prove that the original JSON file with large volume reaches dozens of M or even dozens of M, the volume of the JSON index file obtained after the splitting of the process can be only hundreds of KB, the JSON index file is mainly used for recording key fields and structural relations among the key fields, the volume of each JSON file with small volume formed after the splitting is obviously reduced, and the effect that a user side requests the JSON file as required is achieved.
The invention provides a method for splitting a large-volume JSON file and requesting the file as required, which has the following advantages:
(1) the invention is a technology for splitting a large-volume JSON file into a plurality of associated small-volume JSON files, on the basis of not destroying the data structure of the original large-volume JSON file, the large-volume JSON file is split into a plurality of associated small-volume JSON files and stored in a server, so that each user side needing to use the JSON files can request the required JSON file as required conveniently, and the efficiency and experience of requesting the required JSON file by the user side are improved;
(2) in the development process, the data structure of the JSON file of the main body is not required to be split, and meanwhile, the splitting rule can be configured and finally the server side can automatically split the JSON file; therefore, the corresponding splitting rule can be flexibly changed according to the requirement, and the advantage of flexibly splitting the large-size JSON file according to different requirements is achieved.
(3) For each user side needing to use the JSON file, only a small-volume JSON index file is required, and on one hand, the user side can comprehensively know the original data structure of the large-volume JSON file through the JSON index file; on the other hand, according to the JSON index file, the position in which the user is interested can be located according to the key field, then according to the identifier behind the key field, the on-demand request of the target small-volume JSON file is realized, the on-demand loading of the content is realized, and the relation among the small-volume JSON files does not need to be really known in the using process.
(4) The loading on demand is realized, unnecessary waste of bandwidth is reduced, the request time is reduced, the probability of failure in requesting the JSON file with large volume due to network fluctuation and the like is reduced, and the user experience is improved.
(5) In the aspect of user experience, the waiting time for requesting the JSON index file (namely the main JSON file) for the first time is effectively reduced, and the experience is improved.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements should also be considered within the scope of the present invention.
Claims (2)
1. A method for splitting a large-volume JSON file and requesting the file as required is characterized by comprising the following steps:
step 1, a development end sends a large-volume JSON file which needs to be stored in a split mode and a predefined splitting rule to a server end; the splitting rule comprises a volume minimum threshold M1 of the small-volume JSON file and a layer number maximum threshold M2 allowed by the small-volume JSON file;
step 2, the structure form of the large-volume JSON file is as follows: the key-value pair formed by multilayer nesting; wherein, the key K is positioned in the root directory0Is a main key, the key K0All descendant nodes and leaf nodes of the key K0Value V of0；
The key K0The method comprises the steps that a plurality of sub nodes located in a layer 1 directory are provided, and each sub node is a layer 1 key or a layer 1 value; all descendant nodes and leaf nodes of each layer 1 key are value values of the layer 1 key;
for each layer 1 key, there are multiple children located in the layer 2 directory, each child being a layer 2 key or a layer 2 value; all descendant nodes and leaf nodes of each 2 nd-layer key are value values of the 2 nd-layer key;
and so on, forming a multi-layer nested large-volume JSON file structure; wherein, the nodes corresponding to the value values of each layer without sub-nodes are leaf nodes; for the nodes corresponding to the key keys of each layer with the sub-nodes, the nodes are connection nodes;
step 3, the large-volume JSON file has n layers from top to bottom, namely a 1 st layer, a 2 nd layer and an nth layer; all nodes of the nth layer are leaf nodes; nodes from level 2 to level n, including leaf nodes and/or junction nodes;
the server firstly traverses all leaf nodes of the large-volume JSON file, and each traversed leaf node is represented as a leaf node C0Judging leaf node C0Whether the volume of the corresponding value is larger than a volume minimum threshold value M1, and if so, executing the step 4; if not, continuing to perform traversal operation on the next leaf node;
step 4, leaf node C0The corresponding value generates a new small-volume JSON file D0And then a new small-volume JSON file D for unique identification is generated0Identifier T of0New small-sized JSON file D0Using an identifier T0Naming; then, in the large-volume JSON file, the leaf node C is connected0Identifier T for corresponding value0Replacement;
the process is continuously circulated until all leaf nodes C in the JSON file with large volume are finished0Thus obtaining a large-volume JSON file after one-time processing;
step 5, the server performs secondary traversal on the primarily processed large-volume JSON file, wherein the traversal mode is as follows:
the server traverses each connection node of the n-1 th layer of the once-processed large-volume JSON file, and represents each traversed connection node of the n-1 th layer as a connection node C of the n-1 th layern-1Judging the n-1 th layer connection node Cn-1If the volume of all the descendant nodes is larger than the volume minimum threshold value M1, if so, executing step 6; if not, executing step 7; after traversing all the connection nodes of the (n-1) th layer, executing the step 8;
step 6, connecting the n-1 st layer with the node Cn-1All the descendant nodes are guaranteed to be unchanged in the connection structure between the descendants, and a new JSON file D with small volume is generatedn-1And then a new small-volume JSON file D for unique identification is generatedn-1Identifier T ofn-1New small-sized JSON file Dn-1Using an identifier Tn-1Naming; then, at oneConnecting the n-1 layer with the node C in the JSON file with large volume after secondary processingn-1All descendant nodes of (1) use identifier Tn-1Replacement; then returning to step 5 to continue to connect the nodes C to other n-1 layern-1Traversing;
step 7, further judging the n-1 st layer connection node Cn-1Whether the number of layers of the current descendant nodes reaches the maximum threshold value M2 of the number of layers, if not, returning to the step 5, and continuing to connect the nodes C of the other (n-1) th layern-1Traversing; if yes, returning to the step 6;
and 8, the server performs three times of traversal on the large-volume JSON file after the secondary processing by adopting the methods from the step 5 to the step 7, namely: traversing each connecting node of the (n-2) th layer of the secondarily processed JSON file, and continuously circulating in such a way until the traversal of each connecting node of the 2 nd layer is completed; at the moment, the original JSON file with large volume is changed into a JSON index file with small volume by adopting an identifier replacement mode, and a JSON file group formed by a plurality of related new JSON files with small volume is obtained at the same time; moreover, the file structure of the JSON index file is the same as that of the original large-volume JSON file; the IP address of the JSON index file is the same as that of the original large-volume JSON file;
step 9, the user side sends a request message for acquiring the JSON file corresponding to the IP address to the server side; the server locates the JSON index file through the IP address and sends the JSON index file to the user side;
step 10, a user side receives a complete JSON index file with small volume, analyzes and reads the content of the JSON index file, and sends a request for obtaining the content of a first target identifier to a server side when specific content corresponding to the first target identifier needs to be read;
step 11, the server searches a JSON file group formed by the small-volume JSON files according to the first target identifier to obtain corresponding small-volume JSON files, and sends the small-volume JSON files to the user side;
step 12, after receiving the small-volume JSON file, the user side analyzes and reads the small-volume JSON file, and if the small-volume JSON file still has a certain second target identifier needing to be read, the user side obtains the small-volume JSON file corresponding to the second target identifier from the server side; the method is repeated, and the effect that the user side requests the content of the JSON file according to the requirement is achieved.
2. The method for splitting and requesting the JSON file with large volume according to claim 1, wherein in step 4, a new JSON file D with small volume for uniquely identifying is generated0Identifier T of0As a new small-sized JSON file D0MD5 value of (a).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011349468.3A CN112463735B (en) | 2020-11-26 | 2020-11-26 | Method for splitting large-volume JSON file and requesting according to needs |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011349468.3A CN112463735B (en) | 2020-11-26 | 2020-11-26 | Method for splitting large-volume JSON file and requesting according to needs |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112463735A true CN112463735A (en) | 2021-03-09 |
| CN112463735B CN112463735B (en) | 2023-04-07 |
Family
ID=74808855
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011349468.3A Active CN112463735B (en) | 2020-11-26 | 2020-11-26 | Method for splitting large-volume JSON file and requesting according to needs |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112463735B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113128208A (en) * | 2021-04-26 | 2021-07-16 | 浙江百应科技有限公司 | JSON file parsing method and device and electronic equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170109371A1 (en) * | 2015-10-14 | 2017-04-20 | Beijing Baidu Netcom Science And Technology, Ltd. | Method and Apparatus for Processing File in a Distributed System |
| CN110618983A (en) * | 2019-08-15 | 2019-12-27 | 复旦大学 | JSON document structure-based industrial big data multidimensional analysis and visualization method |
| CN111552899A (en) * | 2020-03-20 | 2020-08-18 | 广联达科技股份有限公司 | Method and system for improving display performance of front-end report |
-
2020
- 2020-11-26 CN CN202011349468.3A patent/CN112463735B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170109371A1 (en) * | 2015-10-14 | 2017-04-20 | Beijing Baidu Netcom Science And Technology, Ltd. | Method and Apparatus for Processing File in a Distributed System |
| CN110618983A (en) * | 2019-08-15 | 2019-12-27 | 复旦大学 | JSON document structure-based industrial big data multidimensional analysis and visualization method |
| CN111552899A (en) * | 2020-03-20 | 2020-08-18 | 广联达科技股份有限公司 | Method and system for improving display performance of front-end report |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113128208A (en) * | 2021-04-26 | 2021-07-16 | 浙江百应科技有限公司 | JSON file parsing method and device and electronic equipment |
| CN113128208B (en) * | 2021-04-26 | 2024-01-05 | 浙江百应科技有限公司 | JSON file analysis method and device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112463735B (en) | 2023-04-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8321503B2 (en) | Context-specific network resource addressing model for distributed services | |
| US7664742B2 (en) | Index data structure for a peer-to-peer network | |
| CN108446376B (en) | Data storage method and device | |
| WO2015110062A1 (en) | Distributed data storage method, device and system | |
| US11221921B2 (en) | Method, electronic device and computer readable storage medium for data backup and recovery | |
| CN109766318B (en) | File reading method and device | |
| WO2013010432A1 (en) | Method, node and system for data storage and query in peer network | |
| US20140244794A1 (en) | Information System, Method and Program for Managing the Same, Method and Program for Processing Data, and Data Structure | |
| CN108282525B (en) | Video resource management system and method based on peer-to-peer network | |
| Von der Weth et al. | Multiterm keyword search in NoSQL systems | |
| CN112463735B (en) | Method for splitting large-volume JSON file and requesting according to needs | |
| JP2008102795A (en) | File management device, system, and program | |
| US20150106468A1 (en) | Storage system and data access method | |
| CN109144514B (en) | JSON format data analysis and storage method and device | |
| WO2016177027A1 (en) | Batch data query method and device | |
| US10761685B2 (en) | Intelligent REST client for operating a data storage system | |
| CN109818948B (en) | Application deployment method, device, system, equipment and medium | |
| CN106649847A (en) | A large data real-time processing system based on Hadoop | |
| CN114579061B (en) | Data storage method, device, equipment and medium | |
| CN103685453B (en) | The acquisition methods of metadata in a kind of cloud storage system | |
| US11205049B2 (en) | Method for managing semantic information on M2M/IoT platform | |
| CN102801757A (en) | Processing method and system for data de-duplication of point-to-point transmission | |
| US10762139B1 (en) | Method and system for managing a document search index | |
| CN112035413B (en) | Metadata information query method, device and storage medium | |
| CN115185997A (en) | Host information processing method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |