Release Notes 4.13
The 4.13 release notes were released on July 23, 2025
Compatibility Matrix
System Requirement |
Details |
---|---|
Supported OS |
RHEL 8.9 / 8.10 |
supported Nvidia driver |
CUDA version 12.3.2 / 12.6.1 |
Storage version |
63 |
New Features and Enhancements
► Show node info will also show the “WITH” alias / table alias name and not only the table name.
► Enhance Null/NaN/NaT handling in PySQream.
Known Issues
Percentile is not supported for Window Functions
Version 4.13 resolved Issues
SQ No. |
Description |
---|---|
SQ-20475 |
Fixed type check issue when using pivot on text literal |
SQ-20401 |
Enhanced support for queries combining constant text and table data |
SQ-20399 |
Encryption Support Stability Improvement |
SQ-20100 |
COPY FROM support for uppercase column names |
SQ-19857 |
Improved performance for catalog queries |
SQ-19308 |
Resolved Worker Unavailability Caused by Blobs Exceeding maxBlobSize |
SQ-16663 |
Resolved Issue with Creating and Inserting into Clustered Tables |
SQ-8440 |
Fixed LAG/LEAD Window Function error when using Text with Offset |
SQ-20567 |
Added new log message type |
SQ-20471, SQ-20414, SQ-20367, SQ-19792 |
Fixed errors related to array data type related to casting |
Deprecation
► Column DDL permission
Column DDL
permission is now deprecated as its functionality is fully included within the table DDL
permission. Upon upgrading to this version, all existing column DDL
permissions will be automatically revoked.
If you are upgrading from a release using the old behavior, please contact SQream support prior to performing the upgrade.
► Haskell CLI
Starting October 2024, support for the Haskell CLI is discontinued, and it is replaced by the Multi Platform CLI that is compatible with the Haskell CLI with the added value of Table-View
and cross platform compatibility.
► CentOS Linux 7.x
As of June 2024, CentOS Linux 7.x has reached its End of Life and is no longer supported by SQreamDB.
► DateTime2 Alias
As of April 2025, the alias DateTime2
for the DateTime
Data Type has been deprecated to simplify our data model and make way for the introduction of a new data type named DateTime2
.
Upgrading to Version 4.13
Generate a back-up of the metadata by running the following command:
select backup_metadata('out_path');
Tip
SQreamDB recommends storing the generated back-up locally in case needed.
SQreamDB runs the Garbage Collector and creates a clean backup tarball package.
Shut down all SQreamDB services.
Copy the recently created back-up file.
Replace your current metadata with the metadata you stored in the back-up file.
Navigate to the new SQreamDB package bin folder.
Run the following command:
./upgrade_storage <levelDB path>
Note
Upgrading from a major version to another major version requires you to follow the Upgrade Storage step. This is described in Step 7 of the Upgrading SQreamDB Version procedure.