CN117290342A - Distributed database version information management method, device, electronic equipment and medium - Google Patents
Distributed database version information management method, device, electronic equipment and medium Download PDFInfo
- Publication number
- CN117290342A CN117290342A CN202311520153.4A CN202311520153A CN117290342A CN 117290342 A CN117290342 A CN 117290342A CN 202311520153 A CN202311520153 A CN 202311520153A CN 117290342 A CN117290342 A CN 117290342A
- Authority
- CN
- China
- Prior art keywords
- version information
- component
- maintenance
- distributed database
- product package
- 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 description 33
- 238000012423 maintenance Methods 0.000 claims abstract description 122
- 238000000034 method Methods 0.000 claims abstract description 30
- 238000004891 communication Methods 0.000 claims abstract description 18
- 238000010276 construction Methods 0.000 claims description 14
- 230000010354 integration Effects 0.000 claims description 7
- 238000012795 verification Methods 0.000 claims description 7
- 238000009434 installation Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 description 15
- 238000010586 diagram Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- 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/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a method, a device, electronic equipment and a medium for managing version information of a distributed database, and relates to the field of operation and maintenance of the distributed database. The method comprises the following steps: creating a target component product package required by a distributed database, and adding a version information file into the target component product package; responding to the event that the target component product package is successfully installed, and establishing communication connection between component operation and maintenance proxy service and operation and maintenance service of the distributed database; reading the component version information from the version information file of the target component product package through the component operation and maintenance proxy service, and sending the component version information to the operation and maintenance service; and storing the received component version information in a target data table through the operation and maintenance service. The scheme of the invention realizes the operation and maintenance management of the version information of each component of the distributed database.
Description
Technical Field
The invention relates to the field of distributed database operation and maintenance, in particular to a distributed database version information management method, a device, electronic equipment and a storage medium.
Background
With the advent of the data age, databases have played a critical role in various fields as an important infrastructure, and with the combination of databases and network technologies, distributed databases have evolved. The distributed database platform provides unified database service through a shared-nothing architecture, and horizontal expansion of database capacity is realized through adding database nodes.
Disclosure of Invention
The invention provides a distributed database version information management method, a distributed database version information management device, electronic equipment and a storage medium.
According to an aspect of the present invention, there is provided a distributed database version information management method, including:
creating a target component product package required by a distributed database, and adding a version information file into the target component product package;
responding to the event that the target component product package is successfully installed, and establishing communication connection between component operation and maintenance proxy service and operation and maintenance service of the distributed database;
reading the component version information from the version information file of the target component product package through the component operation and maintenance proxy service, and sending the component version information to the operation and maintenance service;
and storing the received component version information in a target data table through the operation and maintenance service.
According to another aspect of the present invention, there is provided a distributed database version information management apparatus including:
the system comprises a component creation module, a storage module and a storage module, wherein the component creation module is used for creating a target component product package required by a distributed database and adding a version information file into the target component product package;
the connection module is used for responding to the event that the target component product package is successfully installed, and establishing communication connection between the component operation and maintenance proxy service and the operation and maintenance service of the distributed database;
the version information reading module is used for reading the version information of the component from the version information file of the target component product package through the component operation and maintenance proxy service and sending the version information to the operation and maintenance service;
and the storage module is used for storing the received component version information in a target data table through the operation maintenance service.
According to another aspect of the present invention, there is provided an electronic apparatus including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the distributed database version information management method of any embodiment of the present invention.
According to another aspect of the present invention, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the distributed database version information management method according to any of the embodiments of the present invention.
According to the technology of the invention, manual modification operation is not needed when the versions of the distributed database components are changed, the problem of disordered management of the original operation and maintenance upgrading versions is solved, the later operation and maintenance of a developer are facilitated, and the user can directly check the version number information of the currently used component on the interface.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow diagram of a distributed database version information management method according to an embodiment of the present invention;
FIG. 2a is a flow chart of another method for distributed database version information management according to an embodiment of the present invention;
FIG. 2b is a logic diagram of implementing version information synchronization through an operation and maintenance interface, a component operation and maintenance proxy service, an operation and maintenance service according to an embodiment of the present invention;
FIG. 3 is a flow diagram of another distributed database version information management method according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a distributed database version information management apparatus according to an embodiment of the present invention;
fig. 5 is a block diagram of an electronic device for implementing a distributed database version information management method according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
The distributed database in the embodiment of the invention is generally composed of a plurality of components, and with the continuous development and progress of information technology and the requirement of actual application scenes, the components inside the distributed database need to be upgraded, however, due to the complexity of the actual production environment, the version number management of different components is often disordered, and great inconvenience is brought to later version alternation and operation and maintenance management. Therefore, the invention provides a convenient and reliable distributed database version number management method, and the specific flow of the method can be seen in the following embodiment.
Fig. 1 is a flowchart of a distributed database version information management method according to an embodiment of the present invention. The embodiment is applicable to the case of managing version information of a distributed database, where the version information of the distributed database is composed of component version information of each component in the distributed database. The method may be performed by a distributed database version information management apparatus implemented in software and/or hardware, preferably configured in an electronic device.
As shown in fig. 1, the method specifically includes the following steps:
s101, creating a target component product package required by the distributed database, and adding a version information file into the target component product package.
In this embodiment, the target component product package may be an update package of a component, or may be a newly developed functional component, which is not specifically limited herein. Illustratively, the update package in which the target component product package is a component is described as an example, and thus, the target component product package is created for iteratively updating the corresponding component in the distributed database. Before creating the target component product package needed by the distributed database, branches needed to be constructed and product library paths where the components are located are selected. On the basis, when the target component product package is created, setting configuration or a method required by the construction of the target component product package through a file (such as an xml file) in a preset format; this xml file is then executed by the continuous integration tool Jenkins to build the corresponding package of component products. In this embodiment, the code construction round, the component name, the component branch name and the construction time of the target component product can also be used as component version information to write the version information file through a continuous integration tool Jenkins; and adding the version information file into the target component product package. Further, according to the pre-selected product library address, the constructed target component product package is sent to the corresponding product library for compiling, packaging and other operations. It should be noted that, in this embodiment, the version information file is added to the component product package so that the version information is combined with the product construction, thereby avoiding the version information of the component from being tampered.
S102, in response to the event that the target component product package is successfully installed, communication connection between the component operation and maintenance proxy service and the operation and maintenance service of the distributed database is established.
In this embodiment, after the target component product package is built, the target component product package may be installed in the distributed database, so as to implement update iteration of the component. After the target component product package is successfully installed, establishing communication connection between a component operation and maintenance proxy service and an operation and maintenance service of the distributed database, for example, establishing a Netty channel between the component operation and maintenance proxy service and the operation and maintenance service of the distributed database, so as to realize update synchronization of version information of the distributed database through the component operation and maintenance proxy service and the operation and maintenance service of the distributed database, wherein the component operation and maintenance proxy service is a service for analyzing and acquiring the version information of the component; an operation maintenance service is a service for managing component version information, such as a service for storing or exposing component version information. Specifically, the process of component version information synchronization is referred to in steps S103 to S104.
S103, reading the component version information from the version information file of the target component product package through the component operation and maintenance proxy service, and sending the component version information to the operation and maintenance service.
S104, storing the received component version information in a target data table through the operation and maintenance service.
In this embodiment, for the components in the distributed database, after the components are installed, the component version information of each component is stored under a designated folder, for example, under the etc folder of the user home directory of each component. The component operation and maintenance proxy service can acquire the version information file from the etc file of the user home directory of the target component, and analyze the version information file to acquire the component version information corresponding to the target component; and then the obtained component version information is sent to the operation maintenance service, for example, the component version information is sent to the operation maintenance service through a pre-created Netty channel. The operation and maintenance service stores the received component version information in a target data table, wherein the target data table may be any data table specified in advance, and is not limited herein.
In this embodiment, after the component is upgraded, version information of the component is automatically synchronized and stored, so that operation and maintenance management of version information of each component of the distributed database is realized.
Furthermore, the operation and maintenance service also provides a display function, and through the display function, the component version information stored in the target data table can be displayed in a preset operation and maintenance interface so as to be convenient for operation and maintenance personnel to check. It should be noted that, the operation and maintenance interface may also display all the information of the historical version information, version update time, important time record (such as repair record of major problems) and the like of each component, so that the operation and maintenance personnel can know the details of the version information. Thus, through the display function provided by the operation and maintenance service, the operation and maintenance personnel can directly view the version information of each component of the distributed database on the interface.
Fig. 2a is a flow chart illustrating another method for managing version information of a distributed database according to an embodiment of the present invention. In this embodiment, the operation and maintenance interface also provides a function of actively triggering the version information of the components to update synchronously by the user, and on this basis, the operation and maintenance personnel can implement automatic synchronization of the version information of each component of the distributed database by performing touch operation on the operation and maintenance interface. As shown in fig. 2a, the method for managing version information of the distributed database specifically includes the following steps:
s201, generating a version information synchronization request according to touch operation of the operation and maintenance personnel on the operation and maintenance interface.
S202, responding to the version information synchronization request, reading the version information of the component from the version information file of the appointed component through the component operation and maintenance proxy service, and sending the version information to the operation and maintenance service.
S203, storing the received component version information in a target data table through the operation and maintenance service.
In this embodiment, at least a control for synchronizing version information of the database is provided in the operation and maintenance interface, and an operator can actively trigger synchronization of component version information of the distributed database component by touching the control. In a specific implementation, a version information synchronization request can be generated according to touch operation of the operation and maintenance personnel on the operation and maintenance interface, wherein the version information synchronization request comprises at least one designated component needing to synchronize version information.
And acquiring a version information file from the etc folder of the home directory of the appointed component user through the component operation and maintenance proxy service when the version information synchronization request is acquired, analyzing the version information file to acquire component version information in the version information file, and transmitting the acquired component version information to the operation and maintenance service. And storing the received component version information in a target data table through the operation and maintenance service.
For ease of illustration, reference is made to FIG. 2b, which shows a logic diagram for implementing version information synchronization through an operation and maintenance interface, component operation and maintenance proxy service, operation and maintenance service. Optionally, the operation and maintenance interface generates a version information synchronization request including a plurality of designated components through touch operation of corresponding operation and maintenance personnel, and sends the version information synchronization request to the operation and maintenance service, so that the operation and maintenance service sends a synchronization version information event generated according to the version information synchronization request to the component operation and maintenance proxy service through the Netty channel, and the component operation and maintenance proxy service reads the component version information included in the version information file of the designated component, forms a message with the acquired component version information and feeds the message back to the operation and maintenance service; the operation maintenance service updates the version information to the database according to the received message; meanwhile, the updated result is fed back to the operation and maintenance interface for display, so that the display of version information is realized, and operation and maintenance personnel can conveniently and intuitively check the version information.
Fig. 3 is a flowchart illustrating another distributed database version information management method according to an embodiment of the present invention. As shown in fig. 3, the method specifically includes the following steps:
s301, creating a target component product package required by the distributed database, and adding a version information file into the target component product package.
In this embodiment, the target component product package may be an update package of a component, or may be a newly developed functional component, which is not specifically limited herein. Illustratively, the update package in which the target component product package is a component is described as an example, and thus, the target component product package is created for iteratively updating the corresponding component in the distributed database. Before creating the target component product package needed by the distributed database, branches needed to be constructed and product library paths where the components are located are selected. On the basis, when the target component product package is created, setting configuration or a method required by the construction of the target component product package through a file (such as an xml file) in a preset format; this xml file is then executed by the continuous integration tool Jenkins to build the corresponding package of component products. In this embodiment, the code construction round, the component name, the component branch name and the construction time of the target component product can also be used as component version information to write the version information file through a continuous integration tool Jenkins; and adding the version information file into the target component product package. Further, according to the pre-selected product library address, the constructed target component product package is sent to the corresponding product library for compiling, packaging and other operations. It should be noted that, in this embodiment, the version information file is added to the component product package so that the version information is combined with the product construction, thereby avoiding the version information of the component from being tampered.
S302, before the target component product package is installed, verifying version information of the target component product package, and intercepting the installation of the target component product package under the condition that verification fails; the verification is successful in executing step S303.
In this embodiment, in order to avoid that a component inconsistent with the current version information of the database is installed, which leads to confusion of the version information of the database, before installing the target component product package, the version information of the target component product package is checked, for example, whether the version information of the target component product package is consistent with the current version information of the database is checked, if so, a subsequent step is executed, otherwise, the installation of the target component product package is intercepted.
S303, responding to the event that the target component product package is successfully installed, and establishing communication connection between the component operation and maintenance proxy service and the operation and maintenance service of the distributed database.
In this embodiment, after the target component product package is built, the target component product package may be installed in the distributed database, so as to implement update iteration of the component. After the target component product package is successfully installed, establishing communication connection between a component operation and maintenance proxy service and an operation and maintenance service of the distributed database, for example, establishing a Netty channel between the component operation and maintenance proxy service and the operation and maintenance service of the distributed database, so as to realize update synchronization of version information of the distributed database through the component operation and maintenance proxy service and the operation and maintenance service of the distributed database, wherein the component operation and maintenance proxy service is a service for analyzing and acquiring the version information of the component; an operation maintenance service is a service for managing component version information, such as a service for storing or exposing component version information
S304, reading the component version information from the version information file of the target component product package through the component operation and maintenance proxy service, and sending the component version information to the operation and maintenance service.
S305, storing the received component version information in a target data table through the operation and maintenance service.
In this embodiment, for the components in the distributed database, after the components are installed, the component version information of each component is stored under a designated folder, for example, under the etc folder of the user home directory of each component. The component operation and maintenance proxy service can acquire the version information file from the etc file of the user home directory of the target component, and analyze the version information file to acquire the component version information corresponding to the target component; and then the obtained component version information is sent to the operation maintenance service, for example, the component version information is sent to the operation maintenance service through a pre-created Netty channel. The operation and maintenance service stores the received component version information in a target data table, wherein the target data table may be any data table specified in advance, and is not limited herein.
In this embodiment, before installing the target component product package, verification of version information of the target component product package is performed, and subsequent version information synchronization can be performed only after the verification is passed, so that it is possible to avoid that a component inconsistent with the current version information of the database is installed, resulting in confusion of version information of the database.
Fig. 4 is a schematic structural diagram of a distributed database version information management apparatus according to an embodiment of the present invention, and the embodiment is applicable to a scenario of managing version information of a distributed database. As shown in fig. 4, the apparatus 400 specifically includes:
the component creation module 401 is configured to create a target component product package required by the distributed database, and add a version information file into the target component product package;
a connection module 402, configured to establish a communication connection between a component operation and maintenance proxy service and an operation and maintenance service of the distributed database in response to an event that the installation of the target component product package is successful;
the version information reading module 403 is configured to read, through the component operation and maintenance proxy service, component version information from a version information file of the target component product package, and send the component version information to the operation and maintenance service;
and the storage module 404 is configured to store the received component version information in a target data table through the operation maintenance service.
On the basis of the above embodiment, optionally, the component creation module includes:
the version information generating unit is used for writing the code construction turn, the component name, the component branch name and the construction time of the target component product into the version information file as component version information through a continuous integration tool Jenkins;
and the information adding unit is used for adding the version information file into the target component product package.
On the basis of the above embodiment, optionally, the method further includes:
and the display module is used for displaying the component version information stored in the target data table in a preset operation and maintenance interface so as to be convenient for operation and maintenance personnel to check.
On the basis of the above embodiment, optionally, the method further includes:
the request generation module is used for generating a version information synchronization request according to the touch operation of the operation and maintenance personnel on the operation and maintenance interface; the version information synchronization request comprises at least one appointed component needing to synchronize version information;
the request response module is used for responding to the version information synchronization request, reading the version information of the component from the version information file of the appointed component through the component operation and maintenance proxy service, and sending the version information to the operation and maintenance service;
and the storage module is used for storing the received component version information in a target data table through the operation maintenance service.
On the basis of the above embodiment, optionally, the method further includes:
and the verification module is used for verifying the version information of the target component product package before the target component product package is installed, and intercepting the installation of the target component product package under the condition that the verification fails.
On the basis of the above embodiment, optionally, the version information of the distributed database is composed of component version information of each component in the distributed database.
The product can execute the method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
In the technical scheme of the invention, the related processes of collecting, storing, using, processing, transmitting, providing, inventing and the like of the personal information of the user accord with the regulations of related laws and regulations, and the public order is not violated.
According to embodiments of the present invention, the present invention also provides an electronic device, a readable storage medium and a computer program product.
Fig. 5 shows a schematic diagram of the structure of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 5, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM12 and the RAM13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
Various components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, for example, performs a distributed database version information management method.
In some embodiments, the distributed database version information management method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM12 and/or the communication unit 19. When the computer program is loaded into RAM13 and executed by processor 11, one or more steps of the distributed database version information management method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the distributed database version information management method in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above can be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable distributed database version information management apparatus, such that the computer programs, when executed by the processor, cause the functions/operations specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.
Claims (10)
1. A distributed database version information management method, comprising:
creating a target component product package required by a distributed database, and adding a version information file into the target component product package;
responding to the event that the target component product package is successfully installed, and establishing communication connection between component operation and maintenance proxy service and operation and maintenance service of the distributed database;
reading the component version information from the version information file of the target component product package through the component operation and maintenance proxy service, and sending the component version information to the operation and maintenance service;
and storing the received component version information in a target data table through the operation and maintenance service.
2. The method of claim 1, wherein adding a version information file to the target component product package comprises:
through a continuous integration tool Jenkins, the code construction turn, the component name, the component branch name and the construction time of a target component product are used as component version information to be written into the version information file;
and adding the version information file into the target component product package.
3. The method as recited in claim 1, further comprising:
and displaying the component version information stored in the target data table in a preset operation and maintenance interface so as to be convenient for operation and maintenance personnel to check.
4. A method according to claim 3, further comprising:
generating a version information synchronization request according to touch operation of the operation and maintenance personnel on the operation and maintenance interface; the version information synchronization request comprises at least one appointed component needing to synchronize version information;
responding to the version information synchronization request, reading the version information of the component from the version information file of the appointed component through the component operation and maintenance proxy service, and sending the version information to the operation and maintenance service;
and storing the received component version information in a target data table through the operation and maintenance service.
5. The method as recited in claim 1, further comprising:
before installing the target component product package, verifying version information of the target component product package, and intercepting the installation of the target component product package under the condition that verification fails.
6. The method of claim 1, wherein the version information of the distributed database is comprised of component version information of each component in the distributed database.
7. A distributed database version information management apparatus, comprising:
the system comprises a component creation module, a storage module and a storage module, wherein the component creation module is used for creating a target component product package required by a distributed database and adding a version information file into the target component product package;
the connection module is used for responding to the event that the target component product package is successfully installed, and establishing communication connection between the component operation and maintenance proxy service and the operation and maintenance service of the distributed database;
the version information reading module is used for reading the version information of the component from the version information file of the target component product package through the component operation and maintenance proxy service and sending the version information to the operation and maintenance service;
and the storage module is used for storing the received component version information in a target data table through the operation maintenance service.
8. The apparatus of claim 7, wherein the component creation module comprises:
the version information generating unit is used for writing the code construction turn, the component name, the component branch name and the construction time of the target component product into the version information file as component version information through a continuous integration tool Jenkins;
and the information adding unit is used for adding the version information file into the target component product package.
9. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the distributed database version information management method of any one of claims 1-6.
10. A non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the distributed database version information management method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311520153.4A CN117290342A (en) | 2023-11-15 | 2023-11-15 | Distributed database version information management method, device, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311520153.4A CN117290342A (en) | 2023-11-15 | 2023-11-15 | Distributed database version information management method, device, electronic equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117290342A true CN117290342A (en) | 2023-12-26 |
Family
ID=89251942
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311520153.4A Pending CN117290342A (en) | 2023-11-15 | 2023-11-15 | Distributed database version information management method, device, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117290342A (en) |
-
2023
- 2023-11-15 CN CN202311520153.4A patent/CN117290342A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110162334B (en) | Code management method, device and storage medium | |
| US20200019559A1 (en) | Synchronizing object in local object storage node | |
| CN106648994B (en) | Method, equipment and system for backing up operation log | |
| CN112835616A (en) | Version upgrading method and device, electronic equipment and storage medium | |
| CN109471647B (en) | Data updating method and device, electronic equipment and readable medium | |
| CN114089974B (en) | Cloud code development system, method, device, equipment and storage medium | |
| CN110059011A (en) | Interface test method, device, medium and electronic equipment | |
| CN109299124B (en) | Method and apparatus for updating a model | |
| CN113296796A (en) | Project release method, device, system, storage medium and electronic equipment | |
| CN115129574A (en) | Code testing method and device | |
| CN117290342A (en) | Distributed database version information management method, device, electronic equipment and medium | |
| CN114579120A (en) | Application code processing method and device, electronic equipment and storage medium | |
| CN114328739A (en) | Data synchronization method, data reading method, data synchronization device, data reading device, electronic equipment, storage medium and product | |
| CN108170557B (en) | Method and apparatus for outputting information | |
| CN113806327A (en) | Database design method and device and related equipment | |
| CN113626409B (en) | Test data processing method, device, equipment and storage medium | |
| CN113872808B (en) | Application processing method and device | |
| EP4227796A1 (en) | Service deployment processing method and apparatus, electronic device, and storage medium | |
| CN114860247A (en) | Data processing method, device, equipment and storage medium | |
| CN116841517A (en) | Code maintenance method and device, computer readable storage medium and electronic equipment | |
| CN116991414A (en) | File processing method, device, equipment and storage medium | |
| CN115686479A (en) | File creation method and related device | |
| CN116360823A (en) | Method and device for updating application program in cloud mobile phone | |
| CN115129323A (en) | Method, device and equipment for processing data resource packet and storage medium | |
| CN115469882A (en) | Software project management method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |