ScalarDB Files

Summary

This release includes several improvements and bug fixes.

Community edition

Improvements

• Extended the applicability of one-phase commit optimization in the Consensus Commit protocol. This allows one-phase commit to be used even in SERIALIZABLE isolation level when the transaction only reads records that it subsequently updates, improving performance for read-modify-write workloads. (#3295)

Bug fixes

• Added explicit commits for Oracle database when using SERIALIZABLE isolation level to ensure snapshot updates after each operation. (#3294)
• Upgraded the Jackson library to fix a security issue: GHSA-72hv-8253-57qq (#3394)

Enterprise edition

Bug fixes

ScalarDB Cluster

• Fixed an issue where the batch operation with piggyback commit threw CrudException instead of CrudConflictException when a commit conflict occurred. This allows clients to properly detect and handle commit conflicts.
• Fixed a bug where batch() with piggyback commit threw CrudException instead of UnknownTransactionStatusException on unexpected gRPC errors. This could cause incorrect error handling on the client side, as the transaction status was actually unknown when piggyback commit was enabled.
• Upgraded grpc_health_probe to fix security issues: CVE-2025-68121, CVE-2025-61726, CVE-2025-61728, CVE-2025-61729, and CVE-2025-61730
• Upgraded the Kubernetes Java Client to fix a security issue: CVE-2024-29371
• Excluded com.microsoft.azure:adal4j from the Kubernetes Java Client to fix security issues: CVE-2023-52428, CVE-2021-31684, and CVE-2023-1370
• Upgraded the Jackson library to fix a security issue: GHSA-72hv-8253-57qq

ScalarDB SQL

• Ambiguous column names in ORDER BY and HAVING clauses were detected.
• Fixed a ClassCastException that occurred in StatementUtils.appendTerm() when handling DATE, TIME, TIMESTAMP, and TIMESTAMPTZ values. These values are now correctly formatted as string literals instead of being incorrectly cast to String.
• Fixed SelectStatement.toSql() to correctly generate ORDER BY clauses with aggregate functions such as SUM() and COUNT(). Previously, only column-based orderings were handled, causing incorrect SQL output when function-based orderings were used.