Hypercube Version Overrides for Scalable Scenario Planning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing query evaluation systems face challenges in efficiently managing large and complex hypercube models, particularly in ensuring data consistency and scalability when dealing with increasing data volumes, leading to resource-intensive cloning operations and scalability bottlenecks.
Innovation Solution
Implementing a multiversion concurrency control system that uses anchor objects and snapshot chains to efficiently store and manage hypercube versions, allowing for localized storage and reduced memory overhead by referencing base and scenario versions without full copies, and propagating updates efficiently across dependent locations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full copies of the version cache are made to maintain data consistency, then data consistency is improved, but memory usage increases substantially
Solution Approach 1:
The patent segments the version cache into a base version and multiple scenario versions. Each scenario version only stores differences or references to the base version rather than complete copies. This segmentation allows the system to maintain data consistency across versions while significantly reducing memory consumption by avoiding redundant storage of identical data.
Solution Approach 2:
The patent implements a nested structure where scenario versions are nested within the base version framework. Scenario versions contain references or pointers to the base version data, creating a hierarchical relationship. This nesting enables the system to maintain multiple versions with consistent data while using minimal additional memory, as scenario versions only store what differs from or references the parent base version.
2Adaptability or versatility
If the entire hypercube is copied to maintain version consistency, then version management capability is improved, but system scalability deteriorates
Solution Approach 1:
The patent segments version management into independent base version and scenario version components. This segmentation enables efficient version management by allowing scenario versions to be created, modified, and deleted without copying the entire hypercube. The segmented approach maintains version management capability while improving system scalability by reducing the computational overhead of version operations.
Solution Approach 2:
The patent establishes a base version that serves as a preliminary framework before creating scenario versions. This preliminary action allows subsequent scenario versions to be built upon the existing base structure, eliminating the need to copy the entire hypercube for each new version. This approach enhances version management capability while maintaining system scalability through efficient resource utilization.
3Measurement precision
If complete hypercube copies are stored for each version, then version retrieval accuracy is improved, but memory resource consumption increases
Solution Approach 1:
The patent implements a nested version structure where scenario versions contain references to the base version. This nesting ensures that version retrieval maintains high accuracy because the hierarchical relationship preserves data integrity and consistency. At the same time, memory resource consumption is reduced because scenario versions only store references or differences rather than complete copies of the base version data.
Solution Approach 2:
The patent uses selective copying where only necessary version information is copied rather than complete hypercube copies. Scenario versions copy or reference only the specific data elements that differ from or depend on the base version, maintaining version retrieval accuracy while significantly reducing memory resource consumption by avoiding redundant copying of identical data.
Data Source
AI summary
A system, method, and device for managing dependencies between a hypercube base version and a set of scenario versions for the hypercube are provided. The method includes (i) obtaining a request for a version of a hypercube, and (ii) in response to obtaining the request: (a) obtaining a base version of the hypercube, (b) obtaining an override data structure that indicates a set of scenario values that override corresponding base version values, and (c) providing the version of the hypercube based at least in part on the base version and the override data structure.