Version 6.1.2

Released on 2025-12-10.

Warning

Do not use this version when upgrading from any previous version containing tables created before Version 5.5.0 as this may result in data loss!

If the cluster contains tables created before Version 5.5.0, after upgrading to Version 6.1.2 certain actions on such tables like deleting partitions, changing settings, rename, swap, etc. can lead to corrupted table which causes all the data of the columns created in versions before Version 5.5.0 to be shown as NULL. The bug has been fixed in Version 6.1.4, so we highly recommend to avoid upgrading to any earlier 6.1.x version.

Once already affected by the bug, existing data may be lost forever, while new data (via INSERT or UPDATE) can be retrieved normally.

Note

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

We recommend that you upgrade to the latest 6.0 release before moving to 6.1.2.

A rolling upgrade from >= 6.0.2 to 6.1.2 is supported. Before upgrading, you should back up your data.

Warning

Tables that were created before CrateDB 5.x will not function with 6.x and must be recreated before moving to 6.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 6.1.0 release notes for a full list of changes in the 6.1 series.

Fixes

  • Fixed length function that incorrectly returned 2 for supplementary Unicode characters instead of 1.

  • Added forward compatibility for cast function representation used in CrateDB 6.2.0+. As a side effect this also improves the performance of implicit casts.

  • Fixed an issue that caused SELECT COUNT(NULL) FROM tbl to return one record per row in the table instead of a single row with value 0.

  • Fixed a hash collision issue resulting in some unmatched rows not being returned when using a LEFT JOIN query with an equal join condition. Example:

    SELECT * FROM t1 LEFT JOIN t2 ON t1.id = t2.id;

  • Fixed EOFException and unexpected byte errors that could be raised when using the percentile aggregation.