Skip to main content
Version: 3.19

ScalarDB 3.19 Release Notes

This page includes a list of release notes for ScalarDB 3.19.

v3.19.3​

Release date: November 11, 2026

Summary​

This release improves transaction metadata decoupling by supporting READ COMMITTED isolation on more databases and fixing issues with imported tables. It also addresses several data correctness issues, particularly those involving BLOB values in ScalarDB Cluster and ScalarDB SQL, and improves SQL parsing and validation. Additionally, this release enhances schema management, fixes various storage adapter issues, and strengthens security through dependency upgrades and vulnerability fixes.

Community edition​

Improvements​

  • Lowered the isolation level that ScalarDB requires for consistent virtual table reads to READ COMMITTED for Oracle, PostgreSQL, AlloyDB, YugabyteDB, MySQL, MariaDB, and TiDB. With this change, you can use transaction metadata decoupling on these databases at READ COMMITTED, which is the default isolation level in Oracle and PostgreSQL, and you no longer need SERIALIZABLE on Oracle. (#4148)
  • Made the schema file optional for --repair-all in Schema Loader when --coordinator or --replication-tables is specified, so that you can repair the coordinator tables and replication tables without re-applying table schemas. In addition, running --repair-all without a schema file, --coordinator, or --replication-tables now does nothing and exits successfully instead of failing with an error. (#4183)

Bug fixes​

  • Fixed an issue where a conditional put (PutIfExists or PutIf) that specifies only primary key values failed with an SQL error in JDBC databases. In Spanner, such a put still fails for tables that have only primary key columns. (#4129)
  • Fixed issues with tables imported with transaction metadata decoupling in JDBC databases. A record that no transaction had written since the import could no longer be updated or deleted after a transaction that wrote it was rolled back. Also, a transaction could recreate a record that another transaction deleted after the first transaction read it. In Spanner, the latter still occurs for tables that have only primary key columns. Records that already can't be updated or deleted because of this issue stay that way after you upgrade. To recover them, after upgrading all your applications, delete the records whose tx_id column is NULL from the <table_name>_tx_metadata table of the imported table. For example: DELETE FROM <namespace>.<table_name>_tx_metadata WHERE tx_id IS NULL. (#4131)
  • Fixed an issue where deleting a record that no transaction had written since the import failed with an IllegalArgumentException when one-phase commit was enabled, in tables imported with transaction metadata decoupling in JDBC databases. (#4133)
  • Fixed CVE-2026-91403 and CVE-2026-114820 (eMudhra CA compromise) in the ScalarDB Schema Loader and ScalarDB Data Loader CLI container images by updating the base image to Eclipse Temurin 21.0.13_9, which no longer trusts the compromised emSign root CAs. (#4143)
  • Upgraded the Guava library to fix a security issue: CVE-2026-102554 (#4144)
  • Upgraded Bouncy Castle (bcprov-jdk18on) to 1.86 to fix CVE-2026-8763 and CVE-2025-14813. ScalarDB now declares it directly and excludes it from the libraries that bring it in, so applications that use ScalarDB as a library also get the fixed version, unless they manage the Bouncy Castle version themselves. (#4145)
  • Applications that use ScalarDB as a library now get the fixed Netty and Jackson versions, unless they manage those versions themselves. Previously, fixes for vulnerabilities in these libraries (for example, CVE-2026-75595 in Netty and CVE-2026-89407, CVE-2026-89425, CVE-2026-68497, CVE-2026-91776, and CVE-2026-91777 in Jackson) applied only to ScalarDB's own builds and container images. As a result, Jackson in those applications is upgraded to 2.22. Depending on the ScalarDB version, applications built with Maven previously got much older versions, such as jackson-databind 2.7 and Netty 4.1.94. This release also fixes CVE-2026-73508 in Netty, which affected the Schema Loader and Data Loader CLI images as well as those applications. (#4146)
  • Fixed an issue in the Object Storage adapter with Amazon S3 where truncating or dropping multiple tables concurrently could hang indefinitely. (#4149)
  • Fixed an issue where importing a table from Oracle, MySQL, MariaDB, or TiDB registered the primary key columns in the alphabetical order of the column names instead of the order of the table's primary key. For tables imported after this fix, specify keys, including --partition-key for Data Loader exports, in the order of the table's primary key. Tables imported before this fix keep their existing order. (#4175)
  • Upgraded Micrometer (micrometer-core, micrometer-observation, and micrometer-commons) to 1.15.12 to fix CVE-2026-40983 and CVE-2026-40984. ScalarDB now declares them directly and excludes them from the libraries that bring them in, so applications that use ScalarDB as a library also get the fixed version, unless they manage the Micrometer version themselves. (#4192)

Enterprise edition​

Bug fixes​

ScalarDB Cluster​
  • Fixed an issue where the embedding client threw AssertionError instead of UnsupportedOperationException for an unsupported filter type, such as ContainsString.
  • Fixed CVE-2026-91403 and CVE-2026-114820 (eMudhra CA compromise) in all ScalarDB Cluster container images by updating the base images to Eclipse Temurin 21.0.13_9 and, for the UBI-based node image, java-21-openjdk 21.0.13.0.9, which no longer trust the compromised emSign root CAs.
  • Upgraded the grpc_health_probe binary to fix a security issue: CVE-2026-116587
  • Upgraded the Guava library to fix a security issue: CVE-2026-102554
  • Fixed a bug where the ScalarDB Cluster client read a BLOB value bound as a ByteBuffer to the end of the buffer each time it sent the value, so the value was sent as an empty BLOB from the second time on, such as when a statement was executed again or retried, when the same buffer was bound to more than one bind marker, or when statements in a batch shared the same value. As a result, an empty BLOB could be written, or BLOB columns could be compared with an empty BLOB, without any error. The client now copies the bytes without changing the buffer's position. This fix does not repair data that was already affected.
  • Fixed a bug where, with write buffering enabled, the ScalarDB Cluster client sent buffered INSERT and UPSERT statements with the values they had when the buffered statements were sent, instead of the values they had when they were executed. If an application reused a BoundStatement, or a byte array or ByteBuffer for a BLOB value, after executing a statement, every buffered statement that used it was sent with the last values, so rows could be written with wrong values without any error. The client now copies the values of a statement when it buffers the statement. This fix does not repair data that was already affected.
  • Upgraded Bouncy Castle (bcprov-jdk18on, bcpkix-jdk18on, and bcutil-jdk18on) to 1.86 in the Java client SDK and the embedding Java client SDK to fix CVE-2025-14813, CVE-2026-0636, CVE-2026-5588, CVE-2026-5598, CVE-2026-8763, and CVE-2026-13506. Applications that use these SDKs now get the fixed version, unless they manage the Bouncy Castle version themselves. Previously, the fixed version applied only to ScalarDB Cluster's own builds and container images other than the BYOL ones, which loaded Bouncy Castle 1.70 classes that a dependency brought in. The BYOL container images now use the fixed version, too.
  • Applications that use the Java client SDK or the embedding Java client SDK and build with Maven now get the same version for all Jackson artifacts. Previously, some of them, such as jackson-dataformat-cbor, could be at older versions that other dependencies of the SDKs request. The embedding Java client SDK no longer exposes Jackson as a compile-time dependency. If your application uses Jackson directly and relied on the SDK to provide it, declare Jackson in your application's build.
  • With write buffering enabled in the ScalarDB Cluster client, an INSERT or UPSERT statement that ends inside an unterminated string literal is now rejected when it is executed, instead of when it is sent later together with another statement or at commit.
ScalarDB GraphQL​
ScalarDB SQL​
  • Upgraded the Guava library to fix a security issue: CVE-2026-102554
  • Fixed Value.hashCode() for BLOB values created from byte[] so that it is consistent with equals(). This inconsistency could cause a SELECT, UPDATE, or DELETE statement that repeats the same BLOB equality condition on a primary-key or indexed column in every OR group to be planned with a less efficient scan, or as a cross-partition scan that fails unless cross-partition scan filtering is enabled.
  • Fixed two bugs that could silently write or compare wrong BLOB values. In direct mode, a BLOB value bound as a ByteBuffer through BoundStatement.setBlob(), Value.ofBlob(), Value.of(), or the JDBC setObject() method was read to the end of the buffer each time it was used, so an UPDATE statement that updated multiple rows, or a statement executed again, wrote an empty BLOB or compared BLOB columns with an empty BLOB. In the JDBC driver, setBytes() and setObject() kept a reference to the application's array or buffer, so reusing one array or buffer for each row of a batch wrote the last contents to every row. ScalarDB SQL now copies these values instead of reading the application's buffer or array when it uses them. This fix does not repair data that was already affected.
  • Fixed a bug where SQL that started with a semicolon, ended with two or more semicolons, or had no space between a keyword and the next symbol or string literal, such as SELECT*FROM tbl or WITH'key'='value', was not read correctly. In ScalarDB Cluster, the authentication attributes in the WITH clause of such a DML statement were ignored, so the statement was executed with the credentials in the client configuration instead. In manual-commit mode, the JDBC driver committed such a DML statement immediately, so it could not be rolled back. Command statements with semicolons before or after them, such as COMMIT;;, are now accepted, and SQL that ends inside an unterminated string literal, such as BEGIN WITH 'key'='value'', which was accepted with a different value, is now rejected. An object name without quotes in a command statement, such as the namespace name in USE, is now accepted only if it starts with an ASCII letter and contains only ASCII letters, digits, underscores, and dollar signs, as in the SQL grammar, so quote any other name.
  • Fixed a bug where the SQL parser misread some SQL. It dropped characters that it could not read, so INSERT INTO ns.té was executed on the table ns.t, and names quoted with backticks or square brackets were accepted. It also read a number followed by a word without a space, such as 5AND, as a number and a word, and ignored a block comment that was not terminated together with the rest of the statement. In ScalarDB Cluster, such SQL could make a statement outside a transaction run with the credentials in the client configuration instead of those in its WITH clause. Such SQL is now rejected with a syntax error, and -- now starts a line comment whatever follows it, as in the SQL standard. The comment /*!*/ no longer makes the parser skip the SQL up to the next */, which could make a DELETE statement delete all the rows.
  • Fixed an issue where a HAVING clause in a SELECT statement with neither a GROUP BY clause nor an aggregate function was silently ignored, so the statement returned every row that matched the WHERE clause. As in the SQL standard, a HAVING clause alone makes all the rows one group, so such a statement is now rejected with the same error as other statements that select a column that is neither in the GROUP BY clause nor in an aggregate function. A statement that returned rows before can therefore fail now; to filter rows, move the condition to the WHERE clause. Statements with a GROUP BY clause or an aggregate function are not affected. The error message for such a column now shows the column as written instead of internal details.

v3.19.2​

Release date: October 30, 2026

Summary​

This release adds support for SQL Server 2025 and drops support for SQL Server 2017. It also improves transaction reliability and error handling in Consensus Commit, enhances the Global Transaction API, optimizes table metadata operations, and improves the correctness and reliability of storage adapter operations. Additionally, this release strengthens security through authentication and authorization fixes, dependency upgrades, and vulnerability mitigations, while addressing resource management issues and data comparison and aggregation issues in ScalarDB SQL.

Community edition​

Improvements​

  • Fixed an issue where a conflict error, such as a lock wait timeout or a serialization failure, in a single put or delete operation on JDBC databases was not classified as retriable. As a result, Consensus Commit can now report such a conflict during commit as CommitConflictException instead of CommitException or UnknownTransactionStatusException. (#3852)
  • Fixed the Consensus Commit record recovery to retry conflict errors reported by the underlying storage, and to report a conflict that persists as a conflict so that the transaction can be retried. (#3853)
  • Improved the performance of checking whether a table exists. tableExists() now reads only the metadata of the specified table instead of listing the tables in the namespace, so its cost no longer grows with the number of tables. As a result, on DynamoDB, a table that has no ScalarDB metadata is no longer reported as existing. Also fixed an issue in which getTableMetadata() for DynamoDB and Cosmos DB threw an exception instead of returning null when the ScalarDB metadata table or container did not exist. On these storages, a "table not found" error can therefore now also mean that the metadata table or container itself does not exist. If such a table is visible in the AWS console or the Azure portal, verify that scalar.db.system_namespace_name (and, on DynamoDB, the namespace prefix) match across all configurations before running repairTable(). (#3947)
  • Added support for SQL Server 2025 and dropped support for SQL Server 2017. (#3998)
  • Changed table import to reject column types that can't follow the TEXT collation order: SQL Server nchar, nvarchar, text, and ntext; Oracle NCHAR and NVARCHAR2; and Db2 GRAPHIC, VARGRAPHIC, and DBCLOB. (#4051)
  • Added BranchTransaction.getGlobalTransactionId(), which returns the ID of the global transaction that a branch belongs to. BranchTransaction.getId() now represents the ID of the branch itself, so use getGlobalTransactionId() when you need the ID of the global transaction. getId() may return the same ID as getGlobalTransactionId(), so do not use it to tell the branches of a global transaction apart. (#4059)
  • Upgraded the SQL Server JDBC driver to 13.6.0 and fixed TIMESTAMPTZ values dated before October 15, 1582, being stored up to 10 days off in SQL Server. TIMESTAMPTZ values dated before October 15, 1582, that were stored in SQL Server by a previous ScalarDB version are read back up to 10 days earlier than the value that was written. If you have such data, consider migrating it to remove the offset. (#3971)
  • Improved the S3 and Cloud Storage adapters to retry deleting objects that failed on transient errors when truncating or dropping tables. (#4077)
  • Mitigate CVE-2026-91403 and CVE-2026-114820 (eMudhra CA compromise) by removing the affected emSign root CAs from the cacerts of all container images, and update the base image of the ScalarDB Schema Loader and ScalarDB Data Loader CLI container images from Java 8 (Eclipse Temurin 8) to Java 21 (Eclipse Temurin 21). The images set no JVM options by default, so this affects only users who pass Java 8-specific JVM options (for example, -XX:+PrintGCDateStamps through JAVA_TOOL_OPTIONS), which now make the JVM fail to start. (#4112)

Bug fixes​

  • Fixed the get operation in the Cloud Storage adapter to handle concurrent writes. (#3851)
  • Fixed an issue where rolling back a Consensus Commit transaction with an open scanner, including the automatic rollback of an expired or evicted transaction, could fail with an IllegalArgumentException and leave the remaining scanners open and the group commit slot unreleased. (#3867)
  • Fixed the Cassandra adapter so that an update applied by a conditional write is no longer silently discarded when it runs in the same millisecond as a preceding non-conditional write to the same record. The adapter now takes write timestamps from the server and sends every request for a partition to the same replica. (#3890)
  • Fixed an issue where Consensus Commit accepted invalid conditions on conditional mutations instead of rejecting them. (#3871)
  • Fixed an issue in DynamoDB where a single conditional write that the AWS SDK retried could be reported as not applied, even though the write had been applied. Such a write is now reported as having an unknown outcome. Also fixed an issue where some failures in DynamoDB operations were thrown as unchecked AWS SDK exceptions instead of ExecutionException. (#3922)
  • Fixed an issue where committing a transaction could report a conflict and roll back its already-committed records when its Coordinator state write was retried and finishTransaction was called for the transaction concurrently. The commit now reports an unknown transaction status instead. (#3923)
  • Fixed an issue where a scan condition with the !=, <, or <= operator was satisfied by a NULL column value in Cassandra, Cosmos DB, DynamoDB, and Object Storage. Also fixed an issue where a != condition was satisfied by a NULL column value in PutIf or DeleteIf in Cassandra, DynamoDB, and Consensus Commit, and in UpdateIf in Consensus Commit. (#3930)
  • Fixed an issue where repairTable() on DynamoDB did not enable auto-scaling for existing global secondary indexes, for example after createTable() or createIndex() failed before enabling auto-scaling (such as when Application Auto Scaling permissions were missing). repairTable() now also keeps the existing auto-scaling range of a table instead of resetting it to the given or default request unit, so running repair without --ru no longer lowers the capacity of existing tables, including the Coordinator table. To change the auto-scaling range of an existing table, use the AWS console or CLI. If createTable() or createIndex() with auto-scaling enabled failed before, run repairTable() again after upgrading, with the schema that includes the index and the same request unit as at creation. If repairTable() (or Schema Loader with --repair-all) was run before without --ru or with a smaller request unit, check the auto-scaling range of existing tables, including the Coordinator table, and restore it with the AWS console or CLI, because repairTable() no longer changes the range of existing tables. (#3949)
  • Fixed an issue in the Object Storage adapter with Amazon S3 where a conditional write that the AWS SDK retried could be reported as a conflict, even though the write had been applied. Such a write is now reported as having an unknown outcome. (#3958)
  • Fixed an issue in the Object Storage adapter with Azure Blob Storage where a conditional write that the Azure SDK retried could be reported as a conflict, even though the write had been applied. Such a write is now reported as having an unknown outcome. (#3964)
  • Fixed an issue in the Object Storage adapter with Google Cloud Storage where a deletion that the Cloud Storage client retried could be reported as a conflict, even though the deletion had been applied. Such a deletion is now sent only once, and a failure of it other than an unsatisfied condition is reported as having an unknown outcome. (#3965)
  • Fixed an issue where a scanner opened outside a transaction was never closed if a client abandoned it while active transaction management kept it across requests. Such a scanner kept its transaction and storage resources, for example, a database connection and an open database transaction. Now, such a scanner is closed when it has not been used for the active transaction expiration time, or when more such scanners than the maximum number of active transactions are open. (#3992)
  • Upgraded the Netty and Jackson libraries to fix security issues: CVE-2026-75595, CVE-2026-89407, CVE-2026-89425, CVE-2026-68497, CVE-2026-91776, and CVE-2026-91777 (#3996)
  • Fixed an issue in the Object Storage adapter with Amazon S3 and Google Cloud Storage where truncating or dropping a table could succeed while leaving some of the table's objects undeleted. Such a failure is now reported as an error. (#4043)
  • Fixed an issue where a Put operation on a Spanner table named excluded failed. (#4044)
  • Fixed an issue where the scalar.db.s3.multipart_upload_max_concurrency option limited the number of concurrent requests of all S3 operations, not only multipart uploads, in the S3 adapter. (#4061)

Enterprise edition​

Improvements​

ScalarDB Cluster​
  • Fixed OIDC JWT validation so that an exhausted JWKS retrieval rate limit is reported as an authentication failure instead of an internal error.
  • Fixed the Global Transaction API so that the auth attributes passed to GlobalTransactionManager.begin choose the credential for the begin and the initiator's commit and rollback, and are no longer forwarded to the cluster as transaction attributes.
  • Fixed the Transaction Coordinator backing of the Global Transaction API so that branches of the same transaction that are open at the same time in one GlobalTransactionManager each run as their own credential. Previously, such a branch could run as another branch's credential or as the default credential.

Bug fixes​

ScalarDB Cluster​
  • Fixed an issue where a user whose authentication methods did not include USERPASS could log in with username/password authentication. If such a user needs username/password authentication, add USERPASS to the user's authentication methods and, unless passwordless login is intended, set a password. The fix takes full effect after all nodes in the cluster have been upgraded.
  • Fixed an issue where, with authentication enabled, a client could keep reading from an open scanner after its auth token had expired or been revoked, or after its READ privilege had been revoked. Fetching from a scanner now re-checks the READ privilege. For OIDC clients, a JWT that expires during a scan now causes an authentication error at the next fetch, as with get and scan; a client that supplies the JWT through OidcJwtAccessTokenHolder can set a fresh JWT and continue the scan.
  • Fixed an issue where batch Get and Scan operations on tables with encrypted columns failed with IllegalStateException when associated_data_required was enabled and their projections did not include all primary key columns.
  • Upgraded the Jackson, Netty, and Bouncy Castle libraries to fix security issues: CVE-2026-8763, CVE-2026-13506, CVE-2026-68497, CVE-2026-75595, CVE-2026-89407, CVE-2026-89425, CVE-2026-91776, and CVE-2026-91777
  • Upgraded the grpc_health_probe binary to fix security issues: CVE-2026-56851, CVE-2026-78667, CVE-2026-78669, CVE-2026-84304, CVE-2026-84445, and CVE-2026-97031
  • Fixed an issue where closing a ScalarDB Cluster client in the direct-kubernetes client mode left behind a thread and a connection to the Kubernetes API server. An application that repeatedly created and closed clients, including through the ScalarDB SQL JDBC driver, could eventually fail to create new threads.
  • Mitigate CVE-2026-91403 and CVE-2026-114820 (eMudhra CA compromise) by removing the affected emSign root CAs from the cacerts of all container images
ScalarDB SQL​
  • Fixed BLOB comparisons that ScalarDB SQL evaluates itself, in ORDER BY and in range conditions in HAVING and in WHERE after a join, treating bytes from 0x80 up as smaller than 0x00 to 0x7F.
  • Fixed MIN and MAX on FLOAT and DOUBLE columns returning a result that depended on row order when the values included NaN, or both 0.0 and -0.0.

v3.19.1​

Release date: September 2, 2026

Summary​

This release updates the Global Transaction API to require branches to explicitly declare their outcome, adds support for the AWS Advanced JDBC Wrapper for fast Aurora failover, improves Cosmos DB error handling and ScalarDB Cluster's attribute-based access control metadata cache refresh, deprecates the join() and resume() transaction APIs, adds retry handling for conflict errors during schema operations, and upgrades grpc_health_probe to address security vulnerabilities.

Community edition​

Improvements​

  • Replaced BranchTransaction.end() with BranchTransaction.end(BranchTransaction.Status), which requires a branch of a global transaction to declare the outcome of its work. Replace existing end() calls with end(BranchTransaction.Status.SUCCESS), and call end(BranchTransaction.Status.FAILURE) on failure paths. (#3806)
  • Added support for the AWS Advanced JDBC Wrapper, which enables fast Aurora failover for Aurora PostgreSQL and Aurora MySQL. Configuring HikariCP with an exception override is now rejected at startup, since it would cause a transaction with an unknown outcome to be reported as a definite failure. (#3805)
  • Fixed an issue where the error message for a Cosmos DB error was excessively large because it included the Cosmos DB diagnostics, which could cause the error information to be lost. (#3816)
  • Deprecated DistributedTransactionManager.join() and DistributedTransactionManager.resume(), along with their implementations, for removal in 3.20.0. (#3817)

Bug fixes​

  • Fixed an issue where schema operations could fail with a conflict error, such as ORA-08177 on Oracle when using the SERIALIZABLE isolation level. Conflict errors are now retried. (#3820)

Enterprise edition​

Improvements​

ScalarDB Cluster​
  • Reduced the number of queries issued when the attribute-based access control metadata caches are refreshed, which removes a latency spike on the first request after each refresh.
  • Adopted the ScalarDB Core change that replaced BranchTransaction.end() with BranchTransaction.end(BranchTransaction.Status), which requires a branch of a global transaction to declare the outcome of its work. Replace existing end() calls with end(BranchTransaction.Status.SUCCESS), and call end(BranchTransaction.Status.FAILURE) on failure paths.

Bug fixes​

ScalarDB Cluster​

v3.19.0​

Release date: August 2, 2026

Summary​

This release adds Consensus Commit recovery capabilities, including write-set logging, transaction finishing, and single-record recovery APIs, and improves recovery correctness when Coordinator state records are cleaned up. It also adds attribute-based authentication, OpenTelemetry support, the Transaction Coordinator node for Separated Cluster deployments, and Global Transaction API support in the Cluster client SDK. In addition, this release improves repairTable, active transaction management, Cluster upgrade and authentication behavior, and SQL SELECT execution, while fixing several Consensus Commit, Cluster rollback/pause, and SQL statement cache issues.

Community edition​

Enhancements​

  • Added an opt-in scalar.db.consensus_commit.coordinator.write_set_logging.enabled configuration that, when enabled, adds a tx_write_set column to the Coordinator table and populates it on commit/abort. This lays the groundwork for proactive transaction recovery. Existing Coordinator tables can be migrated by enabling the config and running Admin.repairCoordinatorTables(). (#3570 #3593)
  • Added the DistributedTransactionManager#finishTransaction(String) API, which completes per-record post-commit recovery for a committed transaction and removes its Coordinator state row. It returns true when the transaction was finished (or was already finished) and false when the transaction is not applicable because it carries no write set (for example, a transaction terminated via rollback() / abort() rather than commit()); a TransactionException is thrown when finishing fails. Note that this is a low-level operational API specific to the Consensus Commit transaction manager. Most applications should not call it directly; it is intended for advanced use cases. Callers are expected to understand the underlying transaction lifecycle and the implications of invoking this method directly. (#3567)
  • Added the DistributedTransactionManager#recoverRecord API for recovering a single record left in an uncommitted state by a crashed transaction. Note that this is a low-level operational API specific to the Consensus Commit transaction manager. Most applications should not call it directly; it is intended for advanced use cases. Callers are expected to understand the underlying transaction lifecycle and the implications of invoking this method directly. (#3617)

Improvements​

  • Improved repairTable to skip rewriting a table's metadata when it is already up to date (and, for Cosmos DB, to skip updating the container indexing policy when it already matches), avoiding unnecessary writes. (#3613)
  • Fixed the Consensus Commit recovery and read paths to stay correct when Coordinator state records are removed by cleanup (for example, by finishTransaction), preventing stale reads, spurious aborts, and a crash during group-commit lazy recovery. (#3650)
  • Added a configurable limit on the number of active transactions tracked by active transaction management (scalar.db.active_transaction_management.max_active_transactions, default 10000), backed by a Caffeine cache with Window-TinyLFU eviction, and refreshed the idle timer on every transaction operation so long-running transactions are not reaped while still in use. (#3673)

Bug fixes​

  • Accepts connection string starting with jdbc:spanner to connect to Spanner (emulator, omni, and cloud instance) in addition to the already supported jdbc:cloudspanner pattern. (#3559)
  • Fixed an issue in Consensus Commit where a Get operation using a secondary index could fail with an IllegalArgumentException when another record with the same indexed value was concurrently being deleted and inserted. (#3607)
  • Fixed an issue in Consensus Commit where a read-only transaction could fail when coordinator write omission on read-only was disabled and coordinator group commit was enabled. (#3614)
  • Fixed a bug where aborting an in-flight, group-committed transaction by ID via DistributedTransactionManager.rollback(String) / abort(String) could be lost when the Coordinator group commit feature was enabled. (#3619)
  • Fixed an issue in the Consensus Commit transaction manager where a read could return a stale (pre-commit) value for a record whose writing transaction committed concurrently during lazy recovery. (#3621)

Enterprise edition​

Enhancements​

ScalarDB Cluster​
  • Added attribute-based authentication.
  • Added OpenTelemetry support.
  • Added the Transaction Coordinator node for the new Separated Cluster deployment pattern, which drives two-phase commit across ScalarDB Clusters on behalf of applications using the one-phase transaction interface.
ScalarDB SQL​
  • Added @AutoConfigureBefore to ScalarDbJdbcConfiguration to explicitly declare auto-configuration ordering relative to Spring Boot's auto-configs.

Improvements​

ScalarDB Cluster​
  • ScalarDB Cluster now repairs its authentication and ABAC system metadata tables at node startup to create the companion before-image secondary indexes required after upgrading, so deployments upgraded from an earlier version gain them automatically without a manual repairTable().
  • Fixed an issue where a cluster node failed to start when TLS was disabled but a CA root certificate path was still configured.
  • Added support for the Global Transaction API on the ScalarDB Cluster client SDK. Applications can now use GlobalTransactionManager to run a single transaction that spans multiple processes, such as microservice transactions, where the Transaction Coordinator drives two-phase commit on their behalf. The same application code also works for transactions within a single ScalarDB Cluster, with only configuration selecting which.
  • Added a configurable expiration margin to the userpass auth-token cache so the ScalarDB Cluster client re-authenticates shortly before a cached token expires, reducing spurious authentication errors near token expiration.
  • Added a fixed label to the Kubernetes Secrets that store data encryption keys for self encryption so that operators can select them with a label selector.
ScalarDB SQL​
  • Enabled the read-only optimization for one-shot SELECT statements and SELECT-only batches.

Bug fixes​

ScalarDB Cluster​
  • Fixed a bug where a rollback that exceeded the cluster's request-forwarding hop limit was silently reported as successful instead of surfacing the failure, which could leave records prepared until lazy recovery.
  • ABORTED is new on the pause RPC. Every pause failure was previously FAILED_PRECONDITION. A failure caused by losing a race with another admin request is now ABORTED, which means the pause can simply be retried. Every pause failure also carries a google.rpc.ErrorInfo detail in the status trailers, with domain set to com.scalar.db.cluster.admin and reason set to the outcome, so a caller can tell the outcomes apart without matching on the status code or the description text. In particular, a caller that unpauses to recover from a failed pause must skip that unpause when the reason is TIMED_OUT_STILL_PAUSED, because the server is still paused by an earlier request.
  • Upgraded the Bouncy Castle library and the grpc_health_probe binary to fix security issues: CVE-2025-14813, CVE-2026-5598, CVE-2026-25681, CVE-2026-27136, CVE-2026-27145, CVE-2026-33811, CVE-2026-33814, CVE-2026-39820, CVE-2026-39821, CVE-2026-39822, CVE-2026-39836, CVE-2026-42499, and CVE-2026-42504
ScalarDB SQL​
  • Fixed a statement cache regression where non-parameterized DML statements occupied cache slots intended for parameterized SQL. Cache eligibility is now correctly gated on the presence of bind markers in the parsed SQL.

Enterprise Options​

ScalarDB Analytics​

Backward-incompatible changes
  • Redesigned user / internal-backend / role / permission CLI commands: user register is replaced by user create + user link and user unregister by user delete + user unlink (+ internal-backend create), --username is split into --user / --backend-user, passwords are accepted only via --password / --password-stdin, and data-source delete is renamed to data-source unregister.
Enhancements​
  • Unified error code system (DB-ANALYTICS-NNNNN): server-side and SDK errors are reported as a single AnalyticsException carrying a machine-readable error code and structured metadata, propagated over gRPC as structured AnalyticsError details.
  • Filter push down, column pruning, and limit push down for the ScalarDB Spark data source, reducing data transfer for selective queries.
  • Configure authentication credentials via environment variables (SCALAR_DB_ANALYTICS_CLIENT_AUTH_USERNAME / SCALAR_DB_ANALYTICS_CLIENT_AUTH_PASSWORD) in the Spark connector.
Improvements​
  • Display clean error messages instead of raw stack traces for catalog errors in the spark-sql CLI.
  • Removed the internal tenantId field from Catalog JSON output in CLI commands.
  • Upgraded Spring Boot from 3.5.x to 4.0.4.
Bug fixes​
  • Fixed a NullPointerException in the metering server when reporting an execution that contains no jobs, or a job that contains no stages.