Version 6.3.1

Released on 2026-04-14.

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.3.1 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.3.2, so we highly recommend to avoid upgrading to any earlier 6.3.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.3.1.

We recommend that you upgrade to the latest 6.2 release before moving to 6.3.1.

A rolling upgrade from >= 6.2.0 to 6.3.0 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.3.0 release notes for a full list of changes in the 6.3 series.

Fixes

  • Fixed an issue that caused ALTER COLUMN to require super user permissions, instead of DDL privileges on the table.

  • Fixed an issue that caused empty statements to require super user permissions.

  • Fixed a regression introduced in 6.3.0 that prevented azure repositories to use the default endpoint if not set explicitly.

  • Fixed an issue that caused a Function [...] is not a scalar function. error if using a parameter placeholder as argument to an aggregation function used in the HAVING clause.

  • Fixed an issue that caused tables created by logical replication subscriptions to not receive schema or data updates from a published table, if a publisher cluster’s primary shards were active on polling the state and became inactive before restoring started (for example, due to shards relocation).