Managed Object Store Reads and Writes With Delete-Filter Conflict Checks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managed object stores employing open table formats face challenges with write conflicts and high read costs due to concurrency control mechanisms, particularly in managing large-scale datasets.

Innovation Solution

Implementing bloom and cuckoo filters to manage write conflicts by using hash values and column-level bloom filters to optimize read operations, reducing unnecessary transaction aborts and read validation overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If concurrency control mechanisms are employed in managed object stores, then multiple writers can simultaneously modify table partitions, but write conflicts and read validation operations increase

Engineering Contradiction:
Improveconcurrent write capabilityVSAvoidconcurrency control overhead
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by creating delete files and metadata entries before actual write operations occur. This allows the system to pre-establish the state of deleted rows and files, enabling concurrent writers to check against this pre-established state rather than conflicting during the write operation itself.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces delete files and metadata as intermediary structures that mediate between concurrent writers and the actual data files. These intermediaries carry information about deleted rows and files, allowing writers to validate their operations without direct conflicts and enabling readers to see consistent views without scanning entire data files.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If traditional read validation is performed in managed object stores, then readers can see consistent views of tables, but read costs and validation overhead increase

Engineering Contradiction:
Improveread view consistencyVSAvoidread validation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system extracts validation information from the data files themselves and places it in separate delete files and metadata structures. This extraction allows readers to perform validation by checking only the small metadata files rather than scanning entire data files, dramatically reducing read validation time while maintaining consistency.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments validation information into separate delete files organized by file and row, rather than embedding validation logic throughout the entire data file structure. This segmentation allows readers to selectively check only relevant portions of the metadata corresponding to their query, reducing overall validation overhead.

Inventive Principle:
Principle #1Segmentation

3Manufacturing precision

If delete files are created for every modified row in managed object stores, then write operations can be tracked, but read operations must validate against all delete files increasing read costs

Engineering Contradiction:
Improvewrite operation trackingVSAvoidread operation efficiency
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The system merges multiple delete file entries into consolidated metadata structures and uses bloom filters to combine validation information from multiple sources. This merging reduces the total number of separate validations readers must perform and allows batch processing of delete information, improving read efficiency while maintaining precise write tracking.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent changes the parameter of delete file organization from row-level granularity to file-level and partition-level groupings. By organizing delete information at coarser granularities and using bloom filters with configurable parameters, the system reduces the number of individual validations required while maintaining adequate precision for write tracking.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12579103B1Method and system for performing read/write operations in database systems including managed object stores
Publication Date: 2026.03.17 TERADATA US INC
  • US12579103B1 patent drawing
  • US12579103B1 patent drawing
  • US12579103B1 patent drawing

AI summary

A system and methods for performing read and write operations in a database system including a managed object store with an open table format. These systems and methods provide throughput/concurrency improvements for write operations employing position deletes by avoiding unnecessary transaction aborts due to possible write conflicts. A probabilistic structure, such as a bloom or cuckoo filter, is utilized to log row updates which are matched with delete file entries to identify conflicts at the row level in write operations. Similarly, improvements in the efficiency of read operations when employing an equity delete process are achieved by using bloom filters for logging object file data, which is matched with delete file entries to eliminate rows from consideration in read operations.