Merge branch 'main' into add-language-dropdown-for-3.13-and-later

Author: josh-wong

docs/api-guide.mdx

@@ -580,7 +580,7 @@ And if you need to check if a value of a column is null, you can use the `isNull
 boolean isNull = result.isNull("<COLUMN_NAME>");
 ```
 
-For more details, see the `Result` page in the [Javadoc](https://javadoc.io/doc/com.scalar-labs/scalardb/3.13.1/index.html) of the version of ScalarDB that you're using.
+For more details, see the `Result` page in the [Javadoc](https://javadoc.io/doc/com.scalar-labs/scalardb/3.14.0/index.html) of the version of ScalarDB that you're using.
 
 ###### Execute `Get` by using a secondary index
 

docs/configurations.mdx

@@ -203,11 +203,11 @@ For details about client configurations, see the [ScalarDB Cluster client config
 
 The following are additional configurations available for ScalarDB:
 
-| Name                                                             | Description                                                                                                                                                                                 | Default              |
-|------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
-| `scalar.db.metadata.cache_expiration_time_secs`                  | ScalarDB has a metadata cache to reduce the number of requests to the database. This setting specifies the expiration time of the cache in seconds.                                         | `-1` (no expiration) |
-| `scalar.db.active_transaction_management.expiration_time_millis` | ScalarDB maintains ongoing transactions, which can be resumed by using a transaction ID. This setting specifies the expiration time of this transaction management feature in milliseconds. | `-1` (no expiration) |
-| `scalar.db.default_namespace_name`                               | The given namespace name will be used by operations that do not already specify a namespace.                                                                                                |                      |
+| Name                                                             | Description                                                                                                                                                                                           | Default              |
+|------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
+| `scalar.db.metadata.cache_expiration_time_secs`                  | ScalarDB has a metadata cache to reduce the number of requests to the database. This setting specifies the expiration time of the cache in seconds. If you specify `-1`, the cache will never expire. | `60`                 |
+| `scalar.db.active_transaction_management.expiration_time_millis` | ScalarDB maintains ongoing transactions, which can be resumed by using a transaction ID. This setting specifies the expiration time of this transaction management feature in milliseconds.           | `-1` (no expiration) |
+| `scalar.db.default_namespace_name`                               | The given namespace name will be used by operations that do not already specify a namespace.                                                                                                          |                      |
 
 ## Placeholder usage
 

docs/index.mdx

@@ -7,7 +7,7 @@ tags:
 
 # ScalarDB
 
-import { CardRowAbout, CardRowGettingStarted, CardRowSamples, CardRowDevelop, CardRowDeploy, CardRowManage, CardRowReference } from '/src/components/Cards/3.13';
+import { CardRowAbout, CardRowGettingStarted, CardRowSamples, CardRowDevelop, CardRowDeploy, CardRowManage, CardRowReference } from '/src/components/Cards/3.14';
 
 ScalarDB is a cross-database HTAP engine. It achieves ACID transactions and real-time analytics across diverse databases to simplify the complexity of managing multiple databases.
 

docs/quick-start-overview.mdx

@@ -25,12 +25,11 @@ ScalarDB Cluster is available only in the Enterprise edition.
 
 ## Try running analytical queries through ScalarDB Analytics
 
-In this sub-category, you can see tutorials on how to run analytical queries over the databases that you write through ScalarDB by using a component called ScalarDB Analytics.
-ScalarDB Analytics currently targets only ScalarDB-managed databases, updated through ScalarDB transactions, but will target non-ScalarDB-managed databases in the future.
+In this sub-category, you can see tutorials on how to run analytical queries over the databases that you write to by using a component called ScalarDB Analytics. ScalarDB Analytics targets both ScalarDB-managed databases, which are updated through ScalarDB transactions, and non-ScalarDB-managed databases.
 
 :::note
 
 - ScalarDB Analytics with PostgreSQL is available only under the Apache 2 License and doesn't require a commercial license.
-- ScalarDB Analytics with Spark is in private preview.
+- ScalarDB Analytics with Spark is in public preview.
 
-:::
+:::

docs/releases/release-notes.mdx

@@ -5,38 +5,52 @@ tags:
   - Enterprise Premium
 ---
 
-# ScalarDB 3.13 Release Notes
+# ScalarDB 3.14 Release Notes
 
-This page includes a list of release notes for ScalarDB 3.13.
+This page includes a list of release notes for ScalarDB 3.14.
 
-## v3.13.1
+## v3.14.0
 
-**Release date:** October 13, 2024
+**Release date:** November 22, 2024
 
 ### Summary
 
-This release includes several bug fixes, and vulnerability fixes.
+This release includes a lot of enhancements, improvements, bug fixes, and vulnerability fixes.
 
 ### Community edition
 
 #### Enhancements
 
+- Added the encrypted column concept to ScalarDB. ([#1907](https://github.com/scalar-labs/scalardb/pull/1907) [#1975](https://github.com/scalar-labs/scalardb/pull/1975))
 - Added support for MariaDB 11.4 and Oracle 19. ([#2061](https://github.com/scalar-labs/scalardb/pull/2061))
 
+#### Improvements
+
+- Added options for changing the key column size for MySQL and Oracle and used 128 bytes as the default. ([#2245](https://github.com/scalar-labs/scalardb/pull/2245))
+- Changed the default value of the metadata cache expiration time (`scalar.db.metadata.cache_expiration_time_secs`) to 60 seconds. ([#2274](https://github.com/scalar-labs/scalardb/pull/2274))
+
 #### Bug fixes
 
 - Fixed a bug where `NullPointerException` when a table specified in a Get/Scan object is not found in Consensus Commit. ([#2083](https://github.com/scalar-labs/scalardb/pull/2083))
 - Fixed a corner case issue that causes inconsistent Coordinator states when lazy recovery happens before group commit ([#2135](https://github.com/scalar-labs/scalardb/pull/2135))
 - Upgraded the mysql driver to fix security issues. [CVE-2023-22102](https://github.com/advisories/GHSA-m6vm-37g8-gqvh "CVE-2023-22102") ([#2238](https://github.com/scalar-labs/scalardb/pull/2238))
-- Upgraded the gRPC library, the Protocol Buffers library, grpc_health_probe, and scalar-admin to fix security issues. [CVE-2024-7254](https://github.com/advisories/GHSA-735f-pc8j-v9w8 "CVE-2024-7254"), [CVE-2024-25638](https://github.com/advisories/GHSA-cfxw-4h78-h7fw "CVE-2024-25638"), and [CVE-2024-34156](https://github.com/advisories/GHSA-crqm-pwhx-j97f "CVE-2024-34156") ([#2277](https://github.com/scalar-labs/scalardb/pull/2277))
 
 ### Enterprise edition
 
 #### Enhancements
 
 ##### ScalarDB Cluster
 
-- Support the group commit feature for Coordinator table in ScalarDB cluster
+- Added support for encrypted columns introduced in [#1907](https://github.com/scalar-labs/scalardb/pull/1907).
+- Added support for the group commit feature for the Coordinator table.
+- Added support for encryption.
+- Added support for `getCurrentUser()` in `DistributedTransactionAdmin` and `Metadata` to retrieve the current logged-in user.
+
+##### ScalarDB SQL
+
+- Added support for encrypted columns introduced in [#1907](https://github.com/scalar-labs/scalardb/pull/1907) for the Metadata API.
+- Added support for encrypted columns for `CREATE TABLE` and `ALTER TABLE ADD COLUMN` statements.
+- Added `SHOW USERS` and `SHOW GRANTS` commands, which list users and privileges for a specified user, respectively.
 
 #### Improvements
 
@@ -48,112 +62,7 @@ This release includes several bug fixes, and vulnerability fixes.
 
 ##### ScalarDB Cluster
 
-- Fix a bug where `NullPointerException` occurs when catching an exception without message.
+- Fixed a bug where `NullPointerException` occurs when catching an exception without message.
 - Upgraded `grpc_health_probe` to fix a security issue. [CVE-2024-34156](https://github.com/advisories/GHSA-crqm-pwhx-j97f "CVE-2024-34156")
 - Upgraded `scalar-admin` to fix a security issue. [CVE-2024-25638](https://github.com/advisories/GHSA-cfxw-4h78-h7fw "CVE-2024-25638")
 - Upgraded the Protobuf Java library to fix a security issue. [CVE-2024-7254](https://github.com/advisories/GHSA-735f-pc8j-v9w8 "CVE-2024-7254")
-
-## v3.13.0
-
-### 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](https://github.com/scalar-labs/scalardb/pull/1682))
-- Added the Insert, Upsert, and Update operations to the transactional API. ([#1697](https://github.com/scalar-labs/scalardb/pull/1697))
-- Added YugabyteDB adapter as one of JDBC storages ([#1710](https://github.com/scalar-labs/scalardb/pull/1710))
-- Added Group Commit feature for Coordinator Table ([#1728](https://github.com/scalar-labs/scalardb/pull/1728))
-- Allowed directly executing CRUD operations with transaction managers. ([#1755](https://github.com/scalar-labs/scalardb/pull/1755))
-- Added support for arbitrary filtering for partition scan and index scan. ([#1763](https://github.com/scalar-labs/scalardb/pull/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](https://github.com/scalar-labs/scalardb/pull/1793))
-- Added support for arbitrary filtering for get operations. ([#1834](https://github.com/scalar-labs/scalardb/pull/1834))
-- In MySQL, ScalarDB `FLOAT` type is changed from `DOUBLE` to `REAL` (single-precision floating-point value) ([#2000](https://github.com/scalar-labs/scalardb/pull/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](https://github.com/scalar-labs/scalardb/pull/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](https://github.com/scalar-labs/scalardb/pull/1518))
-- Added error codes to the error messages of Schema Loader. ([#1564](https://github.com/scalar-labs/scalardb/pull/1564))
-- Performance improvement of the group commit by using priority queue in the background worker. ([#1641](https://github.com/scalar-labs/scalardb/pull/1641))
-- Refactored scan with filtering. ([#1715](https://github.com/scalar-labs/scalardb/pull/1715))
-- Avoided creating an internal unique index as much as possible to reduce resource consumption and improve performance. ([#1723](https://github.com/scalar-labs/scalardb/pull/1723))
-- Changed the hard-coded password for the Oracle user to a more secure one in the JDBC adapter. ([#1765](https://github.com/scalar-labs/scalardb/pull/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](https://github.com/scalar-labs/scalardb/pull/1826))
-- Added capability to specify global properties for all storages in multi-storage. ([#1486](https://github.com/scalar-labs/scalardb/pull/1486))
-
-#### Bug fixes
-
-- Upgraded the base image to fix security issues. [CVE-2023-47038](https://github.com/advisories/GHSA-96fh-9q43-rmjh "CVE-2023-47038") ([#1522](https://github.com/scalar-labs/scalardb/pull/1522) [#1521](https://github.com/scalar-labs/scalardb/pull/1521))
-- Upgraded the PostgresSQL lib to fix security issues. [CVE-2024-1597](https://github.com/advisories/GHSA-24rp-q3w6-vc56 "CVE-2024-1597") ([#1547](https://github.com/scalar-labs/scalardb/pull/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](https://github.com/scalar-labs/scalardb/pull/1624))
-- Fixed a bug where lazy recovery was not executed for the implicit pre-read of put and delete operations. ([#1681](https://github.com/scalar-labs/scalardb/pull/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](https://github.com/scalar-labs/scalardb/pull/1727))
-- Upgraded `grpc_health_probe` to fix security issues. [CVE-2024-24790](https://github.com/advisories/GHSA-49gw-vxvf-fc2g "CVE-2024-24790"), [CVE-2023-45283](https://github.com/advisories/GHSA-vvjp-q62m-2vph "CVE-2023-45283"), and [CVE-2023-45288](https://github.com/advisories/GHSA-4v7x-pqxf-cx7m "CVE-2023-45288") ([#1980](https://github.com/scalar-labs/scalardb/pull/1980))
-- Fixed snapshot management issues. ([#1976](https://github.com/scalar-labs/scalardb/pull/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](https://github.com/scalar-labs/scalardb/pull/2001))
-
-### Enterprise edition
-
-#### Enhancements
-
-##### ScalarDB Cluster
-
-- Added support for the insert mode of the Put operation introduced [#1679](https://github.com/scalar-labs/scalardb/pull/1679) in ScalarDB Cluster.
-- Added support for insert, upsert, and update APIs introduced in [#1697](https://github.com/scalar-labs/scalardb/pull/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](https://github.com/scalar-labs/scalardb/pull/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](https://github.com/scalar-labs/scalardb/pull/1793) in ScalarDB Cluster.
-- Added support for arbitrary filtering for get operations introduced in [#1834](https://github.com/scalar-labs/scalardb/pull/1834) to ScalarDB Cluster.
-- Added support for `DistributedTransactionAdmin.getNamespaceNames()`
-
-##### ScalarDB SQL
-
-- Added support for the single CRUD operation transaction manager introduced in [#1793](https://github.com/scalar-labs/scalardb/pull/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
-
-- Upgraded the base image to fix security issues. [CVE-2023-47038](https://github.com/advisories/GHSA-96fh-9q43-rmjh "CVE-2023-47038")
-- Upgraded the Kubernetes Client Java lib to fix security issues: [CVE-2024-25710](https://github.com/advisories/GHSA-4g9r-vxhx-9pgx "CVE-2024-25710") and [CVE-2024-26308](https://github.com/advisories/GHSA-4265-ccf5-phj5 "CVE-2024-26308").
-- Upgraded `grpc_health_probe` to fix security issues. [CVE-2024-24790](https://github.com/advisories/GHSA-49gw-vxvf-fc2g "CVE-2024-24790"), [CVE-2023-45283](https://github.com/advisories/GHSA-vvjp-q62m-2vph "CVE-2023-45283"), and [CVE-2023-45288](https://github.com/advisories/GHSA-4v7x-pqxf-cx7m "CVE-2023-45288")
-- Fixed a bug where incorrect results are returned when executing SELECT queries with the same column names.
-
-##### ScalarDB GraphQL
-
-- Upgraded the base image to fix security issues. [CVE-2023-47038](https://github.com/advisories/GHSA-96fh-9q43-rmjh "CVE-2023-47038")
-
-##### ScalarDB SQL
-
-- Upgraded the base image to fix security issues. [CVE-2023-47038](https://github.com/advisories/GHSA-96fh-9q43-rmjh "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](https://github.com/advisories/GHSA-49gw-vxvf-fc2g "CVE-2024-24790"), [CVE-2023-45283](https://github.com/advisories/GHSA-vvjp-q62m-2vph "CVE-2023-45283"), and [CVE-2023-45288](https://github.com/advisories/GHSA-4v7x-pqxf-cx7m "CVE-2023-45288")

docs/releases/release-support-policy.mdx

@@ -28,12 +28,19 @@ This page describes Scalar's support policy for major and minor version releases
   </thead>
   <tbody>
     <tr>
-      <td><a href="https://scalardb.scalar-labs.com/docs/latest/releases/release-notes#v3130">3.13</a></td>
-      <td>2024-07-08</td>
+      <td><a href="https://scalardb.scalar-labs.com/docs/latest/releases/release-notes#v3140">3.14</a></td>
+      <td>2024-11-22</td>
       <td>TBD*</td>
       <td>TBD*</td>
       <td><a href="https://www.scalar-labs.com/contact">Contact us</a></td>
     </tr>
+    <tr>
+      <td><a href="https://scalardb.scalar-labs.com/docs/3.13/releases/release-notes#v3130">3.13</a></td>
+      <td>2024-07-08</td>
+      <td>2025-11-22</td>
+      <td>2026-05-21</td>
+      <td><a href="https://www.scalar-labs.com/contact">Contact us</a></td>
+    </tr>
     <tr>
       <td><a href="https://scalardb.scalar-labs.com/docs/3.12/releases/release-notes#v3120">3.12</a></td>
       <td>2024-02-17</td>