Skip to main content
Version: 3.12

ScalarDB 3.12 Release Notes

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

v3.12.3​

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 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. For example, in the following situation, the metadata of the columns pk_unexpected and col_unexpected of ns2.tbl1 are handled and the import-table feature fails due to unsupported data types. (#2001)

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​
  • Changed the packages for ConditionSetBuilder and AndConditionSet.
  • 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​
  • 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

v3.12.2​

Release date: April 1, 2024

Summary​

This release includes several improvements, including error message improvements and a vulnerability fix.

Community edition​

Improvements​

  • Added error codes to the error messages of Schema Loader. (#1564)

Enterprise edition​

Improvements​

ScalarDB Cluster​
  • Added error codes to the error messages of the Auth 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).
ScalarDB GraphQL​
  • Added error codes to the error messages.
ScalarDB SQL​
  • Added error codes to the error messages.

Bug fixes​

ScalarDB Cluster​

v3.12.1​

Release date: February 26, 2024

Summary​

This release has a small improvement and several bug and vulnerability fixes.

Community edition​

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)

Bug fixes​

Enterprise edition​

Bug fixes​

ScalarDB Cluster​
ScalarDB GraphQL​
ScalarDB SQL​

v3.12.0​

Release date: February 17, 2024

Summary​

This release has several enhancements, improvements, and bug fixes.

Community edition​

Enhancements​

  • Made Cosmos DB consistency level configurable in the Cosmos DB adapter. Users can change the consistency level used for Cosmos DB operations by specifying the property scalar.db.cosmos.consistency_level. STRONG or BOUNDED_STALENESS can be specified. (#1470)

Improvements​

  • Added error codes to the error messages. (#1493)

Bug fixes​

  • Improved some error handling to avoid potential NPE in JDBC storages. (#1442)
  • Fixed a bug where lazy recovery is not performed when uncommitted records are read while executing implicit pre-read. (#1476)

Enterprise edition​

Enhancements​

ScalarDB Cluster​
  • Added support for wire encryption using TLS. When you enable ScalarDB Auth, you should enable wire encryption in production environments to protect the user credentials.
  • Added an expiration time for the auth token to the response of the AuthLogin.Login endpoint.

Improvements​

ScalarDB GraphQL​
  • Updated several libraries.
ScalarDB SQL​
  • Updated several libraries.

Bug fixes​

ScalarDB Cluster​
  • Fixed a bug where the table or namespace privilege is not handled correctly.