Data Shaping with Pipelines

Warning

SingleStore 9.0 gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 8.9 is recommended for production workloads, which can later be upgraded to SingleStore 9.0.

Lookups from other SingleStore tables (in addition to the destination table(s))
Normalizing data
Denormalizing data
Adding computed columns
Filtering data (excluding specific columns or records)
Mapping data values from the data source to new values
Splitting records from the data source into multiple destination tables
Adding surrogate keys

Data modifications made during shaping are not written back to the data source, unless done explicitly in a transform (SingleStore Self-Managed only).

Ways to specify data shaping logic:

In a CREATE PIPELINE statement.
In a stored procedure that is called from the pipeline.
In a transform that is called from the pipeline.

Methods for Data Shaping with Pipelines

The details of each data shaping method are explained in the following table.

Data Shaping Method	Amount of Customization Logic Allowed	Ease of Use	Comments	Examples
In a `CREATE PIPELINE` statement	Low	Easiest	Pros: Generally, runs the fastest of the three data shaping methods; transactional guarantees. Cons: Limited to SQL WHERE CLAUSE to perform filtering and SQL expressions to perform other shaping logic; can only load data into one target table; cannot perform lookups in other tables; a single row in the data source cannot generate multiple rows in the target table.	`CREATE PIPELINE` uses the `LOAD DATA` clause to perform data shaping. See examples in the LOAD DATA topic.
Pipeline Stored Procedure	Medium	More Difficult	Pros: Transactional guarantees; cons of specifying data shaping logic directly in your `CREATE PIPELINE` statement don’t apply. Cons: Limited to the capabilities of the PSQL language; cannot use third-party libraries.	See examples in CREATE PIPELINE ... INTO PROCEDURE
Transform	High	Most Difficult	Pros: Can use any nearly any programming language and leverage third-party libraries. Cons: Not available in SingleStore Helios; runs slower than stored procedures for most use cases; deployment could be challenging; cannot insert into multiple tables; transactional guarantees apply to data written to `stdout`, only (refer to the guide in the next column for details).	See the guide Writing a Transform to Use with a Pipeline

Data Shaping with Pipelines

On this page

Methods for Data Shaping with Pipelines

Was this article helpful?

On this page

Was this article helpful?