Gluesync JDBC driver changelog

The Gluesync JDBC driver (jdbc:gluesync://) is the client you add to DBeaver, DataGrip, a BI tool, or your own code to query Query Forge. It ships separately from Core Hub, so it has its own version.

Download the latest driver from the Query Forge setup screen in the Control Plane, or from gluesync-jdbc-latest.jar. Each release is also published as gluesync-jdbc-<version>.jar in the same folder. See Driver versions and updates for how the Control Plane tells you a new version is out.

Release notes

1.1.0

Released: October 14, 2026

The first versioned release. Earlier builds were published only as gluesync-jdbc-latest.jar and report themselves as version 1.0.

  • SQL clients show the driver as Gluesync JDBC driver with its version, for example in DBeaver’s connection test, instead of "Avatica Remote JDBC Driver, unknown version";

  • SQL clients show the server as Gluesync Query Forge with the Core Hub version. With a Core Hub older than 2.3.0.1, the version reads "unknown";

  • Each release can be downloaded by version, as gluesync-jdbc-<version>.jar. gluesync-jdbc-latest.jar is always the latest generally available release;

  • The driver’s major and minor version (Driver.getMajorVersion() / getMinorVersion(), DatabaseMetaData.getDriverMajorVersion() / getDriverMinorVersion()) follow the release version;

  • The driver waits up to 10 minutes for a response from Query Forge, or the connection’s queryTimeout plus one minute when that is longer, instead of 3 minutes. Set http_response_timeout (milliseconds) to choose another limit;

  • maxScanRows and queryTimeout given in the JDBC URL reach Query Forge as connection settings. Options meant for the client only, such as truststore_password or avatica_password, are no longer sent to Query Forge;

  • Fixed: an error while reading rows, such as reaching the Query Forge scan cap (SQLState 54000), reaches the client as a SQLException with Query Forge’s SQLState, instead of an unchecked exception that some SQL clients reported as a crash;

  • Fixed: a connection Query Forge refuses, for example because of an invalid token or a maxScanRows above the allowed maximum (SQLState 22023), fails with a SQLException;

  • Fixed: a connection failure, including a read timeout while a statement runs, fails with SQLState 08006;

  • Fixed: the driver runs on Java 11 and later; the very first build required Java 21.