Data Management Engine Query Primitive Calls
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database management systems face challenges in optimizing performance due to complex queries and high transaction volumes, leading to cumbersome access and processing requirements that can reduce response times and increase resource usage.
Innovation Solution
A data management engine is introduced that decouples the application layer from the database layer, using a query execution engine to optimize and compile query plans, and a data management engine that performs primitive calls to access data using value identifier sets in various representations such as vectors, ranges, and bit vectors, allowing efficient execution of queries across different database types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If database management systems handle complex multidimensional analysis queries, then analytical capability is improved, but processing time and resource usage increase
Solution Approach 1:
The patent segments the database system into distinct layers: a query execution engine that handles complex analytical queries and a data management engine that handles primitive data access operations. This segmentation allows each layer to be optimized independently, enabling complex queries to be broken down into efficient primitive operations that reduce processing time while maintaining analytical capability.
Solution Approach 2:
The patent introduces a data management engine as an intermediary between the query execution engine and the database storage layer. This intermediary translates high-level query operations into optimized primitive calls with value identifier sets, acting as a mediator that reduces the processing burden on the database layer while preserving the ability to handle complex analytical queries.
2Productivity
If database systems optimize for high transaction volumes, then throughput is improved, but query complexity handling deteriorates
Solution Approach 1:
The patent creates a universal data management engine that can handle both simple high-volume transactions and complex analytical queries through a unified architecture. The engine uses value identifier sets and primitive operations that are equally efficient for both transaction processing and complex query execution, providing multi-functionality without sacrificing performance in either domain.
3Ease of operation
If the database layer processes complex queries directly, then query execution is simplified, but the processing burden on the database layer increases
Solution Approach 1:
The patent extracts the burden of complex query processing from the database layer by separating query execution logic into a dedicated query execution engine. The database layer is left to handle only simple primitive data access operations, while the extracted query execution engine handles the complexity of translating and optimizing queries, reducing the processing burden on the database layer while maintaining ease of query execution.
4Speed
If value identifier sets are converted between multiple representations, then execution efficiency is improved, but processing overhead increases
Solution Approach 1:
The patent performs preliminary conversion of value identifier sets into optimal representations before execution. The data management engine determines the appropriate representation (vector, range, bit vector, or ranges vector) based on the specific operation requirements and converts the value identifier sets accordingly in advance, eliminating the need for conversions during actual query execution and reducing overall processing overhead.
Data Source
AI summary
In some example embodiments, a system is provided for executing a primitive call that implements a query operation. The system may include a data processor and a memory. The memory may store instructions that result in operations when executed by the data processor. The operations may include: executing, at an data management engine, the primitive call by at least performing a first operation with respect to a value identifier set, the value identifier set including one or more value identifiers, and the primitive call being configured to access a database storing a plurality of value identifiers; and generating, based at least on a result of the first operation, a result for the primitive call. Related methods and articles of manufacture, including computer program products, are also described.