Skip to main content
Version: 3.13
Features and pricing

ScalarDB 3.13 Release Notes

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

v3.13.3​

Release date: March 24, 2025

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​

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.2​

Release date: January 23, 2025

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.1​

Release date: October 13, 2024

Summary​

This release includes several bug fixes, and vulnerability fixes.

Community edition​

Enhancements​

  • Added support for MariaDB 11.4 and Oracle 19. (#2061)

Bug fixes​

  • Fixed a bug where NullPointerException when a table specified in a Get/Scan object is not found in Consensus Commit. (#2083)
  • Fixed a corner case issue that causes inconsistent Coordinator states when lazy recovery happens before group commit (#2135)
  • Upgraded the mysql driver to fix security issues. CVE-2023-22102 (#2238)
  • Upgraded the gRPC library, the Protocol Buffers library, grpc_health_probe, and scalar-admin to fix security issues. CVE-2024-7254, CVE-2024-25638, and CVE-2024-34156 (#2277)

Enterprise edition​

Enhancements​

ScalarDB Cluster​
  • Support the group commit feature for Coordinator table in ScalarDB cluster

Improvements​

ScalarDB GraphQL​
  • With this update, if scalar.db.graphql.namespaces is not specified, GraphQL server generates a GraphQL schema for all tables in all ScalarDB-managed namespaces.

Bug fixes​

ScalarDB Cluster​
  • Fix a bug where NullPointerException occurs when catching an exception without message.
  • Upgraded grpc_health_probe to fix a security issue. CVE-2024-34156
  • Upgraded scalar-admin to fix a security issue. CVE-2024-25638
  • Upgraded the Protobuf Java library to fix a security issue. CVE-2024-7254

v3.13.0​

Release date: July 8, 2024

Summary​

This release includes a lot of enhancements, improvements, bug fixes, and vulnerability fixes.

Community edition​

Enhancements​

  • Added dynamic arbitrary filtering for non-JDBC databases. (#1682)
  • Added the Insert, Upsert, and Update operations to the transactional API. (#1697)
  • Added YugabyteDB adapter as one of JDBC storages (#1710)
  • Added Group Commit feature for Coordinator Table (#1728)
  • Allowed directly executing CRUD operations with transaction managers. (#1755)
  • Added support for arbitrary filtering for partition scan and index scan. (#1763)
  • Added a single CRUD operation transaction manager. This transaction manager implementation does not allow beginning a transaction by calling begin()/start(). It only allows directly executing CRUD operations from the transaction manager. (#1793)
  • Added support for arbitrary filtering for get operations. (#1834)
  • In MySQL, ScalarDB FLOAT type is changed from DOUBLE to REAL (single-precision floating-point value) (#2000)
  • Added a new Admin API admin.getNamespacesNames() to list the user namespaces. Though, this API won't return a namespace that does not contain a table. From ScalarDB 4.0, we plan to improve the design to suppress this limitation. (#2002)

Improvements​

  • Removed the hard-coded collation for MySQL and SQL Server in the JDBC adapter. As a result, the collation configured in the underlying database will be used when creating tables. (#1518)
  • Added error codes to the error messages of Schema Loader. (#1564)
  • Performance improvement of the group commit by using priority queue in the background worker. (#1641)
  • Refactored scan with filtering. (#1715)
  • Avoided creating an internal unique index as much as possible to reduce resource consumption and improve performance. (#1723)
  • Changed the hard-coded password for the Oracle user to a more secure one in the JDBC adapter. (#1765)
  • Update base image of container image. This update fixes an OOM issue on a Kubernetes with cgroup v2 environment. In the previous versions, if you use a Kubernetes cluster with cgroup v2, you might face an OOM-killed issue. (#1826)
  • Added capability to specify global properties for all storages in multi-storage. (#1486)

Bug fixes​

  • Upgraded the base image to fix security issues. CVE-2023-47038 (#1522 #1521)
  • Upgraded the PostgresSQL lib to fix security issues. CVE-2024-1597 (#1547)
  • Fixed a bug where NullPointerException occurs during the EXTRA_READ validation when scanning records in a transaction, but some of them are deleted by other transactions. (#1624)
  • Fixed a bug where lazy recovery was not executed for the implicit pre-read of put and delete operations. (#1681)
  • Fixed a bug where users could see inconsistent results when scanning records by an index key after putting the related records in Consensus Commit transactions. (#1727)
  • Upgraded grpc_health_probe to fix security issues. CVE-2024-24790, CVE-2023-45283, and CVE-2023-45288 (#1980)
  • Fixed snapshot management issues. (#1976)
  • Fix a bug of the import-table feature that it could access tables in other namespace that have the same table name when using MySQL storage. (#2001)

Enterprise edition​

Enhancements​

ScalarDB Cluster​
  • Added support for the insert mode of the Put operation introduced #1679 in ScalarDB Cluster.
  • Added support for insert, upsert, and update APIs introduced in #1697 in ScalarDB Cluster.
  • Added support executing a CRUD operations in a one-shot transaction.
  • Added support for arbitrary filtering for partition scan and index scan introduced in #1763 to ScalarDB Cluster.
  • Added support for transaction managers other than Consensus Commit to ScalarDB Cluster.
  • Added support for the single CRUD operation transaction manager introduced in #1793 in ScalarDB Cluster.
  • Added support for arbitrary filtering for get operations introduced in #1834 to ScalarDB Cluster.
  • Added support for DistributedTransactionAdmin.getNamespaceNames()
ScalarDB SQL​
  • Added support for the single CRUD operation transaction manager introduced in #1793 to ScalarDB SQL.
  • With this update, users now have several ways to access ScalarDB-managed namespaces in ScalarDB SQL.

Improvements​

ScalarDB Cluster​
  • Added error codes to the error messages of the authentication and authorization module.
  • Added error codes to the error messages.
  • Added TLS support for the Prometheus exporter. With this change, when enabling TLS (setting scalar.db.cluster.tls.enabled to true) in ScalarDB cluster nodes, the Prometheus exporter also starts with TLS (HTTPS).
  • Update base image of container image. This update fixes an OOM issue on a Kubernetes with cgroup v2 environment. In the previous versions, if you use a Kubernetes cluster with cgroup v2, you might face an OOM-killed issue.
ScalarDB GraphQL​
  • Added error codes to the error messages.
  • Update base image of container image. This update fixes an OOM issue on a Kubernetes with cgroup v2 environment. In the previous versions, if you use a Kubernetes cluster with cgroup v2, you might face an OOM-killed issue.
ScalarDB SQL​
  • Added error codes to the error messages.
  • Changed the packages for ConditionSetBuilder and AndConditionSet.
  • Allowed using the EXISTS keyword for the CREATE/DROP COORDINATOR TABLES statements.
  • Update base image of container image. This update fixes an OOM issue on a Kubernetes with cgroup v2 environment. In the previous versions, if you use a Kubernetes cluster with cgroup v2, you might face an OOM-killed issue.
  • Improved performance of selection queries with filtering by exploiting partition and index scans.

Bug fixes​

ScalarDB Cluster​
ScalarDB GraphQL​
ScalarDB SQL​
  • Upgraded the base image to fix security issues. CVE-2023-47038
  • Fixes a bug that Spring Data JDBC for ScalarDB doesn't work with Spring Boot 3
  • Fixed a bug where incorrect results are returned when executing SELECT queries with the same column names.
  • Upgraded grpc_health_probe to fix security issues. CVE-2024-24790, CVE-2023-45283, and CVE-2023-45288
This website uses cookies to enhance the visitor experience. By continuing to use this website, you acknowledge that you have read and understood our privacy policy and consent to the use of cookies to help improve your browsing experience and provide you with personalized content.