CN113220528A - Resource object management method, electronic device and storage medium - Google Patents
Resource object management method, electronic device and storage medium Download PDFInfo
- Publication number
- CN113220528A CN113220528A CN202110524385.1A CN202110524385A CN113220528A CN 113220528 A CN113220528 A CN 113220528A CN 202110524385 A CN202110524385 A CN 202110524385A CN 113220528 A CN113220528 A CN 113220528A
- Authority
- CN
- China
- Prior art keywords
- attribute
- resource object
- value
- resource
- change
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3086—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves the use of self describing data formats, i.e. metadata, markup languages, human readable formats
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/20—Natural language analysis
- G06F40/237—Lexical tools
- G06F40/242—Dictionaries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/30—Semantic analysis
Abstract
The embodiment of the invention relates to the field of data processing, and discloses a resource object management method, electronic equipment and a storage medium. Some embodiments of the present application provide a method for managing resource objects, including the following steps: after the attribute of the resource object is changed, determining a change record rule of the attribute of the resource object according to the field type of the attribute of the resource object and/or the field value type of the attribute of the resource object and a pre-stored change record rule; wherein, the change record rules comprise change record rules of different field types and/or change record rules of different field value types; and recording the change information of the resource object according to the determined change recording rule. This embodiment enables to reduce the content of the change information of the resource object.
Description
Technical Field
The embodiment of the invention relates to the field of data processing, in particular to a resource object management method, electronic equipment and a storage medium.
Background
The service resource objects of the content distribution network include not only a large number of Internet Technology (IT) infrastructure resource objects (such as a computer room, a network, hardware, and the like), but also a large number of service logic resource objects (such as nodes, POPs, resource accounts, and the like) defined by the content distribution network. The existence of the correlation influence among the service resource objects forms a huge resource object network topology. A change in the state of one business resource object may cause a change in the state of one or more other business resource objects.
However, the conventional management method generally performs transaction management control with large granularity on the whole service resource object, or allows conflicting service to be executed sequentially through service logic arrangement. This approach may result in too much changed content of the overall resource object information.
Disclosure of Invention
An object of embodiments of the present invention is to provide a method, an electronic device, and a storage medium for managing resource objects, which enable content of change information of resource objects to be reduced.
To solve the foregoing technical problem, in one aspect, an embodiment of the present application provides a method for managing resource objects, including the following steps: after the attribute of the resource object is changed, determining a change record rule of the attribute of the resource object according to the field type of the attribute of the resource object and/or the field value type of the attribute of the resource object and a pre-stored change record rule; wherein, the change record rules comprise change record rules of different field types and/or change record rules of different field value types; and recording the change information of the resource object according to the determined change recording rule.
In another aspect, an embodiment of the present invention further provides an electronic device, 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 method for managing resource objects as set forth in the above embodiments.
On the other hand, the embodiment of the present invention further provides a computer-readable storage medium, which stores a computer program, and the computer program, when executed by a processor, implements the method for managing resource objects mentioned in the above embodiments.
According to the resource object management method, the electronic device and the storage medium provided by the embodiment of the invention, after the attribute of the resource object is changed, the change record rule of the attribute is determined based on the predefined change record rule, and the change information of the resource object is recorded. The audit content and scope is more accurate than recording the change information of the resource object for the change of the resource object. In addition, the information of the attribute of the resource object which is not changed can not be recorded in the change information, so that the content of the change information is reduced, and the occupied storage space is further reduced. Since the change information is generated based on the rule, the quick definition implementation without codes can be supported.
Drawings
One or more embodiments are illustrated by way of example in the accompanying drawings, which correspond to the figures in which like reference numerals refer to similar elements and which are not to scale unless otherwise specified.
FIG. 1 is a flow chart of a method for managing resource objects in an embodiment according to the application;
fig. 2 is a relational topology diagram of attribute elements of a resource object a, a resource object B, a resource object C, and a resource object D in the resource object management method in the embodiment of the present application;
FIG. 3 is a flow diagram of a method for managing resource objects in one embodiment of the present application;
FIG. 4 is a flow diagram of a method for managing resource objects in one embodiment of the present application;
FIG. 5 is a flow diagram of a method for managing resource objects in one embodiment of the present application;
FIG. 6 is a flow diagram of a method for managing resource objects in one embodiment of the present application;
FIG. 7 is a diagram illustrating the relationship between the attributes and sources of change for resource object A and resource object B in an embodiment of the present application;
FIG. 8 is a block diagram of an apparatus for managing resource objects in an embodiment of the present application;
FIG. 9 is a diagram illustrating an exemplary architecture of a device for managing resource objects according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention will be described in detail with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that in various embodiments of the invention, numerous technical details are set forth in order to provide a better understanding of the present application. However, the technical solution claimed in the present application can be implemented without these technical details and various changes and modifications based on the following embodiments. The following embodiments are divided for convenience of description, and should not constitute any limitation to the specific implementation manner of the present invention, and the embodiments may be mutually incorporated and referred to without contradiction.
In a business process, information changes to resource objects may originate from multiple roles and are typically performed through a business workflow. The workflow involves a plurality of manual or automatic processing links, and the duration of the whole workflow process is often uncontrollable. During this period, a scenario may occur in which multiple roles change the same or different attributes of the same resource object, or a conflict in attribute change may occur due to the existence of an association relationship between resource objects in a change operation of different resource objects performed in parallel. If the resource object is not managed effectively, the problem of over-constraint or under-constraint can be caused, and the expected content of the change of each role to the resource object can be covered by the final result when the change conflicts, so that part of the information of the business process is lost. Against this background, the present application provides a resource object management method, which manages resource objects according to the granularity of the attributes of the resource objects, and records the change information of the resource objects in time when the attributes of the resource objects are changed, so as to facilitate the follow-up tracking and auditing. The following describes a method for managing resource objects.
The embodiment of the application provides a method for managing resource objects, which is applied to electronic equipment, wherein the electronic equipment can be a management center of a content distribution network and is used for managing each resource object in the content distribution network. The electronic device may also be a management center for resource objects in other fields, which is not enumerated here. As shown in fig. 1, the method comprises the following steps:
step 101: after the attribute of the resource object is changed, the change record rule of the attribute of the resource object is determined according to the field type of the attribute of the resource object and/or the field value type of the attribute of the resource object and the pre-stored change record rule. The change recording rules comprise change recording rules of different field types and/or change recording rules of different field value types.
Step 102: and recording the change information of the resource object according to the determined change recording rule.
In the embodiment of the application, the change record rule is predefined, so that when the attribute of the resource object is changed, the change information can be quickly confirmed. After the attribute of the resource object is changed, the change recording rule of the attribute is determined based on the predefined change recording rule, and the change information of the resource object is recorded. The audit content and scope is more accurate than recording the change information of the resource object for the change of the resource object. In addition, the information of the attribute of the resource object which is not changed can not be recorded in the change information, so that the content of the change information is reduced, and the occupied storage space is further reduced. Since the change information is generated based on the rule, the quick definition implementation without codes can be supported.
In one example, a record rule for describing a change audit of an attribute of a resource object is stored in an electronic device, and a field type definition and a field value type definition of the attribute of the resource object are recorded so as to quickly confirm the change content. In the embodiment of the application, a change record rule of the resource object attribute is defined and maintained. After the attribute of the resource object is changed, the change record rule corresponding to the field type and/or the field value type of the attribute of the resource object is obtained by matching in the defined change record rule. And converting the abstract data of the attribute of the resource object into identifiable data based on the matched change rule, and recording the change information of the resource object.
For example, in the predefined change record rule, the field type includes any combination of a basic field type, a value object type, and a multi-field combination merge type. The field types and change recording rules may be:
basic field types of entity resource objects; the basic field may be the name, number, etc. of the resource object, and the change recording rule of the basic field type may be the value of the record field, i.e. the basic data of the field;
② value object type; the change recording rule of the value object type may be to record the value object of the field as a character string;
combining and merging types of multiple fields; the change recording rule of the multi-field combination merge type may be to merge and format values of multiple fields and record the formatted data. For example, the resource object a has 2 attributes, a1 and a2, and when the record is changed, the two values are merged and formatted into a value of [ a1(a2) ] and a value of [ a1(a2) ] is recorded.
For another example, in the predefined change recording rule, the field value type and the recording rule may be:
the common value type can directly represent the value (such as name and quantity) of the service information; the change recording rule of the normal value type may be to directly record the value of the field;
boolean value type, i.e. the value of a field is used to indicate the meaning of yes or no; the change recording rule of the boolean value type may be to decode the value of the field according to a predefined interpretation rule to obtain the meaning of the value of the field and record the meaning of the value of the field;
dictionary value type, that is, the value of field is a code value, which is used for representing the corresponding actual service semantics in the data dictionary; the change recording rule of the dictionary value type may be to convert a value of a field, usually a code value, into an actual service semantic according to a predefined data dictionary, and record the actual service semantic;
fourthly, the value type of the metadata Identification (ID), namely the value of the field is the service description value; the change recording rule of the metadata identification value type may be to convert the value of the field into a front-end service description, and record the front-end service description.
In one example, the change record rule defines a change record rule of the field type and the field value type, the electronic device writes a listener for the resource object storage in the project engineering, and the listener captures change events such as addition, deletion, value modification and the like of the attribute of the resource object. After the change event is monitored, the attribute of the changed resource object is matched with the change record rule, and the change record rule hit by the attribute of the resource object is determined. And recording and storing the change information according to the hit change recording rule. For example, after monitoring that the attribute a1 of the resource object a is changed, the change record rule corresponding to the field type of the attribute a1 and the change record rule corresponding to the field value type of the attribute a1 are matched with each other in the change record rules. Based on the matched change recording rule, change information of the attribute a1 is generated.
It should be noted that, as can be understood by those skilled in the art, in practical application, the field type and the field value type may be divided according to the requirement of the field in which the resource object management method is used or other requirements, and the specific content of the change recording rule is not limited in this embodiment.
In one embodiment, after changing the attributes of the resource objects, the electronic device determines whether there are attributes of other resource objects associated with the attributes of the resource objects according to the pre-stored association relationship between the attributes of the resource objects; if the resource object exists, locking the attribute of the other associated resource object, and changing the attribute of the other associated resource object. Specifically, the electronic device stores therein an association relationship between attributes of the resource object. For example, the electronic device constructs a relational topology of resource objects so as to associate business constraint linkage relationships existing between the resource objects to be managed. The method for constructing the relational topology graph of the resource objects can be realized by maintaining directed relationships among attributes of different resource objects based on a graph database.
Taking the resource object management method applied to the content distribution network, and taking the content distribution network including the resource object a, the resource object B, the resource object C, and the resource object D as an example, a topological graph of the relationship among the attributes of the resource object a, the resource object B, the resource object C, and the resource object D is shown in fig. 2. When it is monitored that the attribute 1 of the resource object B is changed, the electronic device locks the attribute 1 of the resource object A and changes the attribute 1 of the resource object A because the attribute 1 of the resource object B affects the attribute 1 of the resource object A. In the process of the electronic device changing the property 1 of the resource object A, the property 1 of the resource object A is in a locked state. If it is monitored that the attribute 1 of the resource object C is changed, the attribute 1 of the resource object C affects the attribute 1 of the resource object A, but since the attribute 1 of the resource object A is in a locked state, the linked operation of the attribute 1 of the resource object A caused by the change of the attribute 1 of the resource object C is performed after the attribute 1 of the resource object A is unlocked. If it is monitored that the attribute 2 of the resource object C is changed, the attribute 2 of the resource object C affects the attribute 2 of the resource object A, and since the attribute 2 of the resource object A is not locked, the attribute 2 of the resource object A can be changed after the attribute 2 of the resource object C is changed. Compared with the technology that the attribute 2 of the resource object A is changed after the resource object A is unlocked when the resource object A is locked and the attribute 2 of the resource object C is monitored to be changed in the process of changing the attribute 1 of the resource object A, the resource object management method of the embodiment locks the attribute of the resource object instead of locking the resource object, so that different attributes of each resource object can be changed more independently, and the concurrent execution efficiency of the change service is improved.
According to the above content, the resource objects are managed according to the granularity of the attributes of the resource objects, and compared with the resource objects managed according to the granularity of the resource objects, the granularity is smaller, so that when multiple associated resource objects are concurrently changed, the change sequence of various resource objects does not need to be strictly arranged or isolated, the concurrent change of the attributes of multiple associated service resources can be more flexible, and the concurrent execution efficiency of the change service is improved. And the electronic equipment is combined with the relation topological graph and the change information, and is quickly propagated according to the change source and the influence path. Before changing the attributes of the other associated resource objects, the attributes of the other associated resource objects are locked, and dirty writing of the information of the attributes of the resource objects is avoided.
In one embodiment, the electronic device determines that the properties of the associated other resource object are in an unlocked state prior to making changes to the properties of the associated other resource object. Specifically, if the attribute of the associated other resource object is in the locked state, it indicates that the attribute of the associated other resource object is in the edited state. In order to avoid dirty writing of the attribute information of the resource object, the attributes of other associated resource objects are not changed currently. And if the attribute of the other associated resource object is in the unlocked state, indicating that the attribute of the other associated resource object is in an editable state. Even if the change operation is currently performed on other properties of other related resource objects, the properties of other related resource objects can be concurrently edited.
It should be noted that, in this embodiment, the resource object is locked from the granularity of the attribute, and dirty writing is prevented, and those skilled in the art can understand that, in practical application, locking may also be performed from the granularity of the resource object, and this embodiment does not play a limiting role.
In one embodiment, changing the attributes of the associated other resource objects includes: and searching the operation rule between the attribute of the resource object and the attribute of the other associated resource object, and calculating and updating the value of the attribute of the other associated resource object. For example, the operation rules are defined using Lambda expressions to facilitate use in cross-language platforms. For example, the operation rule has a subject resource object attribute a, and associated dependent resource objects b and c, defining an expression: (b, c) - > b.m1+ c.n1, which represents the result of adding the attribute field m1 of dependent resource object b and the attribute field n1 of dependent resource object c as the subject resource object attribute a. The operation rules are defined uniformly, repeated definition in a plurality of associated resource objects is not needed, constraint judgment can be completed by following the uniform operation rules, and workload and maintenance cost are reduced.
It should be noted that, as can be understood by those skilled in the art, in practical application, the operation rule may be defined in other ways, and this embodiment is merely an example.
In one embodiment, altering the properties of the resource object includes: determining the value of the attribute of the resource object according to the change source of the attribute of the resource object and the operation rule of the change source and the attribute of the resource object; judging whether the value of the attribute of the resource object meets the preset requirement or not; if yes, changing the value of the attribute of the resource object; and if not, performing exception processing on the attribute of the resource object. For example, there are two sources of change for property 1 of resource object A, change source 1 and change source 2. When the change source 1 and/or the change source 2 is changed, the value of the attribute 1 of the resource object a is calculated according to the operation rule of the change source 1, the change source 2 and the attribute 1 of the resource object a. If the calculated value of the attribute 1 of the resource object A meets the preset requirement of the attribute 1 of the resource object A, if the value of the attribute 1 of the resource object A is more than 10 and less than 100, the calculation result is passed, and the value of the attribute 1 of the resource object A is changed. And if the calculated value of the attribute 1 of the resource object A does not meet the preset requirement of the attribute 1 of the resource object A, performing exception processing on the attribute of the resource object. The attribute of the resource object can be monitored by configuring the preset requirement of the attribute of the resource object, and the abnormal processing link is entered even when the attribute of the resource object is abnormal, so that the influence of error change on service operation is avoided.
In one example, the operation rules and the preset requirements may be expressed by Lambda expressions.
In one embodiment, exception handling of attributes of a resource object includes: acquiring an exception handling strategy corresponding to the attribute of the resource object; and performing exception processing on the attribute of the resource object according to the corresponding exception processing strategy. Specifically, the electronic device stores therein a plurality of exception handling policies. The electronic device may set different exception handling policies for different attributes of different resource objects, so that the exception handling policies are more in line with the business logic of the attribute of the resource object.
In one embodiment, the corresponding exception handling policy includes: and performing any one of rollback according to the change information, determining the attribute of the resource object based on the value of the specified change source, setting the attribute of the resource object to a preset value, and performing content formatting on the attribute of the resource object according to a preset rule.
It should be noted that, as can be understood by those skilled in the art, in practical application, an exception handling policy may also be set as needed, which is not listed in this embodiment.
The above embodiments can be mutually combined and cited, for example, the following embodiments are examples after being combined, but not limited thereto; the embodiments can be arbitrarily combined into a new embodiment without contradiction.
In one embodiment, a method for managing resource objects is shown in FIG. 3, and includes the following steps.
Step 101: after the attribute of the resource object is changed, the change record rule of the attribute of the resource object is determined according to the field type of the attribute of the resource object and/or the field value type of the attribute of the resource object and the pre-stored change record rule. The change recording rules comprise change recording rules of different field types and/or change recording rules of different field value types.
Step 102: and recording the change information of the resource object according to the determined change recording rule.
Step 103: and judging whether the attributes of other resource objects related to the attributes of the resource objects exist or not according to the pre-stored association relationship among the attributes of the resource objects. If yes, go to step 104, and if no, end the process.
Step 104: and locking the attributes of the other related resource objects and changing the attributes of the other related resource objects.
Those skilled in the art can understand that, in practical applications, step 103 may also be used as a previous step of step 102, and this embodiment does not limit the order of step 102 and step 103.
Optionally, before locking the attributes of the associated other resource objects, the method for managing resource objects further includes: it is determined that the attributes of the associated other resource objects are in an unlocked state.
Optionally, changing the attribute of the associated other resource object includes: searching the operation rule between the attribute of the resource object and the attribute of the other associated resource object, and calculating and updating the value of the attribute of the other associated resource object; wherein, the operation rule is expressed by Lambda expression.
Optionally, the field type includes any combination of a basic field type, a value object type and a multi-field combination merge type; the change record rule of the basic field type is the value of the record field, the change record rule of the value object type is the value object of the field is recorded as a character string, and the change record rule of the multi-field combination and combination type is the change record rule of the values of the fields which are combined and formatted and the record data after the change record rule is formatted; the field value type comprises any combination of a common value type, a Boolean value type, a dictionary value type and a metadata identification value type; the change recording rule of the common value type is the value of the record field, and the change recording rule of the Boolean value type is the meaning of the field value obtained by decoding the field value according to the predefined decoding rule; recording the meaning of the value of the field, and converting the value of the field into actual service semantics according to a predefined data dictionary and recording the actual service semantics according to a change recording rule of the dictionary value type; the change recording rule of the metadata identification value type is to convert the value of the field into a front-end service description and record the front-end service description.
In one embodiment, as shown in fig. 4, a method for managing resource objects includes the following steps:
step 1011: and determining the value of the attribute of the resource object according to the change source of the attribute of the resource object and the operation rule of the change source and the attribute of the resource object.
Step 1012: and judging whether the value of the attribute of the resource object meets the preset requirement or not. If yes, go to step 1013, and if not, go to step 105.
Step 1013: the value of the property of the resource object is changed.
Step 1014: and determining the change record rule of the attribute of the resource object according to the field type of the attribute of the resource object and/or the field value type of the attribute of the resource object and the pre-stored change record rule.
Step 102: and recording the change information of the resource object according to the determined change recording rule. The flow is then ended.
Step 105: and performing exception handling on the attribute of the resource object.
Optionally, the exception handling of the attribute of the resource object includes: acquiring an exception handling strategy corresponding to the attribute of the resource object; and performing exception processing on the attribute of the resource object according to the corresponding exception processing strategy.
Optionally, the corresponding exception handling policy includes: and performing any one of rollback according to the change information, determining the attribute of the resource object based on the value of the specified change source, setting the attribute of the resource object to a preset value, and performing content formatting on the attribute of the resource object according to a preset rule.
Optionally, the field type includes any combination of a basic field type, a value object type and a multi-field combination merge type; the change record rule of the basic field type is the value of the record field, the change record rule of the value object type is the value object of the field is recorded as a character string, and the change record rule of the multi-field combination and combination type is the change record rule of the values of the fields which are combined and formatted and the record data after the change record rule is formatted; the field value type comprises any combination of a common value type, a Boolean value type, a dictionary value type and a metadata identification value type; the change recording rule of the common value type is the value of the record field, and the change recording rule of the Boolean value type is the meaning of the field value obtained by decoding the field value according to the predefined decoding rule; recording the meaning of the value of the field, and converting the value of the field into actual service semantics according to a predefined data dictionary and recording the actual service semantics according to a change recording rule of the dictionary value type; the change recording rule of the metadata identification value type is to convert the value of the field into a front-end service description and record the front-end service description.
In one example, as shown in fig. 5, a method for managing resource objects includes the following steps:
step 1011: and determining the value of the attribute of the resource object according to the change source of the attribute of the resource object and the operation rule of the change source and the attribute of the resource object.
Step 1012: and judging whether the value of the attribute of the resource object meets the preset requirement or not. If yes, go to step 1013, and if not, go to step 105.
Step 1013: the value of the property of the resource object is changed.
Step 1014: and determining the change record rule of the attribute of the resource object according to the field type of the attribute of the resource object and/or the field value type of the attribute of the resource object and the pre-stored change record rule.
Step 102: and recording the change information of the resource object according to the determined change recording rule. The flow is then ended.
Step 103: and judging whether the attributes of other resource objects related to the attributes of the resource objects exist or not according to the pre-stored association relationship among the attributes of the resource objects. If yes, go to step 104, and if no, end the process.
Step 104: and locking the attributes of the other related resource objects and changing the attributes of the other related resource objects. After all the linkage operations are completed, the flow is ended.
Step 105: and performing exception handling on the attribute of the resource object.
Optionally, the field type includes any combination of a basic field type, a value object type and a multi-field combination merge type; the change record rule of the basic field type is the value of the record field, the change record rule of the value object type is the value object of the field is recorded as a character string, and the change record rule of the multi-field combination and combination type is the change record rule of the values of the fields which are combined and formatted and the record data after the change record rule is formatted; the field value type comprises any combination of a common value type, a Boolean value type, a dictionary value type and a metadata identification value type; the change recording rule of the common value type is the value of the record field, and the change recording rule of the Boolean value type is the meaning of the field value obtained by decoding the field value according to the predefined decoding rule; recording the meaning of the value of the field, and converting the value of the field into actual service semantics according to a predefined data dictionary and recording the actual service semantics according to a change recording rule of the dictionary value type; the change recording rule of the metadata identification value type is to convert the value of the field into a front-end service description and record the front-end service description.
In one embodiment, as shown in fig. 6, a method for managing resource objects includes the following steps:
step 201: and constructing a relation topological graph of the resource object. Specifically, a relational topological graph is constructed based on the relation of the resource objects input by the operation and maintenance personnel.
Step 202: a change recording rule is defined. Specifically, the change recording rule may refer to the description related to the foregoing embodiment, and is not described herein again.
Step 203: an operation rule defining an attribute of the resource object. Specifically, the operation rule may refer to the description related to the above embodiments, and is not described herein again.
Step 204: and monitoring the change event of the attribute of the resource object.
Step 205: change information of the attribute of the resource object is analyzed. Specifically, reference may be made to the related description of step 101 and step 102, which is not described herein again.
Step 206: the operation of the attributes of the resource object is performed.
Step 207: and judging whether the operation result is abnormal or not. Specifically, reference may be made to the description related to step 1012, which is not described herein again. If yes, go to step 208, otherwise go to step 209.
Step 208: the result was confirmed to pass. The flow is then ended.
Step 209: and executing an exception handling strategy. Specifically, the exception handling policy may refer to the description related to the foregoing embodiment, and is not described herein again.
For example, a schematic diagram of the relationship between the property and the change source of resource object A and resource object B is shown in FIG. 7. When the source of change 1 or the source of change 2 of the property 1 of the resource object B is changed, the following steps are included.
Step 301: an operation is performed on attribute 1 of resource object B. Specifically, the value of attribute 1 of resource object B is calculated based on the calculation rule between change source 1 or change source 2 and attribute 1 of resource object B.
Step 302: the result of the operation of the attribute 1 of the resource object B is checked or subjected to an exception. Specifically, whether the value of the attribute 1 of the resource object B meets a preset requirement is checked, if so, the calculation result is determined to be correct, and the calculation result is used as the value of the attribute 1 of the resource object B, otherwise, the value of the attribute 1 of the resource object B is determined through exception handling.
Step 303: the linkage operation is triggered for attribute 1 of the resource object B. Specifically, the values of the attributes of other resource objects associated with attribute 1 of resource object B, e.g., attribute X of resource object A, are determined and changed. Step 303 comprises the following sub-steps:
step 3031: an operation is performed on the attribute X of the resource object a. Specifically, for the resource object a, the attribute 1 of the resource object B is a source of change of the attribute X of the resource object a, and when the attribute 1 of the resource object B is changed, that is, the source of change 1 of the attribute X of the resource object a is changed. The value of the change source X of the resource object A is calculated according to the operation rule between the change source 1 of the attribute X of the resource object A and the attribute X of the resource object A.
Step 3032: and confirming or performing exception processing on the attribute X operation result of the resource object A. Specifically, whether the value of the attribute X of the resource object A meets a preset requirement is checked, if so, the calculation result is confirmed to be correct, the calculation result is used as the value of the attribute X of the resource object A, and otherwise, the value of the attribute X of the resource object A is determined through exception handling. If the attribute X of the resource object A does not have the attribute of other associated resource objects. If so, the values of the attributes of the other resource objects associated with attribute X of resource object A are determined and changed.
An embodiment of the present application further provides a device for managing resource objects, as shown in fig. 8, including: a resource object management maintenance module 401 and an operation module 402. The resource object management maintenance module 401 defines a change log rule, and the calculation module 402 generates change information based on the change log rule.
In one embodiment, fig. 9 shows a device for managing resource objects, which includes: a resource object management maintenance module 401, an operation module 402 and a resource object relationship maintenance module 403. The resource object relationship maintenance module 403 is configured to construct a relationship between resource objects, and generate a resource object relationship diagram. The operation and maintenance personnel can define the change record rule in the resource object management maintenance module 401, so that the resource object management maintenance module 401 generates the change record rule. The operation and maintenance personnel can define the operation rule of the attribute of the resource object in the resource object management and maintenance module 401, so that the resource object management and maintenance module 401 generates the operation rule of the attribute of the resource object. The operation rule of the attribute of the resource object includes an operation rule between the attributes of the resource objects and an operation rule between the attribute of the resource object and a change source of the attribute. The calculation module 402 obtains a calculation method of the resource object attribute based on the resource object relationship diagram of the resource object relationship maintenance module 403, the change record rule of the resource object management maintenance module 401, and the calculation rule of the resource object attribute of the resource object management maintenance module 401, and generates information of the resource object attribute based on the calculation method. Based on the operation method, generating the information of the attribute of the resource object includes: and generating and recording the change information of the resource object, and calculating the value of the attribute corresponding to the change source and the values of the attributes of other resource objects related to the attribute corresponding to the change source, namely performing linkage calculation.
It should be understood that the present embodiment is an apparatus embodiment corresponding to the above method embodiment, and the present embodiment can be implemented in cooperation with the method embodiment. The related technical details mentioned in the method embodiment are still valid in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related art details mentioned in the present embodiment can also be applied in the method embodiment.
It should be noted that, all the modules involved in this embodiment are logic modules, and in practical application, one logic unit may be one physical unit, may also be a part of one physical unit, and may also be implemented by a combination of multiple physical units. In addition, in order to highlight the innovative part of the present invention, a unit which is not so closely related to solve the technical problem proposed by the present invention is not introduced in the present embodiment, but this does not indicate that there is no other unit in the present embodiment.
An embodiment of the present application further provides an electronic device, as shown in fig. 10, including: at least one processor 501; and a memory 502 communicatively coupled to the at least one processor 501; wherein the memory 502 stores instructions executable by the at least one processor 501, the instructions being executable by the at least one processor 501 to enable the at least one processor 501 to perform the method for managing resource objects as mentioned in the above embodiments.
The electronic device includes: one or more processors 501 and a memory 502, with one processor 501 being an example in fig. 10. The processor 501 and the memory 502 may be connected by a bus or other means, and fig. 10 illustrates the connection by the bus as an example. Memory 502, which is a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The processor 501 executes various functional applications and data processing of the device, that is, implements the above-described resource object management method, by executing nonvolatile software programs, instructions, and modules stored in the memory 502.
The memory 502 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store a list of options, etc. Further, the memory 502 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, memory 502 may optionally include memory located remotely from processor 501, which may be connected to an external device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
One or more modules are stored in the memory 502, and when executed by the one or more processors 501, perform the method of managing resource objects in any of the method embodiments described above.
The product can execute the method provided by the embodiment of the application, has corresponding functional modules and beneficial effects of the execution method, and can refer to the method provided by the embodiment of the application without detailed technical details in the embodiment.
Embodiments of the present application also provide a computer-readable storage medium storing a computer program. The computer program realizes the above-described method embodiments when executed by a processor.
That is, as can be understood by those skilled in the art, all or part of the steps in the method according to the above embodiments may be implemented by a program instructing related hardware, where the program is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps in the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific embodiments for practicing the invention, and that various changes in form and details may be made therein without departing from the spirit and scope of the invention in practice.
Claims (10)
1. A method for managing resource objects, comprising:
after the attribute of the resource object is changed, determining a change record rule of the attribute of the resource object according to the field type of the attribute of the resource object and/or the field value type of the attribute of the resource object and a pre-stored change record rule; wherein, the change record rules comprise change record rules of different field types and/or change record rules of different field value types;
and recording the change information of the resource object according to the determined change recording rule.
2. The method for managing resource objects according to claim 1, wherein after the property of the resource object is changed, the method for managing resource objects further comprises:
judging whether the attributes of other resource objects associated with the attributes of the resource objects exist or not according to the pre-stored association relationship among the attributes of the resource objects;
if the resource object exists, locking the attributes of the other associated resource objects, and changing the attributes of the other associated resource objects.
3. The method of claim 2, wherein prior to said locking the attributes of said associated other resource objects, said method further comprises:
determining that the attributes of the associated other resource objects are in an unlocked state.
4. The method according to claim 2, wherein the changing of the attribute of the associated other resource object includes:
and searching the operation rule between the attribute of the resource object and the attribute of the other associated resource object, and calculating and updating the value of the attribute of the other associated resource object.
5. The method for managing resource objects according to any one of claims 1 to 4, wherein changing the attribute of the resource object includes:
determining the value of the attribute of the resource object according to the change source of the attribute of the resource object and the operation rule of the change source and the attribute of the resource object;
judging whether the value of the attribute of the resource object meets the preset requirement or not;
if yes, changing the value of the attribute of the resource object;
and if not, performing exception processing on the attribute of the resource object.
6. The method for managing resource objects according to claim 5, wherein said exception handling of the attribute of the resource object comprises:
acquiring an exception handling strategy corresponding to the attribute of the resource object;
and performing exception processing on the attribute of the resource object according to the corresponding exception processing strategy.
7. The method of claim 6, wherein the corresponding exception handling policy comprises: and performing any one of rollback according to the change information, determining the attribute of the resource object based on the value of the specified change source, setting the attribute of the resource object to be a preset value, and performing content formatting on the attribute of the resource object according to a preset rule.
8. The method according to any one of claims 1 to 4, wherein the field type includes any combination of a basic field type, a value object type, and a multi-field combination merge type; the change recording rule of the basic field type is a value of a recording field, the change recording rule of the value object type is to record a value object of a field as a character string, and the change recording rule of the multi-field combination merging type is to merge and format values of a plurality of fields and record formatted data;
the field value type comprises any combination of a common value type, a Boolean value type, a dictionary value type and a metadata identification value type; the change recording rule of the common value type is a value of a record field, and the change recording rule of the Boolean value type is to decode the value of the field according to a predefined interpretation rule to obtain the meaning of the value of the field; recording the meaning of the value of the field, wherein the change recording rule of the dictionary value type is that the value of the field is converted into actual service semantics according to a predefined data dictionary, and the actual service semantics are recorded; the change recording rule of the metadata identification value type is to convert the value of the field into a front-end service description and record the front-end service description.
9. An electronic device, comprising: at least one processor; and the number of the first and second groups,
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 a method of managing resource objects as claimed in any one of claims 1 to 8.
10. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the method for managing resource objects of any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110524385.1A CN113220528A (en) | 2021-05-13 | 2021-05-13 | Resource object management method, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110524385.1A CN113220528A (en) | 2021-05-13 | 2021-05-13 | Resource object management method, electronic device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113220528A true CN113220528A (en) | 2021-08-06 |
Family
ID=77095684
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110524385.1A Pending CN113220528A (en) | 2021-05-13 | 2021-05-13 | Resource object management method, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113220528A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10489388B1 (en) * | 2018-05-24 | 2019-11-26 | People. ai, Inc. | Systems and methods for updating record objects of tenant systems of record based on a change to a corresponding record object of a master system of record |
| CN112084199A (en) * | 2020-09-27 | 2020-12-15 | 中国建设银行股份有限公司 | Scene-based general parameter maintenance method and device |
| CN112115153A (en) * | 2020-09-21 | 2020-12-22 | 北京字跳网络技术有限公司 | Data processing method, device, equipment and storage medium |
| CN112540995A (en) * | 2020-11-11 | 2021-03-23 | 特劢丝软件科技(上海)有限公司 | Data updating method, electronic device and storage medium |
| CN112749173A (en) * | 2019-10-29 | 2021-05-04 | 北京国双科技有限公司 | Method and device for updating object |
-
2021
- 2021-05-13 CN CN202110524385.1A patent/CN113220528A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10489388B1 (en) * | 2018-05-24 | 2019-11-26 | People. ai, Inc. | Systems and methods for updating record objects of tenant systems of record based on a change to a corresponding record object of a master system of record |
| CN112749173A (en) * | 2019-10-29 | 2021-05-04 | 北京国双科技有限公司 | Method and device for updating object |
| CN112115153A (en) * | 2020-09-21 | 2020-12-22 | 北京字跳网络技术有限公司 | Data processing method, device, equipment and storage medium |
| CN112084199A (en) * | 2020-09-27 | 2020-12-15 | 中国建设银行股份有限公司 | Scene-based general parameter maintenance method and device |
| CN112540995A (en) * | 2020-11-11 | 2021-03-23 | 特劢丝软件科技(上海)有限公司 | Data updating method, electronic device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2648210C (en) | System and method for automating etl applications | |
| US20150293964A1 (en) | Applications of automated discovery of template patterns based on received requests | |
| CN111324577B (en) | Yml file reading and writing method and device | |
| Klinger et al. | Blockchain-based Cross-Organizational Execution Framework for Dynamic Integration of Process Collaborations. | |
| CN102142014A (en) | System and method for export and import of metadata located in metadata registries | |
| CN107463596B (en) | Block chain parallel query method and system for setting out-of-chain fault table | |
| US8332335B2 (en) | Systems and methods for decision pattern identification and application | |
| Jiang et al. | Assuring the model evolution of protocol software specifications by regression testing process improvement | |
| US8631389B2 (en) | Methods and apparatus for authentication of configuration items via configuration item change analysis | |
| CN117376092A (en) | Fault root cause positioning method, device, equipment and storage medium | |
| Kim et al. | Experimental verification and validation of the SICN-oriented process mining algorithm and system | |
| CN115329011A (en) | Data model construction method, data query method, data model construction device and data query device, and storage medium | |
| CN116821098A (en) | Data warehouse management method, service system and storage medium | |
| CN113220528A (en) | Resource object management method, electronic device and storage medium | |
| CN114756224A (en) | Activity execution method and device | |
| US20100191710A1 (en) | Network Meta-Data Libraries And Related Methods | |
| US20210200758A1 (en) | Edge table representation of processes | |
| CN113568892A (en) | Method and equipment for carrying out data query on data source based on memory calculation | |
| Jing | Set-Based differential evolution algorithm based on guided local exploration for automated process discovery | |
| CN112051987B (en) | Service data processing method, device and equipment, program generating method and device | |
| CN112905153B (en) | Software parallel construction method and device for software defined satellite | |
| CN116860871B (en) | Metadata standardization method, device and storage medium for unified processing source data | |
| Silva et al. | Lm2f: a life-cycle model maintenance framework for co-evolving enterprise architecture meta-models and models | |
| KR101395737B1 (en) | Conforming method of integrity constraint of express in relational database | |
| AU2021287457B2 (en) | "Log Data Compliance" |
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 |