Version 2025.1.5 Release Notes

Release date: 2025-11-21

This list provides an overview of all changes in version 2025.1.5.

Download version 2025.1.5 from the Exasol Download Portal.

Changed behavior

Changelog entry Changed behavior
27542 1. Updated packages Release 10.1.0 of the Script-Languages-Container was integrated, which provides security related updates of several Ubuntu and PyPi packages. Lists of changed packages in SLC since SLC version 9.7.0 can be found at: - https://github.com/exasol/script-languages-release/blob/master/doc/changes/package_diffs/10.1.0/README.md - https://github.com/exasol/script-languages-release/blob/master/doc/changes/package_diffs/10.0.0/README.md 2. New Python version 3.12 which can be activated with alias `PYTHON312`
27329 Confd job `infra_db_scale` no longer waits for the scaled database to be running. It still triggers a start if it was running when the job was called. Worker clusters will not be started under any circumstance.
27107 For rootless installations, "c4 _ preplay" now needs to be rerun on all the nodes before every update.
26758 Previous Behavior * Default Value Fallback for Invalid Parameters - If any of the Parquet Reader parameters were configured with invalid values (e.g., negative or zero), the database silently replaced them with default values and continued with the startup process. - Default values were applied without notifying the user, which could lead to unexpected behavior or degraded performance during database operations. - Example: If etlParquetMaxConnections was set to -10, the system would internally use the default value of 10 without informing the user about the invalid configuration. * No Explicit Error Notification - The database did not provide any error messages or feedback regarding invalid user-provided configuration values during startup. New Behavior * Strict Validation of Parameter Values During Startup - Parquet Reader parameters are now validated during database startup to ensure they meet the required conditions. - If a parameter contains an invalid value, the database will throw an Exa-operation error and abort the startup process. - Default value fallback for invalid values has been removed; users must correct the configuration to proceed. * Actionable Error Notifications - If invalid values are detected, the database generates a clear and actionable error message directed at the user. -The error message includes: -- Parameter name. -- Invalid value. -- The expected valid range. -- Suggestions to resolve the issue. * Parameter Validation Only on Node 0 - Error messages related to invalid Parquet Reader parameters are now displayed only on Node 0, making it easier to diagnose and debug issues in a distributed setup. - Reduces clutter in logs across multiple nodes and simplifies root cause identification.
25484 * The session/system variable SQL_PREPROCESSOR_SCRIPT can now also be used to select preprocessor scripts written in script languages other than Lua. * We added a new non-reserved keyword, "PREPROCESSOR".

New features

Changelog entry Summary
24691 Parquet Import – Column Mapping Support

Improvements

Changelog entry Summary
27542 Script Language Container is updated to version 10.1.0
27507 Better index selection for UNION ALL indices
26758 Validation of Parquet Reader Parameters During DB Startup
26754 c4_cloud_command service should have LimitCORE value set to infinity
26672 Improve client connection feedback interval for queued sessions
25484 Script Language support for SQL Preprocessor

Bug fixes

Changelog entry Summary
27836 Scaling a database always starts workers
27678 'first_value' could produce wrong results when combined with other aggregation functions
27677 SDFS retries on 503 when accessing to S3
27604 Restarting a system with kerberos configured fails to boot.
27520 Fix for Incorrect Weight Calculation in SQL Process Prioritizer During Consumer Group Modifications
27478 AdminUI didn’t support all standard crontab expressions for backups schedules.
27329 An infrastructure scaling operation will no longer wait for the database to be up
27310 Removing expired snapshots may block new snapshots and backups.
27160 Configuration isn’t rolled back to the previous state after an error running the ConfD job db_configure.
27107 Fixed Ubuntu upgrades restarting Exasol services
26999 Moved sessions may cause resource leakage in the connection server on the main cluster
26965 Moving sessions to another cluster may hang
26756 Unattended apt upgrades reset custom coredump file pattern
23714 Fix error messages appearing in C4 configuration parameters
21631 Index access may fail when bmi2 instructions are not supported
20772 Coredumps are not cleaned up automatically.