Repository navigation
Tsurugi 1.11.0 - Release Notes (en) #227
akirakw
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
1.11.0 Release Notes
Overview
Tsurugi 1.11.0 adds support for correlated subqueries as a new SQL feature.
A correlated subquery is a subquery that references columns of the outer query.
In this version, Tsurugi extends the scalar subquery feature introduced in Tsurugi 1.10.0, allowing correlated subqueries to be written.
This makes it possible to describe dynamic subqueries that return different results for each row of the outer query, enabling more advanced conditional evaluation and data extraction.
Tsurugi 1.11.0 also adds official support for the
BLOBandCLOBtypes.The
BLOBandCLOBtypes have been available as an experimental feature since Tsurugi 1.3.0, but they came with major restrictions, such as being available only from clients deployed in the same environment as the Tsurugi server, and being supported by only a limited set of client libraries.This version removes those environment-related restrictions and expands support across client libraries, making the
BLOBandCLOBtypes available for a wider range of use cases.Tsurugi 1.11.0 also includes feature additions and improvements for Tsurugi UDF, including support for
NULLvalues.In addition, this version adds experimental support for Ubuntu 26.04.
This version also includes several important bug fixes and stability improvements.
We strongly recommend all users of previous versions to upgrade to this release.
New Features and Improvements
New Features and Improvements - SQL
EXISTSpredicate, andINsubqueries cannot be usedFULL OUTER JOINcannot be usedVALUEScan only contain exactly one rowEXISTScan only be used in top-level filter conditions (directly underWHEREorHAVING, or as conditions combined withAND)BLOBandCLOBtypesBLOBandCLOBtypes, which had been provided as an experimental feature since Tsurugi 1.3.0, have been significantly enhanced and are now officially supported. For details, see the following document:BLOB/CLOBdata between Tsurugi and clients over gRPC. Starting with this version, it becomes the default mode when using theBLOBandCLOBtypes from supported client libraries.Note
For detailed specifications and current restrictions on SQL features, see the following document in tsurugidb:
New Features and Improvements - Endpoint
tsurugi.inienablein the[grpc_server]section fromtruetofalseBLOBandCLOBtypes in the relay mode described above, and when using the BLOB client for Tsurugi UDF. To use these features, setenablein the[grpc_server]section totruebefore starting Tsurugi.New Features and Improvements - Client
BLOBandCLOBtypesBLOBandCLOBtypes. For details, see the following documents:tgsqlBLOBandCLOBtypes--lob-transfer-typeoption to thetgsqlcommand to specify the LOB transfer type. For details, see the following document:tgsqlBLOBandCLOBtypes. For details, see the following document:BLOBandCLOBtypes--db-timeoutstartup option to specify the connection timeout for Tsurugi. For details, see the following document:BLOBandCLOBtypes. For details, see the following document:BLOBandCLOBtypesBLOBandCLOBtypes. For details, see the following document:New Features and Improvements - UDF
NULLvaluesgrpc_server.endpointin the UDF plugin configuration fileNew Features and Improvements - Distribution
apt installon Ubuntu 26.04.21.0.0to24.0.021.0.0, which is installed by the installer in earlier Tsurugi versions, is not available and causes the installer to fail. If you use the installer on Ubuntu 26.04, use the installer from this version or later, in which the Apache Arrow version has been updated to24.0.0.Bug Fixes
Bug Fixes - SQL
COUNT(DISTINCT ...)multiple times in theHAVINGclause could cause the database to terminate abnormallyNULLand that column is used with an inequality operator in theWHEREclauseDROP INDEXwould incorrectly succeed without an error, leaving the table in an invalid stateDESCinCREATE INDEXINclause with a subquery against a column containingNULLINclause with a subquery whose output column is a secondary index, or a primary index key column or its prefixBug Fixes - Transaction
tglogutil compaction, the database could fail to start or the database contents could become invalid under certain conditionsBug Fixes - Endpoint
tsurugi.iniBug Fixes - Client
session.refresh_timeouton the Tsurugi server (default: 300 seconds)0as the timeout value caused an immediate timeout instead of disabling the timeoutBug Fixes - UDF
.protofile that imports another.protocontaining a service definition (service) would be built as an invalid UDF pluginoneoffields are defined in a message and different types are specified for multiple fields at UDF invocation time.protothat uses the official Protocol Buffers Well-Known Types withudf-plugin-buildercould result in an errorUpgrade Notes
Client Compatibility List
Tsurugi 1.11.0 supports the following clients.
Please upgrade each client as needed when upgrading Tsurugi.
Important
With the official support for the
BLOBandCLOBtypes in this version, all clients must be upgraded to the versions shown in the table below.Important
For Tsurugi UDF, you must regenerate and redeploy UDF plugins using
udf-plugin-builder.Upgrade Procedure
For instructions on upgrading from previous versions, see:
Other Information
For a full list of changes in this version, see the Changelog:
For known issues and additional information about fixes in this version, see:
This discussion was created from the release 1.11.0.
All reactions