Mechanism for deprecating object oriented data
Techniques are described to allow the deprecation of classes in an object-oriented data model, such as a CDM for a CMDB. When a class is deprecated and replaced by another existing or new class, data associated with instances of the deprecated class may be migrated to the replacement class. A mapping between the deprecated class and its replacement class may be provided to allow existing applications to continue to access data using the deprecated class without change until the deprecated class is finally deleted or the application is updated to use the replacement class. New applications written to use the object-oriented data model after the deprecation may use the replacement class to access data instances created using the original data model.
1. A computer system comprising:
at least one processor; and
a memory storing a data model of a database, the data model including at least a first class and a second class, the memory also storing instructions that, when executed by the at least one processor, cause the system to perform operations comprising:
selecting the second class of the data model as a replacement for the first class,
moving data associated with the first class from data structures associated with the first class in the database to data structures associated with the second class in the database, and
marking the first class as deprecated,
wherein the moving enables operations that access the data structures associated with the second class to access the data associated with the first class.
2. The computer system of claim 1 , wherein the operations further comprise:
marking a plurality of subclasses of the first class as deprecated; and
triggering replacement of each respective subclass with a sibling of a superclass of the first class as a replacement for the respective subclass.
3. The computer system of claim 1 , wherein the operations further comprise:
mapping an API call made via a vendor form to a database API; and
mapping data obtained in a format for the second class to a format for the first class.
4. The computer system of claim 1 , wherein the operations further comprise:
in response to an operation accessing the first class, generating a message indicating a suggested application modification to eliminate use of the first class.
5. The computer system of claim 1 , wherein the operations further comprise:
deprecating at least one attribute of the first class and replacing the at least one attribute with a new attribute in the second class that is of the same data type as the at least one attribute being deprecated.
6. The computer system of claim 1 , wherein the operations further comprise:
generating at least one configuration class for mapping the first class to the second class; and
accessing the at least one configuration class to access the data structures associated with the second class.
7. The computer system of claim 6 , wherein mapping the first class to the second class is performed as part of an update to the database.
8. A method comprising:
obtaining access to a database storing a data model including at least a first class and a second class;
marking the first class of the data model as deprecated;
selecting the second class of the data model as a replacement for the first class;
moving data associated with the first class from data structures associated with the first class in the database to data structures associated with the second class in the database;
marking the first class as deprecated; and
redirecting operations that access the data structures associated with the first class to access the data structures associated with the second class,
wherein the moving enables operations that access the data structures associated with the second class to access the data associated with the first class.
9. The method of claim 8 , further comprising:
marking a plurality of subclasses of the first class as deprecated; and
triggering replacement of each respective subclass with a sibling of a superclass of the first class as a replacement for the respective subclass.
10. The method of claim 8 , wherein the redirecting includes:
mapping an API call made via a vendor form to a database API; and
mapping data obtained in a format for the second class to a format for the first class.
11. The method of claim 8 , further comprising:
in response to an operation accessing the first class, generating a message indicating a suggested application modification to eliminate use of the first class.
12. The method of claim 8 , further comprising:
deprecating at least one attribute of the first class and replacing the at least one attribute with a new attribute in the second class that is of the same data type as the at least one attribute being deprecated.
13. The method of claim 8 , further comprising:
generating at least one configuration class for mapping the first class to the second class,
wherein the redirecting includes accessing the at least one configuration class to access the data structures associated with the second class.
14. The method of claim 13 , wherein mapping the first class to the second class is performed as part of an update to the database.
15. A computer-readable medium comprising:
at least one processor; and
a memory storing a data model for a computer-implemented database, the data model including a plurality of classes, the memory also storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
receiving a request to deprecate a portion of classes of the plurality of classes,
selecting, for each class in the portion, a respective replacement class for the class in the portion of classes, and
migrating data associated with each instance of each class in the portion of classes to an instance of each respective replacement class by:
marking each class in the portion of classes as deprecated,
configuring, for each class in the portion of classes, a mapping of each element in the class to an existing or new element in the respective replacement class, and
moving data associated with the instances of each class in the portion of classes to at least one instance of the respective replacement class in the database.
16. The computer-readable medium of claim 15 , wherein deprecating the portion of classes is performed in a multithreaded process.
17. The computer-readable medium of claim 15 , wherein the migration is configured to be performed unless a predefined deprecation period is expired.
18. The computer-readable medium of claim 15 , wherein the operations further comprise:
marking a plurality of subclasses of at least one of the plurality of classes as deprecated; and
triggering replacement of each respective subclass with a sibling of a superclass of at least one of the plurality of classes as a replacement for the respective subclass.
19. The computer-readable medium of claim 15 , wherein the operations further comprise:
redirecting operations that access the instances of each class in the portion of classes to access the instances of the respective replacement classes,
wherein the moving enables operations that access the instances of the respective replacement classes to access the data associated with the instances of classes in the portion of classes.
20. The computer-readable medium of claim 19 , wherein the operations further comprise:
deprecating at least one attribute of the classes in the portion of classes and replacing the at least one attribute with a new attribute that is of the same data type as the at least one attribute being deprecated.