Skip to main content
Version: 3.10

ScalarDB 3.10 Release Notes

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

v3.10.5​

Release date: July 3, 2024

Summary​

This release includes several improvements, bug fixes, and vulnerability fixes.

Community edition​

Improvements​

  • Refactored scan with filtering. (#1715)
  • 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)

Bug fixes​

  • 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 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)

Enterprise edition​

Improvements​

ScalarDB Cluster​
  • 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​
  • 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​
  • 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.

Bug fixes​

ScalarDB Cluster​
ScalarDB SQL​

v3.10.4​

Release date: April 1, 2024

Summary​

This release includes several improvements and a vulnerability fix.

Enterprise edition​

Bug fixes​

ScalarDB Cluster​

v3.10.3​

Release date: February 26, 2024

Summary​

This release has several bug and vulnerability fixes.

Community edition​

Bug fixes​

  • Improved some error handling to avoid potential NPE in JDBC storages. (#1442)
  • 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)

Enterprise edition​

Bug fixes​

ScalarDB Cluster​
ScalarDB GraphQL​
ScalarDB SQL​

v3.10.2​

Release date: December 26, 2023

Summary​

This release has several bug fixes, vulnerability fixes, and document improvements.

Community edition​

Bug fixes​

Enterprise edition​

Improvements​

ScalarDB Cluster​
  • Provide pay-as-you-go containers to AWS Marketplace
  • Provide ScalarDB Cluster (BYOL) in Azure Marketplace. You can use ScalarDB Cluster by subscribing to ScalarDB Cluster in Azure Marketplace.
  • Provide ScalarDB Cluster (BYOL) in AWS Marketplace. You can use ScalarDB Cluster by subscribing to ScalarDB Cluster in AWS Marketplace.

Bug fixes​

ScalarDB Cluster​
ScalarDB GraphQL​
ScalarDB SQL​

v3.10.1​

Release date: August 7, 2023

Summary​

This release has several small improvements and document improvements.

Change logs​

Improvements​

  • Fix java warnings in MutationConditionsValidatorTest (#970)

Documentation​

  • Revise document for handling exceptions for Two-phase Commit Transactions (#934)
  • Revise document for Handle exceptions (#975)

v3.10.0​

Release date: July 20, 2023

Summary​

ScalarDB 3.10 includes many enhancements, improvements, bug fixes, and documentation updates. Please see the following for a list of detailed changes.

ScalarDB provides a Community edition and an Enterprise edition. The Community edition is available as open-source software that you can use under the Apache 2.0 License. The Enterprise edition includes not only the features of the Community edition but also many advanced features. Release notes for the Enterprise edition are available under the “Enterprise edition” section. To use the features in the Enterprise edition, you must have a license agreement with Scalar Inc.

Community edition​

Enhancements​

  • Added functionality to treat the transaction metadata columns in a record as committed if the metadata in ScalarDB is empty (i.e., null). This functionality allows ScalarDB to import tables from another existing database. (#841 #931)
  • Added validation for the consensus commit mutation operation. (#873)
  • Added an interface to Scan to allow conditions (AND, OR, etc.) to be specified. (#889 #900 #925)
  • Added support for specifying conditions for Put and Delete in the transaction API. (#899)

Bug fixes​

  • Upgraded the integrated JRE Docker image to 1.1.13 to fix security issues. CVE-2022-29458 (#881 #882)
  • Upgraded the integrated JRE Docker image to 1.1.14 to fix security issues. CVE-2023-0464 CVE-2023-2650 (#902 #903)
  • Upgraded sqlite-jdbc to 3.42.0.0 to fix security issues. CVE-2023-32697 (#888)
  • Revised the method for checking transaction status before rollback to fix a bug that caused a partial commit during rollback() in the two-phase commit (2PC) interface. (#909)
  • Resolved a race condition in the counter that counts transactions to fix a bug that prevented ScalarDB Server from pausing. (#935)
  • Fixed a problem with the metrics for ScalarDB Server not properly displaying the number of aborts and rollbacks. (#919)
  • Upgraded gRPC library to 1.53.0 to fix security issues. CVE-2023-1428 CVE-2023-32731 (#943)

Documentation​

  • Improved documentation for handling errors in ScalarDB transactions. (#897 #932)
  • Added detailed descriptions for all ScalarDB configurations to the documentation. (#905)

Enterprise edition​

Enhancements​

ScalarDB Cluster​
  • Implemented AWS Marketplace usage reporting so that users can run a ScalarDB Cluster node (Standard or Premium edition) from AWS Marketplace with pay-as-you-go pricing plan.
  • Added support for specifying conditions for Put and Delete in the transaction API.
  • Added support for the table-importing feature in ScalarDB.

Improvements​

ScalarDB Cluster​
  • Updated GraphQL Server to allow graceful shutdown by waiting to shutdown until there are no more requests for the server.
ScalarDB GraphQL​
  • Updated GraphQL Server to allow graceful shutdown by waiting to shutdown until there are no more requests for the server.
ScalarDB SQL​
  • Added a two-phase commit (2PC) high-level API for participants into the ScalarDbTwoPcRepository class for Spring Data JDBC for ScalarDB so that users can implement a 2PC transaction participant safely and easily.

Bug fixes​

ScalarDB Cluster​
  • Upgraded the Guava library to 32.1.1-jre to fix security issues. [CVE-2023-2976]
ScalarDB GraphQL​
  • Upgraded the Guava library to 32.1.1-jre to fix security issues. [CVE-2023-2976]
  • Modified error handling to fix a bug that caused the GraphQL schema update process to stop.
ScalarDB SQL​
  • Updated ScalarDB SQL Server to always rollback a transaction when an error occurs.
  • Added a null check in the close() method of the SqlJdbcDriver class to fix a bug where NullPointerException could occur when executing the close() method.
  • Fixed a partial commit issue that occurred in 2PC when using Spring Data JDBC for ScalarDB by preventing any rollback after the coordinator successfully processes the commit.
  • Fixed a problem with the metrics for ScalarDB Server not properly displaying the number of aborts and rollbacks.
  • Upgraded the Guava library to 32.1.1-jre to fix security issues. [CVE-2023-2976]

Documentation​

ScalarDB Cluster​
  • Added the ScalarDB Cluster gRPC API guide.
  • Reorganized ScalarDB Cluster documents.
  • Added a getting started tutorial for ScalarDB Cluster with Python.
ScalarDB SQL​
  • Revised Spring Data JDBC for ScalarDB documentation, such as adding an architectural diagram, adding limitations, and updating some usage guides.
  • Added detailed descriptions for all ScalarDB configurations to the documentation.
  • Improved documentation for handling errors in ScalarDB transactions.