Gluesync release notes and changes
Welcome to the Gluesync release notes. This page provides detailed information about each release, including new features, improvements, and fixes.
Quick Links
Latest Release: 2.3.2.2
Released: November 13, 2026
Gluesync 2.3.2.2: one-click Platform updates come to Kubernetes
Release highlights
Dear data wranglers,
On Docker, updating Gluesync has been one click in the Core Hub UI for a while, thanks to Conductor. On Kubernetes it still meant a Helm upgrade and a careful eye on your pipelines. Not any more: the Gluesync Kubernetes Operator is now available, and the same Platform updates panel updates Core Hub and its modules on your cluster too.
Gluesync Kubernetes Operator (GKO): Platform updates on Kubernetes
Additional improvements
-
Core Hub:
-
A snapshot read retried after a failure, or restarted after a cancellation, resumes from the checkpoint the target last wrote instead of the one the launch started with, so rows already written are not read and copied again;
-
A CDC start that fails after a completed snapshot (a source agent that does not answer, a source, target or storage failure) raises one critical alert saying CDC did not resume, with its error type and cause, instead of being logged and dropped or warned twice as "Start entity interrupted";
-
GSSD-1487: An entity created through MCP keeps the nullability discovery reports for the key columns of an existing target table instead of storing them all as NOT NULL, which made the writers miss rows whose key holds a NULL;
-
An inbound collection attached to an HTTP Source is deleted only when forced, which detaches it from the HTTP Source;
-
A configuration import refused for its payload is logged at WARN with the reason instead of at ERROR as "Failed to dispatch configuration to agents";
-
The AI Studio editor chats (Spark in the UDF editor, custom function editor, Query Studio, AI SQL, notification explanations, prompt drafts, Visualize) and the Spark agent, pipeline helper and Chronos chats stream the provider answer instead of waiting for one body, so a slow answer through Gluesync Connect no longer fails with an HTML 504 from the proxy, and a provider HTTP error is reported with its status;
-
-
UI:
-
GS-1458: Added a "Resumable snapshot" setting to the fine tuning of a single table entity of a SQL source;
-
The start dialog reads the copy progress of every selected entity and no longer offers to continue a snapshot that Core Hub refuses (a table copied without key order), naming the tables that start over instead of failing the command with a 409;
-
Courier: The route editor follows the new inbound routes: a route is a method, a path, an operation and its bindings, a read route declares its filters, response fields and key, the request preview uses the Courier inbound port, the HTTP Source names its inbound collection, and New entity shows the method of each HTTP Source table;
-
Courier: An entity built on a PATCH route warns until its target skips absent columns, and "Set to Skip column" writes the policy where Core Hub reads it, so the entity is no longer refused after the click;
-
Courier: An inbound collection with endpoints, or attached to an HTTP Source, can be deleted, with a confirmation that detaches it from its pipeline;
-
Courier: The tooltips of the collection tree and of the endpoint forms stay inside the window instead of being cut by their pane, and the Inbound and Outbound tabs use the same size;
-
Modules Manager: The Kubernetes operator is named "Gluesync Kubernetes Operator" instead of "-" or "gluesync-operator", also when its image comes from a Nexus mirror, and the reverse proxy "Traefik reverse proxy";
-
Updates: The update panel waits for the Kubernetes operator to restart as it does for Conductor, so a second update sent during its hand-over no longer fails with "A service is temporarily unavailable";
-
-
Kits:
-
Courier inbound on port 8090: from v0.0.298 (November 17, 2026), every kit sends
/api-inbound/to Core Hub’s inbound server over HTTPS instead of plain HTTP, which the reverse proxy answered with500on Core Hub 2.3.2.2. This covers the Kubernetes Helm chart (scheme: httpswithserversTransport: insecure-transporton thecourierIngressRoute) and the Docker Compose and Docker Swarm kits on Linux and Windows (scheme=httpson the Courier route of Core Hub). The kits no longer tell you to setinboundAllowPlainHttp. On an existing Kubernetes install, runhelm upgradewith the new kit; on Docker Compose, Conductor makes the change, see Conductor 0.14.4 and, for Kubernetes routes added by the operator, GKO 0.4.2;
-
-
Agents:
-
Azure Cosmos DB agent: fixes and improvements;
-
CockroachDB agent: fixes and improvements;
-
Couchbase agent: fixes and improvements;
-
Greenplum agent: fixes and improvements;
-
HTTP Source and HTTP Target agent (Courier): fixes and improvements;
-
MariaDB agent: fixes and improvements;
-
MongoDB agent: fixes and improvements;
-
MS SQL Server CDC agent: fixes and improvements;
-
MS SQL Server Change Tracking agent: fixes and improvements;
-
MySQL agent: fixes and improvements;
-
PostgreSQL agent: fixes and improvements;
-
SingleStore agent: fixes and improvements;
-
YugabyteDB agent: fixes and improvements;
-
2.3.2.1
Released: November 11, 2026
Gluesync 2.3.2.1: meet Courier, your pipelines now speak REST in both directions
Release highlights
Dear data wranglers,
Last time we taught CDC to rewind and kept a second site warm. This time we went after the one system in every integration project that has no database to read, only an API. Until now that meant a script, a cron job and a long debate about who owns it when it stops. Not any more: Courier brings REST APIs into Gluesync as first-class citizens, so a pipeline can deliver its changes to an API, or take records from one, with the same entities, mappings and checkpoints you already use for databases.
Here’s what’s new:
Courier: REST APIs become sources and targets of your pipelines
Additional improvements
-
Agents:
-
HTTP Source and HTTP Target agent (Courier): initial release;
-
Couchbase agent: fixes and improvements;
-
IBM i series agent: fixes and improvements;
-
Informix agent: fixes and improvements;
-
MariaDB agent: fixes and improvements;
-
MySQL agent: fixes and improvements;
-
Oracle LogMiner agent: fixes and improvements;
-
Oracle Triggers agent: fixes and improvements;
-
SAP SQL Anywhere agent: fixes and improvements;
-
Sybase ASE agent: fixes and improvements;
-
-
Core Hub:
-
GSSD-1501: A key that changes again after an insert and a delete cancel out inside one bulk batch is written, instead of every later change to it being dropped while the transaction was confirmed, which lost a row inserted, deleted and inserted again in the same batch;
-
GSSD-1488: The status of a pipeline that is unhealthy for a failed migration names the migration and asks to click Retry, instead of an error banner with no text at all;
-
GSSD-1488: A pipeline stays failed until every agent of a migration retry has migrated, instead of a retry that failed on a later agent answering with an error while the pipeline looked healthy and the failed migration came back at the next boot;
-
2.3.2.0
Released: November 10, 2026
Gluesync 2.3.2.0: restart from any point in time, disaster recovery, query your lake files, run on Podman
Release highlights
Dear data wranglers,
Last time we taught Databricks four new ways to sign in and gave the MCP server a little more patience. This time we went after the question every on-call engineer has asked at least once: "can we just replay everything since Tuesday at 14:00?" Now you can, with no snapshot and no long night. While we were at it, Query Studio learned to read the files your pipelines drop in the lake, a second Core Hub can now stand by to take over when the first one is lost, Gluesync stopped insisting on Docker, and the snapshot settings got a speed test, so you can stop guessing thread counts.
We’ve been busy. Here’s what’s new:
Point-in-time restart: rewind CDC, skip the snapshot
Disaster recovery: a second site that’s ready before you need it
Query your lake files: Parquet, CSV and JSON, no extra tool required
Podman, rootful and rootless: Docker is now optional
Snapshot autotuning: let the speed test pick the threads
Import entities from a file — bring a YAML or ZIP, see every table before it lands
Additional improvements
-
Core Hub
-
Low disk space alert: Core Hub checks the free space of its data folder every minute and sends
gluesync.system.disk-space-low(warning under 20 GB or 10 percent free, critical under 5 GB) to the notifications hub, email, webhooks and Gluesync Connect, with adisk.spacesystem condition. See Free disk space and manage cache and logs; -
GSSD-1185: Core Hub sends baseline security headers, enforces HSTS over TLS, and accepts cross-origin requests only from the origin a request was addressed to or one listed in
GLUESYNC_CORS_ALLOWED_ORIGINS(GLUESYNC_FRAME_ANCESTORSandGLUESYNC_HSTSadjust the defaults). Session tokens expire afterSESSION_DURATION_HOURS(72 by default), the session cookie is Secure behind a TLS proxy, a role change applies at once, and calls with a personal API token no longer leave one session behind each; -
GSSD-1185: mapping functions are read, edited, compiled and run only by Super Admin and Manager, in the REST API and over MCP; the Monitor role loses that access;
-
Upload Logs to Support accepts a support voucher and uploads the archive straight into the voucher’s ticket, also with the
upload_support_logsMCP tool. The curl and FTP fallbacks are gone, and WebDAV is the only other route; -
The validator keeps the settings of the last run of each entity started from the web UI (key, columns, mapping and options) and starts the next run from them, instead of from the pipeline defaults (
/data-comparison/settings); -
Core Hub suggests a chain order that respects foreign keys, parents first, and reports dependencies, self references, cycles and unreadable tables, in the web UI, with
POST /pipelines/{id}/entities/chain-orderand with thesuggest_chain_orderMCP tool; -
GSSD-1495: new Truncate String field function keeps the first N characters of a string, so a value wider than its target column is written instead of refused. The web UI fills N with the length of the target column;
-
A start sent while the agents are still being configured, after a Core Hub restart or a resume from maintenance, runs its snapshot instead of leaving the entities marked running; a redo sent before both agents are configured answers 425;
-
Deleting an entity keeps the files of its mapping function while another entity still uses it, so that entity keeps running instead of failing with "has not been compiled for this version of Gluesync";
-
compile-mapping-functionanswers 400 with the reason on a body it cannot decode, instead of 500; -
64-bit table, object and column ids that a client rounded (a browser or an MCP host reading JSON numbers as doubles) are put back by a storage migration, and requests carrying rounded ids are refused with 400 naming the expected id; the MCP endpoint hands these ids out as JSON strings. A pipeline whose ids were restored logs one warning and its replicating entities need a resync, and a configuration exported before the upgrade must be exported again;
-
Tables Gluesync creates declare a composite primary key in the order of the key, instead of the order of the columns, so a key
(REGION, ORDER_ID)is no longer created as(ORDER_ID, REGION), which is the clustered index on SQL Server, MySQL and MariaDB and the sharding column on YugabyteDB. Existing tables are not altered; -
GSSD-1346: nullable key columns stay index keys when CDC updates, deletes and bulk flushes match rows on Oracle, PostgreSQL, YugabyteDB, CockroachDB, MySQL, MariaDB, SingleStore, Vertica, Db2 LUW, Informix and SQL Anywhere, so a flush no longer scans a whole history table: 136 s down to 0.1 s on Oracle, 249 s down to 24 ms on PostgreSQL;
-
The daily anonymous usage heartbeat also reports which features an installation uses (yes or no, the date of last use, counts and connection kinds, for MCP, Enterprise Brain, AI Studio, Query Forge, Query Studio, the validator, Visualize, Chronos, alerts, OIDC, users and groups, and data access policies), never prompts, queries or names. It is sent only while usage analytics is on;
-
-
Spark and AI Studio
-
Starting and stopping entities with Spark takes about half the input tokens: one
sync_commandMCP tool takes entity names and replacesstart_sync,stop_sync,redo_syncand the other sync tools (stored allow lists keep working), and a bare string inentity_namesorentity_idsis refused instead of meaning the whole pipeline; -
GSSD-1482: the AI Studio OpenAI provider uses the Responses API instead of chat completions, so OpenAI models that take function tools only there work. An endpoint answering 404 or 405 on
/responsesfalls back to chat completions once; an endpoint with chat completions only should use the OpenAI-compatible provider type;
-
-
Query Studio and Query Forge
-
Every join strategy across agents (semi-join reduction, merge, range and band joins, outer-join pre-aggregation, agent join reordering) is on by default instead of opt-in;
GLUESYNC_JDBC_JOIN_STRATEGIES=noneturns them off; -
Query Forge reads a MongoDB collection in pages bounded by
maxScanRowsinstead of failing past the first 10,000 documents; -
Query Forge returns the same results as the source for
MINandMAXover floating point columns holding NaN,AVGover wide decimals, zoned timestamps (read as UTC) and array columns, instead of overflowing or shifting values, and Query Studio shows PostgreSQLmoneyvalues of 1,000 and above instead of failing; -
GSSD-1487: Query Studio shows a timestamp without a zone as the wall clock the database holds, instead of reading it as browser-local time, which moved a midnight skipped by daylight saving an hour later;
-
-
Validator and data comparison
-
Key ordering expressions work on Oracle, Db2 LUW and IBM i (the hidden key aliases are quoted, so
ORA-00911andSQL20521Nno longer occur, and_RRNreads asRRN(T)on IBM i), and the reconciliation of a job with a target key ordering expression updates and deletes the target row by its physical key;
-
-
Web UI
-
Import entities from a YAML or ZIP file on the New Entity page: every table checked with Core Hub before it is added, missing target tables created, ZIP UDFs and Custom Field Functions compiled, entities saved on Confirm and continue and left stopped (!798);
-
GSSD-1496: the entities list of a pipeline searches by entity name, source table or target table, and a new entity is named
<source> -> <target>by default when the two names differ, cut to fit 50 characters; -
The web UI works on the Edge 86 that Windows Server 2022 ships with, instead of opening the error page with "Object.hasOwn is not a function";
-
The object browser searches by
schema,schema.tableor.tableand selects a named table without listing the whole source, so a source with thousands of schemas or tables no longer keeps you waiting for minutes; -
The start dialog keeps saved
In,NotIn,Regex,IsNullandIsNotNulldelete filters, instead of savingInback as an equality, which deleted other rows, and keeping Start disabled onIsNullandIsNotNull; -
A target type without a length, such as Databricks
STRING, no longer asks for one in the field mapping; -
An empty custom property row no longer blocks Test and continue on an agent connection;
-
Entity settings names the target by its connection (user and host) instead of the agent nickname;
-
Minor: the speed tags and the same-key menu of the start dialog are no longer cut off, the toast mute menu opens above the toasts, and the agent configuration form is more compact;
-
-
Agents
-
AWS S3 agent: Parquet decimals at the right scale, JSON numbers written exactly, files readable in Query Studio;
-
Azure Cosmos DB agent: partitioned snapshot pages stored in order;
-
Azure Data Lake Gen2 agent: Parquet decimals at the right scale, JSON numbers written exactly;
-
CockroachDB agent: nullable key columns stay index keys;
-
Couchbase agent: stream widened to collections of later entities, source TTL after sync, snapshot no longer repeats or skips documents;
-
Databricks agent: complex values checked against their column, array types from source arrays, catalog check on connection test;
-
DynamoDB agent: partitioned snapshot pages stored in order;
-
Fabric Open Mirroring agent: landing zone URL required, other fields optional, port 443 by default;
-
Google Cloud Storage agent: Parquet decimals at the right scale, JSON numbers written exactly;
-
GridGain agent: table creation and truncate fixed for GridGain 8, plain-path TLS stores, optional credentials;
-
IBM Db2 LUW agent: nullable keys matched by NULL pattern, NULL key next to scalar functions;
-
IBM Db2 LUW CDC agent: nullable keys matched by NULL pattern, NULL key next to scalar functions;
-
IBM i series agent: shared tables kept for CDC entities, journal rows kept per entity, outdated checkpoints on reused receiver names;
-
Informix agent: nullable bulk keys indexed, NULL-key upserts, entity started while another one syncs is watched;
-
MariaDB agent: binlog read from snapshot start, purged-checkpoint detection, UTF-8 and BIT bulk load, recursion protection takes effect;
-
MongoDB agent: partitioned snapshot pages stored in order, Query Forge reads in pages;
-
MS SQL Server CDC agent: changes read in LSN order, tables matched by name, tables left without capture reported;
-
MS SQL Server Change Tracking agent: tables matched by name, tables left without Change Tracking reported;
-
MySQL agent: binlog read from snapshot start, purged-checkpoint detection, UTF-8 and BIT bulk load, recursion protection takes effect;
-
Oracle LogMiner agent: text columns sized in characters, indexed nullable bulk keys;
-
Oracle Triggers agent: idle CDC tables purged hourly, text columns sized in characters;
-
Oracle XStream agent: changes kept between polls, unsigned position order, text columns sized in characters;
-
PostgreSQL agent: replication slot dropped with its entity, nullable key columns stay index keys;
-
Redis agent: connection test names the root cause, no credentials in messages;
-
Redis Streams agent: connection test names the root cause, no credentials in messages;
-
ScyllaDB agent: partitioned snapshot pages stored in order;
-
SingleStore agent: nullable key columns stay hash-index keys;
-
SAP SQL Anywhere agent: NULL key merged next to scalar-function columns;
-
Sybase ASE agent: nullable columns created NULL;
-
Universal File Store agent: Parquet decimals at the right scale, JSON numbers written exactly, files readable in Query Studio;
-
Vertica agent: array columns typed for every target, safe bucket snapshot checkpoints, nullable bulk keys;
-
YugabyteDB agent: replication slot dropped with its entity, NULL-key upserts indexed;
-
2.3.1
2.3.1.4
Released: November 2, 2026
Gluesync 2.3.1.4: log upload with a ticket voucher, data comparison fixes for Databricks
Release highlights
Dear data wranglers,
2.3.1.4 completes the Databricks target with more ways to sign in, Unity Catalog metadata and lineage on the tables Gluesync creates, and wide decimals that no longer refuse writes. The MCP server now works behind your reverse proxy out of the box and no longer gives up on slow operations.
Databricks: more sign-in options, Unity Catalog metadata and lineage
-
New Apache CouchDB source and target agent for CouchDB 3.3, 3.4 and 3.5, on a single node or a cluster, over the HTTP JSON API with no vendor SDK. As a source it lists the ids from the
_changesfeed and reads the documents with parallel_bulk_getrequests (94,000 documents per second with 16 requests at a time), resumes an interrupted snapshot from the feed position it had reached, and follows the_changesfeed for CDC, replaying the changes made during the snapshot. As a target it writes with parallel_bulk_docsrequests, looks up revisions, retries conflicts, deletes with tombstones, merges partial changes and creates databases with the number of shards you choose, the main lever of the write throughput (15,000 documents per second with 2 shards, 81,000 with 32 on a single node). Attachments and purges are not replicated. See changelog;
Additional improvements
-
Core Hub:
-
Every support ticket has a voucher,
GSV-XXXX-XXXX-XXXX, shown on the ticket page of the support portal and in the e-mail sent when the ticket is opened. Settings → Support → Log collection for support uploads the log archive straight into the ticket with it (Support voucher), up to 5 GB, in resumable parts of 16 MB, with the size verified. The voucher is valid while the ticket is open and for 30 days after it is closed. See Your ticket voucher; -
The host needs outbound HTTPS to the support portal API and to
*.s3.eu-central-1.amazonaws.com.GLUESYNC_SUPPORT_API_URLoverrides the address of the API; -
The ticket number and e-mail address remain as a legacy option, over WebDAV only: Core Hub no longer falls back to FTP and no longer uses
curl;
-
-
Validator and data comparison
-
Databricks array, map and struct columns are now compared by their JSON form, so they no longer show up as differences when the pipeline wrote them correctly.
-
A MongoDB decimal or a date nested in an object or an array is compared as the source agent hands it on, instead of as the Extended JSON of the document, which reported one mismatch per document holding such a value;
-
-
MCP
-
The MCP endpoint accepts requests on any hostname unless you restrict it with
GLUESYNC_MCP_ALLOWED_HOSTS, so it works behind a reverse proxy without extra setup; requests stay authenticated and the browser origin check stays on. -
Slow operations called through MCP, such as attaching an IBM i connection or waiting for a trigger flow, no longer fail after 15 seconds while Core Hub completes them.
-
-
Spark
-
The agent chat attaches the tools a turn needs and loads the others on request instead of sending the whole allow-list every round, so an agent set to All tools no longer exceeds OpenAI’s limit of 128 tools and its first round drops from 208 tools and 117,781 characters of schema to 18 tools and 8,562;
-
A request that exceeds the provider’s tool limit is refused before the call with a message naming how many tools to remove, and a routed completion moves on to the next model, instead of the provider answering with a raw HTTP 400 body;
-
-
Core Hub
-
GSSD-1481: Upload Logs to Support holds the connection open for the whole archive and upload instead of being cut at the ten minute REST timeout, and rotated .gz logs go into the tar.xz as they are, which took 1.4 seconds against 252 seconds on 1 GB of gzipped logs, with the free space checked first;
-
GSSD-1473: The operations that replace an earlier one on the same key are counted and logged once per list, instead of one warning per operation, which on a source whose key is not unique wrote 1,575,925 lines in two hours and slowed the snapshot down;
-
Saving an entity whose sides carry new agent entity ids replaces the stored side instead of adding one, which left the entity with two target sides and every later save refused as a duplicated entity side;
-
GSSD-1471: /authentication/me answers 401 instead of an unhandled 500 when it finds no user;
-
The cache eviction loop of an agent that leaves its pipeline is stopped, instead of running on the cleared configuration and failing every fifteen minutes after the pipeline was deleted;
-
-
Web UI
-
Every notification toast now dismisses itself, errors after 10 seconds; the notification drawer keeps the history.
-
The how-to guides tooltip is no longer clipped in Settings and the notification drawer, and the functions hint can be dismissed.
-
-
Agents
-
Couchbase agent: DCP refuses two entities whose key patterns can accept the same document id;
-
CouchDB agent: new agent, source and target with a resumable changes feed snapshot;
-
Databricks agent: new authentication modes, Unity Catalog metadata and lineage, wide decimals;
-
Elasticsearch agent: HTTP client on OkHttp for TLS 1.3 and hostname-checked certificates;
-
IBM Db2 LUW CDC agent: CDC row flagged read only once it has been emitted;
-
IBM Db2 LUW log reader library: 1.0.17: quarantine instead of stopped CDC, NOT NULL guard, LR error codes, Db2 12.1 row migration fixes;
-
IBM i series agent: batched Db2 for i inserts, wall-clock query timeouts, start position logged once per entity;
-
MongoDB agent: resume positions kept in one time unit across targets;
-
MySQL agent: transactions written with binlog_transaction_compression are captured;
-
Oracle LogMiner agent: PARALLEL written as a real optimizer hint where it belongs;
-
Oracle Triggers agent: PARALLEL optimizer hint and INDEX_ASC ordered snapshot;
-
PostgreSQL agent: maps and lists written as JSON text on binary COPY and JDBC batch insert;
-
SAP SQL Anywhere agent: snapshot query and partitioned read fixes;
-
2.3.1.3
Released: October 29, 2026
Gluesync 2.3.1.3: SAP SQL Anywhere joins the catalog, and CDC resumes exactly where it stopped
Release highlights
Dear data wranglers,
2.3.1.3 brings the SAP SQL Anywhere agent, as a source that reads the transaction log and as a target. CDC on SQL Server, ScyllaDB and DynamoDB now resumes from the right position every time, Couchbase and Aerospike writes keep their order, IBM i keeps pace with busy journals, and the Validator stops flagging data the pipelines wrote correctly.
New agent: SAP SQL Anywhere
Additional improvements
-
Core Hub:
-
A lookup Core Hub sends to itself for an MCP tool, a Spark question or Visualize authoring no longer raises a pipeline notification, while a start, snapshot or configuration change made the same way still does;
-
-
Validator:
-
GSSD-1420: a count-only run ends with a warning carrying both counts and their difference, instead of a clean result the UI shows as No differences found;
-
Fixes for the differences the live QA kits flagged on data the pipelines wrote correctly, including PostgreSQL ranges read as text, a non-UTF-8 ClickHouse
Stringread as its bytes, SQL Server geometry compared as well-known text, the Databricks types, and array elements that are times compared by their instant; -
A member of a multi-member IBM i file is compared through the alias the agent creates over it, instead of failing with
SQL0204because a member is not an SQL table;
-
-
Agents:
-
SAP SQL Anywhere agent: new source and target agent;
-
Couchbase agent: ordered write lanes, deleted and reinserted documents written;
-
Aerospike agent: ordered write lanes;
-
MS SQL Server CDC agent: resume at the capture instance minimum, unsigned LSN comparison;
-
MS SQL Server Change Tracking agent: expired read position refused with an error;
-
ScyllaDB agent: CDC positions compared by timestamp;
-
Amazon DynamoDB agent: stream sequence numbers compared by value;
-
Oracle LogMiner agent: faster, exact
IS NULLmatching in redo; -
IBM i series agent: no idle wait after a journal page with no matching rows;
-
Vertica agent: zoned times stored as UTC on CDC;
-
SAP HANA agent: typed binary and LOB values in
MERGE;
-
2.3.1.2
Released: October 28, 2026
Gluesync 2.3.1.2: steadier snapshots, safer shutdowns and tighter TLS for MySQL and MariaDB
Release highlights
Dear data wranglers,
2.3.1.2 is a reliability update on top of 2.3.1.1: every row of a partitioned snapshot gets read, Core Hub shuts down cleanly, memory stays under control across all your pipelines, MySQL, MariaDB, PostgreSQL, YugabyteDB and Informix CDC keep up with far more small commits, and MySQL and MariaDB connections verify the server you trust.
Additional improvements
-
Core Hub:
-
Partitioned snapshots read every row: the rows whose split column is NULL and, with a single partition, the rows equal to the maximum were skipped in the read and in the partition counts, and an
ORin the entity filter no longer leaks rows into every partition; -
A continued partitioned snapshot skips the partitions it already completed instead of reading them again;
-
GSSD-1462: case-insensitive deduplication merges keys only within a run of rows sharing the same operation, so a key change no longer loses its delete and leaves the old row on the target when the insert conflict strategy is Skip;
-
Shutting down Core Hub no longer closes the cache while the CDC readers are running, which left a pending transaction behind, saved a checkpoint past changes that never reached the cache and grew
pending.mmfwithout bound; -
One shared memory budget limits the pages in flight across all pipelines, half of the heap by default and set with
GLUESYNC_PAGE_MEMORY_BUDGET_BYTES, so a hundred CDC entities with 8 MB pages can no longer pin about 5 GB of heap. A pipeline that waits for longer than a minute is named in a notification, and one waiting on its own target is told so; -
The specific configuration and the custom host credentials accept numbers and booleans sent as strings instead of answering
500, and a value that cannot be converted is refused with a400naming the key; -
Webhook delivery logs keep every delivery: concurrent deliveries no longer overwrite each other’s entries, a delivery that fails to send is still logged, and test sends are recorded;
-
-
MCP:
-
create_entitydrafts the entity again from the target’s own discovery once the table exists, so a MySQL to SQL Server entity no longer carries the source collation into the target and fails every write withInvalid collation; -
MCP tools percent-encode the query values they send to Core Hub, so a notification search containing a space no longer answers
400and a value with&,+,%or#is no longer split or altered;
-
-
Validator:
-
The expected target row is predicted before comparing, replaying the row-level UDF, the per-column field functions and the entity filter, so a masked, trimmed, reformatted or composed column is no longer reported as a difference on every row. A reconciliation writes the predicted values only on request and is refused for a UDF;
-
Runs compare leniently by default: floats within a relative 1e-6, timestamps a whole zone offset apart or truncated, and character texts that differ only by trailing spaces are the same value, and what was tolerated is reported once per column as a
TOLERATED_VALUESnotice.STRICTis available on request and ascomparison_profileon MCP; -
A reconciliation goes through the same data-access policy check as reading the differences, and a run’s differences are no longer readable once its tables cannot be resolved under a restrictive policy;
-
Fixes from live QA across fifteen database pairs, including a Couchbase reconciliation that rewrites the document whole at the CAS it was read with instead of leaving it half updated, and Validate and Reconcile blocked in the UI on connectors that cannot compare;
-
-
Query Studio:
-
A statement the database stopped at its timeout answers
408 query-timeoutinstead of a422query failure, a connection error is never reported as a timeout, and a query you cancelled is audited as cancelled;
-
-
Security:
-
The Query Forge JDBC gateway enforces the JDBC permission and the agent scopes of the Personal API Token, binds every connection and statement to the token session that opened it, and stores its connections without the token, so another client can no longer use a known connection or statement id;
-
-
UI:
-
Field mapping shows a Looking for additional fields? hint when the source agent offers technical fields such as the IBM i
RRN. Its link opens the source agent’s Advanced settings in a new tab, on a highlighted Technical fields row, so the mapping in progress is kept; dismiss it with its close button (GSSD-1464);
-
-
Kits:
-
Agents:
-
PostgreSQL agent: faster CDC of small commits;
-
YugabyteDB agent: faster CDC of small commits, daylight saving hour fix;
-
Informix agent: non-blocking CDC reads, faster checkpointing, replaced capture session fix,
BOOLEAN,CLOBandFLOATtypes, daylight saving hour fix; -
Oracle Triggers agent: faster ordered snapshot start;
-
Couchbase agent: exact decimals, untyped
INFERfields, own writes no longer replayed, partial writes over sixteen fields, partitioned snapshot fixes; -
Azure Cosmos DB agent: partitioned snapshot fixes;
-
MongoDB agent: partitioned snapshot fixes;
-
Amazon DynamoDB agent: partitioned snapshot reads every item once;
-
ScyllaDB agent: partitioned snapshot by token ranges;
-
SAP ASE agent: CDC table for
MONEYcolumns, daylight saving hour fix; -
Vertica agent: padded
CHARkeys, partitioned snapshot fix, daylight saving hour fix; -
SingleStore agent: MySQL types, quoted column names;
-
GridGain agent: byte array columns;
-
CockroachDB agent: array columns, daylight saving hour fix;
-
Redshift agent: daylight saving hour fix;
-
MS SQL Server CDC agent: daylight saving hour fix;
-
MS SQL Server Change Tracking agent: daylight saving hour fix;
-
IBM Db2 LUW triggers agent: daylight saving hour fix;
-
IBM Db2 LUW CDC agent: daylight saving hour fix;
-
Universal file store agent: WebDAV custom path fix;
-
Chronos:
-
Chronos 0.3.2, see changelog:
-
No longer stops responding at the daylight saving time change in autumn, and runs missed while it was stopped are run when it starts again; a missed maintenance exit always runs, so a pipeline is never left in maintenance (GSSD-1457);
-
Schedules in a timezone other than UTC keep their correct next run time across restarts and upgrades;
-
-debianimages for x86-64 CPUs without x86-64-v2 support, chosen automatically by Gluesync Control and the installers;
-
-
2.3.1.1
Released: October 27, 2026
Additional improvements
-
Core Hub:
-
Problems that affect the whole Core Hub are reported as system conditions (
GET /system/conditions, the UI websocket and theget_system_conditionsMCP tool) that clear themselves once the problem is gone, instead of one toast per failed attempt; -
Request headers up to 32 KB are accepted instead of 8 KB, so a browser carrying SSO and analytics cookies of the parent domain no longer gets
431 Request Header Fields Too Largeon the login page (GSSD-1452);
-
-
MCP:
-
The MCP endpoint answers on your own hostnames: list them in
GLUESYNC_MCP_ALLOWED_HOSTS(and browser origins inGLUESYNC_MCP_ALLOWED_ORIGINS) instead of getting403 Invalid Hostbehind a reverse proxy.localhostis always allowed,/mcp/httpkeeps its DNS-rebinding protection when SSE is disabled, and a refused host is named in the Core Hub log. See Running behind a reverse proxy or on a custom hostname (GSSD-1459);
-
-
Security:
-
The MCP
export_pipeline_yamltool obfuscates agent secrets, asGET /pipelines/{id}/configdoes; -
The support bundle leaves out
bootstrap-core-hub.json,security-config.json,ssl-config.jsonand the certificates and keys uploaded for connections and agents;
-
-
Query Studio:
-
Query Forge pushes
COUNT(NULLIF(…))down to the source again instead of reading the source row by row; -
A Query Forge statement cancelled at its timeout fails with SQLSTATE
HYT00instead ofHY000; -
The agent rounds the JDBC query timeout up to whole seconds, so a statement is no longer cancelled before its deadline;
-
-
UI:
-
A status chip and banner in the top bar show the open system conditions, with when each started, the next retry and the technical detail;
-
The bell opens a notification drawer with level filters, grouped repeats and Mark all read;
-
Calmer toasts: at most three, newest on top, errors stay until dismissed, info and warnings leave after 6 seconds, repeats update in place, and a mute menu replaces the snooze dropdown;
-
The entity detail shows its open issue, with View notifications and Copy error;
-
On mobile, a pipeline’s entities list shows the empty placeholder instead of a blank screen;
-
-
Agents:
-
IBM i series agent: opt-in capture suspension of stopped entities, faster cache drain, NoSQL objects written as JSON;
-
Informix agent: faster cache drain, checkpoint reset fix, NoSQL objects written as JSON;
-
MySQL agent: faster cache drain, checkpoint reset fix, NoSQL objects written as JSON;
-
MariaDB agent: faster cache drain, checkpoint reset fix, NoSQL objects written as JSON;
-
Oracle LogMiner agent: faster cache drain, checkpoint reset fix, NoSQL objects written as JSON;
-
Oracle Triggers agent: entities sharing a table, faster cache drain, CDC purge of stopped entities, NoSQL objects written as JSON;
-
Couchbase agent: faster DCP cache drain, checkpoint reset fix;
-
SAP ASE agent: CDC purge of stopped entities, log reader checkpoint reset fix, NoSQL objects written as JSON;
-
SAP HANA agent: CDC purge of stopped entities, NoSQL objects written as JSON;
-
IBM Db2 LUW triggers agent: CDC purge of stopped entities, NoSQL objects written as JSON;
-
IBM Db2 LUW CDC agent: CDC purge of stopped entities;
-
Snowflake agent: semi-structured columns, batched inserts again, NoSQL objects written as JSON;
-
Redshift agent:
SUPERcolumns and bulk file fixes, NoSQL objects written as JSON; -
PostgreSQL agent: NoSQL objects written as JSON;
-
YugabyteDB agent: NoSQL objects written as JSON;
-
CockroachDB agent: NoSQL objects written as JSON;
-
SingleStore agent: NoSQL objects written as JSON;
-
Vertica agent: NoSQL objects written as JSON;
-
MS SQL Server CDC agent: NoSQL objects written as JSON;
-
MS SQL Server Change Tracking agent: NoSQL objects written as JSON;
-
Amazon DynamoDB agent: read time metric fix;
-
MongoDB agent: read time metric fix;
-
Azure Cosmos DB agent: read time metric fix;
-
ScyllaDB agent: read time metric fix;
-
2.3.1.0
Released: October 25, 2026
Gluesync 2.3.1: write only what changed, start where you left off, and three new databases join the party
Release highlights
Dear data wranglers,
Two weeks ago 2.3.0 handed you AI on your own keys and a write path where you make the calls. 2.3.1 keeps going in the same direction: fewer wasted writes, snapshots that pick up where they stopped without skipping a row, and three new agents.
Here’s what’s new:
Write policies — only the columns that actually changed
Start where you left off — and see it before you click
Three new agents: Greenplum, Vertica and SAP ASE
Faster snapshots into SQL Server
Query Studio in your pocket
Additional improvements
-
Core Hub:
-
Resume position reported for each entity of a pipeline;
-
CDC polls again at once after a full page;
-
Total Data Transferred counts the actual payload, and a new Snapshot Data Transferred metric is reported per source and target;
-
Continuing an interrupted snapshot keeps the time of its first start;
-
Bulk snapshot loads restart from their last checkpoint when a flush fails;
-
Stopping an entity under heavy load cancels its running operations;
-
Tables created on the target give array columns their element type;
-
Entities start reliably;
-
-
MCP:
-
create_entityanddraft_entityon an existing entity keep its stored source settings (message size, fetch size, snapshot partitions, snapshot only) and change the polling interval only whenpolling_interval_msis given. Before, a redraft reset them to their defaults;
-
-
Security:
-
Deny sign-in by OIDC group: users in a denied group cannot sign in, whatever their other groups grant (
*denies everyone outside the role mappings);
-
-
UI:
-
Settings → Users & access groups user, group and access settings;
-
Settings → Support has a Remote support card;
-
A failed update explains the cause and stays reachable from the top bar;
-
Check for updates on mobile no longer stays idle;
-
Clicking an entity row opens its detail, Validate opens in a new tab, and the name tooltip shows source and target tables;
-
The entity detail shows data transferred over all its targets;
-
Group and chain Save is blocked while an optional setting is invalid;
-
AI Studio icon-button tooltips stay on screen;
-
Greenplum, Vertica and SAP ASE log reader listed in the agent catalog;
-
-
Agents:
-
Source agents: the local cache stays readable after an append that fills a cache file exactly, and a table’s position moves only when its transaction commits;
-
Greenplum agent: new target agent;
-
Vertica agent: new source agent;
-
SAP ASE agent: new log reader source, column order and text fixes in the triggers agent;
-
MS SQL Server CDC agent: faster snapshots as a target;
-
MS SQL Server Change Tracking agent: faster snapshots as a target;
-
PostgreSQL agent: BC dates, years after 9999 and
timetzfixes, bulk target fixes; -
YugabyteDB agent:
timetzand date fixes, typed array columns; -
CockroachDB agent: typed array columns;
-
Informix agent: faster CDC reads;
-
IBM i series agent: bulk flush fix;
-
Universal file store agent: CSV and FTP fixes;
-
Cassandra agent: payload-sized write chunks;
-
ScyllaDB agent: payload-sized write chunks;
-
Google Pub/Sub agent: payload-sized write chunks;
-
Azure Cosmos DB agent: payload-sized write chunks;
-
Apache Kafka agent: payload-sized write chunks;
-
Aerospike agent: payload-sized write chunks, date and time type mapping;
-
Couchbase agent: payload-sized write chunks;
-
2.3.0
2.3.0.4
Released: October 23, 2026
-
Core Hub:
-
New Remote support button (lifesaver icon) in the top bar: enter the ID of your open MOLO17 support ticket and Core Hub opens a separate Gluesync Connect tunnel through
connect.molo17.com, so MOLO17 support can reach this Core Hub for 24 hours. The ticket is checked with MOLO17 before anything is opened, and a ticket that does not exist or is not valid is reported. Revoke closes the access at any time, and it closes on its own after 24 hours. Requesting or revoking it needs permission to change the configuration; -
The field mapping reads the target tables again each time it opens, so a table created after the page loaded is listed, and a target table with no columns shows an error instead of loading forever (GSSD-1438);
-
28 Japanese translations, such as Delete, Edit entity and Exit maintenance, no longer end in a leftover
<<<<<<< HEAD;
-
-
Security:
-
Vulnerabilities from the Trivy report 2106, including CVE-2026-110879, are patched by raising Netty, Jackson, Bouncy Castle, Jetty, httpcore5, lz4-java and org.json to their fixed releases, updating the Couchbase SDK to 3.13.0 and PostgreSQL JDBC to 42.7.14, and moving the base image to Azul Java 21.0.12;
-
-
Agents:
-
Aerospike agent, see fixes and improvements:
-
TLS connections open again: the Netty transport classes the client uses to recognise its event loop group now ship with the agent, so TLS connections no longer fail with "Unexpected EventLoopGroup";
-
-
2.3.0.3
Released: October 21, 2026
-
Core Hub:
-
Leaving maintenance returns at once and reconfigures agents and restarts entities in the background, so large pipelines no longer hit the 10-minute REST timeout and stay half-configured (GSSD-1427);
-
Saving connection credentials no longer fails with a
500after 600 seconds on a busy Core Hub: the connection is saved first, then pushed to every agent, and a rejecting agent is named in the error (GSSD-1431); -
Deleting a pipeline in maintenance, also with the MCP
delete_pipelinetool, removes its replication slots, triggers and shadow tables from the database; -
A second target on a pipeline or an entity is refused on save, validation, agent assignment and configuration import;
-
A start with snapshot on an entity whose snapshot is complete warns that only CDC runs, and names Restart sync from zero and the one-shot snapshot;
-
Snapshot metrics count only snapshot pages, and a new snapshot run on a buffering target restarts its progress;
-
Metrics updates no longer scan the whole entity metrics table (metrics database schema 6, migrated at startup);
-
Secrets in the legacy format are re-encrypted in the background after startup, after a backup to
gluesync.db.pre-reencrypt.bak, so reading pipelines on upgraded installations is fast again; -
Webhook delivery logs the storage key cannot decrypt are rewritten empty instead of failing every retention cleanup;
-
Anonymous usage analytics has its own consent, on by default and separate from telemetry, in Settings → Support and through the MCP tools
get_usage_analytics_statusandset_usage_analytics;
-
-
Query Studio:
-
Cell edits, row inserts and deletes, and
?parameters work on MariaDB, MySQL, SingleStore, Oracle, Db2, Informix, Snowflake and Vertica; -
A query with a PostgreSQL cast such as
email::intno longer opens the Query Parameters prompt; -
PII unmask grants apply when the driver leaves out a column’s schema or table, and aliases or expressions over masked columns stay masked unless every column is granted;
-
A masked column can no longer leak through a cast, an expression, or a database error message, and values in database errors no longer reach the Core Hub log;
-
-
Query Forge:
-
Database errors about queries on masked columns are redacted;
-
-
Security:
-
commons-lang2.4 (CVE-2025-48924) is removed by updating Apache Calcite to 1.42.0 (GSSD-1433);
-
-
Agents:
-
New Microsoft Fabric Open Mirroring target agent: snapshots and CDC as Parquet change files in a Fabric mirrored database (GS2-606). See changelog;
-
New Supabase target agent: snapshots and CDC into Supabase Postgres with the PostgreSQL write path and TLS on by default. See changelog;
-
PostgreSQL agent, see fixes and improvements:
-
Bulk operations and batch writes handle every type of the type matrix, keep the type of
money,numeric,bit(n)and unboundedvarcharstaging columns, and write dates before 1582 exactly; -
CDC keeps
timetzoffsets, replicatesNaNand infinities (wal2json 2.6 or later), and no longer turns an update of an array key into a delete and an insert; -
CDC resumed from a saved position no longer drops changes of interleaved transactions, and the replication slot is confirmed only up to what the target has stored;
-
-
YugabyteDB agent, see fixes and improvements:
-
CDC resumed from a saved position no longer drops changes of interleaved transactions, and the replication slot is confirmed only up to what the target has stored;
-
-
Oracle LogMiner agent, see fixes and improvements:
-
Rows written after a higher-SCN commit and savepoint rollback rows with an unresolved transaction id are no longer dropped (GSSD-1245);
-
New
logminerMaxWindowScnssetting caps the span of a mining window (GSSD-1245);
-
-
ScyllaDB agent, see fixes and improvements:
-
CDC starts on tables with an empty CDC log, no longer carries the previous change’s old values, and composite-key updates and deletes work;
-
-
Db2 for IBM i agent, see fixes and improvements:
-
Multi-member files are resolved for all tables at once, so leaving maintenance on large pipelines no longer times out (GSSD-1427);
-
-
Solace PubSub+ agent, see fixes and improvements:
-
Each agent connects with its own client name, so two agents on one broker and Message VPN no longer disconnect each other;
-
-
Aerospike agent, see fixes and improvements:
-
With Use batch writes on, each record gets only its own row’s bins;
-
-
Amazon DynamoDB agent, see fixes and improvements:
-
Unprocessed batch-write items are retried instead of dropped, and stream reads ask for at most 1,000 records, so source CDC no longer fails on every poll;
-
-
-
Chronos:
-
Chronos 0.3.1, see changelog:
-
Cron schedules with both a day of the month and a day of the week run when either matches, as standard cron does, with the new
day_orsetting to require both;
-
-
-
Documentation:
-
Target pages document that bulk operations during CDC apply an update as a delete plus an insert;
-
-
UI:
-
Snapshot metrics show Snapshot Time Left;
-
The entity edit screen has Exit, Discard and exit and breadcrumbs;
-
The Gluesync Connect tunnel shows as reconnecting for up to 5 minutes after a Core Hub restart;
-
Settings → Support → Clear Logs empties Core Hub’s logs without a restart;
-
A pipeline in maintenance can be deleted from its gear menu;
-
Trackpad swipe gestures work again in desktop Chrome and Edge;
-
2.3.0.2
Released: October 19, 2026
-
Agents:
-
New Databricks target agent: snapshots and CDC into Delta Lake tables in Unity Catalog through a Databricks SQL warehouse, over HTTPS with an OAuth service principal or a personal access token. Changes are applied with key-matched Delta
MERGEstatements, bulk snapshots load from a Unity Catalog volume, and Query Studio and data comparison run on the same warehouse (GS2-607); -
New Elasticsearch target agent, with OpenSearch as a flavor of the same agent: snapshots and CDC into Elasticsearch and OpenSearch indexes through the
_bulkREST API. Missing indexes are created with a mapping generated from the entity columns, and every operation on a row reaches the same document, so a replay writes it once; -
New Redis Streams target agent: appends every snapshot row and CDC change to a Redis Stream with
XADD, standalone or cluster, with flat or JSON entries and optional stream trimming. The existing Redis agent is unchanged; -
Topic prefix on the Solace PubSub+, Google Pub/Sub, and Apache Kafka target agents (GSSD-1428): an optional agent setting placed in front of every topic name the agent builds, for destinations such as
acme/erp/<collection>/<action>. Solace joins it as topic levels with/, Pub/Sub and Kafka add it as typed (end it with.to getacme.orders). A prefix the broker would refuse is rejected when the entity is set up, before the first message. Left empty, topic names are unchanged; -
Apache Kafka agent: snapshots and CDC are written up to 190 times faster, and Use Transactions now works. See fixes and improvements;
-
Solace PubSub+ agent: in persistent mode a batch counts as written only once the broker has it, a broker rejection is retried instead of lost, and large snapshots no longer run Core Hub out of memory. See fixes and improvements;
-
MS SQL Server CDC agent: snapshots into SQL Server run 1.6 to 1.8 times faster with bulk operations, and bulk copy no longer fails on
realcolumns or cutsdatetime2values. See fixes and improvements; -
MS SQL Server Change Tracking agent: the same target improvements. See fixes and improvements;
-
PostgreSQL agent: an update that changes the primary key now reaches the target as a delete plus an insert, and
hstorecolumns can be replicated. See fixes and improvements; -
YugabyteDB agent: an update that changes the primary key now reaches the target as a delete plus an insert. See fixes and improvements;
-
-
AI Studio:
-
Spark can add the new Databricks, Elasticsearch / OpenSearch, and Redis Streams agents to a pipeline;
-
-
UI:
-
Buttons, table cells, list rows, and status labels show the compact spinner again while they load; full-page, panel, and dialog loading keep the Gluesync loader;
-
The Databricks, Elasticsearch, and OpenSearch agents show their logos, and Query Studio formats Databricks queries as Spark SQL, keeping backtick-quoted names;
-
2.3.0.1
Released: October 15, 2026
|
Upgrade note
2.3.0.1 moves |
-
Core Hub:
-
EBCDIC code pages in field functions — Byte Array to String and String to Byte Array offer the national single-byte EBCDIC code pages (
IBM037,IBM273,IBM277,IBM278,IBM280,IBM284,IBM285,IBM297,IBM500,IBM871), each with its euro variant (IBM01140toIBM01149), plusIBM1047(z/OS Latin-1). An IBM iCHAR … FOR BIT DATAcolumn (CCSID 65535) read with Translate binary off can now be turned into text without a UDF, from the Fields Editor or the MCPcreate_entity/draft_entitytools; -
Fields Editor, NoSQL targets: a discovered target type that would be incompatible with the source column is replaced by the matching target type (for example PostgreSQL
timestamp with time zonemaps to Couchbaseoffset_date_timeinstead ofstring), and a discovered field picked by hand offers every compatible type; -
PII discovery no longer flags composite column names built on a generic word, such as
project_name,company_name,file_name,mac_address,server_address,mobile_app_version, orzip_file.nameandaddresson their own, and person-qualified names such ascustomer_nameorbilling_address, are still PII. Boolean columns get no name verdict, and a stored automatic name verdict that no longer applies stops masking right away; -
Email alerts to multiple recipients (GSSD-1403) — Settings → Notifications → Emails takes up to 20 recipients, one per row, with inline validation. Alerts and the digest reach every address as a separate message, so a rejected address does not drop the others and recipients do not see each other.
GET/PUT /global-config/smtpaccept thealertEmailslist; the singlealertEmailstill works; -
Validator on chained entities — the Validator compares the tables of a chained (multi-table) entity one table at a time instead of refusing the entity. Pick the table with
tableIdon the data comparison API ortable_idon the MCPtrigger_data_comparisonandlist_data_comparison_runstools; history, reconciliation, and events are kept per table; -
The READ button of a notification opens the Notifications hub also when the Control Plane is served under a custom base path, instead of landing on Pipelines;
-
User groups for query data access — super admins can create groups of local and OIDC users in a new User groups settings tab, and bind data-access policies and templates to a group as well as to a single user. A user’s own policy on a connection replaces their groups' policies there, and a policy on a single connection can now be deleted on its own; otherwise their groups' policies combine (
OPENwhen any group isOPEN, rules and PII unmask grants unioned, deny wins). Administrators can see a user’s effective policy; -
New anonymous
GET /healthliveness endpoint for Docker, Kubernetes, and load balancers: it answers{"status":"UP"}without touching the database or the license./metrics/hw-statsadds the disk usage (total, usable, used) of the data directory volume, measured on the filesystem of the data directory rather than on the container’s image overlay; -
The support bundle’s
pipelines-config.jsonnow carries (GSSD-1407) each entity’s snapshot and performance settings (fetch and batch sizes, polling interval, partition column and count, target snapshot writing concurrency), never partition bounds or free-text SQL commands; -
REST paths accept an encoded backslash (
%5C), so a source table with a backslash in its name can be configured through the API; encoded control characters are refused; -
Security fix: a pipeline id, agent id, or UDF name in a REST path can no longer reach a file outside the pipeline’s data directory, also when written with an encoded slash or backslash (
%2F,%5C); such requests answer400; -
A browser request for a missing page under
/ui/v2answers404instead of redirecting to itself until the browser gives up;
-
-
Query Forge:
-
Query Forge identifies itself to SQL clients as Gluesync Query Forge; with the Gluesync JDBC driver 1.1.0, DBeaver shows the product and driver versions;
-
GET /query-forge/driverand the read-only MCP toolget_query_forge_driver_inforeport the latest Gluesync JDBC driver and whether it is an update for the caller; -
Much more of a query runs on the source database: filters, projections, aggregates with
GROUP BY,ORDER BY,LIMIT/OFFSET, joins,UNION ALL,INlists and the functions BI tools generate, so aCOUNT(*)on a large table now finishes. See How Query Forge runs a query; -
Joins across agents read far fewer rows: aggregates run on each agent first, a selective side sends its keys to the other database, and large sides are merged or read by key. See Aggregates over joins across agents;
-
Results stream page by page, and a query that would hold more than 1,000,000 rows of one table fails with SQLState
54000instead of exhausting Core Hub’s memory; a connection sets its own cap withmaxScanRows. See Limits; -
A long
queryTimeoutalso extends each call to the source, closing a connection cancels its queries, a server-side statement timeout stops long queries, and a burst of BI queries can no longer pile up on Core Hub. See Cancel queries and set timeouts in BI tools; -
Results are exact whichever database or plan computes them: decimals keep their declared precision and scale and compare by value,
AVGandSUMof integers returnDECIMALandBIGINT,TIMESTAMPandDATEkeep their stored value, correlated subqueries are exact around `NULL`s, and non-Latin text and emoji are handled; -
Every error carries a meaningful SQLState, and the Gluesync JDBC driver reports every failure as a
SQLException. See Troubleshooting; -
A masked column reaches the source only as a plain read, a comparison with a value of its own type, or a count. See PII masking in Query Forge;
-
Tables created, dropped, or altered on a source show on an open connection when you refresh it;
-
-
Query Studio:
-
Reading a page of a large result no longer makes the database produce the whole result for every page;
-
Cancelling a query stops that query, not whichever query started last on the same agent;
-
DATEandTIMESTAMP(without time zone) values are returned as the wall-clock value the database holds, without theZsuffix, so the grid shows them correctly in any browser time zone and no longer moves a time in the daylight-saving spring-forward hour. Columns with a time zone keep the instant form. Scripts that call the Query Studio REST execute endpoint and parse these values as instants must be updated. See Date and time values; -
A column you mark as PII or as not PII by hand (GSSD-1344) is now masked or shown that way in query results too, including
SELECT *, aliased columns, and tables written in a different case, not only in the schema tree. Marking a column as not PII needs a data-access grant that can unmask it (HTTP 403 otherwise), and the schema-tree menu offers only the action that applies. In a query over several tables, a column you marked as not PII is unmasked only for its own table, so a join no longer unmasks a column with the same name in another table;
-
-
Visualize:
-
Spark can group a date by day, week, month, quarter, or year, so "licenses by quarter" becomes one point per quarter. Its catalog search skips each database’s own system schemas, reads a physical database once even when several agents point at it, and stops after 30 seconds with what it found, offering to search longer;
-
Chart errors name the agent (for example
Agent 'HR SQL Server (SOURCE)' is not running) instead of its id, and Spark no longer grounds a chart on a pipeline in maintenance unless you pick that pipeline. A proposal bound to one shows a warning;
-
-
AI Studio:
-
AI Studio settings backup and restore: every AI setting of a Core Hub (LLM providers, AI Studio agents, models, skills and agent versions, remote MCP servers, Enterprise brain settings, platform API keys, budgets and each user’s conversation retention) exports as one bundle and imports into another Core Hub with the same ids and versions. Secrets travel only when asked, sealed with your passphrase. See Back up and restore AI settings;
-
Spark can export the AI settings and check an import with two new MCP tools,
export_ai_settingsandimport_ai_settings; secrets never pass through them; -
AI settings export with secrets checks your role before the passphrase, and after five wrong passphrases no passphrase is accepted for fifteen minutes;
-
Spark answers cut at the model’s output limit are marked as incomplete instead of looking finished. The notice is saved with the conversation, typing "continue" finishes the answer, and no SQL or Java draft is offered from a cut answer. Output budgets are larger: 8,192 tokens in the UDF and custom function editors, 4,096 in Query Studio chat and AI SQL;
-
When a brain build cannot read some agents, AI Studio names each agent and its pipeline instead of listing bare agent ids;
-
The Enterprise brain Catalog panel lists the indexed tables and its search finds them, instead of reporting "No tables indexed yet";
-
The Atlassian (Jira & Confluence) company tool signs in without editing the allowed hosts: the wizard now allow-lists Atlassian’s authorization server too;
-
-
Security:
-
Personal API Token scopes are enforced on every request (
gluesync.api,gluesync.api_read,gluesync.mcp,gluesync.mcp_read,gluesync.jdbc_gateway), new tokens need at least one scope, and tokens without scopes keep full access as Full access (legacy). See Personal API Tokens and scopes; -
Read-only scopes always run queries read-only, tokens can no longer manage tokens, a token limited to some agents reaches only those agents, and an MCP session answers only the token and user that opened it;
-
Query Studio’s read-only mode refuses data-modifying statements and functions with side effects, and runs read-only queries in a read-only transaction. See Read-only mode;
-
Support archives are downloaded and uploaded only from Core Hub’s logs directory, and names taken from requests or imported configurations can no longer point outside their directories;
-
-
Agents:
-
Aerospike agent: fixes and improvements;
-
Amazon DynamoDB agent: fixes and improvements;
-
Amazon Redshift agent: fixes and improvements;
-
Apache Kafka agent: fixes and improvements;
-
AWS S3 agent: fixes and improvements;
-
Azure Cosmos DB agent: fixes and improvements;
-
Azure Data Lake Storage Gen2 agent: fixes and improvements;
-
Cassandra agent: fixes and improvements;
-
ClickHouse agent: fixes and improvements;
-
CockroachDB agent: fixes and improvements;
-
Couchbase agent: fixes and improvements;
-
Google BigQuery agent: fixes and improvements;
-
Google Cloud Storage agent: fixes and improvements;
-
Google Pub/Sub agent: fixes and improvements;
-
GridGain agent: fixes and improvements;
-
IBM Db2 LUW CDC agent: fixes and improvements;
-
IBM Db2 LUW triggers agent: fixes and improvements;
-
IBM i series agent: fixes and improvements;
-
Informix agent: fixes and improvements;
-
MariaDB agent: fixes and improvements;
-
MongoDB agent: fixes and improvements;
-
MS SQL Server CDC agent: fixes and improvements;
-
MS SQL Server Change Tracking agent: fixes and improvements;
-
MySQL agent: fixes and improvements;
-
Oracle LogMiner agent: fixes and improvements;
-
Oracle Triggers agent: fixes and improvements;
-
Oracle XStream agent: fixes and improvements;
-
PostgreSQL agent: fixes and improvements;
-
RavenDB agent: fixes and improvements;
-
Redis agent: fixes and improvements;
-
SAP HANA agent: fixes and improvements;
-
ScyllaDB agent: fixes and improvements;
-
SingleStore agent: fixes and improvements;
-
Snowflake agent: fixes and improvements;
-
Solace PubSub+ agent: fixes and improvements;
-
Sybase ASE agent: fixes and improvements;
-
Universal file store agent: fixes and improvements;
-
Vertica agent: fixes and improvements;
-
YugabyteDB agent: fixes and improvements;
-
Oracle OpenLogReplicator agent: the agent is removed;
-
-
UI:
-
The Query Forge driver download shows the JDBC driver version and what changed in it. When a newer driver is out and you have a Query Forge token, a red badge on the Query Forge toolbar offers Download and Mark as updated. See Driver versions and updates;
-
Entity add and edit: each table in Selected entities shows a tag for every feature turned on for it (field function, UDF, filter, bulk), and clicking a tag opens the dialog where that feature is configured;
-
Fields Editor: several warnings fold into one banner with View warnings, which opens a new Warning tab, the same way several errors already open the Error tab;
-
Pipelines: entity rows flash green when new metrics arrive, and the rps chip turns green while it shows a value, so you can see at a glance what is replicating;
-
Entity detail: Field Mappings shows the column mapping with arrows, including N:1 and 1:N relations, field functions, custom field functions, and the UDF, instead of pairing columns row by row;
-
Query Studio: the schema tree column menu offers Mark as PII or Not PII according to the column’s current state and your unmask grants (GSSD-1344);
-
Validator: pipelines are sorted by name, and a pipeline in maintenance shows a badge;
-
Add to group: group names show in full and are sorted by name (GSSD-1421);
-
Fields Editor: a cell’s menu closes once its cell scrolls out of sight instead of staying over the header;
-
UDF editor: Delete UDF moves next to Test as an icon button, and the screen shows a loader until the UDF code is ready instead of an empty editor;
-
Chronos scheduler: unselected days in the weekly picker show as outline buttons, so the selected days stand out;
-
The Platform updates dialog no longer hides behind other dialogs, such as the Query Studio announcement;
-
Loading states across the Control Plane use the Gluesync loader;
-
-
Gluesync JDBC driver: see the JDBC driver changelog;
2.3.0
Released: October 13, 2026
| 2.3 is our biggest release to date, containing 100+ new functionalities across any module. Make sure to test it in your dedicated test environment before moving to production. |
Gluesync 2.3.0: bring your own brain, pick your own write rules, and let the target fill in its own blanks
Release highlights
Dear data wranglers,
Last time we taught your CDC readers to remember where they were and your Grafana dashboard to stop lying about lag. This time we went after the last place Gluesync was still deciding things on your behalf: the quiet ones. AI now runs on models you own, with your keys and your permissions — and every spot in the write path that used to guess for you is now a choice you get to make.
We’ve been busy. Here’s what’s new:
Spark & AI Studio — your models, your keys, your rules
Enterprise brain — one shared memory for every agent and every AI client
Write path — you choose the rules, the target computes the blanks
Fields Editor — draw the mapping instead of negotiating with it
MCP catalog at 125 tools
Query Studio — MongoDB in your dialect, whole rows from the grid
Data governance — PII labelled everywhere, access scoped per connection
Connectors — ClickHouse, self-enabling SQL Server CDC, and better streaming payloads
Data Validator and operations — prove it matches, alert only when it is broken
Additional improvements
-
Core Hub:
-
OIDC RP-initiated logout via discovery
end_session_endpoint(local logout first, then the IdP; register\{CoreHub origin}/ui/v2/loginon the IdP allowlist). See Logout flow; -
Custom Field Functions can compose a target primary-key column (source key columns are always present on the change, so the save is no longer refused);
-
Mapping UDFs: Core Hub rewrites every installed UDF to the new
isSnapshotsignature at startup and blocks publishing a function that clashes with the reserved parameter; the UI lists which UDFs need an update; -
Validator events (
gluesync.validation.started,completed,differences-found,failed,reconciled) can drive webhooks, email, and in-app notifications; -
Existing stored target column names are normalized to the node’s case on the next entity save;
-
-
AI Studio:
-
Super admins can disable a vaulted LLM provider without deleting its credentials (disabled providers fail closed at chat time);
-
MANAGER can publish skills and agent versions (not only SUPER_ADMIN);
-
Enterprise brain: discovery on a stored remote MCP server refreshes its tool list in place; a non-authentication
403shows the server’s own message instead of starting a sign-in; -
Enterprise brain: company tools register on the Core Hub MCP server as
company_<server>_<tool>; setGLUESYNC_MCP_DYNAMIC_COMPANY_TOOLS=falseto turn them off;
-
-
Agents:
-
Amazon Redshift agent: fixes and improvements;
-
Cassandra agent: fixes and improvements;
-
ClickHouse agent: fixes and improvements;
-
CockroachDB agent: fixes and improvements;
-
Couchbase agent: fixes and improvements;
-
Google BigQuery agent: fixes and improvements;
-
GridGain agent: fixes and improvements;
-
IBM Db2 LUW CDC agent: fixes and improvements;
-
IBM Db2 LUW triggers agent: fixes and improvements;
-
IBM i series agent: fixes and improvements;
-
Informix agent: fixes and improvements;
-
MariaDB agent: fixes and improvements;
-
MS SQL Server CDC agent: fixes and improvements;
-
MS SQL Server Change Tracking agent: fixes and improvements;
-
MySQL agent: fixes and improvements;
-
Oracle LogMiner agent: fixes and improvements;
-
Oracle Triggers agent: fixes and improvements;
-
Oracle XStream agent: fixes and improvements;
-
PostgreSQL agent: fixes and improvements;
-
SAP HANA agent: fixes and improvements;
-
ScyllaDB agent: fixes and improvements;
-
SingleStore agent: fixes and improvements;
-
Snowflake agent: fixes and improvements;
-
Sybase ASE agent: fixes and improvements;
-
Vertica agent: fixes and improvements;
-
YugabyteDB agent: fixes and improvements;
-