CN117827982A - Distributed management method and device for product data, computer equipment and medium - Google Patents
Distributed management method and device for product data, computer equipment and medium Download PDFInfo
- Publication number
- CN117827982A CN117827982A CN202311696865.1A CN202311696865A CN117827982A CN 117827982 A CN117827982 A CN 117827982A CN 202311696865 A CN202311696865 A CN 202311696865A CN 117827982 A CN117827982 A CN 117827982A
- Authority
- CN
- China
- Prior art keywords
- data
- product
- file
- warehouse
- index
- 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.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 53
- 238000000034 method Methods 0.000 claims abstract description 38
- 238000004590 computer program Methods 0.000 claims description 15
- 238000004519 manufacturing process Methods 0.000 claims description 2
- 238000012423 maintenance Methods 0.000 abstract description 10
- 238000010586 diagram Methods 0.000 description 6
- 238000013500 data storage Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 3
- 239000003795 chemical substances by application Substances 0.000 description 2
- 230000002085 persistent effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 239000004575 stone Substances 0.000 description 1
- 238000000547 structure data Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- 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
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The application relates to the technical field of Internet and discloses a distributed management method, a device, computer equipment and a medium for product data, wherein the method comprises the steps of determining the type of a product according to the product data, user data and warehouse data when receiving an instruction for uploading the product file; uploading the product file to an object storage system OSS according to the product type to generate file path information; determining index data corresponding to the product file according to preset maven index information and the file path information; and uploading the index data and the product file to a MySQL database to complete distributed Maven warehouse deployment. By the method, corresponding file path information is generated in the OSS according to different product types. Index data of the product file is generated according to the file path information and the preset index information so as to guide the product file to be uploaded to the MySQL database, and therefore deployment and maintenance efficiency of the enterprise-level user product library is improved.
Description
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to a method, an apparatus, a computer device, and a medium for distributed management of product data.
Background
In Java CI (persistent integration)/CD (persistent deployment) engineering, we typically use Maven's dependency system to manage dependencies of the build, including system development, which is also widely used. The Maven warehouse system is a very important foundation stone in the whole engineering system. The central warehouse of the domestic agent generally only provides downloading capability, or becomes a user of the domestic agent but cannot customize requirements, and data security cannot be guaranteed. A stable, reliable and efficient Maven warehouse system not only can facilitate the daily development work of developers, but also can facilitate the project engineering management of enterprise level, and reasonably utilizes and plans the warehouse, thereby reducing the resource waste. The Maven private library is a hard function required by many enterprises. A high performance system must support lateral capacity expansion capability, tenant-level data isolation, underlying data storage reliability, and containerized deployment, which are capabilities that are currently necessary for cloud services.
In the prior art, the design of the Maven warehouse mainly provides the using capability of the warehouse, including an open source version and a commercial version, and has certain limitations. Taking an open source Nexus OSS as an example, the latest version of the open source Nexus OSS does not support high availability and does not support multi-tenant; the business version of the cloud service system supports high availability, but is used for cloud service, encounters service performance bottlenecks, does not support transverse multi-node capacity expansion, and only supports a certain number of tenants. Therefore, how to improve the deployment and maintenance efficiency of the enterprise-class user product library becomes a technical problem to be solved.
Disclosure of Invention
The application provides a distributed management method, a distributed management device, computer equipment and a distributed management medium for product data, so as to improve the deployment and maintenance efficiency of an enterprise-level user product library.
In a first aspect, the present application provides a method of distributed management of article data, the method comprising:
when receiving an instruction for uploading the product file, determining the type of the product according to the product data, the user data and the warehouse data;
uploading the product file to an object storage system OSS according to the product type to generate file path information;
determining index data corresponding to the product file according to preset maven index information and the file path information;
and uploading the index data and the product file to a MySQL database to complete distributed Maven warehouse deployment.
Further, the distributed management method of the product data further comprises the following steps:
when receiving an instruction for downloading the product file, determining the warehouse data and the product data according to the user data and the product type;
judging whether the product data exists in the MySQL database or not;
and downloading the product data under the condition that the product data exists in the MySQL database.
Further, after determining whether the product data exists in the MySQL database, the method further includes:
and reading the product data from the OSS according to the index data under the condition that the product data does not exist in the MySQL database.
Further, after determining whether the product data exists in the MySQL database, the method further includes:
reading external warehouse data of at least one external warehouse in the absence of the product data in the OSS;
traversing each external warehouse data, and matching the product data with each external warehouse data;
in each of the external warehouse data, external warehouse data matching the product data exists, and the traversal is terminated.
Further, traversing each of the external warehouse data, matching the product data with each external warehouse data, comprising:
and if the external warehouse data does not comprise the product data, sending a prompt identification to indicate that the product file does not exist.
Further, when receiving the instruction for uploading the product file, before determining the product type according to the product data, the user data and the warehouse data, the method comprises the following steps:
and determining whether the instruction for uploading the product file is a legal instruction or not based on a preset load balancing strategy and the user data.
Further, the index data includes: warehouse name, tenant ID, artifact path, artifact version number, store OSS file path, maven-metadata. Xml file path information, and the artifact type.
In a second aspect, the present application further provides a distributed management apparatus for product data, the apparatus comprising:
the product type determining module is used for determining the product type according to the product data, the user data and the warehouse data when receiving the command for uploading the product file;
the file path information generation module is used for uploading the product file to an object storage system OSS according to the product type to generate file path information;
the index data determining module is used for determining index data corresponding to the product file according to preset maven index information and the file path information;
and the product file uploading module is used for uploading the index data and the product file to a MySQL database to complete distributed Maven warehouse deployment.
In a third aspect, the present application also provides a computer device comprising a memory and a processor; the memory is used for storing a computer program; the processor is configured to execute the computer program and implement the distributed management method of the product data as described above when the computer program is executed.
In a fourth aspect, the present application also provides a computer readable storage medium storing a computer program, which when executed by a processor causes the processor to implement a method for distributed management of product data as described above.
The application discloses a distributed management method, a device, computer equipment and a medium of product data, wherein the distributed management method of the product data comprises the steps of determining the type of a product according to the product data, user data and warehouse data when receiving an instruction for uploading a product file; uploading the product file to an object storage system OSS according to the product type to generate file path information; determining index data corresponding to the product file according to preset maven index information and the file path information; and uploading the index data and the product file to a MySQL database to complete distributed Maven warehouse deployment. By the method, corresponding file path information is generated in the OSS according to different product types. Index data of the product file is generated according to the file path information and the preset index information so as to guide the product file to be uploaded to the MySQL database, and therefore deployment and maintenance efficiency of the enterprise-level user product library is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic flow chart of a method of distributed management of article data provided by a first embodiment of the present application;
FIG. 2 is a schematic flow chart of a method of distributed management of article data provided by a second embodiment of the present application;
FIG. 3 is a schematic block diagram of a distributed management apparatus for product data provided by an embodiment of the present application;
fig. 4 is a schematic block diagram of a computer device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The flow diagrams depicted in the figures are merely illustrative and not necessarily all of the elements and operations/steps are included or performed in the order described. For example, some operations/steps may be further divided, combined, or partially combined, so that the order of actual execution may be changed according to actual situations.
It is to be understood that the terminology used in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
The embodiment of the application provides a distributed management method, a distributed management device, computer equipment and a distributed management medium for product data. The distributed management method of the product data can be applied to a server, and corresponding file path information is generated in an OSS according to different product types. Index data of the product file is generated according to the file path information and the preset index information so as to guide the product file to be uploaded to the MySQL database, and therefore deployment and maintenance efficiency of the enterprise-level user product library is improved. The server may be an independent server or a server cluster.
Some embodiments of the present application are described in detail below with reference to the accompanying drawings. The following embodiments and features of the embodiments may be combined with each other without conflict.
Referring to fig. 1, fig. 1 is a schematic flow chart of a method for distributed management of product data according to a first embodiment of the present application. The distributed management method of the product data can be applied to a server and used for generating corresponding file path information in an OSS according to different product types. Index data of the product file is generated according to the file path information and the preset index information so as to guide the product file to be uploaded to the MySQL database, and therefore deployment and maintenance efficiency of the enterprise-level user product library is improved.
As shown in fig. 1, the method for distributed management of product data specifically includes steps S10 to S40.
Step S10, when receiving an instruction for uploading the product file, determining the type of the product according to the product data, the user data and the warehouse data;
step S20, uploading the product file to an object storage system OSS according to the product type to generate file path information;
step S30, determining index data corresponding to the product file according to preset maven index information and the file path information;
and step S40, uploading the index data and the product file to a MySQL database to complete distributed Maven warehouse deployment.
In one embodiment, the main engineering architecture of the embodiment is built on the basis of Springboot2, and mainly comprises the following four major modules: gateway authentication module, metadata storage module, index data storage module, OSS object storage module.
The gateway authentication module mainly works to be responsible for user information authentication, judges whether the request is legal or not, and then forwards the flow to a corresponding back-end RM example according to a load balancing strategy so as to finish authentication load work;
the data storage module mainly works to store tenant, account information of a user, product record information uploaded by the user, warehouse metadata information and used elastic search, OSS file system information into a MySQL database, so that maintenance and management are facilitated, and a statistical report is generated;
the index data storage module is mainly responsible for storing the index data of the warehouse file of the user into the elastic search, so that the processing speed of the request can be increased, the file information required by the user can be quickly searched and positioned, and the product can be conveniently and quickly pulled;
the OSS object storage module mainly works to store warehouse file data onto a corresponding OSS object storage file system, so that an RM system can shield file storage capacity expansion pressure, avoid operations such as host disk capacity expansion and the like, select different OSS storage according to the affiliated areas (east China, north China, south China and the like), lighten single OSS cluster pressure, ensure data safety and ensure that data among all instances are not needed to be synchronized.
In one embodiment, the user uploads the article flow steps:
the first step: uploading the Maven dependency structure data to the RM back-end instance by a user through an RM front-end page and a Maven reply command;
and a second step of: after the RM reads the product data, the RM acquires the current tenant data and the user warehouse data according to the user data, and determines the product type (release/snapshot) through the version attribute in the dependency;
and a third step of: uploading the product to a corresponding OSS object storage system according to the type of the product, wherein the product comprises maven-metadata.xml, a product source file, md5 and sha1 check files;
fourth step: the file path information and the description maven index information obtained after being uploaded to an OSS file system are all written into an elastic search to construct necessary RM index data, so that positioning of file data is quickened;
fifth step: after the index data is stored, the record information uploaded by the user is stored in Mysql, so that the user can conveniently check the record, and statistics is carried out on RM resources used by the user to make a data report.
In one embodiment, the following are some of the main statistics structures:
warehouse user table:
| field name | Meaning of field |
| User_name | Member user name |
| Role_id | Character id |
| User_id | User id |
| Tenant_id | Tenant id |
| Is_owner | Whether or not it is the warehouse owner |
The table is responsible for storing warehouse user information, including tenants to which the users belong, roles of the users, and whether the identification is a warehouse owner or not, and the warehouse owner has the authority of managing tenant private libraries;
warehouse account list:
| field name | Meaning of field |
| Account_name | Account name |
| pwd | Cipher (ciphertext) |
| User_id | User id |
| Tenant_id | Tenant id |
| Is_init_settings | Whether to initialize settings |
The table is responsible for storing warehouse user account information, is convenient for gateway authentication use, contains basic information of users and tenant information, and identifies whether maven settings.xml has been initialized or not, and is used for jenkins pipeline pulling maven products;
warehouse base table:
the table is responsible for storing the dependent external system elastic search and oss file system, and using the corresponding external system according to the belonged area, thereby relieving the pressure of a single elasticsearch, oss cluster and accessing the external system authentication connection by utilizing the Auth_code;
warehouse information table:
this table is responsible for storing user-allocated repository information, including the accessed uri addresses, including release and snapshot libraries, and recording elasticsearch, oss information on which the repository article storage needs to rely, as well as the tenant information, since the repository is initialized according to the tenant information, the repository owner is responsible for managing the repository;
warehouse color chart:
| field name | Meaning of field |
| Role_id | Character id |
| Role_name | Character name |
| Role_group | Role group |
| Role_desc | Role description |
The table is responsible for storing character constant information of the current system, and comprises three types of characters of an administrator, a developer and a common member, wherein the three types of characters have the following operation rights:
the embodiment discloses a distributed management method, a device, computer equipment and a medium of product data, wherein the distributed management method of the product data comprises the steps of determining the type of a product according to the product data, user data and warehouse data when receiving an instruction for uploading a product file; uploading the product file to an object storage system OSS according to the product type to generate file path information; determining index data corresponding to the product file according to preset maven index information and the file path information; and uploading the index data and the product file to a MySQL database to complete distributed Maven warehouse deployment. By the method, corresponding file path information is generated in the OSS according to different product types. Index data of the product file is generated according to the file path information and the preset index information so as to guide the product file to be uploaded to the MySQL database, and therefore deployment and maintenance efficiency of the enterprise-level user product library is improved.
Referring to fig. 2, fig. 2 is a schematic flowchart of a method for distributed management of product data according to a second embodiment of the present application. The distributed management method of the product data can be applied to a server and used for generating corresponding file path information in an OSS according to different product types. Index data of the product file is generated according to the file path information and the preset index information so as to guide the product file to be uploaded to the MySQL database, and therefore deployment and maintenance efficiency of the enterprise-level user product library is improved.
Based on the embodiment shown in fig. 1, the method for distributed management of product data in this embodiment shown in fig. 2 specifically further includes steps S50 to S70.
Step S50, when receiving an instruction for downloading a product file, determining the warehouse data and the product data according to the user data and the product type;
step S60, judging whether the product data exists in the MySQL database;
and step S70, downloading the product data under the condition that the product data exist in the MySQL database.
In one embodiment, the user download article flow steps are as follows:
the first step: the RM instance receives a Maven product message requested by a user, takes org/apache/Maven/apache-Maven/3.8.4/apache-Maven-3.8.4-bin.tar.gz as an example, and obtains corresponding warehouse metadata according to user information and product type (release, snapshot);
and a second step of: reading corresponding maven-metadata. Xml metadata, and obtaining metadata information of the product description;
and a third step of: after the product information is determined, the product data is read from the local cache firstly, the product data is directly returned if the product data is available, and the index data is not checked;
fourth step: in the index data, according to the data information stored in the index data, the oss file system data is directly read, otherwise, other warehouse information is required to be obtained from the Group to which the user belongs;
fifth step: according to the obtained other warehouse information, the corresponding warehouses are sequentially accessed according to the traversing sequence from top to bottom, the data is directly returned after being searched, and after all the warehouses are traversed, the data cannot be found yet, so that the file is prompted to be absent 404.
The embodiment discloses a distributed management method, a device, a computer device and a medium of product data, wherein the distributed management method of the product data comprises the steps of determining warehouse data and product data according to user data and product types when receiving an instruction for downloading a product file; judging whether the product data exists in the MySQL database or not; and downloading the product data under the condition that the product data exists in the MySQL database. By the method, corresponding file path information is generated in the OSS according to different product types. Index data of the product file is generated according to the file path information and the preset index information so as to guide the product file to be uploaded to the MySQL database, and therefore deployment and maintenance efficiency of the enterprise-level user product library is improved.
Based on the embodiment shown in fig. 2, after step S70, the method further includes:
and reading the product data from the OSS according to the index data under the condition that the product data does not exist in the MySQL database.
Based on the above embodiment, in this embodiment, after determining whether the product data exists in the MySQL database, the method further includes:
reading external warehouse data of at least one external warehouse in the absence of the product data in the OSS;
traversing each external warehouse data, and matching the product data with each external warehouse data;
in each of the external warehouse data, external warehouse data matching the product data exists, and the traversal is terminated.
In one embodiment, traversing each of the external warehouse data, matching the product data to each external warehouse data, comprises:
and if the external warehouse data does not comprise the product data, sending a prompt identification to indicate that the product file does not exist.
Based on the embodiment shown in fig. 1, in this embodiment, step S10 includes:
and determining whether the instruction for uploading the product file is a legal instruction or not based on a preset load balancing strategy and the user data.
Based on any of the above embodiments, in this embodiment, the index data includes: warehouse name, tenant ID, artifact path, artifact version number, store OSS file path, maven-metadata. Xml file path information, and the artifact type.
Referring to fig. 3, fig. 3 is a schematic block diagram of a distributed management apparatus for product data, which is used to perform the foregoing method for distributed management of product data according to an embodiment of the present application. Wherein the distributed management device of the product data can be configured on a server.
As shown in fig. 3, the distributed management apparatus for product data includes:
the product type determining module 410 is configured to determine a product type according to product data, user data, and warehouse data when receiving an instruction to upload a product file;
the file path information generating module 420 is configured to upload the product file to the object storage system OSS according to the product type, and generate file path information;
the index data determining module 430 is configured to determine index data corresponding to the product file according to preset maven index information and the file path information;
and the product file uploading module 440 is configured to upload the index data and the product file to a MySQL database to complete the distributed Maven repository deployment.
Further, the distributed management device for product data further includes:
the product file downloading instruction module is used for determining the warehouse data and the product data according to the user data and the product type when receiving a product file downloading instruction;
the product data judging module is used for judging whether the product data exists in the MySQL database or not;
and the product data downloading module is used for downloading the product data under the condition that the product data exists in the MySQL database.
Further, the distributed management device for product data further includes:
and the product data reading module is used for reading the product data from the OSS according to the index data under the condition that the product data does not exist in the MySQL database.
Further, the distributed management device for product data further includes:
an external warehouse data reading module for reading external warehouse data of at least one external warehouse in the absence of the product data in the OSS;
the product data matching module is used for traversing each external warehouse data and matching the product data with each external warehouse data;
and the termination traversal module is used for terminating traversal if the external warehouse data matched with the product data exists in each external warehouse data.
Further, the distributed management device for product data further includes:
and the prompt identification module is used for sending out prompt identification to indicate that the product file does not exist if the external warehouse data does not comprise the product data.
Further, the distributed management device for product data further includes:
and the instruction validity judging module is used for determining whether the instruction of the uploaded product file is a legal instruction or not based on a preset load balancing strategy and the user data.
It should be noted that, for convenience and brevity of description, the specific working process of the apparatus and each module described above may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
The apparatus described above may be implemented in the form of a computer program which is executable on a computer device as shown in fig. 4.
Referring to fig. 4, fig. 4 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device may be a server.
With reference to FIG. 4, the computer device includes a processor, memory, and a network interface connected by a system bus, where the memory may include a non-volatile storage medium and an internal memory.
The non-volatile storage medium may store an operating system and a computer program. The computer program comprises program instructions that, when executed, cause the processor to perform any of a number of methods of distributed management of product data.
The processor is used to provide computing and control capabilities to support the operation of the entire computer device.
The internal memory provides an environment for the execution of a computer program in a non-volatile storage medium that, when executed by a processor, causes the processor to perform any of a number of methods for distributed management of manufactured data.
The network interface is used for network communication such as transmitting assigned tasks and the like. Those skilled in the art will appreciate that the structures shown in FIG. 4 are block diagrams only and do not constitute a limitation of the computer device on which the present aspects apply, and that a particular computer device may include more or less components than those shown, or may combine some of the components, or have a different arrangement of components.
It should be appreciated that the processor may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital SignalProcessor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field-programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. Wherein the general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Wherein in one embodiment the processor is configured to run a computer program stored in the memory to implement the steps of:
when receiving an instruction for uploading the product file, determining the type of the product according to the product data, the user data and the warehouse data;
uploading the product file to an object storage system OSS according to the product type to generate file path information;
determining index data corresponding to the product file according to preset maven index information and the file path information;
and uploading the index data and the product file to a MySQL database to complete distributed Maven warehouse deployment.
In one embodiment, the distributed management method of the product data is further used for realizing:
when receiving an instruction for downloading the product file, determining the warehouse data and the product data according to the user data and the product type;
judging whether the product data exists in the MySQL database or not;
and downloading the product data under the condition that the product data exists in the MySQL database.
In one embodiment, after determining whether the artifact data exists in the MySQL database, the method is further configured to:
and reading the product data from the OSS according to the index data under the condition that the product data does not exist in the MySQL database.
In one embodiment, after determining whether the artifact data exists in the MySQL database, the method is further configured to:
reading external warehouse data of at least one external warehouse in the absence of the product data in the OSS;
traversing each external warehouse data, and matching the product data with each external warehouse data;
in each of the external warehouse data, external warehouse data matching the product data exists, and the traversal is terminated.
In one embodiment, after traversing each of the external warehouse data and matching the product data to each external warehouse data, the method is used to implement:
and if the external warehouse data does not comprise the product data, sending a prompt identification to indicate that the product file does not exist.
In one embodiment, upon receiving an instruction to upload an artifact file, prior to determining the artifact type based on the artifact data, the user data, and the warehouse data, the instructions are configured to:
and determining whether the instruction for uploading the product file is a legal instruction or not based on a preset load balancing strategy and the user data.
Embodiments of the present application further provide a computer readable storage medium, where the computer readable storage medium stores a computer program, where the computer program includes program instructions, and the processor executes the program instructions to implement a method for distributed management of any article of manufacture data provided in the embodiments of the present application.
The computer readable storage medium may be an internal storage unit of the computer device according to the foregoing embodiment, for example, a hard disk or a memory of the computer device. The computer readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, which are provided on the computer device.
While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method of distributed management of product data, comprising:
when receiving an instruction for uploading the product file, determining the type of the product according to the product data, the user data and the warehouse data;
uploading the product file to an object storage system OSS according to the product type to generate file path information;
determining index data corresponding to the product file according to preset maven index information and the file path information;
and uploading the index data and the product file to a MySQL database to complete distributed Maven warehouse deployment.
2. The method of distributed management of article of manufacture data of claim 1, further comprising:
when receiving an instruction for downloading the product file, determining the warehouse data and the product data according to the user data and the product type;
judging whether the product data exists in the MySQL database or not;
and downloading the product data under the condition that the product data exists in the MySQL database.
3. The method of claim 2, wherein after determining whether the artifact data exists in the MySQL database, further comprising:
and reading the product data from the OSS according to the index data under the condition that the product data does not exist in the MySQL database.
4. The method of claim 3, wherein after determining whether the artifact data exists in the MySQL database, further comprising:
reading external warehouse data of at least one external warehouse in the absence of the product data in the OSS;
traversing each external warehouse data, and matching the product data with each external warehouse data;
in each of the external warehouse data, external warehouse data matching the product data exists, and the traversal is terminated.
5. The method of distributed management of product data according to claim 4, wherein said traversing each of said external warehouse data, after matching said product data with each external warehouse data, comprises:
and if the external warehouse data does not comprise the product data, sending a prompt identification to indicate that the product file does not exist.
6. The method of claim 1, wherein upon receiving the instruction to upload the product file, the method further comprises, before determining the product type based on the product data, the user data, and the repository data:
and determining whether the instruction for uploading the product file is a legal instruction or not based on a preset load balancing strategy and the user data.
7. The distributed management method of article data according to any one of claims 1 to 6, wherein the index data includes: warehouse name, tenant ID, artifact path, artifact version number, store OSS file path, maven-metadata. Xml file path information, and the artifact type.
8. A distributed management apparatus for product data, comprising:
the product type determining module is used for determining the product type according to the product data, the user data and the warehouse data when receiving the command for uploading the product file;
the file path information generation module is used for uploading the product file to an object storage system OSS according to the product type to generate file path information;
the index data determining module is used for determining index data corresponding to the product file according to preset maven index information and the file path information;
and the product file uploading module is used for uploading the index data and the product file to a MySQL database to complete distributed Maven warehouse deployment.
9. A computer device, the computer device comprising a memory and a processor;
the memory is used for storing a computer program;
the processor being configured to execute the computer program and to implement the method of distributed management of article data according to any one of claims 1 to 7 when the computer program is executed.
10. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, causes the processor to implement the distributed management method of the article data according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311696865.1A CN117827982A (en) | 2023-12-11 | 2023-12-11 | Distributed management method and device for product data, computer equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311696865.1A CN117827982A (en) | 2023-12-11 | 2023-12-11 | Distributed management method and device for product data, computer equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117827982A true CN117827982A (en) | 2024-04-05 |
Family
ID=90514447
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311696865.1A Pending CN117827982A (en) | 2023-12-11 | 2023-12-11 | Distributed management method and device for product data, computer equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117827982A (en) |
-
2023
- 2023-12-11 CN CN202311696865.1A patent/CN117827982A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10540173B2 (en) | Version control of applications | |
| CN106506587B (en) | Docker mirror image downloading method based on distributed storage | |
| US9575871B2 (en) | System and method for dynamically debugging data in a multi-tenant database environment | |
| US8812627B2 (en) | System and method for installation and management of cloud-independent multi-tenant applications | |
| US10469330B1 (en) | Client account versioning metadata manager for cloud computing environments | |
| US7624116B2 (en) | System and method for managing objects according to the common information model | |
| US20120079083A1 (en) | Sharing Performance Data Between Different Information Technology Product/Solution Deployments | |
| US9535754B1 (en) | Dynamic provisioning of computing resources | |
| US9910881B1 (en) | Maintaining versions of control plane data for a network-based service control plane | |
| US10891569B1 (en) | Dynamic task discovery for workflow tasks | |
| CN109522043B (en) | Method and device for managing configuration data and storage medium | |
| US10262024B1 (en) | Providing consistent access to data objects transcending storage limitations in a non-relational data store | |
| US11405328B2 (en) | Providing on-demand production of graph-based relationships in a cloud computing environment | |
| US10855750B2 (en) | Centralized management of webservice resources in an enterprise | |
| CN111737227A (en) | Data modification method and system | |
| US10951540B1 (en) | Capture and execution of provider network tasks | |
| US20220300491A1 (en) | Materialized views assistant | |
| US20140047447A1 (en) | Work scheduling method and system implemented via cloud platform | |
| CN117827982A (en) | Distributed management method and device for product data, computer equipment and medium | |
| US8635331B2 (en) | Distributed workflow framework | |
| US10909019B2 (en) | Runtime performance introspection | |
| US20210286826A1 (en) | Computer-Implemented Method and System for Attribute Discovery for Operation Objects from Operation Data | |
| CN112416980A (en) | Data service processing method, device and equipment | |
| EP2869245A2 (en) | Service modeling and execution | |
| Shao | About the design changes required for enabling ECM systems to exploit cloud technology |
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 |