Skip to content

Commit 9a69c26

Browse files
committed
Merge branch 'main' into mark-out-of-support-version-3.10
2 parents 73e0d20 + eab8fbc commit 9a69c26

File tree

5 files changed

+72
-5
lines changed

5 files changed

+72
-5
lines changed

docs/releases/release-notes.mdx

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,31 @@ displayed_sidebar: docsEnglish
1010

1111
This page includes a list of release notes for ScalarDB 3.15.
1212

13+
## v3.15.4
14+
15+
**Release date:** June 21, 2025
16+
17+
### Summary
18+
19+
This release includes fixes for vulnerabilities and bugs.
20+
21+
### Community edition
22+
23+
#### Bug fixes
24+
25+
- Add exception handling for DateTimeParseException on column value conversion. ([#2662](https://github.com/scalar-labs/scalardb/pull/2662))
26+
- Upgraded the PostgreSQL driver to fix security issues. [CVE-2025-49146](https://github.com/advisories/GHSA-hq9p-pm7w-8p54 "CVE-2025-49146") ([#2772](https://github.com/scalar-labs/scalardb/pull/2772))
27+
- Fixed potential connection leak when using `jdbc` storage and Scan operation fails because the target table doesn't exist. ([#2766](https://github.com/scalar-labs/scalardb/pull/2766))
28+
29+
### Enterprise edition
30+
31+
#### Bug fixes
32+
33+
##### ScalarDB Cluster
34+
35+
- Fixed a memory leak issue when the coordinator group commit feature is enabled.
36+
- Upgraded the OpenSearch Java client to fix a security issue. [CVE-2025-27820](https://github.com/advisories/GHSA-73m2-qfq3-56cx "CVE-2025-27820")
37+
1338
## v3.15.3
1439

1540
**Release date:** May 15, 2025

docs/scalardb-analytics/run-analytical-queries.mdx

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -146,6 +146,23 @@ You can use an arbitrary name for `<DATA_SOURCE_NAME>`.
146146
| `spark.sql.catalog.<CATALOG_NAME>.data_source.<DATA_SOURCE_NAME>.database` | No | The name of the database to connect to |
147147
| `spark.sql.catalog.<CATALOG_NAME>.data_source.<DATA_SOURCE_NAME>.secure` | No | Whether to use a secure connection to the SQL Server server. Set to `true` to use a secure connection. |
148148

149+
:::tip
150+
151+
You can use an arbitrary name for `<DATA_SOURCE_NAME>`.
152+
153+
:::
154+
155+
</TabItem>
156+
<TabItem value="dynamodb" label="DynamoDB">
157+
158+
| Configuration Key | Required | Description |
159+
|:---------------------------------------------------------------------------|:------------------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------|
160+
| `spark.sql.catalog.<CATALOG_NAME>.data_source.<DATA_SOURCE_NAME>.type` | Yes | Always set to `dynamodb` |
161+
| `spark.sql.catalog.<CATALOG_NAME>.data_source.<DATA_SOURCE_NAME>.region` | Either `region` or `endpoint` must be set | The AWS region of the DynamoDB instance |
162+
| `spark.sql.catalog.<CATALOG_NAME>.data_source.<DATA_SOURCE_NAME>.endpoint` | Either `region` or `endpoint` must be set | The AWS endpoint of the DynamoDB instance |
163+
| `spark.sql.catalog.<CATALOG_NAME>.data_source.<DATA_SOURCE_NAME>.schema` | Yes | A JSON object representing the schema of the catalog. For details on the format, see [Catalog-level mappings](./design.mdx#catalog-level-mappings). |
164+
165+
149166
:::tip
150167

151168
You can use an arbitrary name for `<DATA_SOURCE_NAME>`.

docusaurus.config.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ const config = {
7878
label: '3.15',
7979
path: 'latest', // When a new version is released and this is no longer the current version, change this to the version number and then delete this comment.
8080
banner: 'none',
81-
className: '3.15.3',
81+
className: '3.15.4',
8282
},
8383
"3.14": { // When a new version is released and this is no longer the current version, change this to the version number and then delete this comment.
8484
label: '3.14',

i18n/versioned_docs/ja-jp/docusaurus-plugin-content-docs/current/releases/release-notes.mdx

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,31 @@ import TranslationBanner from '/src/components/_translation-ja-jp.mdx';
1414

1515
このページには、ScalarDB 3.15 のリリースノートのリストが含まれています。
1616

17+
## v3.15.4
18+
19+
**発売日:** 2025年06月21日
20+
21+
### まとめ
22+
23+
このリリースには脆弱性とバグの修正が含まれています。
24+
25+
### Community edition
26+
27+
#### バグの修正
28+
29+
- カラム値変換におけるDateTimeParseExceptionの例外処理を追加しました。([#2662](https://github.com/scalar-labs/scalardb/pull/2662))
30+
- セキュリティ問題を修正するためにPostgreSQLドライバーをアップグレードしました。[CVE-2025-49146](https://github.com/advisories/GHSA-hq9p-pm7w-8p54 "CVE-2025-49146") ([#2772](https://github.com/scalar-labs/scalardb/pull/2772))
31+
- `jdbc`ストレージを使用し、対象テーブルが存在しないためにスキャン操作が失敗した場合の潜在的な接続リークを修正しました。([#2766](https://github.com/scalar-labs/scalardb/pull/2766))
32+
33+
### Enterprise edition
34+
35+
#### バグの修正
36+
37+
##### ScalarDB Cluster
38+
39+
- コーディネーターのグループコミット機能が有効になっている場合のメモリリーク問題を修正しました。
40+
- セキュリティ問題を修正するためにOpenSearch Javaクライアントをアップグレードしました。[CVE-2025-27820](https://github.com/advisories/GHSA-73m2-qfq3-56cx "CVE-2025-27820")
41+
1742
## v3.15.3
1843

1944
**発売日:** 2025年05月15日

src/data/notifications.js

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,12 @@
33
const notificationsList = [
44
{
55
message: {
6-
en: 'Check out the release notes for ScalarDB 3.15.3',
7-
ja: 'ScalarDB 3.15.3 のリリースノートをご覧ください'
6+
en: 'Check out the release notes for ScalarDB 3.15.4',
7+
ja: 'ScalarDB 3.15.4 のリリースノートをご覧ください'
88
},
99
url: {
10-
en: 'releases/release-notes#v3153?utm_source=docs-site&utm_medium=notifications',
11-
ja: 'releases/release-notes#v3153?utm_source=docs-site&utm_medium=notifications'
10+
en: 'releases/release-notes#v3154?utm_source=docs-site&utm_medium=notifications',
11+
ja: 'releases/release-notes#v3154?utm_source=docs-site&utm_medium=notifications'
1212
},
1313
unread: true
1414
},

0 commit comments

Comments
 (0)