Sign inTry Free

SingleStore Flow Release Notes

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.

On this page

Maintenance Release Changelog

SingleStore Ingest

2025/06/04 Version 4.1_b875

Features

  • Added support for SingleStore as a source to the Any Database driver

  • Real-time CDC for MySQL - Added a new dropdown “Continuous” to MySQL

  • Added support for multi-tenant databases

Fixes

  • More consistent display of tables in databases without a schema (or database)

2025/05/08 Version 4.1_b804

Features

  • Added support for MongoDB (private preview only)

  • Added support for Where clause for Snowflake source

Fixes

  • Handled database and table names with hyphens. Hyphen changed to an underscore in the destination

  • When history is stored, all timestamps will be in UTC

  • Vector data type extracted and saved as JSON in Postgres

  • Fixed Issues with Rollback

Known Issues

  • Timestamp with Timezone datatypes is not converted to UTC

2025/04/02 Version 4.1_b702

Fixes

  • Fixed delta load error in PostgreSQL for masked column

  • Cleared out .err files from spool directory for MySQL

  • Added support for the JSON data type in MySQL

  • DATETIME(3) now created to retain milliseconds for MySQL to SingleStore

2025/03/05 Version 4.1_b699

Features

  • Added support for the JDBC database source (Snowflake).

    Databases vary considerably and this driver has only been tested with Snowflake. JDBC database source extracts do not support a CDC mechanism and are full extracts only.

  • Enhancements to the PostgreSQL source driver

    • Array data type (inserted as JSON in SingleStore)

    • Custom data types

    • JSON and JSONB data types

    • Column names that are reserved words

    • Table names with mixed case

Fixes

  • Fixed MySQL delta extract errors

Known Issues

  • Masked columns are not supported for PostgreSQL

  • The BYTEA data type is not handled correctly on PostgreSQL

  • The BIT(size) data type is not handled correctly on MySQL

  • The TINYINT/BIT data type may show a mismatch on Sync Struct

2025/02/17 Version 4.1_b671

Fixes

  • Fixed MySQL delta extract errors

  • Added support for PostgreSQL user-defined data types

  • Added support for PostgreSQL extract of tables with reserved-word columns

2025/01/31 Version 4.1_b643

Features

  • Implemented a new licensing scheme which is based wholly on the destination SingleStore instance size

  • Added connection attributes to SingleStore connection

  • Added support for loading binary data. Flow now uses Avro format internally.

  • Mapped the Microsoft SQL Server type DATETIME to DATETIME(6)

Fixes

  • Sync Struct does not get false negatives when matching data types

  • Handled reserved words in column names

  • Fixed loading deltas for history tables

Known Issues

  • Delta extracts can sometimes fail on MySQL

  • Timezone-based timestamps do not take the time zone into account

  • Masked columns can fail on PostgreSQL

  • Binary data may be ignored on PostgreSQL

  • MySQL BIT(n) data types are not handled correctly

  • Rollback may not work as expected in some cases

  • Load message in the logs may show incorrect record counts

2025/01/21 Version 4.0.2_b587

Features

  • Updated how reserved words are handled in column names, which can be done by either adding an underscore (default) or enclosing them in backticks

  • Increased the precision for DATETIME in the SQL Server input source

2024/12/24 Version 4.0.2_b571

Features

  • Implemented data type mapping for all four sources

  • Primary key and shard key are automatically created on SingleStore

  • Removed extraneous sources from the drop-down list

Known Issues

  • Binary data not loaded

  • Timestamps with time zones are not converted to UTC

  • Masking columns may give load errors

  • Loading with history may fail in some cases

2024/12/03 Version 4.0.2_b536

Features

  • Full extracts provide a detailed progress bar on the Dashboard

  • Default transfer type is now set to not keep history

  • PostgreSQL databases will now show tables in the PUBLIC schema

Fixes

  • Auto-selecting the primary key now works as expected

  • The Dashboard shows scheduled period for values under 1 minute

  • The Advanced tab for Destination now works as expected

  • Fixed the occasional null value error on startup

  • Changes in the underlying runtime metadata tables

SingleStore XL Ingest

2025/03/05 Version 2.4_b1257

Features

  • Added support for the JDBC database source (Snowflake)

  • Enhancements to the PostgreSQL source driver

    • UUID column can be used for slicing

    • Array data type (added to SingleStore as JSON)

    • Custom data types

    • JSON and JSONB data types

    • Column names that are reserved words

    • Table names with mixed case

2025/02/17 Version 2.4_b1227

Fixes

  • Handled reserved-word column names

2025/01/31 Version 2.4_b1224

Features

  • Implemented a new licensing scheme which is based wholly on the destination SingleStore instance size

  • Added connection attributes to SingleStore connection

  • Added support for loading binary data. Flow now uses Avro format internally.

Fixes

  • Added support for loading data for tables with masked columns

Known Issues

  • Timezone-based timestamps do not take the time zone into account

  • BLOB data is not extracted for Oracle

2025/01/21 Version 2.3_b1178

Features

  • Updated how reserved words are handled in column names, which can be done by either adding an underscore (default) or enclosing them in backticks

  • Increased the precision for DATETIME in the SQL Server input source

2024/12/24 Version 2.3_b1174

Features

  • Implemented data type mapping for all four sources

Known Issues

  • Binary data not loaded

  • Timestamps with time zones are not converted to UTC

  • Masking columns may give load errors

ControlRoom

2025/05/06 Version 43-b8

Known Issues

  • Minor cosmetic issues on dashboard

  • No details are shown for an XL Ingest instance

Last modified: June 4, 2025

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK