Common Metadata Instance for Data Store Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data synchronization techniques, such as state-based and event-based methods, face inefficiencies in metadata management, leading to increased storage space usage and resource consumption, particularly due to the need for multiple metadata instances and time-consuming metadata fixup processes.
Innovation Solution
The implementation of a system that uses a common instance of metadata to indicate the provisioning time of a data store, generating a tracking table with no initial records and dynamically adding records only for changes post-provisioning, thereby reducing storage space and processing time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If state based techniques are used to maintain one-to-one mapping between items and metadata instances, then item tracking is reliable, but storage space increases and metadata fixup time increases
Solution Approach 1:
The patent merges multiple individual metadata instances into a single shared metadata instance that is common to multiple items. Instead of maintaining separate metadata for each item, the system creates one metadata instance that tracks changes for all items, eliminating redundancy and reducing storage space while maintaining reliable change tracking through the shared instance.
Solution Approach 2:
The shared metadata instance serves multiple functions simultaneously - it tracks changes for multiple items, provides synchronization information for all associated items, and eliminates the need for separate metadata instances. This multi-functional approach reduces the overall quantity of metadata while maintaining comprehensive item tracking capability.
2Reliability
If state based techniques are used to maintain one-to-one mapping between items and metadata instances, then item tracking is reliable, but metadata fixup time and processing resources increase
Solution Approach 1:
By merging multiple metadata instances into a single shared instance, the patent eliminates the need for serial metadata fixup operations on each individual instance. The shared metadata instance can be updated once to reflect changes for multiple items, dramatically reducing metadata fixup time and processing resource consumption while maintaining reliable change tracking.
3Reliability
If event based techniques are used to track events and create metadata for each event, then change tracking is comprehensive, but metadata amount becomes proportional to number of events
Solution Approach 1:
The patent combines multiple event-generated metadata instances into a single shared metadata instance that consolidates change tracking information. Instead of creating separate metadata for each event, the shared instance aggregates changes from multiple events, maintaining comprehensive change tracking while reducing the total amount of metadata stored.
4Measurement precision
If multiple instances of metadata are created for respective items, then individual item tracking is precise, but storage space and processing resources increase
Solution Approach 1:
The patent merges individual item-specific metadata instances into a single shared metadata instance that maintains the ability to track changes for each item precisely. The shared instance contains consolidated change information that can be queried and processed with the same precision as individual instances would provide, but with significantly reduced storage requirements.
Data Source
AI summary
Techniques are described herein that are capable of provisioning and/or synchronizing a data store using common metadata. For instance, a common instance of metadata may be used in lieu of multiple instances of the metadata that correspond to respective items in the data store for indicating a time at which the data store was provisioned. Each time a change occurs with respect to an item in a data table of the data store after provisioning of the data store, a record may be added or updated in a corresponding tracking table. When a request is made for changes that have occurred with respect to the items in a data table, the common instance of the metadata may be used to generate a record in the corresponding tracking table for each item in the data table that did not change since the data store was provisioned.