Query Pipeline Serialization for Non-Standardized Data Exchange

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems struggle to efficiently exchange non-standardized data between operations in a query pipeline, particularly when these operations are performed on different computing nodes, leading to inefficiencies and incomplete data processing.

Innovation Solution

A database execution engine facilitates the exchange of non-standardized data by inserting a serialization operation before the second operation in the query pipeline to transform non-standardized data into a relational format for ingestion, and optionally converting it back to its original form if needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If non-standardized data is exchanged between operations on different computing nodes, then data processing completeness is improved, but data exchange efficiency deteriorates due to lack of standardization

Engineering Contradiction:
Improvedata processing completenessVSAvoiddata exchange efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent introduces a serialization operation as an intermediary component between data production and consumption operations. This mediator transforms non-standardized data into a standardized relational format, enabling efficient exchange across distributed computing nodes while ensuring complete data processing. The serialization layer acts as a buffer that reconciles format differences without sacrificing data integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the format parameter of data from non-standardized to serialized relational format during transmission. By transforming the data structure through serialization, the system maintains data completeness while improving exchange efficiency between operations on different computing nodes. The format transformation is reversible, allowing restoration of original data characteristics when needed.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If a serialization operation is inserted before data ingestion, then data exchange compatibility is improved, but query pipeline complexity increases

Engineering Contradiction:
Improvedata exchange compatibilityVSAvoidquery pipeline complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the query pipeline by inserting a dedicated serialization operation between data production and consumption stages. This segmentation isolates the format transformation logic to a specific pipeline stage, improving data exchange compatibility without unnecessarily complicating other pipeline operations. The serialization step is a discrete, well-defined operation that can be independently managed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs serialization as a preliminary action before data ingestion by the consuming operation. By pre-serializing the non-standardized data output from the first operation, the system ensures compatibility with subsequent operations without requiring complex real-time transformations. This advance preparation simplifies the overall pipeline architecture.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If non-standardized data is processed directly without serialization, then processing speed is improved, but data interoperability between different operations deteriorates

Engineering Contradiction:
Improveprocessing speedVSAvoiddata interoperability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a serialization operation as an intermediary that enables fast processing while ensuring interoperability. The mediator converts non-standardized data to a standardized format that can be efficiently processed by subsequent operations, achieving both speed and compatibility. Without this intermediary, direct processing would sacrifice interoperability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12505086B2Transport of non-standardized data between relational database operations
Publication Date: 2025.12.23 SAP SE
  • US12505086B2 patent drawing
  • US12505086B2 patent drawing
  • US12505086B2 patent drawing

AI summary

A method for processing non-standardized data in a relational database may include identifying, within a sequence of operations forming a query pipeline for executing a query, a first operation ingesting a non-standardized data. In response to identifying the first operation ingesting the non-standardized data, a second operation may be inserted before the first operation. The non-standardized data may be output by a third operation preceding the first operation or a source external to the query pipeline. The second operation may serialize the non-standardized data for ingestion by the first operation, for example, by generating a relational table populated by the non-standardized data. The query may be executed by performing the sequence of operations included in the query pipeline. Related systems and computer program products are also provided.