Database Metadata Graph Node Migration for Version Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
During database version changes, obsolete objects must be modified to ensure compatibility, but existing methods lack an efficient mechanism for migrating and updating these objects to new versions.
Innovation Solution
The solution involves storing metadata within a database for objects in frames with version identifiers, identifying objects requiring migration based on version differences, and migrating them to new frames with updated headers and sizes, allowing for efficient compatibility with new build identifiers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If objects are migrated to new frames with updated headers during database version changes, then compatibility with new build identifiers is improved, but the complexity of the migration process increases
Solution Approach 1:
The system performs preliminary identification of objects requiring migration by comparing version identifiers before the actual migration process. This preliminary action allows the system to prepare and plan the migration, reducing the complexity of the execution phase by having already determined which objects need to be moved to new frames.
Solution Approach 2:
The migration process is segmented into distinct phases: identification of objects needing migration based on version comparison, creation of new frames with updated headers, population of migrated objects, and deactivation of old frames. This segmentation reduces overall complexity by breaking down the complex migration task into manageable, independent steps.
2Adaptability or versatility
If objects are migrated from old frames to new frames, then database upgrade compatibility is improved, but storage overhead during migration increases
Solution Approach 1:
The system creates new frames with updated headers for migrated objects while retaining the original frames until the migration is complete. Once verification confirms successful migration, the old frames are deactivated and their storage space becomes available for recovery. This approach ensures compatibility during transition while temporarily increasing storage overhead, which is then reduced after migration completion.
3Adaptability or versatility
If version identifiers are updated in object headers, then object compatibility with new builds is improved, but the risk of data corruption during migration increases
Solution Approach 1:
The system creates a copy of each object in the new frame with the updated version identifier in its header, while the original object remains intact in the old frame during the migration process. This copying approach allows verification of the copied data before deactivating the original, thereby maintaining data integrity and reducing the risk of corruption while achieving version compatibility.
Data Source
AI summary
Metadata is stored within a database for each of a plurality of objects in different frames associated with a structure descriptor (e.g., a container directory entry, etc.). The frames are part of a metadata page and each comprising an object and a header specifying a version identifier for the object and a size of the object. The structure descriptor initially is built for a first build identifier. Thereafter, upon the structure descriptor changing from the first build identifier to a second build identifier, at least one of the objects that require migration is identified. The identification is based on the version identifier for the object being different from the second build identifier. In response, the identified objects are migrated from their corresponding frame to a new frame. The new frame includes the objects and new headers that include a version identifier equal to the second build identifier.