Distributed management method, device, computer equipment and medium for product data

Abstract

The present application relates to the field of Internet technology, and discloses a distributed management method, device, computer equipment and medium for product data, wherein the method includes determining the product type based on product data, user data and warehouse data when receiving an instruction to upload a product file; uploading the product file to the object storage system OSS according to the product type, generating file path information; determining the index data corresponding to the product file according to preset Maven index information and the file path information; uploading the index data and the product file to the MySQL database to complete the distributed Maven warehouse deployment. In the above manner, the present application generates corresponding file path information in OSS according to different product types. Generate index data of the product file based on the file path information and the preset index information to guide the product file to be uploaded to the MySQL database, thereby improving the deployment and maintenance efficiency of the enterprise-level user product library.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a distributed management method, apparatus, computer equipment, and medium for product data. Background Art

[0002] In Java CI (continuous integration) / CD (continuous deployment) projects, we usually use Maven's dependency system to manage build dependencies, which is also widely used in system development. The Maven repository system is a very important cornerstone of the entire engineering system. The central repositories of domestic agents generally only provide download capabilities, or become their users but cannot customize their needs, and data security cannot be guaranteed. A stable, reliable and efficient Maven repository system can not only facilitate developers' daily development work, but also facilitate enterprise-level project engineering management, rationally plan the use of warehouses, and reduce resource waste. Maven private repositories are a hard-core feature required by many companies. A high-performance system must support horizontal expansion capabilities, tenant-level data isolation, underlying data storage reliability, and support containerized deployment. These are the capabilities that current cloud services must have.

[0003] Existing technical solutions for Maven repositories primarily focus on providing storage capabilities, including both open source and commercial versions, all of which have certain limitations. For example, the latest version of the open source Nexus OSS does not support high availability or multi-tenancy. While the commercial version supports high availability, it encounters performance bottlenecks when used for cloud services, does not support horizontal multi-node scaling, and only supports a limited number of tenants. Therefore, improving the deployment and maintenance efficiency of enterprise-level artifact repositories has become a pressing technical challenge. Summary of the Invention

[0004] The present application provides a distributed management method, apparatus, computer equipment and medium for product data to improve the deployment and maintenance efficiency of enterprise-level user product libraries.

[0005] In a first aspect, the present application provides a method for distributed management of product data, the method comprising:

[0006] When receiving the instruction to upload the product file, the product type is determined based on the product data, user data and warehouse data;

[0007] Upload the product file to the object storage system OSS according to the product type and generate file path information;

[0008] Determine the index data corresponding to the artifact file according to the preset Maven index information and the file path information;

[0009] Upload the index data and the artifact files to the MySQL database to complete the distributed Maven warehouse deployment.

[0010] Furthermore, the distributed management method for product data also includes:

[0011] Upon receiving a product file download instruction, determining the warehouse data and the product data according to the user data and the product type;

[0012] Determine whether the product data exists in the MySQL database;

[0013] If the product data exists in the MySQL database, the product data is downloaded.

[0014] Furthermore, after determining whether the product data exists in the MySQL database, the method further includes:

[0015] If the product data does not exist in the MySQL database, the product data is read from the OSS according to the index data.

[0016] Furthermore, after determining whether the product data exists in the MySQL database, the method further includes:

[0017] If the product data does not exist in the OSS, read external warehouse data of at least one external warehouse;

[0018] Traversing each of the external warehouse data, and matching the product data with each of the external warehouse data;

[0019] If there is external warehouse data matching the product data in each of the external warehouse data, the traversal is terminated.

[0020] Furthermore, after traversing each of the external warehouse data and matching the product data with each of the external warehouse data, the following steps are included:

[0021] If the external warehouse data does not include the product data, a prompt mark is issued to indicate that the product file does not exist.

[0022] Furthermore, upon receiving the instruction to upload a product file, before determining the product type based on the product data, user data, and warehouse data, the following steps are performed:

[0023] Based on the preset load balancing strategy and the user data, determine whether the instruction to upload the product file is a legal instruction.

[0024] Furthermore, the index data includes: warehouse name, tenant ID, artifact path, artifact version number, storage OSS file path, maven-metadata.xml file path information and the artifact type.

[0025] In a second aspect, the present application further provides a distributed management device for product data, the device comprising:

[0026] A product type determination module is used to determine the product type based on product data, user data and warehouse data when receiving an instruction to upload a product file;

[0027] A file path information generation module is used to upload the product file to the object storage system OSS according to the product type and generate file path information;

[0028] An index data determination module, configured to determine the index data corresponding to the artifact file based on preset Maven index information and the file path information;

[0029] The product file upload module is used to upload the index data and the product file to the MySQL database to complete the distributed Maven warehouse deployment.

[0030] In a third aspect, the present application also provides a computer device comprising a memory and a processor; the memory is used to store a computer program; the processor is used to execute the computer program and implement the distributed management method of product data as described above when executing the computer program.

[0031] In a fourth aspect, the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor implements the distributed management method of product data as described above.

[0032] The present application discloses a distributed management method, device, computer equipment and medium for product data, wherein the distributed management method for product data includes determining the product type according to product data, user data and warehouse data when receiving an instruction to upload a product file; uploading the product file to the object storage system OSS according to the product type, generating file path information; determining the index data corresponding to the product file according to preset Maven index information and the file path information; uploading the index data and the product file to the MySQL database to complete the distributed Maven warehouse deployment. In the above manner, the present application generates corresponding file path information in OSS according to different product types. Generate index data of the product file according to the file path information and the preset index information to guide the product file to be uploaded to the MySQL database, thereby improving the deployment and maintenance efficiency of the enterprise-level user product library. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0034] Figure 1 This is a schematic flow chart of a distributed management method for product data provided in the first embodiment of the present application;

[0035] Figure 2 is a schematic flow chart of a distributed management method for product data provided in the second embodiment of the present application;

[0036] Figure 3 A schematic block diagram of a distributed management device for product data provided in an embodiment of the present application;

[0037] Figure 4 A schematic block diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0039] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, combined, or partially merged, so the actual execution order may vary depending on the actual situation.

[0040] It should be understood that the terms used in this specification are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms unless the context clearly indicates otherwise.

[0041] It will also be understood that the term "and / or" used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

[0042] Embodiments of the present application provide a method, apparatus, computer equipment, and medium for distributed management of product data. The distributed management method for product data can be applied to a server, generating corresponding file path information in OSS based on different product types. Index data for product files is generated based on the file path information and preset index information to guide product files to be uploaded to a MySQL database, thereby improving the deployment and maintenance efficiency of enterprise-level user product libraries. The server can be a standalone server or a server cluster.

[0043] The following describes some embodiments of the present application in detail with reference to the accompanying drawings. In the absence of conflict, the following embodiments and features therein may be combined with each other.

[0044] See also Figure 1 , Figure 1 This is a schematic flow chart of a distributed product data management method provided in the first embodiment of this application. This distributed product data management method can be applied to a server to generate corresponding file path information in OSS based on different product types. Based on this file path information and preset index information, index data for product files is generated to guide product file uploads to a MySQL database, improving the deployment and maintenance efficiency of enterprise-level user product libraries.

[0045] like Figure 1 As shown, the distributed management method for product data specifically includes steps S10 to S40.

[0046] Step S10: upon receiving the instruction to upload the product file, determine the product type based on the product data, user data, and warehouse data;

[0047] Step S20: Upload the product file to the object storage system OSS according to the product type and generate file path information;

[0048] Step S30: Determine the index data corresponding to the artifact file according to the preset Maven index information and the file path information;

[0049] Step S40: Upload the index data and the artifact files to the MySQL database to complete the distributed Maven warehouse deployment.

[0050] In one embodiment, the main engineering architecture of this embodiment is built on Springboot2, which mainly includes the following four modules: gateway authentication module, metadata storage module, index data storage module, and OSS object storage module.

[0051] The gateway authentication module is responsible for authenticating user information, determining whether the request is legitimate, and then forwarding the traffic to the corresponding backend RM instance according to the load balancing strategy, thus completing the authentication load.

[0052] The data storage module is responsible for storing tenant and user account information, user uploaded product records, warehouse metadata, and the used Elasticsearch and OSS file system information in the MySQL database to facilitate maintenance and management and generate statistical reports.

[0053] The index data storage module is mainly responsible for storing the user's warehouse file index data in elasticsearch. This can speed up the processing of requests and quickly retrieve and locate the file information required by the user, making it easier to quickly pull products.

[0054] The OSS object storage module's main function is to store warehouse file data on the corresponding OSS object storage file system. This allows the RM system to shield file storage capacity expansion pressure and avoid operations such as host disk expansion. Furthermore, different OSS storage can be selected based on the region (East China, North China, South China, etc.), reducing the pressure on a single OSS cluster, ensuring data security, and ensuring that data synchronization between instances is not required.

[0055] In one embodiment, the user uploads the product process steps:

[0056] Step 1: The user uploads the Maven dependency structure data to the RM backend instance through the RM front-end page and the Maven deploy command;

[0057] Step 2: After RM reads the artifact data, it obtains the current tenant data and user warehouse data based on the user data, and determines the artifact type (release / snapshot) through the version attribute in dependency.

[0058] Step 3: Upload the artifact to the corresponding OSS object storage system based on the artifact type, including maven-metadata.xml, artifact source files, and MD5 and SHA1 verification files;

[0059] Step 4: Write the file path information and Maven index information obtained after uploading to the OSS file system into Elasticsearch to build the necessary RM index data and speed up the location of file data;

[0060] Step 5: After storing the index data, store the record information uploaded by the user in MySQL to facilitate users to view the records, and count the users' use of RM resources to create data reports.

[0061] In one embodiment, the following are some main statistical report structures:

[0062] Warehouse user table:

[0063] Field Name Field meaning User_name Member User Name Role_id Character ID User_id User ID Tenant_id Tenant ID Is_owner Is the warehouse owner?

[0064] This table is responsible for storing warehouse user information, including the tenant to which the user belongs, the user's role, and whether the user is the warehouse owner. The warehouse owner has the authority to manage the tenant's private repository.

[0065] Warehouse account table:

[0066] Field Name Field meaning Account_name Account Name pwd Password (ciphertext) User_id User ID Tenant_id Tenant ID Is_init_settings Whether to initialize settings

[0067] This table is responsible for storing warehouse user account information to facilitate gateway authentication. It contains basic user information and tenant information, and indicates whether Maven settings.xml has been initialized, which is used for Jenkins pipeline to pull Maven products.

[0068] Warehouse basic table:

[0069]

[0070] This table is responsible for storing dependent external systems, such as Elasticsearch and OSS file systems. It uses the corresponding external system based on the region to reduce the pressure on a single Elasticsearch or OSS cluster and uses Auth_code to authenticate connections and access to the external system.

[0071] Warehouse information table:

[0072]

[0073] This table is responsible for storing user-assigned warehouse information, including access URI addresses, including release libraries and snapshot libraries. It also records the elasticsearch and OSS information required for warehouse artifact storage, as well as tenant information. Because the warehouse is initialized based on tenant information, the warehouse owner is responsible for managing the warehouse.

[0074] Warehouse role table:

[0075] Field Name Field meaning Role_id Character ID Role_name Character Name Role_group Role Group Role_desc Role Description

[0076] This table is responsible for storing the role constant information of the current system, including three types of roles: administrator, developer, and ordinary member. The operation permissions of each role are as follows:

[0077]

[0078] This embodiment discloses a distributed management method, device, computer equipment and medium for product data. The distributed management method for product data includes determining the product type based on product data, user data and warehouse data when receiving an instruction to upload a product file; uploading the product file to the object storage system OSS according to the product type to generate file path information; determining the index data corresponding to the product file according to preset Maven index information and the file path information; uploading the index data and the product file to the MySQL database to complete the distributed Maven warehouse deployment. Through the above method, the present application generates corresponding file path information in OSS according to different product types. Generate index data of the product file based on the file path information and the preset index information to guide the product file to be uploaded to the MySQL database, thereby improving the deployment and maintenance efficiency of the enterprise-level user product library.

[0079] See also Figure 2 , Figure 2 This is a schematic flow chart of a distributed product data management method provided in the second embodiment of this application. This distributed product data management method can be applied to a server to generate corresponding file path information in OSS based on different product types. Based on this file path information and preset index information, index data for product files is generated to guide product file uploads to a MySQL database, improving the deployment and maintenance efficiency of enterprise-level user product libraries.

[0080] based on Figure 1 The embodiment shown, this embodiment Figure 2As shown, the distributed management method for product data further includes steps S50 to S70.

[0081] Step S50: upon receiving the instruction to download the product file, determining the warehouse data and the product data according to the user data and the product type;

[0082] Step S60: Determine whether the product data exists in the MySQL database;

[0083] Step S70: If the product data exists in the MySQL database, download the product data.

[0084] In one embodiment, the steps for a user to download a product are as follows:

[0085] Step 1: The RM instance receives a Maven artifact request from the user. Taking org / apache / maven / apache-maven / 3.8.4 / apache-maven-3.8.4-bin.tar.gz as an example, it obtains the corresponding repository metadata based on the user information and artifact type (release, snapshot).

[0086] Step 2: Read the corresponding maven-metadata.xml metadata to obtain the metadata information of the product description;

[0087] Step 3: After confirming the product information, first read the product data from the local cache. If it exists, return it directly. If not, check the index data.

[0088] Step 4: In the index data, based on the data information stored in the index data, directly read the OSS file system data if available; otherwise, obtain other warehouse information from the Group to which the user belongs;

[0089] Step 5: Based on the other warehouse information obtained, visit the corresponding warehouses in order from top to bottom. If data is found, return it directly. After traversing all warehouses, if the data is still not found, it will prompt that the file does not exist 404.

[0090] This embodiment discloses a distributed management method, apparatus, computer equipment and medium for product data. The distributed management method for product data includes, upon receiving a download product file instruction, 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; and downloading the product data if the product data exists in the MySQL database. In the above manner, the present application generates corresponding file path information in OSS according to different product types. Based on the file path information and preset index information, index data of the product file is generated to guide the upload of the product file to the MySQL database, thereby improving the deployment and maintenance efficiency of the enterprise-level user product library.

[0091] based on Figure 2 In the embodiment shown, in this embodiment, after step S70, the following steps are further included:

[0092] If the product data does not exist in the MySQL database, the product data is read from the OSS according to the index data.

[0093] Based on the above embodiment, in this embodiment, after determining whether the product data exists in the MySQL database, the method further includes:

[0094] If the product data does not exist in the OSS, read external warehouse data of at least one external warehouse;

[0095] Traversing each of the external warehouse data, and matching the product data with each of the external warehouse data;

[0096] If there is external warehouse data matching the product data in each of the external warehouse data, the traversal is terminated.

[0097] In one embodiment, after traversing each of the external warehouse data and matching the product data with each of the external warehouse data, the following steps are included:

[0098] If the external warehouse data does not include the product data, a prompt mark is issued to indicate that the product file does not exist.

[0099] based on Figure 1 In the embodiment shown, in this embodiment, before step S10, the following steps are included:

[0100] Based on the preset load balancing strategy and the user data, determine whether the instruction to upload the product file is a legal instruction.

[0101] Based on any of the above embodiments, in this embodiment, the index data includes: warehouse name, tenant ID, product path, product version number, storage OSS file path, maven-metadata.xml file path information and the product type.

[0102] See also Figure 3 , Figure 3 This is a schematic block diagram of a distributed management device for product data provided by an embodiment of the present application, wherein the distributed management device for product data is used to execute the aforementioned distributed management method for product data.

[0103] like Figure 3 As shown, the distributed management device for product data includes:

[0104] The product type determination module 410 is configured to determine the product type based on the product data, user data, and warehouse data upon receiving a product file upload instruction;

[0105] A 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;

[0106] An index data determination module 430 is configured to determine the index data corresponding to the artifact file based on the preset Maven index information and the file path information;

[0107] The artifact file uploading module 440 is used to upload the index data and the artifact file to the MySQL database to complete the distributed Maven warehouse deployment.

[0108] Furthermore, the distributed management device for product data further includes:

[0109] A product file download instruction module, configured to determine the warehouse data and the product data according to the user data and the product type upon receiving the product file download instruction;

[0110] A product data judgment module, used to judge whether the product data exists in the MySQL database;

[0111] The product data download module is used to download the product data if the product data exists in the MySQL database.

[0112] Furthermore, the distributed management device for product data further includes:

[0113] The product data reading module is configured to read the product data from the OSS according to the index data when the product data does not exist in the MySQL database.

[0114] Furthermore, the distributed management device for product data further includes:

[0115] an external warehouse data reading module, configured to read external warehouse data of at least one external warehouse when the product data does not exist in the OSS;

[0116] A product data matching module, configured to traverse the external warehouse data and match the product data with the external warehouse data;

[0117] The traversal termination module is used to terminate the traversal if there is external warehouse data matching the product data in each of the external warehouse data.

[0118] Furthermore, the distributed management device for product data further includes:

[0119] The prompt identification module is used to issue a prompt identification to indicate that the product file does not exist if the external warehouse data does not include the product data.

[0120] Furthermore, the distributed management device for product data further includes:

[0121] The instruction legality judgment module is used to determine whether the instruction to upload the product file is a legal instruction based on a preset load balancing strategy and the user data.

[0122] It should be noted that those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and modules can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0123] The above-mentioned device can be realized in the form of a computer program. The computer program can be used in Figure 4 Runs on the computer equipment shown.

[0124] See also Figure 4 , Figure 4 1 is a schematic block diagram of a computer device provided in an embodiment of the present application. The computer device may be a server.

[0125] See Figure 4 The computer device includes a processor, a memory, and a network interface connected through a system bus, wherein the memory may include a non-volatile storage medium and an internal memory.

[0126] The non-volatile storage medium can store an operating system and a computer program. The computer program includes program instructions, and when the program instructions are executed, the processor can execute any one of the distributed management methods for product data.

[0127] The processor is used to provide computing and control capabilities and support the operation of the entire computer equipment.

[0128] The internal memory provides an environment for the operation of the computer program in the non-volatile storage medium. When the computer program is executed by the processor, the processor can execute any distributed management method of product data.

[0129] The network interface is used for network communication, such as sending assigned tasks, etc. Those skilled in the art will understand that Figure 4 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0130] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0131] In one embodiment, the processor is configured to execute a computer program stored in the memory to implement the following steps:

[0132] When receiving the instruction to upload the product file, the product type is determined based on the product data, user data and warehouse data;

[0133] Upload the product file to the object storage system OSS according to the product type and generate file path information;

[0134] Determine the index data corresponding to the artifact file according to the preset Maven index information and the file path information;

[0135] Upload the index data and the artifact files to the MySQL database to complete the distributed Maven warehouse deployment.

[0136] In one embodiment, the distributed management method for artifact data is further used to implement:

[0137] Upon receiving a product file download instruction, determining the warehouse data and the product data according to the user data and the product type;

[0138] Determine whether the product data exists in the MySQL database;

[0139] If the product data exists in the MySQL database, the product data is downloaded.

[0140] In one embodiment, after determining whether the product data exists in the MySQL database, it is also used to implement:

[0141] If the product data does not exist in the MySQL database, the product data is read from the OSS according to the index data.

[0142] In one embodiment, after determining whether the product data exists in the MySQL database, it is also used to implement:

[0143] If the product data does not exist in the OSS, read external warehouse data of at least one external warehouse;

[0144] Traversing each of the external warehouse data, and matching the product data with each of the external warehouse data;

[0145] If there is external warehouse data matching the product data in each of the external warehouse data, the traversal is terminated.

[0146] In one embodiment, after traversing each of the external warehouse data and matching the product data with each of the external warehouse data, it is used to achieve:

[0147] If the external warehouse data does not include the product data, a prompt mark is issued to indicate that the product file does not exist.

[0148] In one embodiment, upon receiving an instruction to upload a product file, before determining the product type based on the product data, user data, and warehouse data, the following steps are implemented:

[0149] Based on the preset load balancing strategy and the user data, determine whether the instruction to upload the product file is a legal instruction.

[0150] A computer-readable storage medium is also provided in an embodiment of the present application, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and the processor executes the program instructions to implement any of the distributed management methods for product data provided in the embodiments of the present application.

[0151] The computer-readable storage medium may be an internal storage unit of the computer device described in the aforementioned embodiment, such as a hard disk or 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 SmartMedia Card (SMC), a Secure Digital (SD) card, a flash memory card, etc., equipped on the computer device.

[0152] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present application, and such modifications or substitutions should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A distributed management method for product data, characterized in that: include: When receiving the instruction to upload the product file, the product type is determined based on the product data, user data and warehouse data; Upload the product file to the object storage system OSS according to the product type and generate file path information; Determine the index data corresponding to the artifact file according to the preset Maven index information and the file path information; Upload the index data and the artifact files to the MySQL database to complete the distributed Maven warehouse deployment.

2. The distributed management method for product data according to claim 1, characterized in that: The distributed management method for product data further includes: Upon receiving a product file download instruction, determining the warehouse data and the product data according to the user data and the product type; Determine whether the product data exists in the MySQL database; If the product data exists in the MySQL database, the product data is downloaded.

3. The distributed management method for product data according to claim 2, characterized in that: After determining whether the product data exists in the MySQL database, the method further includes: If the product data does not exist in the MySQL database, the product data is read from the OSS according to the index data.

4. The distributed management method for product data according to claim 3, characterized in that: After determining whether the product data exists in the MySQL database, the method further includes: If the product data does not exist in the OSS, read external warehouse data of at least one external warehouse; Traversing each of the external warehouse data, and matching the product data with each of the external warehouse data; If there is external warehouse data matching the product data in each of the external warehouse data, the traversal is terminated.

5. The distributed management method for product data according to claim 4, characterized in that: After traversing the external warehouse data and matching the product data with the external warehouse data, the method includes: If the external warehouse data does not include the product data, a prompt mark is issued to indicate that the product file does not exist.

6. The distributed management method for product data according to claim 1, characterized in that: When receiving the instruction to upload the product file, before determining the product type based on the product data, user data and warehouse data, the following steps are included: Based on the preset load balancing strategy and the user data, determine whether the instruction to upload the product file is a legal instruction.

7. The distributed management method for product data according to any one of claims 1 to 6, characterized in that: The index data includes: warehouse name, tenant ID, product path, product version number, storage OSS file path, maven-metadata.xml file path information and the product type.

8. A distributed management device for product data, characterized in that: include: A product type determination module is used to determine the product type based on product data, user data and warehouse data when receiving an instruction to upload a product file; A file path information generation module is used to upload the product file to the object storage system OSS according to the product type and generate file path information; An index data determination module, configured to determine the index data corresponding to the artifact file based on preset Maven index information and the file path information; The product file upload module is used to upload the index data and the product file to the MySQL database to complete the distributed Maven warehouse deployment.

9. A computer device, characterized in that: The computer device includes a memory and a processor; The memory is used to store computer programs; The processor is configured to execute the computer program and implement the distributed management method for product data according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed by a processor, enables the processor to implement the distributed management method for product data according to any one of claims 1 to 7.

Images