Version 5.10.3

Released on 2025-03-18.

Note

If you are upgrading a cluster, you must be running CrateDB 4.0.2 or higher before you upgrade to 5.10.3.

We recommend that you upgrade to the latest 5.9 release before moving to 5.10.3.

A rolling upgrade from 5.9.x to 5.10.3 is supported. Before upgrading, you should back up your data.

Warning

Tables that were created before CrateDB 4.x will not function with 5.x and must be recreated before moving to 5.x.x.

You can recreate tables using COPY TO and COPY FROM or by inserting the data into a new table.

Table of contents

See the Version 5.10.0 release notes for a full list of changes in the 5.10 series.

Fixes

  • Fixed an issue that would prevent users with DDL privilege on CLUSTER level, to execute DROP ANALYZER, thus before the fix, only allowing the crate superuser to execute DROP ANALYZER statements.

  • Fixed an issue that caused a float vector column to be created with length exceeding the maximum.

  • Fixed an issue that prevented the use of custom analyzers with shingle token filters.

  • Fixed an issue that would prevent usage of a column with a custom ANALYZER which has been added to a table with ADD COLUMN. The fix doesn’t apply for columns which were already added to tables after their creation before Version 5.10.3. Those columns need to be dropped and recreated.

  • Fixed a regression introduced in Version 5.10.0 that caused tables become unavailable after ALTER TABLE RENAME statements followed by a cluster restart.

  • Fixed a regression introduced in Version 5.10.0 that caused settings set by the SET GLOBAL TRANSIENT statement be persisted and survive cluster restart.

  • Fixed a regression introduced in Version 5.10.0 that caused CREATE SNAPSHOT to write more data and, as a consequence, use more memory when creating incremental snapshots and reading data of the previously taken snapshots and fail with OutOfMemoryError under memory pressure.

  • Fixed an issue that caused selecting from partitioned tables created before Version 5.5.0 to falsely return NULL values.

  • Fixed an issue that caused selecting from partitioned tables created before Version 5.5.0 to return oids as column names of the result set.

  • Fixed an issue that caused replica shards of partitioned tables created before Version 5.5.0 to fail to be allocated.