CN111831274B - Metadata analysis engine configuration system, method, terminal and readable storage medium - Google Patents
Metadata analysis engine configuration system, method, terminal and readable storage medium Download PDFInfo
- Publication number
- CN111831274B CN111831274B CN202010603040.0A CN202010603040A CN111831274B CN 111831274 B CN111831274 B CN 111831274B CN 202010603040 A CN202010603040 A CN 202010603040A CN 111831274 B CN111831274 B CN 111831274B
- Authority
- CN
- China
- Prior art keywords
- metadata
- sql
- loader
- interface
- api
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24564—Applying rules; Deductive queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/907—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- Software Systems (AREA)
- Mathematical Physics (AREA)
- Library & Information Science (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a metadata analysis engine configuration system, a method, a terminal and a readable storage medium, comprising the following steps: a metadata engine subsystem; the metadata engine subsystem includes: a metadata loader, an interface renderer, an API component, an SQL constructor and an SQL executor; the metadata loader is respectively connected with the interface renderer and the API component and respectively pushes metadata to the interface renderer and the API component; the API component is respectively connected with the SQL constructor and the SQL executor; the API component sends a construction SQL control instruction to the SQL constructor; the SQL constructor constructs SQL and sends the executed SQL to the SQL executor; the SQL executor feeds back data to the API component after execution. The application can reduce the professional requirements of practitioners, improve the development efficiency and the construction quality, and effectively solve the problems encountered in informationized construction.
Description
Technical Field
The present application relates to the field of metadata processing technologies, and in particular, to a metadata parsing engine configuration system, a metadata parsing engine configuration method, a metadata parsing engine configuration terminal, and a readable storage medium.
Background
Metadata, also known as intermediate data, is data describing data, information describing attributes of the data, and is used to support functions such as indicating storage locations, history data, resource searching, file recording, and the like.
In the process of information project construction, the information project construction method can be divided into a data filling system, a flow approval system, a statistical analysis system, a big data computing system and a demand customization system according to service scenes, wherein about 10% of each service system has the same function (authority functions of organization, users, roles and the like), about 60% of each data filling system has the same filling function, about 70% of the flow approval system has the same flow, about 60% of documents have the same similarity, about 80% of the charts presented by the statistical analysis system have the same similarity and the like.
In the conventional development mode, each system function is realized by writing codes. On one hand, the complexity of the system has too high requirements on professional quality of the developer, so that the output quality can be ensured, and on the other hand, the repeated work of the similarity of system functions and the repeated generation of requirements occupies the project resource which is short, so that the informationized construction project personnel have the problems of high requirements, uneven output quality, long development period, low customer satisfaction, high input cost and the like.
Disclosure of Invention
In order to overcome the defects in the prior art, the application provides a method for reducing the threshold of a practitioner and saving the labor input; and unifying output standards and shielding schemes of quality differences caused by personnel differences. And more particularly to the four aspects.
The first aspect relates to a metadata parsing engine configuration system, comprising: a metadata engine subsystem;
the metadata engine subsystem includes: a metadata loader, an interface renderer, an API component, an SQL constructor and an SQL executor;
the metadata loader is respectively connected with the interface renderer and the API component and respectively pushes metadata to the interface renderer and the API component;
the API component is respectively connected with the SQL constructor and the SQL executor;
the API component sends a construction SQL control instruction to the SQL constructor;
the SQL constructor constructs SQL and sends the executed SQL to the SQL executor;
the SQL executor feeds back data to the API component after execution.
The metadata loader reads, loads and parses YAML metadata and DB metadata, respectively.
Preferably, the method further comprises: the platform loader, the Event loader and the Event cache;
the platform loader is respectively connected with the metadata loader and the Event loader;
the platform loader sends metadata calling instructions to the metadata loader and the Event loader respectively;
the Event loader injects a metadata call instruction into the Event cache;
and the metadata loader pushes metadata to the interface renderer and the API component according to the metadata call instruction.
Preferably, the method further comprises: caching metadata;
the metadata loader is connected with the metadata cache and injects metadata into the metadata cache;
the SQL constructor is connected with the metadata cache and reads the metadata in the metadata cache.
Preferably, the interface renderer is connected with the system display interface;
the API component connects with an API interface.
The SQL executor is connected with a metadata SQL cache.
The second aspect relates to a metadata parsing engine configuration method, the method comprising:
formulating standard metadata configuration specifications at a metadata configuration layer;
storing metadata in YAML files or databases, supporting real-time reading;
providing a metadata interface of the API component based on the metadata specification, and configuring metadata of the standard;
loading a metadata loader at a metadata analysis layer;
reading metadata configuration from the YAML file or database by metadata source identification;
calling a metadata loader to acquire metadata configuration, analyzing and converting the metadata according to parameters transferred by an API calling mode, and returning the metadata to an API calling party;
the interface renderer renders the metadata into a standard interface for output after acquiring the interface metadata;
modeling the metadata by the SQL constructor, configuring a data query port, and updating the SQL data;
the SQL executor executes SQL data processing;
metadata SQL caches cache common operations on metadata.
Preferably, the step of analyzing and converting the metadata according to the parameters transferred by the API calling mode and returning the metadata to the API calling party further comprises the following steps of; the API calling party is a client;
the client sends an interface request instruction to the API component;
the API component obtains an interface metadata inquirer from a metadata SQL cache;
querying interface metadata based on the interface metadata querier;
constructing an SQL executor;
acquiring metadata configuration specifications from an Event loader;
sending metadata configuration specifications through an Event cache;
executing an SQL executor;
and sending the metadata execution operation rule to the Event loader, and caching through the Event cache.
A third aspect relates to a terminal implementing a metadata parsing engine configuration system, comprising:
a memory for storing a computer program and a metadata parsing engine configuration system;
and the processor is used for executing the computer program and the metadata analysis engine configuration system to realize the metadata analysis engine configuration system.
A fourth aspect relates to a readable storage medium having a metadata parsing engine configuration system, the readable storage medium having a computer program stored thereon, the computer program being executable by a processor to implement the metadata parsing engine configuration system.
From the above technical scheme, the application has the following advantages:
the application abstracts the common content in the informatization construction process to form a metadata analysis engine, and sinks the change part into metadata configuration. The system carries out metadata configuration through the visual interface, and renders the metadata into standard system functions through an engine for output. The application can reduce the professional requirements of practitioners, improve the development efficiency and the construction quality, and effectively solve the problems encountered in informationized construction.
Drawings
In order to more clearly illustrate the technical solutions of the present application, the drawings that are needed in the description will be briefly introduced below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a metadata parsing engine configuration system;
FIG. 2 is a flowchart of an embodiment of a method for configuring a metadata parsing engine.
Detailed Description
Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the elements and steps of the examples have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices, or elements, or may be an electrical, mechanical, or other form of connection.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the application may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the application.
The application provides a metadata parsing engine configuration system, as shown in fig. 1, comprising: a metadata engine subsystem;
the metadata engine subsystem includes: a metadata loader 1, an interface renderer 2, an API component 3, an SQL builder 4, and an SQL executor 5;
the metadata loader 1 is respectively connected with the interface renderer 2 and the API component 3, and the metadata loader 1 respectively pushes metadata to the interface renderer 2 and the API component 3;
the API component 3 is respectively connected with the SQL constructor 4 and the SQL executor 5; the API component 3 sends a construction SQL control instruction to the SQL constructor 4; the SQL constructor 4 constructs SQL and sends the executed SQL to the SQL executor 5; the SQL executor 5 feeds back data to the API component 3 after execution.
Wherein the interface renderer 2 is connected with the system display interface 12; the API component 3 connects to an API interface 13. The system display interface may display the current state of the system, metadata loading process data, and so on.
The API interface is used as an interface for data communication, and can be used for receiving data, instructions, control information and the like transmitted outside the system.
The metadata loader 1 reads, loads and parses YAML metadata and DB metadata, respectively. That is, the metadata loader 1 may process YAML metadata as well as DB metadata. Wherein the method comprises the steps of
YAML metadata is a highly readable metadata used to express serialization of data. YAML may be based on a language comprising: c language, python, perl. YAML metadata in the system can be obtained from XML, the data format of e-mail.
The system according to the present application further comprises: a platform loader 6, an Event loader 7 and an Event cache 8;
the platform loader 6 is respectively connected with the metadata loader 1 and the Event loader 7; the platform loader 6 sends metadata call instructions to the metadata loader 1 and the Event loader 7 respectively; the Event loader 7 injects a metadata call instruction into the Event cache 8; the metadata loader 1 pushes metadata to the interface renderer 2 and the API component 3 according to a metadata call instruction.
The platform loader 6 can be used as a starting unit for starting the metadata analysis engine to load and start the metadata analysis engine, so that the metadata engine subsystem starts the program.
An embodiment of the present application further includes: a metadata cache 9; the metadata loader 1 is connected with the metadata cache 9, and injects metadata into the metadata cache 9; the SQL builder 4 is connected with the metadata cache 9 and reads metadata in the metadata cache 9.
The SQL executor 5 is connected with a metadata SQL cache 11.
Based on the system, the application also provides a metadata analysis engine configuration method, which comprises the following steps:
formulating standard metadata configuration specifications at a metadata configuration layer;
the standard metadata configuration specification may provide for metadata to be specified accordingly, such as:
the above table is an embodiment of the setting specification, and the specific form is not limited.
Storing metadata in YAML files or databases, supporting real-time reading;
providing a metadata interface of the API component based on the metadata specification, and configuring metadata of the standard;
loading a metadata loader at a metadata analysis layer;
reading metadata configuration from the YAML file or database by metadata source identification;
calling a metadata loader to acquire metadata configuration, analyzing and converting the metadata according to parameters transferred by an API calling mode, and returning the metadata to an API calling party;
here, the API caller is a client;
the client sends an interface request instruction to the API component;
the API component obtains an interface metadata inquirer from a metadata SQL cache;
querying interface metadata based on the interface metadata querier;
constructing an SQL executor;
acquiring metadata configuration specifications from an Event loader;
sending metadata configuration specifications through an Event cache;
executing an SQL executor;
and sending the metadata execution operation rule to the Event loader, and caching through the Event cache.
The interface renderer renders the metadata into a standard interface for output after acquiring the interface metadata;
modeling the metadata by the SQL constructor, configuring a data query port, and updating the SQL data;
the SQL executor executes SQL data processing;
metadata SQL caches cache common operations on metadata.
Therefore, the method is simple and easy to use, reduces the threshold of a practitioner, and saves the labor input; the application unifies the output standard and shields the quality difference caused by personnel difference. The method is suitable for various informationized scenes and is widely applied;
based on the system and the method, the application also provides a terminal for realizing the metadata analysis engine configuration system, which comprises the following steps:
a memory for storing a computer program and a metadata parsing engine configuration system;
and the processor is used for executing the computer program and the metadata analysis engine configuration system to realize the metadata analysis engine configuration system.
The present application also provides a readable storage medium having a metadata parsing engine configuration system, the readable storage medium having stored thereon a computer program for execution by a processor to implement the metadata parsing engine configuration system.
The terminals implementing the metadata parsing engine configuration system are the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein, can be implemented in electronic hardware, computer software, or a combination of both, and to clearly illustrate the interchangeability of hardware and software, the components and steps of the examples have been generally described in terms of functionality in the foregoing description. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
From the above description of the embodiments, it will be readily understood by those skilled in the art that the terminal for implementing the metadata parsing engine configuration system described herein may be implemented by software, or may be implemented by combining software with necessary hardware. Accordingly, the technical solution according to the disclosed embodiments of the configuration system for implementing the metadata parsing engine may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the indexing method according to the disclosed embodiments.
Implementation of the metadata parsing engine configuration system program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (9)
1. A metadata parsing engine configuration system, comprising: a metadata engine subsystem;
the metadata engine subsystem includes: a metadata loader, an interface renderer, an API component, an SQL constructor and an SQL executor;
the metadata loader is respectively connected with the interface renderer and the API component and respectively pushes metadata to the interface renderer and the API component;
the API component is respectively connected with the SQL constructor and the SQL executor;
the API component sends a construction SQL control instruction to the SQL constructor;
the SQL constructor constructs SQL and sends the executed SQL to the SQL executor;
after the SQL executor executes, feeding back data to the API component;
the metadata engine subsystem is realized based on a metadata analysis engine configuration method, and the method comprises the following steps:
formulating standard metadata configuration specifications at a metadata configuration layer;
storing metadata in YAML files or databases, supporting real-time reading;
providing a metadata interface of the API component based on the metadata specification, and configuring metadata of the standard;
loading a metadata loader at a metadata analysis layer;
reading metadata configuration from the YAML file or database by metadata source identification;
calling a metadata loader to acquire metadata configuration, analyzing and converting the metadata according to parameters transferred by an API calling mode, and returning the metadata to an API calling party;
the interface renderer renders the metadata into a standard interface for output after acquiring the interface metadata;
modeling the metadata by the SQL constructor, configuring a data query port, and updating the SQL data;
the SQL executor executes SQL data processing;
metadata SQL caches cache common operations on metadata.
2. The metadata parsing engine configuration system of claim 1, wherein,
the metadata loader reads, loads and parses YAML metadata and DB metadata, respectively.
3. The metadata parsing engine configuration system of claim 1, wherein,
further comprises: the platform loader, the Event loader and the Event cache;
the platform loader is respectively connected with the metadata loader and the Event loader;
the platform loader sends metadata calling instructions to the metadata loader and the Event loader respectively;
the Event loader injects a metadata call instruction into the Event cache;
and the metadata loader pushes metadata to the interface renderer and the API component according to the metadata call instruction.
4. The metadata parsing engine configuration system of claim 1, wherein,
further comprises: caching metadata;
the metadata loader is connected with the metadata cache and injects metadata into the metadata cache;
the SQL constructor is connected with the metadata cache and reads the metadata in the metadata cache.
5. The metadata parsing engine configuration system of claim 1, wherein,
the interface renderer is connected with the system display interface;
the API component connects with an API interface.
6. The metadata parsing engine configuration system of claim 1, wherein,
the SQL executor is connected with a metadata SQL cache.
7. The metadata parsing engine configuration system of claim 1, wherein,
analyzing and converting the metadata according to parameters transferred by the API calling mode, and returning the metadata to the API calling party further comprises; the API calling party is a client;
the client sends an interface request instruction to the API component;
the API component obtains an interface metadata inquirer from a metadata SQL cache;
querying interface metadata based on the interface metadata querier;
constructing an SQL executor;
acquiring metadata configuration specifications from an Event loader;
sending metadata configuration specifications through an Event cache;
executing an SQL executor;
and sending the metadata execution operation rule to the Event loader, and caching through the Event cache.
8. A terminal for implementing a metadata parsing engine configuration system, comprising:
a memory for storing a computer program and a metadata parsing engine configuration system;
a processor for executing the computer program and the metadata parsing engine configuration system to implement the metadata parsing engine configuration system according to any one of claims 1 to 7.
9. A readable storage medium having a metadata parsing engine configuration system, wherein the readable storage medium has stored thereon a computer program that is executed by a processor to implement the metadata parsing engine configuration system of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010603040.0A CN111831274B (en) | 2020-06-29 | 2020-06-29 | Metadata analysis engine configuration system, method, terminal and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010603040.0A CN111831274B (en) | 2020-06-29 | 2020-06-29 | Metadata analysis engine configuration system, method, terminal and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111831274A CN111831274A (en) | 2020-10-27 |
| CN111831274B true CN111831274B (en) | 2023-10-20 |
Family
ID=72898369
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010603040.0A Active CN111831274B (en) | 2020-06-29 | 2020-06-29 | Metadata analysis engine configuration system, method, terminal and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111831274B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103369367A (en) * | 2012-03-29 | 2013-10-23 | 索尼公司 | System and method to improve user experience with streaming content |
| CN104391892A (en) * | 2014-11-11 | 2015-03-04 | 成都锐理开创信息技术有限公司 | Real estate information access system based on metadata driving |
| CN105468345A (en) * | 2014-08-27 | 2016-04-06 | 厦门雅迅网络股份有限公司 | Method for remotely changing visit job at mobile phone end in fast moving consumer goods system |
| CN109582647A (en) * | 2018-11-21 | 2019-04-05 | 珠海市新德汇信息技术有限公司 | A kind of analysis method and system towards the unstructured instrument of evidence |
| CN110377621A (en) * | 2019-07-17 | 2019-10-25 | 深圳前海微众银行股份有限公司 | A kind of interface processing method and device based on computing engines |
| US10691653B1 (en) * | 2017-09-05 | 2020-06-23 | Amazon Technologies, Inc. | Intelligent data backfill and migration operations utilizing event processing architecture |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10489170B2 (en) * | 2017-06-19 | 2019-11-26 | Salesforce.Com, Inc. | Application warmup engine |
-
2020
- 2020-06-29 CN CN202010603040.0A patent/CN111831274B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103369367A (en) * | 2012-03-29 | 2013-10-23 | 索尼公司 | System and method to improve user experience with streaming content |
| CN105468345A (en) * | 2014-08-27 | 2016-04-06 | 厦门雅迅网络股份有限公司 | Method for remotely changing visit job at mobile phone end in fast moving consumer goods system |
| CN104391892A (en) * | 2014-11-11 | 2015-03-04 | 成都锐理开创信息技术有限公司 | Real estate information access system based on metadata driving |
| US10691653B1 (en) * | 2017-09-05 | 2020-06-23 | Amazon Technologies, Inc. | Intelligent data backfill and migration operations utilizing event processing architecture |
| CN109582647A (en) * | 2018-11-21 | 2019-04-05 | 珠海市新德汇信息技术有限公司 | A kind of analysis method and system towards the unstructured instrument of evidence |
| CN110377621A (en) * | 2019-07-17 | 2019-10-25 | 深圳前海微众银行股份有限公司 | A kind of interface processing method and device based on computing engines |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111831274A (en) | 2020-10-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108519967B (en) | Chart visualization method and device, terminal and storage medium | |
| CN108388622B (en) | API interface dynamic generation method and device, computer equipment and storage medium | |
| WO2019134340A1 (en) | Salary calculation method, application server, and computer readable storage medium | |
| CN110647316B (en) | Method and device for generating universal business object, computer equipment and storage medium | |
| CN113641700A (en) | Data processing method and device based on Spring boot frame | |
| WO2019161620A1 (en) | Application dependency update method, terminal and device, and storage medium | |
| CN114282129A (en) | Information system page generation method, system, electronic equipment and storage medium | |
| CN110109983B (en) | Method and device for operating Redis database | |
| CN108959294B (en) | Method and device for accessing search engine | |
| CN112613964A (en) | Account checking method, account checking device, account checking equipment and storage medium | |
| CN111831274B (en) | Metadata analysis engine configuration system, method, terminal and readable storage medium | |
| CN112100260A (en) | Interface engine-based multi-application data fusion method and system | |
| CN116611411A (en) | Business system report generation method, device, equipment and storage medium | |
| CN116561146A (en) | Database log recording method, device, computer equipment and computer readable storage medium | |
| CN114489674A (en) | Data verification method and device of dynamic data model | |
| CN117009397A (en) | Data query method, data query device, electronic equipment and storage medium | |
| CN113609128A (en) | Method and device for generating database entity class, terminal equipment and storage medium | |
| KR100545348B1 (en) | An integrated development system for a SyncML server application development | |
| CN113326230A (en) | Case state automatic identification and control method, system, electronic terminal and medium | |
| CN112199428B (en) | Application management system, method and terminal equipment of functional data block | |
| US11928423B1 (en) | Transaction entity prediction through learned embeddings | |
| CN114238292B (en) | Data cleaning method, device, computer equipment and computer readable storage medium | |
| CN109857390B (en) | Annotation transmission method of Git warehouse file annotation system | |
| CN113688152B (en) | System function self-checking method and device | |
| CN111782183B (en) | Method and device for judging component dependency, electronic device and 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 |