v3.15.2

Summary

This release has several improvements and bug fixes.

Community edition

Improvements

• ScalarDB BIGINT datatype will now be mapped to Oracle's NUMBER(16). (#2566)

Bug fixes

• Upgraded the Netty library to fix a security issue. CVE-2025-24970 (#2552)

Enterprise edition

Enhancements

ScalarDB Cluster

• Added a configuration option (scalar.db.transaction.enabled) to enable or disable the transaction feature in ScalarDB Cluster. The default value is true.

Bug fixes

ScalarDB Cluster

• Fixed a bug related to the metadata cache behavior when using auth in the SQL interface.
• Fixed configurations for the embedding feature.
• Fixed a bug that allowed superusers to execute ABAC administrative operations for non-existing users.
• Fixed a bug a table-not-found error occurs when dropping empty ABAC system tables.

v3.14.2

Summary

This release has several improvements and bug fixes.

Community edition

Improvements

• ScalarDB BIGINT datatype will now be mapped to Oracle's NUMBER(16). (#2566)

Bug fixes

• Upgraded the Netty library to fix a security issue. CVE-2025-24970 (#2552)

Enterprise edition

Bug fixes

ScalarDB Cluster

• Upgraded grpc_health_probe to fix security issues. CVE-2024-45337 CVE-2024-45338
• Fixed a bug related to the metadata cache behavior when using auth in the SQL interface.

ScalarDB SQL

• Fix an issue causing the SQL statement parser to reject negative numeric literal for columns of type INT and BIGINT.

v3.13.3

Summary

This release has several improvements and bug fixes.

Community edition

Improvements

• ScalarDB BIGINT datatype will now be mapped to Oracle's NUMBER(16). (#2566)

Bug fixes

• Upgraded the Netty library to fix a security issue. CVE-2025-24970 (#2552)

Enterprise edition

Bug fixes

ScalarDB Cluster

• Upgraded grpc_health_probe to fix security issues. CVE-2024-45337 CVE-2024-45338
• Fixed a bug related to the metadata cache behavior when using auth in the SQL interface.

ScalarDB SQL

• Fix an issue causing the SQL statement parser to reject negative numeric literal for columns of type INT and BIGINT.

v3.12.6

Summary

This release has several improvements and bug fixes.

Community edition

Improvements

• ScalarDB BIGINT datatype will now be mapped to Oracle's NUMBER(16). (#2566)

Bug fixes

• Upgraded the Netty library to fix a security issue. CVE-2025-24970 (#2552)

Enterprise edition

Bug fixes

ScalarDB Cluster

• Upgraded grpc_health_probe to fix security issues. CVE-2024-45337 CVE-2024-45338
• Fixed a bug related to the metadata cache behavior when using auth in the SQL interface.

ScalarDB SQL

• Fix an issue causing the SQL statement parser to reject negative numeric literal for columns of type INT and BIGINT.

v3.11.6

Summary

This release has several improvements and bug fixes.

Community edition

Improvements

• ScalarDB BIGINT datatype will now be mapped to Oracle's NUMBER(16). (#2566)

Bug fixes

• Upgraded the Netty library to fix a security issue. CVE-2025-24970 (#2552)

Enterprise edition

Bug fixes

ScalarDB Cluster

• Upgraded grpc_health_probe to fix security issues. CVE-2024-45337 CVE-2024-45338
• Fixed a bug related to the metadata cache behavior when using auth in the SQL interface.

ScalarDB SQL

• Fix an issue causing the SQL statement parser to reject negative numeric literal for columns of type INT and BIGINT.

v3.15.1

Summary

This release includes numerous enhancements, improvements, and bug fixes. The 3.15.0 release has been discarded, making this the first official release for 3.15.

Community edition

Enhancements

• Introduced operation attributes, providing the capability to include additional key-value information in operations. (#2333)
• Add the new time-related data types DATE, TIME, TIMESTAMP, and TIMESTAMPTZ. (#2468 #2491)

Improvements

• ScalarDB now supports MySQL 8.4, 8.0; PostgreSQL 17, 16, 15, 14, and 13; Amazon Aurora PostgreSQL 16, 15, 14, and 13; Amazon Aurora MySQL 3, and 2. (#2302)
• Use the MariaDB Connector/J JDBC driver for any connection URL starting with jdbc:mariadb (#2391)
• Removed unnecessary loggings in the statement handlers for Cassandra and Cosmos DB. (#2469)

Bug fixes

• Added validation for primary key columns in the Cosmos DB adapter. The validation ensures that the text values of the primary key columns do not contain illegal characters (:, /, \, #, and ?). (#2292)
• Fixed the behavior of multiple mutations for the same record in a transaction in Consensus Commit. (#2340)
• Fixed the behavior when deleting a non-existing record in the Cosmos adapter. (#2341)
• Fixed bugs in GetBuilder and ScanBuilder. (#2352)

Enterprise edition

Enhancements

ScalarDB Cluster

• Added support for operation attributes introduced in #2333 to ScalarDB Cluster.
• Added the attribute-based access control feature.
• Added support for the time-related types introduced in #2468 to ScalarDB Cluster.
• Added support for the metadata API for ABAC introduced in scalar-labs/scalardb-sql#708.
• Added vector search capability to ScalarDB Cluster by integrating LangChain4j.

ScalarDB SQL

• Added support for operation attributes to DMLs. Also added support for read tags and write tags in ABAC to DMSs.
• Support the time-related types DATE, TIME, TIMESTAMP, and TIMESTAMPTZ.
• Added metadata API for ABAC.
• Added SQL statements for ABAC.

Bug fixes

ScalarDB Cluster

• Upgraded grpc_health_probe to fix security issues. CVE-2024-45337 CVE-2024-45338

ScalarDB SQL

• [Spring Data JDBC For ScalarDB] Fixed a bug existsById() API not working
• Fix an issue causing the SQL statement parser to reject negative numeric literal for columns of type INT and BIGINT.

v3.15.0 DISCARDED

This release has been discarded. Please use the 3.15.1 release.

v3.14.1

Summary

This release has several improvements and bug fixes.

Community edition

Improvements

• ScalarDB now supports MySQL 8.4 and 8.0; PostgreSQL 17, 16, 15, 14, and 13; Amazon Aurora PostgreSQL 16, 15, 14, and 13; and Amazon Aurora MySQL 3 and 2. (#2302)

Bug fixes

• Added validation for primary key columns in the Cosmos DB adapter. The validation ensures that the text values of the primary key columns do not contain illegal characters (:, /, \, #, and ?). (#2292)
• Fixed the behavior of multiple mutations for the same record in a transaction in Consensus Commit. (#2340)
• Fixed the behavior when deleting a non-existing record in the Cosmos adapter. (#2341)
• Fixed bugs in GetBuilder and ScanBuilder. (#2352)

Enterprise edition

Bug fixes

ScalarDB SQL

• [Spring Data JDBC For ScalarDB] Fixed a bug regarding the existsById() API not working.

v3.13.2

Summary

This release has several improvements and bug fixes.

Community edition

Improvements

• ScalarDB now supports MySQL 8.4 and 8.0; PostgreSQL 17, 16, 15, 14, and 13; Amazon Aurora PostgreSQL 16, 15, 14, and 13; and Amazon Aurora MySQL 3 and 2. (#2302)

Bug fixes

• Added validation for primary key columns in the Cosmos DB adapter. The validation ensures that the text values of the primary key columns do not contain illegal characters (:, /, \, #, and ?). (#2292)
• Fixed the behavior of multiple mutations for the same record in a transaction in Consensus Commit. (#2340)
• Fixed the behavior when deleting a non-existing record in the Cosmos adapter. (#2341)
• Fixed bugs in GetBuilder and ScanBuilder. (#2352)

Enterprise edition

Bug fixes

ScalarDB SQL

• [Spring Data JDBC For ScalarDB] Fixed a bug regarding the existsById() API not working.

v3.12.5

Summary

This release has several improvements and bug fixes.

Community edition

Improvements

• ScalarDB now supports MySQL 8.4 and 8.0; PostgreSQL 17, 16, 15, 14, and 13; Amazon Aurora PostgreSQL 16, 15, 14, and 13; and Amazon Aurora MySQL 3 and 2. (#2302)

Bug fixes

• Added validation for primary key columns in the Cosmos DB adapter. The validation ensures that the text values of the primary key columns do not contain illegal characters (:, /, \, #, and ?). (#2292)
• Fixed the behavior when deleting a non-existing record in the Cosmos adapter. (#2341)
• Fixed bugs in GetBuilder and ScanBuilder. (#2352)

Enterprise edition

Bug fixes

ScalarDB SQL

• [Spring Data JDBC For ScalarDB] Fixed a bug regarding the existsById() API not working.