Unified Expanded Network Definition for Distributed Database Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed databases, determining a consistent table definition for logical tables across multiple nodes is challenging due to differences in column types, which can lead to query response inconsistencies, ambiguities, and potential disruptions, especially when nodes have non-matching column types or incorrect definitions.
Innovation Solution
A method and system that independently establish a common table definition at each node by selecting between local and network definitions, propagating the selected definition with queries, and updating network definitions across nodes to ensure consistency, using an 'expanded network definition' that includes all distinct column names and types, and resolving type mismatches by promotion or removal.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If nodes independently define local table schemas, then adaptability to local data variations is improved, but query response consistency across the network deteriorates
Solution Approach 1:
The system segments table definitions into local node-specific schemas and network-wide common schemas. Each node maintains its own local definition for flexibility while participating in network-wide definition establishment for consistency. This segmentation allows nodes to adapt to local variations while ensuring query responses remain consistent across the distributed database network.
Solution Approach 2:
The system creates a universal common table definition that serves all nodes in the network. This common definition acts as a standardized interface that all nodes can use for queries, ensuring consistency. Meanwhile, nodes retain their local definitions for specialized local operations, achieving multi-functionality where a single system supports both universal query consistency and local adaptability.
2Loss of information
If nodes propagate their local definitions across the network, then completeness of table definition information is improved, but network communication overhead and complexity increase
Solution Approach 1:
The system extracts only the essential common elements from local table definitions to create a common network definition. Instead of propagating entire local definitions across the network, nodes extract and share only the necessary schema information that applies universally. This reduces communication overhead while maintaining completeness of essential definition information.
Solution Approach 2:
Nodes perform preliminary processing of their local definitions to identify and prepare common elements before network propagation. By pre-processing definitions to extract only the necessary common schema information, nodes reduce the amount of data that needs to be communicated across the network while ensuring all essential definition information is captured and propagated efficiently.
3Productivity
If nodes resolve definition conflicts automatically through type promotion, then query processing speed is improved, but risk of incorrect type conversions increases
Solution Approach 1:
The system implements beforehand validation and conflict detection mechanisms that cushion against incorrect type conversions. Before automatic type promotion is applied, the system validates whether the promotion is appropriate and safe. This preliminary validation layer protects against erroneous conversions while still enabling automatic resolution for valid cases, maintaining both speed and accuracy.
Data Source
AI summary
Determining common table definitions in distributed databases includes receiving a query at a node in a distributed database. The query targets a logical table. Upon determining the logical table is locally defined, one of the local definition and a network definition is selected to use. The network definition is independently established for shared logical table names. The selected definition is used and propagated with the query through the distributed database. Upon determining the logical table is not locally defined, an initial query is issued to other nodes in network to find the network definition for the logical table, the network definition is stored in memory, and the selected definition is propagated through the distributed database with the query.