CN113590213B - Component maintenance method, electronic device and storage medium - Google Patents
Component maintenance method, electronic device and storage medium Download PDFInfo
- Publication number
- CN113590213B CN113590213B CN202110704634.5A CN202110704634A CN113590213B CN 113590213 B CN113590213 B CN 113590213B CN 202110704634 A CN202110704634 A CN 202110704634A CN 113590213 B CN113590213 B CN 113590213B
- Authority
- CN
- China
- Prior art keywords
- component
- maintenance
- version data
- priority
- component maintenance
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Mathematical Physics (AREA)
- Computational Linguistics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a component maintenance method, electronic equipment and a storage medium, wherein the method comprises the following steps: acquiring current version data of the component and version data in the maintenance information; matching the current version data of the component with the version data in the maintenance information; generating a component maintenance state identifier according to the matching result; the component maintenance state identifier is used for representing two different component maintenance states of component maintenance completion and component maintenance non-maintenance; component maintenance is performed with reference to the component maintenance status identifier. Through the implementation of the invention, a large amount of data is analyzed by using a simple logic structure, so that the high-complexity component maintenance work is effectively completed, and the components are comprehensively and timely maintained.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method and an apparatus for maintaining a component.
Background
In the current component maintenance process, the process loading the component to be maintained is firstly required to be closed, then an upgrading process is started, the latest version of the component is downloaded from a server through the upgrading process, the latest version is finally used for replacing the local old version, and then the closed process is started, so that the component maintenance is completed, and the identification of maintenance data is mainly a version number.
In recent years, more and more third party components are introduced in software development, and some of the third party components are open-source, so that a plurality of remote developers are allowed to work cooperatively, the maintenance period is faster, the version data is more, the overall maintenance is relatively slower, and the real-time performance is poorer.
Disclosure of Invention
The technical problems to be solved by the invention are as follows: the maintenance efficiency of the component maintenance mode provided in the related art is low and the real-time performance is poor.
In order to solve the above technical problem, a first aspect of the present invention provides a component maintenance method, including: acquiring current version data of the component and version data in the maintenance information; matching the current version data of the component with the version data in the maintenance information; generating a component maintenance state identifier according to the matching result; the component maintenance state identifier is used for representing two different component maintenance states of component maintenance completion and component maintenance non-maintenance; component maintenance is performed with reference to the component maintenance status identifier.
A second aspect of the present application provides an electronic device, including: a processor, a memory, and a communication bus; the communication bus is used for realizing connection communication between the processor and the memory; the processor is configured to execute one or more programs stored in the memory to implement the component maintenance method.
A third aspect of the present application provides a storage medium having a computer program stored therein, the data storage device performing the component maintenance method when the computer program is executed by at least one processor of the data storage device.
The method has the advantages that for the components with normal update versions, the components can be directly updated by multithreading through the technology of the application, and the update is more timely; for components lacking version data, or newly constructed components, the components may be exposed and summarized directly by the techniques of the present application. Therefore, a large amount of data is analyzed by using a simple logic structure, so that high-complexity component maintenance work is effectively completed, and components are comprehensively and timely maintained.
Drawings
The following details the specific construction of the present invention with reference to the accompanying drawings
FIG. 1 is an overall flow chart of a component maintenance method according to a first embodiment of the present invention;
FIG. 2 is a flow chart of performing component maintenance according to a first embodiment of the present invention;
FIG. 3 is a flow chart of the acquisition of component maintenance priorities in accordance with a first embodiment of the present invention;
FIG. 4 is a flow chart of determining the order of maintenance of the medium priority components according to a first embodiment of the present invention;
FIG. 5 is a flowchart for updating maintenance information according to a first embodiment of the present invention;
FIG. 6 is a schematic diagram of a program module of a component maintenance apparatus according to a second embodiment of the present invention;
fig. 7 is a schematic structural diagram of an electronic device according to a third embodiment of the present invention.
Detailed Description
In order to describe the technical content, the constructional features, the achieved objects and effects of the present invention in detail, the following description is made in connection with the embodiments and the accompanying drawings.
A component is a simple package of data and methods. The components can be used for realizing drag-and-drop programming, rapid attribute processing and real object-oriented design, and the existing component maintenance means are used, so that maintenance personnel are required to acquire the version information of each component, such as finger palm, in real time, and the professional is required to monitor the version information of various components. With the development of the age, one project has more and more components, and a large amount of data needing to be maintained is generated, so that the components are difficult to maintain. This is particularly true for projects developed using Ruby, where the development cycle is relatively short, and more components are easier to use.
Ruby is a language, is completely object-oriented, is an object, comprises basic data types in other languages, can store any type of data, and has a value whether a mathematical or logical expression or a statement.
It should be appreciated that Ruby is open-source, offered free of charge on the Web, can be used to write Common Gateway Interface (CGI) scripts, and can be embedded in hypertext markup language (HTML). The method has strong expandability, and a large program written by Ruby is easy to maintain. Ruby supports many GUI tools such as Tcl/Tk, GTK and OpenGL; it can be easily connected to DB2, mySQL, oracle, and Sybase. Moreover, the method has rich built-in functions and can be directly used in Ruby scripts.
Based on this, in order to change this status quo, version information and maintenance information are not manually recorded. The system automatically compares and matches the data to determine the difference and the connection of the data and generate the maintenance state identification. By maintaining the state identification, multiple threads can be invoked directly while maintaining multiple components.
It can be appreciated that if the maintenance status identifiers are the same, then multiple components can be maintained simultaneously; if the maintenance status identifiers are different, multiple components may be maintained separately, which may be maintained from different locations, and may also have time-lapse maintenance.
First embodiment:
referring to fig. 1, fig. 1 is an overall flowchart of a component maintenance method according to a first embodiment of the present invention. The first aspect of the present invention introduces a component maintenance method, including:
step S101, the current version data of the component and the version data in the maintenance information are acquired.
In this embodiment, the current version data of the component mainly refers to the current version data of the specific component in the Ruby item to be detected or other items. The current version data of the component can be obtained through a database, and the version data in the component to be maintained can also be obtained through analyzing the component to be maintained so as to obtain more accurate data.
In this embodiment, the version data in the maintenance information mainly refers to the recorded version data of the component in some networks or software libraries, which may be static or dynamic. The current version data of the component is associated with the version data in the maintenance information by a key, which may be the name of the component, the name of a specific object in the component, or an ID value or other identifier of the component.
The version data may represent version information of the entire component, or may include version information of a component having a dependency relationship with the component.
Step S102, matching the current version data of the component with the version data in the maintenance information.
It should be understood that the component and the maintenance information respectively contain the same or matched fields, and the specific field is used as a bridge, so that data between two databases can be connected, and a plurality of databases are combined to form a database set. Matching the current version data of the component with the version data in the maintenance information comprises at least two matching schemes: under the first matching scheme, the current version data of the component is identical to the version data in the maintenance information, and the current version data and the version data in the maintenance information are considered to be matched; under the first matching scheme, in the current version data of the component and the version data in the maintenance information, it is necessary to obtain version numbers from the version data respectively and calculate a gap between the version numbers. As long as the difference between the version number in the current version data of the component and the version data in the maintenance information lies within a certain threshold range, the two can be considered to be matched.
In the above description, the component maintenance status identifier is used to characterize two different component maintenance statuses, namely, component non-maintenance status and component maintenance completion status. It should be appreciated that the component maintenance status identifier may be various, may be any string including "space" or may be some database.
In the above, if the component maintenance status identifier is used for representing, the component is not maintained; it may be characterized that the component has never been serviced, or that the component has not been serviced for a certain period, or that the component requires further maintenance. Correspondingly, if the component maintenance state identifier is used for representing, the component maintenance is completed; it may be characterized that the component has completed maintenance, or that the component has completed maintenance within a certain period, or that the component does not require further maintenance.
It should be appreciated that the component is not maintained and is maintained in two opposite states, in some cases, interchangeable, and there is a relationship between the two. Because different components may have different update requirements, it is also possible to guarantee the relationship and status of certain important components or special components by formulating certain priorities.
Step S104, the component maintenance is carried out by referring to the component maintenance state identifier.
In this embodiment, for components that can update a new version normally, the components can be updated directly by directly calling the multithreading through the scheme of this embodiment, so that the updating is more timely; for components lacking version data, or newly constructed components, the components may be exposed and summarized directly by the techniques of the present application. Therefore, a large amount of data is analyzed by using a simple logic structure, so that high-complexity component maintenance work is effectively completed, and components are comprehensively and timely maintained.
Further, referring to fig. 2, fig. 2 is a flowchart of a method for performing component maintenance according to a first embodiment of the present invention. The step S104 specifically includes the following steps:
step S201, acquiring the priority of component maintenance according to the component maintenance state identification; the component maintenance state identifiers are in one-to-one correspondence with the priority of component maintenance;
step S202, asynchronous component maintenance is carried out according to the priority of component maintenance.
In this embodiment, when the component maintenance is performed according to the requirement of the client, the component maintenance status identifier has multiple forms, and the component maintenance status identifier may be used as standard data for distinguishing the component maintenance priority. If the component has a different component maintenance status identification, it has a different priority.
It should be understood that after certain component maintenance is complete, different priorities should be set; for some secondary switch components, the components can be kept in a special state that the components are not maintained. Therefore, the method can adapt to the customer demands of different technical fields. It should be noted that in this embodiment, different components may have different priorities, however, the two different component maintenance states of the component maintenance-free state and the component maintenance-completed state may have any set priority.
In a specific embodiment, please refer to fig. 3, fig. 3 is a flowchart of a method for acquiring a priority of component maintenance according to a first embodiment of the present invention; the step S201 specifically includes the following steps:
step S301, if the component maintenance state identification characterizes that the component maintenance is completed, determining that the component is a low-priority component;
step S302, if the component maintenance state identification represents that the component is not maintained, determining that the component is a high-priority component;
correspondingly, the step S104 specifically includes: after the high priority components are maintained, the low priority components are maintained.
It should be understood that in this embodiment, the solution described is only one arrangement of high and low priority components, and should be replaced with equivalent ones if the priorities of the two components are fully changed.
In the above, the asynchronous component maintenance belongs to the asynchronous processing of the computer multithreading. In contrast to synchronous processing, asynchronous processing does not block the current thread to wait for processing to complete, but rather allows subsequent operations until the other threads complete processing and callback informs the thread of the results of the other threads.
In a further scheme, the component maintenance state identifiers are further subdivided, and certain specific component identifiers are separated to formulate certain specific assignment strategies.
The step S103 specifically includes: if the component maintenance state identification is detected to represent the component maintenance in progress, determining that the component is a medium priority component;
correspondingly, the step S104 further includes, before the maintenance of the low priority component: the medium priority component is maintained.
It should be appreciated that in this embodiment, the high priority components may be further partitioned, from which the medium priority components are separated, and different strategies or means may be adopted for both. In another embodiment, low priority components may be identified, with certain specific components selected as medium priority components. Priority is a contract, first done with high priority and then done with low priority. The priority is a parameter for determining the priority level of each job program to accept the system resource when the computer time-sharing operating system processes a plurality of job programs.
Further, referring to fig. 4, fig. 4 is a flowchart illustrating a method for determining an order of maintenance of a priority component according to a first embodiment of the present invention; before the step of maintaining the middle priority component, the method further comprises the following steps:
step S401, comparing the current version data of the middle priority component with the version data in the maintenance information to obtain the version difference information of the middle priority component;
step S402, determining the maintenance sequence of the plurality of medium priority components according to the version difference information of the medium priority components.
In this embodiment, the version difference information of the middle priority component characterizes the number of versions between the current version data of the middle priority component and the version data in the maintenance information; the strategy for maintaining the medium priority component is formulated mainly through version difference information of the medium priority component. Generally, a certain file among the components stores version information of the components, which can be used as a basis for judgment.
It should be appreciated that the number of versions between the current version data of the medium priority component and the version data in the maintenance information may be the difference between the version numbers or the number of differences in the version information. Since the components with larger version differences are more likely to be bug-prone, component maintenance can be better performed using the version difference information.
It should be appreciated that during maintenance of the component, two databases are not used to store data, nor are component maintenance status identifiers used in most cases. In this application, at least two databases are partitioned for the sake of clarity of the overall data structure.
Based on this, the method further comprises: creating a first database and a second database;
storing the component identification, the current version data and the first mapping relation by using a first database; the first mapping relation is: the mapping relation between the component identification and the current version data;
storing the component identifier, the component maintenance state identifier and the second mapping relation by using a second database; the second mapping relation is: the component identifier and the component maintenance state identifier are mapped.
It should be understood that, the first mapping relationship and the second mapping relationship in this embodiment are merely a representation description manner, which is used for representation, and there is a certain association between two data. It should be understood that the first mapping relationship and the second mapping relationship do not have a specific tendency.
Correspondingly, after the component maintenance is performed by referring to the component maintenance state identifier, the method further comprises the step of updating the first database:
generating an acquisition sequence of the component maintenance state identifiers according to the priority of the component maintenance; the acquisition sequence of the component maintenance state identifiers corresponds to the priority of component maintenance;
generating an acquisition sequence of the component identifiers according to the acquisition sequence of the component maintenance state identifiers and the second mapping relation; the acquisition sequence of the component identifiers corresponds to the acquisition sequence of the component maintenance state identifiers;
and updating the current version data in the first database according to the acquisition sequence of the component identifiers and the first mapping relation.
Wherein, in order to update the first database more accurately, the relevant information in the first database can be directly changed after the component is maintained once. Therefore, the simplicity of the whole data structure can be improved, the granularity is enhanced, the whole data is conveniently divided into a plurality of parts, and a plurality of groups are used for analysis and maintenance.
Specifically, the component identifier is a component name; updating the current version data in the first database according to the acquisition sequence of the component identifiers and the first mapping relation, wherein the updating comprises the following steps:
and updating the current version data in the first database according to the acquisition sequence of the component names and the first mapping relation.
In a specific embodiment, first, the database builds a table sql script, creates a component name table as a first database, and creates a component version table as a second database. Where sql generally refers to a structured query language, a database query and programming language, used to access data and query, update, and manage relational database systems.
Next, in order to obtain the component name, the following assembly request address needs to be used: url https:// rubygems. Org/gemsletter = { cletter } & page = { page }; wherein, the letter field is replaced by the capital English letters from A to Z in sequence by using a cyclic matching array or other means; the pageno field is replaced by 1, the paging sending request is sequentially increased, the name data of the response data acquisition component is analyzed, and the name data is stored in the component name library.
Then, the component name library is queried, the component name of the undetermined version data is obtained according to the version identification field, and the request address is assembled: url https:// rubygems. Org/gems/{ name }/versions; and replacing the name with the name of the component inquired from the library, sending an http request, analyzing response data to acquire the name and version data of the component, and storing the name and version data into the component version library.
Further, referring to fig. 5, fig. 5 is a flowchart of a method for updating maintenance information according to a first embodiment of the present invention. The method further comprises the steps of: after at least one preset component maintenance period, version data in maintenance information are obtained;
step S501, obtaining update information corresponding to maintenance information; the update information includes: version data;
step S502, comparing version data in the update information with version data in the maintenance information to obtain version difference information; the version difference information characterizes that version data in the update information and version data in the maintenance information are different;
step S503, replacing the version data in the maintenance information by the version data in the update information according to the version difference information.
It should be appreciated that in order to better maintain the effectiveness of maintenance, version data in the maintenance information needs to be updated dynamically. The preset component maintenance period can be a time period or a process period of data maintenance. Thereby, real-time data updating can be ensured. Further improving the comprehensiveness. It should be appreciated that low priority components may not be maintained during a maintenance cycle; it is contemplated that only one component maintenance status identifier for characterizing a component as a high priority component is included in the change.
Second embodiment:
fig. 6 is a schematic program module of a component maintenance apparatus according to a second embodiment of the present invention. A fourth aspect of the present application provides a component maintenance device, comprising:
the data acquisition module is used for acquiring the current version data of the component and version data in the maintenance information;
the data matching module is used for matching the current version data of the component with the version data in the maintenance information;
the identification generation module is used for generating a component maintenance state identification according to the matching result; the component maintenance state identifier is used for representing two different component maintenance states of component maintenance completion and component maintenance non-maintenance;
and the data maintenance module is used for carrying out component maintenance by referring to the component maintenance state identifier.
In an alternative embodiment, the data maintenance module is configured to obtain a priority of component maintenance according to the component maintenance status identifier; the component maintenance state identifiers are in one-to-one correspondence with the priority of component maintenance; and carrying out asynchronous component maintenance according to the priority of the component maintenance.
The data maintenance module is used for determining that the component is a low-priority component if the component maintenance state identification indicates that the maintenance of the component is completed; if the component maintenance state identification characterizes that the component is not maintained, determining that the component is a high-priority component;
the data maintenance module is used for: after the high priority components are maintained, the low priority components are maintained.
In the above, the component maintenance status identifier is further used for characterizing that component maintenance is in progress; the identification generation module is further used for:
if the component maintenance state identification is detected to represent the component maintenance in progress, determining that the component is a medium priority component;
before the maintenance of the low priority component, the method further comprises:
the medium priority component is maintained.
In an alternative embodiment, the data maintenance module is further configured to: comparing the current version data of the middle priority component with the version data in the maintenance information to obtain version difference information of the middle priority component; version difference information of the middle priority component, representing the number of versions between the current version data of the middle priority component and the version data in the maintenance information;
and determining the maintenance sequence of the plurality of medium priority components according to the version difference information of the medium priority components.
Further, the apparatus further comprises: the database construction module is used for storing the component identification, the current version data and the first mapping relation by using the first database; the first mapping relation is: the mapping relation between the component identification and the current version data;
storing the component identifier, the component maintenance state identifier and the second mapping relation by using a second database; the second mapping relation is: the mapping relation between the component identifier and the component maintenance state identifier;
the apparatus further comprises: a database maintenance module for: generating an acquisition sequence of the component maintenance state identifiers according to the priority of the component maintenance; the acquisition sequence of the component maintenance state identifiers corresponds to the priority of component maintenance;
generating an acquisition sequence of the component identifiers according to the acquisition sequence of the component maintenance state identifiers and the second mapping relation; the acquisition sequence of the component identifiers corresponds to the acquisition sequence of the component maintenance state identifiers;
and updating the current version data in the first database according to the acquisition sequence of the component identifiers and the first mapping relation.
In the above description, the component is identified as a component name.
In an optional embodiment, the apparatus further includes a period calculation module, configured to obtain version data in the maintenance information after at least one preset component maintenance period;
acquiring update information corresponding to the maintenance information; the update information includes: version data;
comparing version data in the update information with version data in the maintenance information to obtain version difference information; the version difference information characterizes that version data in the update information and version data in the maintenance information are different;
and replacing the version data in the maintenance information by using the version data in the update information according to the version difference information.
Third embodiment:
the present embodiment provides an electronic device, referring to fig. 7, which includes a processor 701, a memory 702, and a communication bus 703, wherein: a communication bus 703 is used to enable connected communication between the processor 701 and the memory 702; the processor 701 is configured to execute one or more computer programs stored in the memory 702 to implement at least one step of the component maintenance method in the above-described embodiment.
The present embodiments also provide a computer-readable storage medium including volatile or nonvolatile, removable or non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, computer program modules or other data. Computer-readable storage media includes, but is not limited to, RAM (Random Access Memory ), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory, charged erasable programmable Read-Only Memory), flash Memory or other Memory technology, CD-ROM (Compact Disc Read-Only Memory), digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
The computer readable storage medium in this embodiment may be used to store one or more computer programs, where the stored one or more computer programs may be executed by a processor to implement at least one step of the method in the first embodiment.
The present embodiment also provides a computer program which can be distributed on a computer readable medium and executed by a computable device to implement at least one step of the method of the above embodiment; and in some cases at least one of the steps shown or described may be performed in a different order than that described in the above embodiments.
The present embodiment also provides a computer program product comprising computer readable means having stored thereon a computer program as shown above. The computer readable means in this embodiment may comprise a computer readable storage medium as shown above.
It will be apparent to one skilled in the art that all or some of the steps of the methods, systems, functional modules/units in the apparatus disclosed above may be implemented as software (which may be implemented in computer program code executable by a computing apparatus), firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between the functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed cooperatively by several physical components. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit.
Furthermore, as is well known to those of ordinary skill in the art, communication media typically embodies computer readable instructions, data structures, computer program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and may include any information delivery media. Therefore, the present invention is not limited to any specific combination of hardware and software.
The foregoing is a further detailed description of embodiments of the invention in connection with the specific embodiments, and it is not intended that the invention be limited to the specific embodiments described. It will be apparent to those skilled in the art that several simple deductions or substitutions may be made without departing from the spirit of the invention, and these should be considered to be within the scope of the invention.
Claims (9)
1. A method of component maintenance, comprising:
acquiring current version data of the component and version data in the maintenance information;
matching the current version data of the component with the version data in the maintenance information;
generating a component maintenance state identifier according to the matching result; the component maintenance state identifier is used for representing two different component maintenance states of component maintenance completion and component maintenance non-maintenance;
performing component maintenance by referring to the component maintenance state identifier;
storing the component identification, the current version data and the first mapping relation by using a first database; the first mapping relation is as follows: the component identification and the mapping relation between the current version data;
the second database is used for storing the component identifier, the component maintenance state identifier and the second mapping relation; the second mapping relation is as follows: the mapping relation between the component identifier and the component maintenance state identifier;
after the component maintenance is performed by the reference component maintenance state identifier, the method further comprises the following steps:
generating an acquisition sequence of the component maintenance state identifiers according to the priority of the component maintenance; the acquisition sequence of the component maintenance state identifiers corresponds to the priority of the component maintenance;
generating an acquisition sequence of the component identifier according to the acquisition sequence of the component maintenance state identifier and the second mapping relation; the acquisition sequence of the component identifiers corresponds to the acquisition sequence of the component maintenance state identifiers;
and updating the current version data in the first database according to the acquisition sequence of the component identifiers and the first mapping relation.
2. The component maintenance method of claim 1, wherein the referencing the component maintenance status identifier for component maintenance comprises:
acquiring the priority of component maintenance according to the component maintenance state identification; the component maintenance state identifiers are in one-to-one correspondence with the priority levels of the component maintenance;
and carrying out asynchronous component maintenance according to the priority of the component maintenance.
3. The component maintenance method according to claim 2, wherein the obtaining the priority of component maintenance according to the component maintenance status identifier includes:
if the component maintenance state identification characterizes that the component maintenance is completed, determining that the component is a low-priority component;
if the component maintenance state identification represents that the component is not maintained, determining that the component is a high-priority component;
and performing asynchronous component maintenance according to the priority of the component maintenance, wherein the asynchronous component maintenance comprises the following steps:
after the high priority component is maintained, the low priority component is maintained.
4. The component maintenance method of claim 3, wherein the component maintenance status identifier is further used to characterize component maintenance in progress; the step of obtaining the priority of component maintenance according to the component maintenance state identifier comprises the following steps:
if the component maintenance state identification is detected to represent the component maintenance in progress, determining that the component is a medium priority component;
before the maintenance of the low priority component, the method further comprises:
and maintaining the medium priority component.
5. The component maintenance method of claim 4, wherein: before the maintenance of the medium priority component, the method further comprises:
comparing the current version data of the medium priority component with the version data in the maintenance information to obtain version difference information of the medium priority component; version difference information of the medium priority component characterizes the version number between the current version data of the medium priority component and the version data in the maintenance information;
and determining the maintenance sequence of a plurality of medium priority components according to the version difference information of the medium priority components.
6. The component maintenance method of claim 1, wherein the component is identified as a component name; the updating the current version data in the first database according to the acquisition sequence of the component identifiers and the first mapping relation comprises the following steps:
and updating the current version data in the first database according to the acquisition sequence of the component names through the mapping relation between the component names and the first mapping relation.
7. The component maintenance method of claim 1, wherein the method further comprises: after at least one preset component maintenance period, version data in the maintenance information are acquired;
acquiring update information corresponding to the maintenance information; the update information includes: version data;
comparing the version data in the update information with the version data in the maintenance information to obtain version difference information; the version difference information characterizes that version data in the update information and version data in the maintenance information are different;
and replacing the version data in the maintenance information by using the version data in the update information according to the version difference information.
8. An electronic device, the electronic device comprising: a processor, a memory, and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more programs stored in the memory to implement the component maintenance method of any of claims 1-7.
9. A storage medium having a computer program stored therein, the data storage device performing the component maintenance method of any of claims 1-7 when executed by at least one processor of the data storage device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110704634.5A CN113590213B (en) | 2021-06-24 | 2021-06-24 | Component maintenance method, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110704634.5A CN113590213B (en) | 2021-06-24 | 2021-06-24 | Component maintenance method, electronic device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113590213A CN113590213A (en) | 2021-11-02 |
| CN113590213B true CN113590213B (en) | 2023-04-25 |
Family
ID=78244529
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110704634.5A Active CN113590213B (en) | 2021-06-24 | 2021-06-24 | Component maintenance method, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113590213B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115237439A (en) * | 2022-06-14 | 2022-10-25 | 深圳开源互联网安全技术有限公司 | Method and device for maintaining C# component data |
Citations (42)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101883123A (en) * | 2009-05-04 | 2010-11-10 | 华为技术有限公司 | Method, device and system for verifying security status of telecommunication equipment |
| EP2013718A4 (en) * | 2006-04-14 | 2012-08-08 | Vertafore Inc | Method, system, and computer-readable medium to provide version management of documents in a file management system |
| WO2013170871A1 (en) * | 2012-05-14 | 2013-11-21 | Abb Research Ltd | Method and industrial control system for industrial process equipment maintenance |
| CN104143067A (en) * | 2014-08-05 | 2014-11-12 | 广东欧珀移动通信有限公司 | Implementation method of a terminal device and software sharing mechanism |
| CN104932395A (en) * | 2015-06-08 | 2015-09-23 | 江汉大学 | Intelligent maintenance device and method of photovoltaic assembly monitoring system |
| CN105653901A (en) * | 2015-12-29 | 2016-06-08 | 深圳市科漫达智能管理科技有限公司 | Component repository management method and system |
| CN106559251A (en) * | 2015-09-30 | 2017-04-05 | 中兴通讯股份有限公司 | A kind of Compilation Method and corresponding interface, component and system based on YANG models |
| CN106886410A (en) * | 2017-01-06 | 2017-06-23 | 深圳云天励飞技术有限公司 | A kind of software version management system |
| CN108170465A (en) * | 2018-01-04 | 2018-06-15 | 武汉斗鱼网络科技有限公司 | A kind of version information management method, electronic equipment and readable storage medium storing program for executing |
| CN108363564A (en) * | 2018-01-23 | 2018-08-03 | 平安普惠企业管理有限公司 | Entry modularization implementation method, device, terminal device and storage medium |
| EP3403177A1 (en) * | 2016-01-15 | 2018-11-21 | Google LLC. | Managing delivery of code and dependent data using application containers |
| CN108897969A (en) * | 2018-07-12 | 2018-11-27 | 椭圆方程（深圳）信息技术有限公司 | A method of the facility maintenance Automatic dispatching based on BIM |
| CN108984160A (en) * | 2018-06-21 | 2018-12-11 | 中国石油集团安全环保技术研究院有限公司 | Information-based Quick Development Framework and method based on modularization |
| CN108989072A (en) * | 2017-06-05 | 2018-12-11 | 阿里巴巴集团控股有限公司 | A method and device for deploying, managing and invoking components |
| CN109165055A (en) * | 2018-08-30 | 2019-01-08 | 百度在线网络技术（北京）有限公司 | A kind of component loading method, device, computer equipment and storage medium |
| CN109446492A (en) * | 2018-10-17 | 2019-03-08 | 南京垂宇网络科技有限公司 | Method for maintaining consistency of document editing data |
| CN109474759A (en) * | 2018-10-24 | 2019-03-15 | 咪咕音乐有限公司 | Information processing method, device and storage medium |
| CN109542366A (en) * | 2018-10-26 | 2019-03-29 | 金蝶软件（中国）有限公司 | Method of printing, device, equipment and storage medium based on browser |
| CN109542475A (en) * | 2018-10-22 | 2019-03-29 | 平安科技（深圳）有限公司 | Data-updating method, device, storage medium and the server of system multi version |
| CN109726192A (en) * | 2018-12-24 | 2019-05-07 | 普元信息技术股份有限公司 | System and method for separate management function of master data model version and field based on big data environment |
| CN109743298A (en) * | 2018-12-19 | 2019-05-10 | 安徽典典科技发展有限责任公司 | A kind of control system and control method of uniform data publication component |
| CN110120880A (en) * | 2018-02-06 | 2019-08-13 | 海能达通信股份有限公司 | Component update method and system |
| CN110162318A (en) * | 2019-04-12 | 2019-08-23 | 厦门天锐科技股份有限公司 | A kind of implementation method that terminal batch unimodule updates |
| CN110417598A (en) * | 2019-07-30 | 2019-11-05 | 普信恒业科技发展（北京）有限公司 | The management method and component manager of gateway component |
| CN110489120A (en) * | 2019-07-03 | 2019-11-22 | 平安证券股份有限公司 | Page development method component-based and server |
| CN111078200A (en) * | 2019-11-29 | 2020-04-28 | 深圳前海微众银行股份有限公司 | Task construction method, device, equipment, medium and system |
| CN111176617A (en) * | 2019-12-10 | 2020-05-19 | 中国航空工业集团公司成都飞机设计研究所 | Technical state management method for multiple system configurations |
| CN111309388A (en) * | 2020-02-03 | 2020-06-19 | 杭州迪普科技股份有限公司 | Automatic rollback system and method for system software version of device |
| EP3669659A1 (en) * | 2018-12-20 | 2020-06-24 | Constantin Pascu | Products and conservation without boiling for fruits, vegetables and edible flower petals |
| CN111400070A (en) * | 2020-03-24 | 2020-07-10 | 广州华多网络科技有限公司 | Terminal equipment and cross-process interface calling implementation and execution method thereof |
| CN111552737A (en) * | 2020-04-15 | 2020-08-18 | 国电南瑞科技股份有限公司 | A zookeeper-based multi-source data wide-area access system and method |
| CN111552504A (en) * | 2020-07-13 | 2020-08-18 | 深圳开源互联网安全技术有限公司 | Asset information maintenance method and device of open source assembly and storage medium |
| CN111897694A (en) * | 2020-07-30 | 2020-11-06 | 北京百度网讯科技有限公司 | Method and device, device and storage medium for message processing in applet |
| CN111932215A (en) * | 2020-09-18 | 2020-11-13 | 杭州趣链科技有限公司 | Intelligent contract version management method, equipment and readable storage medium |
| CN111932260A (en) * | 2020-09-18 | 2020-11-13 | 杭州趣链科技有限公司 | Intelligent contract version management method, equipment and readable storage medium |
| CN112050681A (en) * | 2019-06-05 | 2020-12-08 | 罗伯特·博世有限公司 | Cleaning system, heat exchanger assembly and method for air conditioning system |
| CN112231302A (en) * | 2020-10-30 | 2021-01-15 | 深圳开源互联网安全技术有限公司 | Method and device for maintaining Java switch component database and storage medium |
| CN112261171A (en) * | 2020-10-19 | 2021-01-22 | 天津津航计算技术研究所 | Method for determining IP camera position based on Ethernet protocol |
| CN112269634A (en) * | 2020-10-13 | 2021-01-26 | 苏州浪潮智能科技有限公司 | Method and system for deploying Ambari component based on Docker container |
| CN112328177A (en) * | 2020-11-04 | 2021-02-05 | 苏州浪潮智能科技有限公司 | A method, apparatus, device and readable medium for checking the health status of a storage system |
| CN112486629A (en) * | 2020-11-27 | 2021-03-12 | 成都新希望金融信息有限公司 | Micro-service state detection method and device, electronic equipment and storage medium |
| CN112862123A (en) * | 2021-03-02 | 2021-05-28 | 岭东核电有限公司 | Execution work order generation method and device, computer equipment and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9667646B2 (en) * | 2015-02-12 | 2017-05-30 | Netapp, Inc. | Maintaining dynamic configuration information of a multi-host off-cluster service on a cluster |
| US20170255663A1 (en) * | 2016-03-07 | 2017-09-07 | Researchgate Gmbh | Propagation of data changes in a distributed system |
| US12020011B2 (en) * | 2018-08-29 | 2024-06-25 | VMware LLC | Managing an upgrade of a virtualization infrastructure component |
-
2021
- 2021-06-24 CN CN202110704634.5A patent/CN113590213B/en active Active
Patent Citations (43)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2013718A4 (en) * | 2006-04-14 | 2012-08-08 | Vertafore Inc | Method, system, and computer-readable medium to provide version management of documents in a file management system |
| CN101883123A (en) * | 2009-05-04 | 2010-11-10 | 华为技术有限公司 | Method, device and system for verifying security status of telecommunication equipment |
| WO2013170871A1 (en) * | 2012-05-14 | 2013-11-21 | Abb Research Ltd | Method and industrial control system for industrial process equipment maintenance |
| CN104143067A (en) * | 2014-08-05 | 2014-11-12 | 广东欧珀移动通信有限公司 | Implementation method of a terminal device and software sharing mechanism |
| CN104932395A (en) * | 2015-06-08 | 2015-09-23 | 江汉大学 | Intelligent maintenance device and method of photovoltaic assembly monitoring system |
| CN106559251A (en) * | 2015-09-30 | 2017-04-05 | 中兴通讯股份有限公司 | A kind of Compilation Method and corresponding interface, component and system based on YANG models |
| CN105653901A (en) * | 2015-12-29 | 2016-06-08 | 深圳市科漫达智能管理科技有限公司 | Component repository management method and system |
| EP3403177A1 (en) * | 2016-01-15 | 2018-11-21 | Google LLC. | Managing delivery of code and dependent data using application containers |
| EP3584696A1 (en) * | 2016-01-15 | 2019-12-25 | Google LLC | Managing delivery of code and dependent data using application containers |
| CN106886410A (en) * | 2017-01-06 | 2017-06-23 | 深圳云天励飞技术有限公司 | A kind of software version management system |
| CN108989072A (en) * | 2017-06-05 | 2018-12-11 | 阿里巴巴集团控股有限公司 | A method and device for deploying, managing and invoking components |
| CN108170465A (en) * | 2018-01-04 | 2018-06-15 | 武汉斗鱼网络科技有限公司 | A kind of version information management method, electronic equipment and readable storage medium storing program for executing |
| CN108363564A (en) * | 2018-01-23 | 2018-08-03 | 平安普惠企业管理有限公司 | Entry modularization implementation method, device, terminal device and storage medium |
| CN110120880A (en) * | 2018-02-06 | 2019-08-13 | 海能达通信股份有限公司 | Component update method and system |
| CN108984160A (en) * | 2018-06-21 | 2018-12-11 | 中国石油集团安全环保技术研究院有限公司 | Information-based Quick Development Framework and method based on modularization |
| CN108897969A (en) * | 2018-07-12 | 2018-11-27 | 椭圆方程（深圳）信息技术有限公司 | A method of the facility maintenance Automatic dispatching based on BIM |
| CN109165055A (en) * | 2018-08-30 | 2019-01-08 | 百度在线网络技术（北京）有限公司 | A kind of component loading method, device, computer equipment and storage medium |
| CN109446492A (en) * | 2018-10-17 | 2019-03-08 | 南京垂宇网络科技有限公司 | Method for maintaining consistency of document editing data |
| CN109542475A (en) * | 2018-10-22 | 2019-03-29 | 平安科技（深圳）有限公司 | Data-updating method, device, storage medium and the server of system multi version |
| CN109474759A (en) * | 2018-10-24 | 2019-03-15 | 咪咕音乐有限公司 | Information processing method, device and storage medium |
| CN109542366A (en) * | 2018-10-26 | 2019-03-29 | 金蝶软件（中国）有限公司 | Method of printing, device, equipment and storage medium based on browser |
| CN109743298A (en) * | 2018-12-19 | 2019-05-10 | 安徽典典科技发展有限责任公司 | A kind of control system and control method of uniform data publication component |
| EP3669659A1 (en) * | 2018-12-20 | 2020-06-24 | Constantin Pascu | Products and conservation without boiling for fruits, vegetables and edible flower petals |
| CN109726192A (en) * | 2018-12-24 | 2019-05-07 | 普元信息技术股份有限公司 | System and method for separate management function of master data model version and field based on big data environment |
| CN110162318A (en) * | 2019-04-12 | 2019-08-23 | 厦门天锐科技股份有限公司 | A kind of implementation method that terminal batch unimodule updates |
| CN112050681A (en) * | 2019-06-05 | 2020-12-08 | 罗伯特·博世有限公司 | Cleaning system, heat exchanger assembly and method for air conditioning system |
| CN110489120A (en) * | 2019-07-03 | 2019-11-22 | 平安证券股份有限公司 | Page development method component-based and server |
| CN110417598A (en) * | 2019-07-30 | 2019-11-05 | 普信恒业科技发展（北京）有限公司 | The management method and component manager of gateway component |
| CN111078200A (en) * | 2019-11-29 | 2020-04-28 | 深圳前海微众银行股份有限公司 | Task construction method, device, equipment, medium and system |
| CN111176617A (en) * | 2019-12-10 | 2020-05-19 | 中国航空工业集团公司成都飞机设计研究所 | Technical state management method for multiple system configurations |
| CN111309388A (en) * | 2020-02-03 | 2020-06-19 | 杭州迪普科技股份有限公司 | Automatic rollback system and method for system software version of device |
| CN111400070A (en) * | 2020-03-24 | 2020-07-10 | 广州华多网络科技有限公司 | Terminal equipment and cross-process interface calling implementation and execution method thereof |
| CN111552737A (en) * | 2020-04-15 | 2020-08-18 | 国电南瑞科技股份有限公司 | A zookeeper-based multi-source data wide-area access system and method |
| CN111552504A (en) * | 2020-07-13 | 2020-08-18 | 深圳开源互联网安全技术有限公司 | Asset information maintenance method and device of open source assembly and storage medium |
| CN111897694A (en) * | 2020-07-30 | 2020-11-06 | 北京百度网讯科技有限公司 | Method and device, device and storage medium for message processing in applet |
| CN111932215A (en) * | 2020-09-18 | 2020-11-13 | 杭州趣链科技有限公司 | Intelligent contract version management method, equipment and readable storage medium |
| CN111932260A (en) * | 2020-09-18 | 2020-11-13 | 杭州趣链科技有限公司 | Intelligent contract version management method, equipment and readable storage medium |
| CN112269634A (en) * | 2020-10-13 | 2021-01-26 | 苏州浪潮智能科技有限公司 | Method and system for deploying Ambari component based on Docker container |
| CN112261171A (en) * | 2020-10-19 | 2021-01-22 | 天津津航计算技术研究所 | Method for determining IP camera position based on Ethernet protocol |
| CN112231302A (en) * | 2020-10-30 | 2021-01-15 | 深圳开源互联网安全技术有限公司 | Method and device for maintaining Java switch component database and storage medium |
| CN112328177A (en) * | 2020-11-04 | 2021-02-05 | 苏州浪潮智能科技有限公司 | A method, apparatus, device and readable medium for checking the health status of a storage system |
| CN112486629A (en) * | 2020-11-27 | 2021-03-12 | 成都新希望金融信息有限公司 | Micro-service state detection method and device, electronic equipment and storage medium |
| CN112862123A (en) * | 2021-03-02 | 2021-05-28 | 岭东核电有限公司 | Execution work order generation method and device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113590213A (en) | 2021-11-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110309071B (en) | Test code generation method and module, and test method and system | |
| CN110795455B (en) | Dependency analysis method, electronic device, computer apparatus, and readable storage medium | |
| US9038030B2 (en) | Methods for predicting one or more defects in a computer program and devices thereof | |
| US9021440B1 (en) | System and method for automated test script generation | |
| CN108647357B (en) | Data query method and device | |
| US10942840B2 (en) | System and method for managing a code repository | |
| CN112181951B (en) | Heterogeneous database data migration method, device and equipment | |
| CN113360519B (en) | Data processing method, device, equipment and storage medium | |
| CN112559641B (en) | Pull chain table processing method and device, readable storage medium and electronic equipment | |
| CN108345658B (en) | Decomposition processing method of algorithm calculation track, server and storage medium | |
| CN111625472B (en) | A unit testing method and device | |
| WO2021191702A1 (en) | Offloading statistics collection | |
| CN113010208A (en) | Version information generation method, version information generation device, version information generation equipment and storage medium | |
| CN113220530B (en) | Data quality monitoring method and platform | |
| US10592400B2 (en) | System and method for creating variants in a test database during various test stages | |
| CN113326401A (en) | Method and system for generating field blood margin | |
| CN110580253A (en) | Time sequence data set loading method and device, storage medium and electronic equipment | |
| CN113590213B (en) | Component maintenance method, electronic device and storage medium | |
| US20200057685A1 (en) | Automatically deploying hardware accelerators based on requests from users | |
| CN113760950A (en) | Index data query method and device, electronic equipment and storage medium | |
| CN116756173A (en) | Database conversion method, device, equipment, medium and program product | |
| KR101975998B1 (en) | Apparatus and Method for Data Migration Based on SQL sentences | |
| US8321844B2 (en) | Providing registration of a communication | |
| CN113377604A (en) | Data processing method, device, equipment and storage medium | |
| US8949819B2 (en) | Rationalizing functions to identify re-usable services |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |