Database Interface for Conditional Write Failure State Return

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users of database systems face difficulties in obtaining immediate and targeted feedback on the state of data items during condition failures in conditional write operations, especially in complex transactions, as the data state may change after the failure and manual investigations are tedious.

Innovation Solution

The database system implements an interface with a failure state return (FSR) indicator that allows users to specify the return of item states upon condition failures, ensuring the returned state is the exact state evaluated at the time of failure, configurable to return specific attributes and only when requested, thereby reducing network traffic and maintaining system performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual examination of data state is performed after failure, then investigation of failure cause is possible, but data may have changed and investigation becomes tedious

Engineering Contradiction:
Improvefailure investigation reliabilityVSAvoidinvestigation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system captures and returns the data item state at the moment of condition failure before any subsequent operations can modify it. This preliminary capture ensures the state is preserved for immediate analysis, eliminating the need for later manual examination and preventing state changes during investigation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides immediate feedback by returning the data item state directly in the error response to the client. This feedback mechanism delivers the required information instantly without requiring separate manual investigation steps, thus saving time and ensuring reliability.

Inventive Principle:
Principle #23Feedback

2Loss of information

If item state is returned upon condition failure, then immediate feedback is provided, but network traffic and system overhead increase

Engineering Contradiction:
Improvefeedback information availabilityVSAvoidnetwork traffic
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The system selectively returns data item state information only when condition failures occur, rather than continuously or unconditionally. This localized provision of information ensures feedback availability when needed while minimizing unnecessary network traffic during successful operations.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system extracts and returns only the specific data item state information relevant to the failure condition, rather than returning entire datasets or unnecessary information. This extraction approach provides necessary feedback while keeping network traffic minimal.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If comprehensive data state information is returned, then troubleshooting is simplified, but system performance decreases

Engineering Contradiction:
Improvetroubleshooting easeVSAvoidsystem performance
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system extracts and returns only the specific attributes of the data item that are relevant to the failure condition, rather than returning comprehensive or redundant information. This targeted extraction simplifies troubleshooting by providing exactly the needed information while maintaining system performance.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10956250B1Database interface to obtain item state on conditional operation failure
Publication Date: 2021.03.23 AMAZON TECH INC
  • US10956250B1 patent drawing
  • US10956250B1 patent drawing
  • US10956250B1 patent drawing

AI summary

Systems and methods are provided to implement a database system configured to return the state of a data item upon failure of a condition check on the data item during a conditional write. In embodiments, a write request may specify an indicator to return the item state upon condition failure. The request may specify multiple database operations to execute as a transaction, where failure of a single condition check will cause the entire transaction to fail and an item state causing the failure to be returned. The returned state of the data item may include a selection of the item's attributes specified by the request. Advantageously, these features allow a client to easily obtain the precise cause of a write's failure. Moreover, because the item state is returned only when a conditional write fails and only when requested, the response size of most write requests remains unchanged.