Couchbase agent changelog
Release notes
2.3.2.2
Released: November 13, 2026
-
A snapshot continued after a pause or a restart resumes after the last document it read instead of reading the collection again from the start, so documents are no longer copied twice and the progress no longer climbs past 100% (233% and 346% seen on a Couchbase to Capella pipeline);
-
A snapshot reads the documents that exist when it starts and leaves the ones added while it reads to CDC, so a collection with steady inserts and ever-growing ids no longer keeps the snapshot running indefinitely;
2.3.2.1
Released: November 11, 2026
-
A region of the cache whose flush to the disk fails stays dirty and is flushed again, instead of being forgotten after that one failed attempt;
2.3.2.0
Released: November 10, 2026
-
DCP: an entity added to a running agent on another collection streams its changes at once, because the running stream is handed over to a wider one from the recorded offsets, instead of getting its snapshot and then no change until every entity of the agent stopped, and a full stop and start no longer rolls vbuckets back to seqno 0;
-
DCP: a widening that cannot open the wider stream reopens the previous one from the same resume points, so the running entities keep streaming, and raises an agent notification only when that fails too, instead of leaving the reader stopped;
-
DCP: new per-entity Source TTL after sync (seconds,
0= off, DCP read mode only): once the target confirms a batch, the agent sets that expiry on each document of the batch, so the bucket works as a short-lived inbox; the expiry applies only to the version the target stored and is not replayed on the target as a delete; -
Snapshot: with scopes and collections the snapshot index is on
META().idand belongs to its entity, and an index an older version left behind is dropped, instead of a type-field index Couchbase 7.6 could not use, whose ordered pages repeated and skipped documents (15,000 documents read as 14,262 rows, 13,834 distinct) and failed the write on a target with a primary key; -
Snapshot: partitions update the shared checkpoint and hand their page on in that order, instead of a page counting another partition’s rows being stored first, which made a stop or a write error resume past documents the target never got, or closed the snapshot before the other pages arrived;
2.3.1.4
Released: November 2, 2026
-
DCP: Two streamed entities whose key patterns can accept the same document id are refused at setup, since on a bucket without collections a deletion carries only the document id and removed rows in both of their targets;
2.3.1.3
Released: October 29, 2026
-
Target: a page is written on ordered lanes bounded by the
writerssetting, which until now changed nothing on this target, so two writes of the same document never overtake each other; -
Target: the change-source document is upserted on every path, so a document deleted and then inserted again is no longer rejected as a duplicate, which left the row unwritten with the Skip insert conflict strategy and stopped the entity with Fail;
2.3.1.2
Released: October 28, 2026
-
Discovery: a collection whose
INFERanswer has an untyped field or a flavor without properties lists its columns instead of failing the whole table withLinkedHashMap cannot be cast to CouchbaseInformationSchema; -
Decimals are read and written with their exact text, so
3000.00no longer becomes3000.0, a value wider than a double no longer loses digits and a"NaN"text reads as null instead of failing; -
Target: a full write is marked with the checksum of its JSON body, the same way the DCP reader recomputes it, so Gluesync’s own write is no longer read back as a change and replayed;
-
Target: a partial write is merged into the stored document under its CAS, so a row with more than sixteen kept fields no longer fails with an
IllegalArgumentExceptionfrom the sub-document mutation limit, and stored numbers with more than seven significant digits are no longer truncated; -
Snapshot: a partitioned snapshot reads the documents whose split field is null, missing or of another type than the bounds, and a partitioned count no longer fails with a syntax error or matches nothing because a string bound was read as a field name;
2.3.1.1
Released: October 27, 2026
-
Couchbase DCP: CDC: the local cache is drained up to its head in one poll instead of one message per poll, so a backlog reaches the target faster;
-
Couchbase DCP: GSSD-1456: resetting the entities deletes the shared read checkpoint, so the reader no longer resumes from the old position;
-
Metrics: a page’s read time no longer includes the wait for the target to consume the previous page;
2.3.0.1
Released: October 15, 2026
-
Couchbase without collections: the custom type key is written on the target and left out of the discovered columns;
-
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;
-
Couchbase DCP: a document whose id does not follow the entity key, such as the
_copythe Couchbase UI makes, is skipped with an error notification naming it, instead of failing the target transaction on delete and overwriting the original row on mutation; -
Couchbase DCP: the id/body key check compares numeric key values by value, so an entity with a numeric key mapped on the document id no longer gets a false "deletions would remove the wrong row" notification;
-
The source cache saves the corrected read position after a recovery scan, so a restart no longer starts reading mid-record or discards records written after a torn record;