Release Notes 4.1
SQream is introducing a new version release system that follows the more commonly used Major.Minor.Patch versioning schema. The newly released 4.0 version is a minor version upgrade and does not require considerable preparation.
The 4.1 release notes were released on 03/01/2023 and describe the following:
Lightweight Directory Access Protocol (LDAP) management enhancement
A new brute-force attack protection mechanism locks out user accounts for 15 minutes following 5 consecutive failed login attempts
JDBC 4.5.7 .jar file
The storage version presently in effect is version 45.
SQream Studio v5.5.4 has been released.
Percentile is not supported for Window functions.
Function definition SQL UDF parenthesis issue
Slow catalog queries
Text column additional characters when using
Encryption memory issues
No configuration changes
No naming changes
► Square Brackets
, which are frequently used to delimit identifiers such as column names, table names, and other database objects, will soon be deprecated to facilitate the use of the
ARRAY data type.
for delimiting database object identifiers ends on June 1st, 2023.
To delimit database object identifiers, you will be able to use double quotes
VARCHAR data type is deprecated to improve the core functionalities of the platform and to align with the constantly evolving ecosystem requirements.
Support in the
VARCHARdata type ends at September 30th, 2023.
VARCHARis no longer supported for new customers, effective from Version 2022.1.3.
TEXTdata type is replacing the
No End of Support changes were made.
Generate a back-up of the metadata by running the following command:
$ select backup_metadata('out_path');
SQream recommends storing the generated back-up locally in case needed.
SQream runs the Garbage Collector and creates a clean backup tarball package.
Shut down all SQream 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 SQream package bin folder.
Run the following command:
$ ./upgrade_storage <levelDB path>
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 SQream Version procedure.