CN110780950B - Interface metadata management method, device, computer equipment and storage medium - Google Patents
Interface metadata management method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN110780950B CN110780950B CN201911015582.XA CN201911015582A CN110780950B CN 110780950 B CN110780950 B CN 110780950B CN 201911015582 A CN201911015582 A CN 201911015582A CN 110780950 B CN110780950 B CN 110780950B
- Authority
- CN
- China
- Prior art keywords
- metadata
- interface
- 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.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 66
- 238000000034 method Methods 0.000 claims abstract description 45
- 238000012360 testing method Methods 0.000 claims abstract description 32
- 238000004590 computer program Methods 0.000 claims description 14
- 238000004458 analytical method Methods 0.000 claims description 8
- 238000006243 chemical reaction Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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; CALCULATING OR 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; CALCULATING OR 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; a collector for transmitting the collected interface metadata to a metadata server; receiving the interface metadata through a collector of the metadata server and storing the interface metadata; and providing interface metadata query to the outside through an API so as to manage 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 the test is easy to miss caused by the split of the service.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for managing interface metadata, a computer device, and a storage medium.
Background
Metadata, generally defined as data describing data, is intended to facilitate access, management, sharing, and processing of large amounts of structured and/or unstructured data. The concept of metadata has been used in large numbers in reality over the past few years, such as 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 cooperate with each other to realize the service function. However, due to the split of the service, under the condition of lacking management of interface metadata, omission is easy to occur in test.
Disclosure of Invention
In view of the foregoing, it is desirable to provide an interface metadata management method, apparatus, computer device, and storage medium that implement interface metadata management in a micro-service framework.
An interface metadata management method, 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;
a collector for transmitting the collected interface metadata to a metadata server;
receiving the interface metadata through a collector of the metadata server and storing the interface metadata;
and providing interface metadata query to the outside through an API so as to manage the interface metadata.
In one embodiment, the step of collecting the 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 application Runner, and scanning and extracting interface metadata according to configuration in the run method;
judging whether the interface is a Controller interface according to the annotation, if so, extracting method information corresponding to the interface;
and judging whether the interface is a Dubbo interface according to the annotation, and if so, extracting metadata information corresponding to the interface from the registry.
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 which is processed inside the metadata server so as to support subsequent storage, analysis and display.
In one embodiment, the step of providing the interface metadata query to the outside through the API to manage the interface metadata further includes:
in the test tool, aiming at the same application program, interface metadata at different time points are selected for comparison to realize targeted 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 the 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 to the outside through an API so as to realize management of 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 application Runner, and scanning and extracting interface metadata according to configuration in the run method;
judging whether the interface is a Controller interface according to the annotation, if so, extracting method information corresponding to the interface;
and judging whether the interface is a Dubbo interface according to the annotation, and if so, extracting metadata information corresponding to the interface from the registry.
In one embodiment, the apparatus further comprises a metadata conversion module for:
and converting the received metadata information into a format which is 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 test tool, aiming at the same application program, interface metadata at different time points are selected for comparison to realize targeted 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 one of the methods described above when the computer program is executed.
A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of any of the methods described above.
The interface metadata management method, the device, the computer equipment and the storage medium are used for acquiring the interface metadata management request; collecting corresponding interface metadata after application service is started according to the interface metadata management request; a collector for transmitting the collected interface metadata to a metadata server; receiving the interface metadata through a collector of the metadata server and storing the interface metadata; and providing interface metadata query to the outside through an API so as to manage 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 the test is easy to miss caused by the split of the service. In addition, 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 dissimilarity of each start or each version of the service for targeted testing; thus, the test is more complete and the coverage is comprehensive.
Drawings
FIG. 1 is an application environment diagram of an interface metadata management method in one embodiment;
FIG. 2 is a diagram illustrating a data flow in an interface metadata management method according to an embodiment;
FIG. 3 is a flow diagram of a method of interface metadata management in one embodiment;
FIG. 4 is a flow chart of a method for managing interface metadata according to another embodiment;
FIG. 5 is a flow chart of a method of managing interface metadata in yet another embodiment;
FIG. 6 is a block diagram of an interface metadata management apparatus in one embodiment;
FIG. 7 is a block diagram illustrating an interface metadata management apparatus according to another embodiment;
fig. 8 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only 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, the method comprising:
step 302, obtaining 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, the collected interface metadata is sent 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;
in step 310, the interface metadata query is provided to the outside through the API to manage the interface metadata.
Specifically, the method for managing interface metadata provided in this embodiment may be applied to an application environment as shown in fig. 1, where the architecture of the application environment may specifically include:
collector: the collector component is mainly used for processing Metadata information sent from an external system and converting the Metadata information into a format of Metadata Server internal processing so as to support the subsequent functions of storage, analysis, display and the like. Storage: the storage component is used for storing the information received by the processing collector into the memory, and can also modify the storage strategy and store the information into the 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 based on an upper application realized by the API component, and a user can conveniently inquire and analyze metadata information through the UI component.
In connection with 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 acquired. Corresponding interface metadata is then collected after the application service is started according to the request. Specifically, metadata Client exists in the application, which is transparent to the user, and after the application service is started normally, metadata of the interface is collected, specifically for example: metadata of the Controller interface or the RPC interface. The data is then transmitted in several ways, for example: one of the Mq is sent to the Collector of the Metadata Server. Finally, metadata Server stores Metadata in Database, and the API provides query to the outside. Specifically, for example, in a testing tool, the interface metadata at different time points are selected for comparison with respect to the same application program, so that it is clear which changes are made to the interface, for example, the interface is added or modified, and the testing can be performed in a targeted manner.
In this embodiment, the metadata management request is acquired through the acquisition interface; collecting corresponding interface metadata after application service is started according to the interface metadata management request; a collector for transmitting the collected interface metadata to a metadata server; receiving the interface metadata through a collector of a metadata server and storing the interface metadata; and providing interface metadata query to the outside through an API so as to manage the interface metadata. The embodiment 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 occurs easily during testing caused by splitting the service. In addition, 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 dissimilarity of each start or each version of the service for targeted testing; thus, the test is more complete and the coverage is comprehensive.
In one embodiment, as shown in fig. 4, there is provided an interface metadata management method, where 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, and scanning and extracting interface metadata according to configuration in the run method;
step 404, judging whether the interface is a Controller interface according to the annotation, if so, extracting the method information corresponding to the interface;
and step 406, judging whether the interface is a Dubbo interface according to the annotation, and if so, extracting metadata information corresponding to the interface from the registry.
In this embodiment, a process of acquiring metadata in an interface metadata management method is specifically described, including:
firstly, after normal starting of the application is completed, 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, according to the annotation @ RestController, a decision is made as to the Controller interface, and then the method information is extracted.
Finally, according to the annotation @ org. Apoche. Dubbo. Config. Accounting. Service, @ org. Apoche. Dubbo. Config. Accounting. Reference, the Dubbo interface is determined, where Dubbo is one implementation type of RPC, and then metadata information of the Dubbo interface is extracted from the registry, and the Dubbo interface will store the metadata information to the registry at application start.
In one embodiment, the step of receiving, by the collector of the metadata server, the interface metadata further comprises: and converting the received metadata information into a format which is processed inside the metadata server so as to support subsequent storage, analysis and display.
In one embodiment, as shown in fig. 4, there is provided an interface metadata management method, in which the step of providing an interface metadata query to the outside through an API to implement management of the interface metadata further includes:
step 502, in the test tool, comparing the interface metadata of different time points for the same application program to realize targeted test;
step 504, query and analysis of interface metadata is performed through the UI component implemented based on the API.
In this embodiment, metadata Server stores Metadata in Database, and the API provides a 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 it is clear which changes are made to the interface, for example, the interface is added or modified, and the testing can be performed in a targeted manner. Through unified management of the interface metadata, the metadata of the interface can be provided for a testing tool to use and test; the method can also be used for comparing the dissimilarity of each start or each version of the service for targeted testing; thus, the test is more complete and the coverage is comprehensive.
In addition, the metadata information can be conveniently queried and analyzed by the UI component which is an upper layer application realized based on the API component.
It should be understood that, although the steps in the flowcharts of fig. 3-5 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in fig. 3-5 may include multiple sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the sub-steps or stages are performed necessarily occur sequentially, but may be performed alternately or alternately with at least a portion of the sub-steps or stages of other steps or other steps.
In one embodiment, as shown in fig. 6, there is provided an interface metadata management apparatus 600 comprising:
an obtaining module 601, configured to obtain an interface metadata management request;
the metadata collection module 602 is configured to collect corresponding interface metadata after the application service is started according to the interface metadata management request;
a metadata transmitting module 603 for transmitting the collected interface metadata to a collector of the metadata server;
a metadata storage module 604 for receiving interface metadata through a collector of the metadata server and storing the interface metadata;
the metadata management module 605 is configured to provide an interface metadata query to the outside through an API to implement management of the interface metadata.
In one embodiment, metadata collection module 602 is further to:
after the application service is started, automatically calling a run method in an implementation class of an interface application Runner, and scanning and extracting interface metadata according to configuration in the run method;
judging whether the interface is a Controller interface according to the annotation, if so, extracting method information corresponding to the interface;
and judging whether the interface is a Dubbo interface according to the annotation, and if so, extracting metadata information corresponding to the interface from the registry.
In one embodiment, as shown in fig. 7, there is provided an interface metadata management apparatus 600, which further includes a metadata conversion module 606 for:
and converting the received metadata information into a format which is processed inside the metadata server so as to support subsequent storage, analysis and display.
In one embodiment, the metadata management module 605 is further to:
in the test tool, aiming at the same application program, interface metadata at different time points are selected for comparison to realize targeted test;
and inquiring and analyzing the interface metadata through a UI component realized based on the API.
For specific limitations of the interface metadata management apparatus, reference may be made to the above limitations of the interface metadata management method, and no further description is given here.
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 includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements an interface metadata management method.
It will be appreciated by those skilled in the art that the structure shown in fig. 8 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided that includes a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the steps in the method embodiments above when executing the computer program.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, carries out the steps of the above method embodiments.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile 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), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples merely represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the invention. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.
Claims (6)
1. 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;
a collector for transmitting the collected interface metadata to a metadata server;
receiving the interface metadata through a collector of the metadata server and storing the interface metadata;
providing interface metadata query to the outside through an API so as to manage the interface metadata;
the step of providing the interface metadata query to the outside through the API to manage the interface metadata further includes: in the test tool, aiming at the same application program, interface metadata at different time points are selected for comparison to realize targeted test; inquiring and analyzing interface metadata through a UI component realized based on the API;
the step of collecting the 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 application Runner, and scanning and extracting interface metadata according to configuration in the run method; judging whether the interface is a Controller interface according to the annotation, if so, extracting method information corresponding to the interface; and judging whether the interface is a Dubbo interface according to the annotation, and if so, extracting metadata information corresponding to the interface from the registry.
2. The interface metadata management method according to claim 1, further comprising, after the step of receiving the interface metadata through the collector of the metadata server:
and converting the received metadata information into a format which is processed inside the metadata server so as to support subsequent storage, analysis and display.
3. 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 the 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;
the metadata management module is used for providing interface metadata inquiry to the outside through an API so as to realize management of the interface metadata;
the metadata management module is further configured to: in the test tool, aiming at the same application program, interface metadata at different time points are selected for comparison to realize targeted test; inquiring and analyzing interface metadata through a UI component realized based on the API;
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 application Runner, and scanning and extracting interface metadata according to configuration in the run method; judging whether the interface is a Controller interface according to the annotation, if so, extracting method information corresponding to the interface; and judging whether the interface is a Dubbo interface according to the annotation, and if so, extracting metadata information corresponding to the interface from the registry.
4. The interface metadata management apparatus of claim 3, wherein the apparatus further comprises a metadata conversion module for:
and converting the received metadata information into a format which is processed inside the metadata server so as to support subsequent storage, analysis and display.
5. 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 processor implements the steps of the method of claim 1 or 2 when executing the computer program.
6. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of claim 1 or 2.
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 CN110780950A (en) | 2020-02-11 |
| CN110780950B true 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) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111414194B (en) * | 2020-03-19 | 2023-08-11 | 政采云有限公司 | Method, system, electronic device and storage medium for generating interface information |
| CN111666205B (en) * | 2020-04-24 | 2023-07-11 | 杭州睿疆科技有限公司 | Data auditing method, system, computer equipment and storage medium |
| CN113242221B (en) * | 2021-04-29 | 2022-08-23 | 湖南快乐阳光互动娱乐传媒有限公司 | Protocol conversion method and protocol conversion device based on http micro-service gateway |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6996556B2 (en) * | 2002-08-20 | 2006-02-07 | International Business Machines Corporation | Metadata manager for database query optimizer |
| US8819080B2 (en) * | 2007-06-13 | 2014-08-26 | The Boeing Company | 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 |
-
2019
- 2019-10-24 CN CN201911015582.XA patent/CN110780950B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
|---|
| 数据仓库中实时元数据管理的研究;潘定等;《计算机工程》;20050930;第31卷(第17期);29-31 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110780950A (en) | 2020-02-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110209652B (en) | Data table migration method, device, computer equipment and storage medium | |
| CN109408746B (en) | Image information query method, image information query device, computer equipment and storage medium | |
| CN110780950B (en) | Interface metadata management method, device, computer equipment and storage medium | |
| CN110781143B (en) | Method and device for querying and extracting server logs | |
| CN111475376A (en) | Method and device for processing test data, computer equipment and storage medium | |
| CN112347165B (en) | Log processing method and device, server and computer readable storage medium | |
| WO2017174013A1 (en) | Data storage management method and apparatus, and data storage system | |
| CN108255735B (en) | Associated environment testing method, electronic device and computer readable storage medium | |
| CN110798445A (en) | Public gateway interface testing method and device, computer equipment and storage medium | |
| CN112732819A (en) | ETL-based data processing method, device, equipment and storage medium | |
| CN113014623A (en) | Method and device for processing real-time streaming data of embedded point, computer equipment and storage medium | |
| CN113918437B (en) | User behavior data analysis method, device, computer equipment and storage medium | |
| CN113660359B (en) | Domain name resolution record management method and device, storage medium and electronic equipment | |
| CN110457279B (en) | Data offline scanning method and device, server and readable storage medium | |
| CN113377789A (en) | Processing method and device for database change data, computer equipment and medium | |
| CN113158118A (en) | Page buried point data acquisition method, device and system | |
| CN109474386B (en) | Signaling tracking method, system, network element equipment and storage medium | |
| CN111984660A (en) | Data synchronization method, device, equipment and storage medium | |
| CN113761043B (en) | Data extraction method, device, computer equipment and storage medium | |
| CN113704203B (en) | A log file processing method and device | |
| CN110825459B (en) | Enumeration constant hot loading method, device, computer equipment and storage medium | |
| US8775528B2 (en) | Computer readable recording medium storing linking keyword automatically extracting program, linking keyword automatically extracting method and apparatus | |
| CN108183966A (en) | A kind of cloud stocking system | |
| CN113055243B (en) | DPI interface data processing method and device | |
| CN114254027B (en) | Data processing method, device, 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 |