CN110780950A - Interface metadata management method and device, computer equipment and storage medium - Google Patents
Interface metadata management method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN110780950A CN110780950A CN201911015582.XA CN201911015582A CN110780950A CN 110780950 A CN110780950 A CN 110780950A CN 201911015582 A CN201911015582 A CN 201911015582A CN 110780950 A CN110780950 A CN 110780950A
- Authority
- CN
- China
- Prior art keywords
- interface
- metadata
- interface metadata
- management
- server
- 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 OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
- G06F9/4484—Executing subprograms
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
-
- 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)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to an interface metadata management method, an interface metadata management device, computer equipment and a storage medium, wherein the method comprises the following steps: acquiring an interface metadata management request; collecting corresponding interface metadata after application service is started according to the interface metadata management request; sending the collected interface metadata to a collector of a metadata server; receiving the interface metadata by a collector of the metadata server and storing the interface metadata; and providing an interface metadata query externally through the API so as to realize the management of the interface metadata. The invention realizes the unified management of the interface metadata by combining the characteristics of the micro-service architecture from the actual needs, and avoids the condition that omission easily occurs during testing caused by the split service.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for managing interface metadata, a computer device, and a storage medium.
Background
Metadata, generally defined as data that describes data, is intended to facilitate the access, management, sharing, and processing of large amounts of structured and/or unstructured data. In the last few years, the concept of metadata has been used extensively in reality, e.g. for supporting information retrieval, or for software configuration, or for data interaction between different systems.
In the traditional technology, in the development process of a micro-service framework, the original single application is split into a group of small services, and the services are mutually cooperated to realize the service function. But due to the split of the service, under the condition of lacking the management of the interface metadata, the omission condition is easy to occur during the test.
Disclosure of Invention
In view of the foregoing, it is desirable to provide an interface metadata management method, an interface metadata management apparatus, a computer device, and a storage medium for implementing interface metadata management in a microservice framework.
A method of interface metadata management, the method comprising:
acquiring an interface metadata management request;
collecting corresponding interface metadata after application service is started according to the interface metadata management request;
sending the collected interface metadata to a collector of a metadata server;
receiving the interface metadata by a collector of the metadata server and storing the interface metadata;
and providing an interface metadata query externally through the API so as to realize the management of the interface metadata.
In one embodiment, the step of collecting corresponding interface metadata after the application service is started according to the interface metadata management request further includes:
after the application service is started, automatically calling a run method in an implementation class of an interface ApplicationRunner, scanning according to configuration in the run method and extracting interface metadata;
judging whether the interface is a Controller interface or not according to the annotation, and if so, extracting method information corresponding to the interface;
and judging whether the interface is a Dubbo interface or not according to the annotation, and if so, extracting metadata information corresponding to the interface from the registration center.
In one embodiment, after the step of receiving the interface metadata by the collector of the metadata server, the method further comprises:
and converting the received metadata information into a format processed inside the metadata server so as to support subsequent storage, analysis and display.
In one embodiment, the step of providing an external interface metadata query through an API to manage the interface metadata further includes:
in the testing tool, aiming at the same application program, interface metadata of different time points are selected for comparison so as to realize the pertinence test;
and inquiring and analyzing the interface metadata through the UI component realized based on the API.
An interface metadata management apparatus, the apparatus comprising:
the acquisition module is used for acquiring an interface metadata management request;
the metadata collection module is used for collecting corresponding interface metadata after the application service is started according to the interface metadata management request;
the metadata sending module is used for sending the collected interface metadata to a collector of a metadata server;
the metadata storage module is used for receiving the interface metadata through a collector of the metadata server and storing the interface metadata;
and the metadata management module is used for providing interface metadata inquiry for the outside through an API (application programming interface) so as to manage the interface metadata.
In one embodiment, the metadata collection module is further configured to:
after the application service is started, automatically calling a run method in an implementation class of an interface ApplicationRunner, scanning according to configuration in the run method and extracting interface metadata;
judging whether the interface is a Controller interface or not according to the annotation, and if so, extracting method information corresponding to the interface;
and judging whether the interface is a Dubbo interface or not according to the annotation, and if so, extracting metadata information corresponding to the interface from the registration center.
In one embodiment, the apparatus further comprises a metadata conversion module configured to:
and converting the received metadata information into a format processed inside the metadata server so as to support subsequent storage, analysis and display.
In one embodiment, the metadata management module is further configured to:
in the testing tool, aiming at the same application program, interface metadata of different time points are selected for comparison so as to realize the pertinence test;
and inquiring and analyzing the interface metadata through the UI component realized based on the API.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of any of the above methods when executing the computer program.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of any of the methods described above.
The interface metadata management method, the device, the computer equipment and the storage medium acquire the interface metadata management request; collecting corresponding interface metadata after application service is started according to the interface metadata management request; sending the collected interface metadata to a collector of a metadata server; receiving the interface metadata by a collector of the metadata server and storing the interface metadata; and providing an interface metadata query externally through the API so as to realize the management of the interface metadata. The invention realizes the unified management of the interface metadata by combining the characteristics of the micro-service architecture from the actual needs, and avoids the condition that omission easily occurs during testing caused by the split service. In addition, the metadata of the interface can also be provided for a testing tool (such as Yapi) to use and test; the method can also be used for comparing the similarities and differences of each start-up or each version of the service, and is used for targeted testing; therefore, the test is more sufficient and the coverage is comprehensive.
Drawings
FIG. 1 is a diagram of an application environment of a method for interface metadata management in one embodiment;
FIG. 2 is a diagram illustrating a data flow in a method for interface metadata management according to an embodiment;
FIG. 3 is a flow diagram that illustrates a method for interface metadata management in one embodiment;
FIG. 4 is a flowchart illustrating a method for managing interface metadata according to another embodiment;
FIG. 5 is a flowchart illustrating a method for interface metadata management according to yet another embodiment;
FIG. 6 is a block diagram showing the structure of an interface metadata management apparatus according to an embodiment;
FIG. 7 is a block diagram showing the construction of an interface metadata management apparatus according to another embodiment;
FIG. 8 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further 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 present application and are not intended to limit the present application.
In one embodiment, as shown in fig. 3, there is provided an interface metadata management method including:
step 302, acquiring an interface metadata management request;
step 304, collecting corresponding interface metadata after the application service is started according to the interface metadata management request;
step 306, sending the collected interface metadata to a collector of a metadata server;
step 308, receiving the interface metadata through a collector of the metadata server, and storing the interface metadata;
and step 310, providing an interface metadata query externally through the API to realize management of the interface metadata.
Specifically, the interface metadata management method provided in this embodiment may be applied to an application environment as shown in fig. 1, and specifically may include, in a framework of the application environment:
a Collector: the collector component is mainly used for processing Metadata information sent from an external system and then converting the information into a format processed internally by the Metadata Server so as to support subsequent functions of storage, analysis, display and the like. Storage: the storage component is mainly used for storing the information received by the processing collector into a memory, and can also modify a storage strategy and store the information into a database by using other storage components. RestfulApi: the API component is mainly used for providing an external access interface, such as external system access. Web UI: and the UI component is an upper application realized based on the API component, and a user can conveniently inquire and analyze the metadata information through the UI component.
With reference to the schematic diagram of the data flow in the interface metadata management method shown in fig. 2, in this embodiment, first, an interface metadata management request is obtained. Then, corresponding interface metadata is collected after the application service is started according to the request. Specifically, Metadata Client exists in the application program, which is transparent to the user, and collects Metadata of the interface after the application service is normally started, specifically, for example: metadata of a Controller interface or an RPC interface. The data is then transmitted by several transmission means, for example: one of the HTTP, Mq is sent to the Collector of the Metadata Server. And finally, the Metadata Server stores the Metadata in Database, and the API provides the query for the outside. Specifically, for example, in a test tool, for the same application, the metadata of the interface at different time points are selected for comparison, so that it is clear what changes are made to the interface, for example, the interface is added or modified, and a targeted test can be performed.
In the embodiment, the request is managed by acquiring interface metadata; collecting corresponding interface metadata after the application service is started according to the interface metadata management request; sending the collected interface metadata to a collector of a metadata server; receiving the interface metadata through a collector of a metadata server and storing the interface metadata; and providing an interface metadata query externally through the API so as to realize the management of the interface metadata. The embodiment realizes the purpose of starting from actual needs, combines the characteristics of a micro-service architecture, provides the unified management of the interface metadata, and avoids the condition that omission easily occurs during the test caused by the split service. In addition, the metadata of the interface can also be provided for a testing tool (such as Yapi) to use and test; the method can also be used for comparing the similarities and differences of each start-up or each version of the service, and is used for targeted testing; therefore, the test is more sufficient and the coverage is comprehensive.
In one embodiment, as shown in fig. 4, there is provided an interface metadata management method, in which the step of collecting corresponding interface metadata after the application service is started according to the interface metadata management request further includes:
step 402, after the application service is started, automatically calling a run method in an implementation class of an interface application runner, scanning according to configuration in the run method, and extracting interface metadata;
step 404, judging whether the interface is a Controller interface or not according to the annotation, and if so, extracting method information corresponding to the interface;
and step 406, judging whether the interface is a Dubbo interface or not according to the annotation, and if so, extracting metadata information corresponding to the interface from the registration center.
In this embodiment, a process of acquiring metadata in an interface metadata management method is specifically described, including:
firstly, after the application is normally started, a run method in an implementation class of an interface application runner is automatically called, scanning is carried out in the run method according to configuration, and then metadata is extracted.
Then, based on the annotation @ RestController, it is determined to be a Controller interface, and then method information is extracted.
And finally, determining a Dubbo interface according to the annotations @ org.apache.dubbo.config.association.service, @ org.apache.dubbo.config.association.reference, wherein the Dubbo is an implementation type of RPC, extracting the metadata information of the Dubbo interface from the registration center, and storing the metadata information into the registration center by the Dubbo interface when the application is started.
In one embodiment, after the step of receiving the interface metadata by the collector of the metadata server, further comprising: and converting the received metadata information into a format processed inside the metadata server so as to support subsequent storage, analysis and display.
In one embodiment, as shown in fig. 4, an interface metadata management method is provided, in which the step of providing an external interface metadata query through an API to manage the interface metadata further includes:
step 502, in a testing tool, comparing interface metadata of different time points selected for the same application program to realize a pertinence test;
and step 504, inquiring and analyzing the interface metadata through the UI component realized based on the API.
In this embodiment, the Metadata Server stores the Metadata, and the API provides the query to the outside. For example: in the testing tool, for the same application program, the interface metadata at different time points are selected for comparison, so that the change of the interface can be clear, for example, the interface is added or modified, and the targeted test can be performed. Through the unified management of the interface metadata, the metadata of the interface can be provided for a test tool to use and test; the method can also be used for comparing the similarities and differences of each start-up or each version of the service, and is used for targeted testing; therefore, the test is more sufficient and the coverage is comprehensive.
In addition, through a UI component which is an upper application realized based on the API component, a user can conveniently inquire and analyze the metadata information.
It should be understood that although the various steps in the flow charts of fig. 3-5 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 3-5 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 6, there is provided an interface metadata management apparatus 600 including:
an obtaining module 601, configured to obtain an interface metadata management request;
a metadata collection module 602, configured to collect corresponding interface metadata after the application service is started according to the interface metadata management request;
a metadata sending module 603, configured to send the collected interface metadata to a collector of a metadata server;
a metadata storage module 604, configured to receive the interface metadata through a collector of the metadata server, and store the interface metadata;
a metadata management module 605, configured to provide an interface metadata query externally through the API to implement management of the interface metadata.
In one embodiment, the metadata collection module 602 is further configured to:
after the application service is started, automatically calling a run method in an implementation class of an interface ApplicationRunner, scanning according to configuration in the run method and extracting interface metadata;
judging whether the interface is a Controller interface or not according to the annotation, and if so, extracting method information corresponding to the interface;
and judging whether the interface is a Dubbo interface or not according to the annotation, and if so, extracting metadata information corresponding to the interface from the registration center.
In one embodiment, as shown in fig. 7, there is provided an interface metadata management apparatus 600, further comprising a metadata conversion module 606 for:
and converting the received metadata information into a format processed inside the metadata server so as to support subsequent storage, analysis and display.
In one embodiment, the metadata management module 605 is further configured to:
in the testing tool, aiming at the same application program, interface metadata of different time points are selected for comparison so as to realize the pertinence test;
and inquiring and analyzing the interface metadata through a UI component realized based on the API.
For specific definition of the interface metadata management device, reference may be made to the above definition of the interface metadata management method, which is not described herein again.
In one embodiment, a computer device is provided, the internal structure of which may be as shown in FIG. 8. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement an interface metadata management method.
Those skilled in the art will appreciate that the architecture shown in fig. 8 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the above method embodiments when executing the computer program.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the above respective method embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for interface metadata management, the method comprising:
acquiring an interface metadata management request;
collecting corresponding interface metadata after application service is started according to the interface metadata management request;
sending the collected interface metadata to a collector of a metadata server;
receiving the interface metadata by a collector of the metadata server and storing the interface metadata;
and providing an interface metadata query externally through the API so as to realize the management of the interface metadata.
2. The interface metadata management method according to claim 1, wherein the step of collecting corresponding interface metadata after the application service is started according to the interface metadata management request further comprises:
after the application service is started, automatically calling a run method in an implementation class of an interface ApplicationRunner, scanning according to configuration in the run method and extracting interface metadata;
judging whether the interface is a Controller interface or not according to the annotation, and if so, extracting method information corresponding to the interface;
and judging whether the interface is a Dubbo interface or not according to the annotation, and if so, extracting metadata information corresponding to the interface from the registration center.
3. The interface metadata management method according to claim 2, further comprising, after the step of receiving the interface metadata by the collector of the metadata server:
and converting the received metadata information into a format processed inside the metadata server so as to support subsequent storage, analysis and display.
4. The interface metadata management method according to any one of claims 1 to 3, wherein the step of providing an external interface metadata query through an API to implement management of the interface metadata further comprises:
in the testing tool, aiming at the same application program, interface metadata of different time points are selected for comparison so as to realize the pertinence test;
and inquiring and analyzing the interface metadata through the UI component realized based on the API.
5. An interface metadata management apparatus, the apparatus comprising:
the acquisition module is used for acquiring an interface metadata management request;
the metadata collection module is used for collecting corresponding interface metadata after the application service is started according to the interface metadata management request;
the metadata sending module is used for sending the collected interface metadata to a collector of a metadata server;
the metadata storage module is used for receiving the interface metadata through a collector of the metadata server and storing the interface metadata;
and the metadata management module is used for providing interface metadata inquiry for the outside through an API (application programming interface) so as to manage the interface metadata.
6. The interface metadata management apparatus of claim 5, wherein the metadata collection module is further configured to:
after the application service is started, automatically calling a run method in an implementation class of an interface ApplicationRunner, scanning according to configuration in the run method and extracting interface metadata;
judging whether the interface is a Controller interface or not according to the annotation, and if so, extracting method information corresponding to the interface;
and judging whether the interface is a Dubbo interface or not according to the annotation, and if so, extracting metadata information corresponding to the interface from the registration center.
7. The interface metadata management apparatus of claim 6, further comprising a metadata conversion module to:
and converting the received metadata information into a format processed inside the metadata server so as to support subsequent storage, analysis and display.
8. The interface metadata management apparatus of any of claims 5-7, wherein the metadata management module is further configured to:
in the testing tool, aiming at the same application program, interface metadata of different time points are selected for comparison so as to realize the pertinence test;
and inquiring and analyzing the interface metadata through the UI component realized based on the API.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 4 are implemented when the computer program is executed by the processor.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911015582.XA CN110780950B (en) | 2019-10-24 | 2019-10-24 | Interface metadata management method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911015582.XA CN110780950B (en) | 2019-10-24 | 2019-10-24 | Interface metadata management method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110780950A true CN110780950A (en) | 2020-02-11 |
| CN110780950B CN110780950B (en) | 2024-02-20 |
Family
ID=69387037
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911015582.XA Active CN110780950B (en) | 2019-10-24 | 2019-10-24 | Interface metadata management method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110780950B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111414194A (en) * | 2020-03-19 | 2020-07-14 | 政采云有限公司 | Interface information generation method, system, electronic device and storage medium |
| CN111666205A (en) * | 2020-04-24 | 2020-09-15 | 杭州传化智能制造科技有限公司 | Data auditing method, system, computer equipment and storage medium |
| CN113242221A (en) * | 2021-04-29 | 2021-08-10 | 湖南快乐阳光互动娱乐传媒有限公司 | Protocol conversion method and protocol conversion device based on http micro-service gateway |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040039729A1 (en) * | 2002-08-20 | 2004-02-26 | International Business Machines Corporation | Metadata manager for database query optimizer |
| US20080313207A1 (en) * | 2007-06-13 | 2008-12-18 | Chad Modad | System and method for collection, retrieval, and distribution of data |
| US20130055291A1 (en) * | 2011-08-31 | 2013-02-28 | Microsoft Corporation | Describing native application programming interfaces of an operating system with metadata |
| CN103634135A (en) * | 2012-08-24 | 2014-03-12 | 曙光信息产业(北京)有限公司 | Data acquisition method based on metadata |
| WO2014068749A1 (en) * | 2012-11-01 | 2014-05-08 | 株式会社日立製作所 | Metadata management system, metadata management method, and storage medium |
| CN104461863A (en) * | 2014-10-29 | 2015-03-25 | 中国建设银行股份有限公司 | Service system testing method, device and system |
| CN109739893A (en) * | 2018-12-28 | 2019-05-10 | 上海连尚网络科技有限公司 | A kind of metadata management method, equipment and computer-readable medium |
| CN110109617A (en) * | 2019-04-22 | 2019-08-09 | 电子科技大学 | A kind of Metadata Management method in encryption data deduplication system |
-
2019
- 2019-10-24 CN CN201911015582.XA patent/CN110780950B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040039729A1 (en) * | 2002-08-20 | 2004-02-26 | International Business Machines Corporation | Metadata manager for database query optimizer |
| US20080313207A1 (en) * | 2007-06-13 | 2008-12-18 | Chad Modad | System and method for collection, retrieval, and distribution of data |
| US20130055291A1 (en) * | 2011-08-31 | 2013-02-28 | Microsoft Corporation | Describing native application programming interfaces of an operating system with metadata |
| CN103634135A (en) * | 2012-08-24 | 2014-03-12 | 曙光信息产业(北京)有限公司 | Data acquisition method based on metadata |
| WO2014068749A1 (en) * | 2012-11-01 | 2014-05-08 | 株式会社日立製作所 | Metadata management system, metadata management method, and storage medium |
| CN104461863A (en) * | 2014-10-29 | 2015-03-25 | 中国建设银行股份有限公司 | Service system testing method, device and system |
| CN109739893A (en) * | 2018-12-28 | 2019-05-10 | 上海连尚网络科技有限公司 | A kind of metadata management method, equipment and computer-readable medium |
| CN110109617A (en) * | 2019-04-22 | 2019-08-09 | 电子科技大学 | A kind of Metadata Management method in encryption data deduplication system |
Non-Patent Citations (1)
| Title |
|---|
| 潘定等: "数据仓库中实时元数据管理的研究", 《计算机工程》, vol. 31, no. 17, 30 September 2005 (2005-09-30), pages 29 - 31 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111414194A (en) * | 2020-03-19 | 2020-07-14 | 政采云有限公司 | Interface information generation method, system, electronic device and storage medium |
| CN111414194B (en) * | 2020-03-19 | 2023-08-11 | 政采云有限公司 | Method, system, electronic device and storage medium for generating interface information |
| CN111666205A (en) * | 2020-04-24 | 2020-09-15 | 杭州传化智能制造科技有限公司 | Data auditing method, system, computer equipment and storage medium |
| CN113242221A (en) * | 2021-04-29 | 2021-08-10 | 湖南快乐阳光互动娱乐传媒有限公司 | Protocol conversion method and protocol conversion device based on http micro-service gateway |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110780950B (en) | 2024-02-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108965381B (en) | Nginx-based load balancing implementation method and device, computer equipment and medium | |
| CN110266752B (en) | Block chain information pushing method and device, computer equipment and storage medium | |
| CN111143163B (en) | Data monitoring method, device, computer equipment and storage medium | |
| US8055739B2 (en) | Sharing performance data between different information technology product/ solution deployments | |
| CN111159233B (en) | Distributed caching method, system, computer equipment and storage medium | |
| CN110780950A (en) | Interface metadata management method and device, computer equipment and storage medium | |
| CN113051162B (en) | Experimental test method, experimental test device, computer system and readable storage medium | |
| CN110213392B (en) | Data distribution method and device, computer equipment and storage medium | |
| CN113010224A (en) | Front-end micro-service method, device, computer equipment and storage medium | |
| CN111200523B (en) | Method, device, equipment and storage medium for configuring middle platform system | |
| US10223397B1 (en) | Social graph based co-location of network users | |
| CN111770022B (en) | Capacity expansion method, system, equipment and computer storage medium based on link monitoring | |
| CN111193789A (en) | Subscription information pushing method and device, computer equipment and readable storage medium | |
| US20150365308A1 (en) | Automatic transformation of messages between service versions | |
| CN109600381B (en) | Interface adaptation method, device and system | |
| CN109802842B (en) | Application topology generation method and related equipment | |
| CN115202800A (en) | Edge cloud service data processing method and device, computer equipment and storage medium | |
| CN111224939B (en) | Task request intercepting method and device, computer equipment and storage medium | |
| CN111274091A (en) | Log processing method and device, computer equipment and storage medium | |
| CN113592114A (en) | User fault reporting research and judgment method and device in power grid, computer equipment and storage medium | |
| CN110543509B (en) | Monitoring system, method and device for user access data and electronic equipment | |
| CN119292735A (en) | Virtual machine tuning method, system, electronic device and readable storage medium | |
| CN109474386B (en) | Signaling tracking method, system, network element equipment and storage medium | |
| CN113132961B (en) | Internet of things complete machine equipment debugging method and device, computer equipment and storage medium | |
| CN110825459B (en) | Enumeration constant hot loading method, device, computer 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 |