Release Notes 4.17

The 4.17 release notes were released on April 23, 2026

Compatibility Matrix

System Requirement

Details

Supported OS

RHEL 8.9 / 8.10 / 9.5 / 9.6

supported Nvidia driver

CUDA version 12.3.2 / 12.6.1 / 12.9.1 / 13.0

Storage version

101

New Features

► Add comment per column - Allow adding descriptive metadata to table and columns.

► Native HDFS Partition Support - Enable HDFS partitioning on foreign/external tables.

► Compression enhancements - Full nvcomp support.

► MCP interface support - allows you to query your data using natural language, using Claude as LLM. Please see MCP documentation.

► Add ANY syntax to Saved Query parameters should allow a dynamic IN list (SQ-22008). Please see Saved Query.

► Add support for casting TEXT_TO_ARRAY. Please see casting TEXT_TO_ARRAY.

Known Issues

Using Grant operation on a specific UDF function fail.

Percentile is not supported for Window Functions

The Node.JS connector does not support ARRAY data types.

Version 4.17 resolved Issues

SQ No.

Description

SQ-20823 | Data sorting query failed in particular circumstances

SQ-20981 | DELETE WHERE EXISTS failed when adding another condition

SQ-21140 | New utility functions for rechunking encrypted columns

SQ-21283 | Improve Saved Query runtime

SQ-21395 | Improve metadata performance

SQ-21412 | Enhanced loading of multiple ORC files

SQ-21456 | Fix the server status output on all available services

SQ-21479 | Improved schema information display in Studio

SQ-21518 | Resolved runtime error when copying from ORC after copy to ORC

SQ-21596 | Improved handling of permission checks on delete operations

SQ-21609 | Tables with special characters failing recompilation and cleanup operations

SQ-21631 | Improve DELETE performance when joining large tables with empty tables

SQ-21760 | Improve compilation runtime

SQ-21843 | Saved Query parameters support a dynamic IN list

SQ-22281 | Cross-database operations with identity or sequence columns

SQ-22345 | Improved reliability when accessing files across databases

SQ-22399 | Stability improvements for UNNEST join query compilation

SQ-22442 | Resolved COUNT window function compilation error

SQ-22588 | Worker memory usage improvements

SQ-22608 | Resolved window function query internal runtime error

SQ-22621 | Enhanced performance when querying sqream_catalog.chunks

SQ-22710 | Delete execution plan no longer includes inappropriate rechunk producer

SQ-22739 | Improved post statement memory release

SQ-22755 | Improved cleanup_chunks performance

SQ-22756 | Improved performance for sqream_catalog.metadata_partitions queries

SQ-22830 | S3 connectivity endpoint flag wasn’t enforced correctly

SQ-22838 | Cleanup extents mechanism improvement

Deprecation

► Flag maxBlobSizeNetworkInsert depracted

  • Instead use maxBlobSize

► 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.17

Upgrading to this version requires an additional infrastructure, to support some of it’s functionality. The requirements are listed below. In addition, it is required to perform a storage upgrade according to the listed process.

Additional packages

Please see additional installation requirements for In-process functions in this page

Storage upgrade

  1. 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.

  2. Shut down all SQreamDB services.

  3. Copy the recently created back-up file.

  4. Replace your current metadata with the metadata you stored in the back-up file.

  5. Navigate to the new SQreamDB package bin folder.

  6. 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.