メインコンテンツまでスキップ
バージョン: 3.11
Features and pricing

ScalarDB 3.11 Release Notes

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

v3.11.4​

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

Bug fixes​

ScalarDB Cluster​
  • Fixed a bug where incorrect results are returned when executing SELECT queries with the same column names.
  • 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
ScalarDB GraphQL​
  • Upgraded the GraphQL Java library to fix security issues. CVE-2024-40094

v3.11.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.11.2​

Release date: April 1, 2024

Summary​

This release includes several improvements and a vulnerability fix.

Enterprise edition​

Bug fixes​

ScalarDB Cluster​

v3.11.1​

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)
  • Fixed a bug where lazy recovery is not performed when uncommitted records are read while executing implicit pre-read. (#1476)
  • 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​
  • Fixed a bug where the table or namespace privilege is not handled correctly.
  • Upgraded the base image to fix security issues. CVE-2023-47038
ScalarDB GraphQL​
ScalarDB SQL​

v3.11.0​

Release date: December 27, 2023

Summary​

This release has a lot of enhancements, improvements, and bug fixes. There are many SQL enhancements including JOIN support and cross-partition scan support. This release also includes an authentication and authorization mechanism for ScalarDB Cluster. 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 import functionalities for existing relational databases. (#841 #931 #1055)
  • Added support for cross-partition scan for relational databases with arbitrary conditions, including LIKE expressions. (#889 #900 #925 #984 #1006 #1045 #1046)

Improvements​

  • Added support for implicit pre-read in Consensus Commit. With implicit pre-read, users can perform mutations (Put and Delete operations) without reading the records beforehand. (#1222)

Bug fixes​

Enterprise edition​

Enhancements​

ScalarDB Cluster​
  • Added support for cross-partition scan for relational databases with arbitrary conditions, including LIKE expressions.
  • Added import functionalities for existing relational databases.
  • Added support for operating a ScalarDB Cluster node in standalone mode to make development and testing more convenient. You can activate standalone mode by setting scalar.db.cluster.node.standalone_mode.enabled to true.
  • Added the docker-compose.yaml file to test standalone mode. You can run ScalarDB Cluster for testing purposes in your local environment by using the docker compose up command.
  • Introduced an authentication and authorization mechanism for ScalarDB Cluster.
ScalarDB SQL​
  • Added support for cross-partition scan for relational databases with arbitrary conditions, including LIKE expressions.
  • Added support for table aliases for UPDATE, DELETE, and SELECT statements. User can write a query with table aliase like SELECT t.col FROM tbl AS t.
  • Added support for the JOIN operation. This enhancement supports INNER JOIN, LEFT OUTER JOIN, and RIGHT OUTER JOIN.
  • Added support for specifying multiple values in INSERT statements.
  • Introduced support for the START TRANSACTION and ABORT commands, which serve as aliases for the BEGIN and ROLLBACK commands, respectively.
  • Added support for cross-partition WHERE clauses in UPDATE and DELETE statements.
  • Introduced an UPSERT command that creates a new record if it doesn't exist, or updates the record if it does.

Improvements​

ScalarDB Cluster​
  • Added pay-as-you-go containers to the AWS Marketplace.
  • Added ScalarDB Cluster (BYOL) to the Azure Marketplace. You can use ScalarDB Cluster by subscribing to it in the Azure Marketplace.
  • Added ScalarDB Cluster (BYOL) to the AWS Marketplace. You can use ScalarDB Cluster by subscribing to it in the AWS Marketplace.
  • Added support for implicit pre-read introduced in the enterprise edition. With implicit pre-read, users can perform mutations (Put and Delete operations) without reading the records beforehand.

Bug fixes​

ScalarDB Cluster​
ScalarDB GraphQL​
ScalarDB SQL​