Nested Error Tables for Cloud Database Recovery Actions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data systems, such as database systems, face challenges in tracking and managing errors during data operations, particularly when input rows fail to load due to parsing or transform errors, making it difficult for users to identify and address these issues efficiently.
Innovation Solution
The implementation of error tables that are nested objects of base tables, populated with error records and contextual information, providing a centralized location for error tracking and facilitating efficient recovery actions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Area of stationary object
If data is stored and managed in a cloud database system, then data accessibility and storage capacity are improved, but error tracking and management become more difficult
Solution Approach 1:
The patent segments error tracking by creating separate error tables for different base tables. Each error table stores only the errors related to its corresponding base table, dividing the complex error tracking problem into manageable, organized segments that are easier to detect and manage in cloud database systems.
Solution Approach 2:
The patent introduces error tables as intermediary structures between base tables and users. These error tables act as mediators that capture, store, and present error information in a centralized and accessible manner, making error tracking easier without affecting the core data storage and management functions of the cloud database system.
2Ease of operation
If error records are tracked separately from base tables, then error information is easier to manage, but contextual information about errors is lost
Solution Approach 1:
The patent implements error tables as nested objects of base tables. Each error table is logically nested within its corresponding base table structure, allowing error records to be managed separately while maintaining their contextual relationship to the base table data. This nesting preserves contextual information while enabling easier error management operations.
Solution Approach 2:
The error table structure is designed to be universal and multi-functional. It can store various types of error records (parsing errors, transform errors, load errors) while maintaining a consistent structure that preserves contextual information. The same error table mechanism works across different base tables and error types, providing both ease of management and information preservation.
3Reliability
If multiple error tracking locations are provided, then comprehensive error coverage is achieved, but user effort to resolve errors increases
Solution Approach 1:
The patent merges multiple error tracking locations into a single centralized error table per base table. Instead of scattering error information across multiple locations, all errors related to a base table are combined and stored in one accessible error table, maintaining comprehensive error coverage while reducing user effort to locate and resolve errors.
Data Source
AI summary
Techniques for creating and using error tables to track errors associated with a base table are described. A command to perform an operation on a base table stored in a network-based data system can be received and executed, causing at least one error. At least one error record corresponding to the at least one error can be inputted into an error table, which is nested with the base table. Contextual information can be added to the at least one error record.