SingleStore agent changelog
Release notes
2.3.2.2
Released: November 13, 2026
-
GSSD-1487: On an entity keyed by nullable columns, the row by row writer matches a NULL key with IS NULL, so an update no longer inserts a second copy of the row and a delete no longer leaves it in place;
-
GSSD-1487: On an entity keyed by nullable columns, an insert of a row the target already holds with a NULL in its key is looked up first and handled by the insert conflict strategy (UPSERT, SKIP, FAIL) instead of being written as a second copy after a resume, a Core Hub failover or a snapshot overlapping the changes;
2.3.2.0
Released: November 10, 2026
-
GSSD-1346: Target: the bulk delete matches one NULL pattern at a time, so the staged keys reach the hash indexes and 5,000 staged keys read 5,273 target rows instead of 969,330;
2.3.1.2
Released: October 28, 2026
-
The MySQL types SingleStore reports (
MEDIUMINT,YEAR,DOUBLE,TINYTEXTtoLONGTEXT,TINYBLOBtoLONGBLOB) are supported, and every column name is quoted, so a column named after a keyword no longer fails the write;
2.3.1.1
Released: October 27, 2026
-
Target: an object field from a NoSQL source is written as its JSON text instead of
{name=Ada, age=36}, and an array that holds a map or a nested array is written as a JSON array instead of[Ljava.lang.Object;@…;
2.3.0.1
Released: October 15, 2026
-
Bulk operations: an insert and a delete, or two updates, of a row keyed by binary or array values in one batch are merged instead of leaving the row on the target or failing with a duplicate key;
-
The agent hands its pooled database back when its pipeline is deleted or detached and when its initialization fails. Before, the next pipeline writing to the same database could fail in a loop with
NoClassDefFoundError;