Search docs.molo17.com

    Vertica glyph screenshot Vertica agent changelog

    Release notes

    2.3.2.0

    Released: November 10, 2026

    • Source: an ARRAY column is reported with its element type (_int8, _float8, _bool, _numeric, _text, _bytea, _date, _timestamp, _uuid), and a SET as an array of its members, so a PostgreSQL-family target creates the column instead of failing CREATE TABLE, and ClickHouse no longer declares every Vertica array as Array(String);

    • Snapshot: the bucket that finishes last no longer emits a page whose checkpoint is already completed, which closed the snapshot while other buckets were still emitting, and a stop or a write error no longer resumes past rows the target never got;

    • GSSD-1346: Target: nullable bulk keys are matched with <=>, so the bulk delete no longer fails with ERROR 2787: Correlated subquery expressions under OR not supported, and the old-values fill takes 0.5 s instead of 23 s;

    2.3.1.3

    Released: October 29, 2026

    • Target: a zoned time written into a column without a zone is stored as UTC on the change capture path too, which stored a MySQL TIMESTAMP an hour later in Europe/Rome while the snapshot stored it in UTC;

    2.3.1.2

    Released: October 28, 2026

    • Target: a text written into a CHAR(n) column goes without its trailing spaces, so an update carrying a padded key (a PostgreSQL bpchar) no longer makes the MERGE insert a second row;

    • A time in the hour the agent’s time zone skips at the daylight saving change is replicated as the wall clock the source holds instead of an hour later, and a time written into a column with a zone keeps its instant;

    • Snapshot: a partitioned snapshot reads the rows whose split column is NULL and, with a single partition, the rows equal to the maximum;

    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;@…​;

    • Metrics: a page’s read time no longer includes the wait for the target to consume the previous page;

    2.3.1.0

    Released: October 25, 2026

    • New: Vertica source. The snapshot reads every table at one pinned epoch (AT EPOCH), in parallel hash buckets (snapshotReadParallelism), and CDC delivers the net change of each poll window by comparing epochs: no log, no triggers and no objects in the database. A table whose history is gone (TRUNCATE, DROP_PARTITIONS, the Ancient History Mark moved past the position) is reloaded, or fails when resyncOnHistoryLoss is off. Setup checks that HistoryRetentionTime is at least minHistoryRetentionSeconds (default 3600) and that every CDC entity has a key;

    • Vertica int is treated as 64 bit (LONG) and float as 64 bit (DOUBLE), as Vertica reports them. Before, they were read as 32-bit values, which overflowed above 2^31 and lost the precision of a float;

    • Intervals are read as STRING, an ISO-8601 duration with the sign on every component, so that a negative interval keeps its meaning on the target;

    • The Vertica target refuses to create a column for an ARRAY, SET or ROW type with a clear error that tells you to map it to a string type, instead of creating a column that no write could fill;

    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;

    2.3.0

    Released: October 13, 2026

    • Agent compatibility upgrade to Gluesync 2.3;

    • Columns are discovered in their table order instead of the order the query plan happened to produce;

    • Column discovery reads comments by child_object, instead of failing on every table with Column "cm.anchor_table_name" does not exist;

    • Discovery returns schemas and tables in alphabetical order, so Query Studio pages no longer skip or repeat objects;