Release Notes 2022.1.3
The 2022.1.3 release notes were released on 9/20/2022 and describe the following:
The 2022.1.3 Release Notes describes the following:
Optimize the delete operation by removing redundant calls.
Support LIKE condition for filtering metadata.
Migration tool for converting VARCHAR columns into TEXT columns.
Support sub-queries in the UPDATE condition.
The storage version presently in effect is version 42.
The following table lists the issues that are known limitations in Version 2022.1.3:
UPADTE or DELETE using a sub-query that includes ‘%’ (modulo) is crashing SQreamDB worker
The following table lists the issues that were resolved in Version 2022.1.3:
COPY FROM with offset = 0 (which is an unsupported option) is stuck up to the query timeout.
SQL statement fails after changing the foreign table the statement tries to query.
Locked users are not being released on system reset.
Using “create table like” on foreign tables results in flat compression of the created table.
SQL User Defined Function fails when function definition contain parenthesis
FLAT compression is wrongly chosen when dealing with data sets starting with all-nulls
Update - enhanced error message when trying to run update on foreign table.
No configuration changes were made.
No relevant naming changes were made.
SQream is declaring end of support of VARCHAR data type, the decision resulted by SQream’s effort to enhance its core functionalities and with respect to ever changing echo system requirements.
VARCHAR is no longer supported for new customers - effective immediately.
TEXT data type is replacing VARCHAR - SQream will maintain VARCHAR data type support until 09/30/2023.
As part of this release 2022.1.3, SQream provides an automated and secured migration tool to help customers with the conversion phase from VARCHAR to TEXT data type, please address delivery for further information.
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.
Extract 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.