CrateDB 5.3.2 Release Notes: Bug Fixes and Improvements

CrateDB 5.3.2 has been officially released with a series of bug fixes and improvements.

Fixed issue where empty partition tables were omitted from sys.snapshots listing.

Resolved regression in 5.3.0 where a missing object in an INSERT INTO statement prevented evaluation of the DEFAULT clause for an OBJECT column.

Improved error messages for OBJECT type columns when a DEFAULT clause is provided.

Fixed regression causing INSERT INTO ... ON CONFLICT statements to confuse values and target columns, leading to validation errors or wrong data storage.

Corrected LIKE and ILIKE operators when a pattern contains ? , e.g., SELECT * FROM tbl WHERE q ILIKE '%.com?apiPath%' .

Fixed restoration of empty partition tables that previously caused all tables in a snapshot to be restored, e.g., RESTORE SNAPSHOT repo1.snap1 TABLE empty_parted .

Addressed an Azure repository issue where multiple repositories configured on the same cluster could corrupt sys.snapshots queries, create incorrect snapshots, or delete snapshots from the wrong repository.

Fixed a problem where a node under memory pressure could cause queries to hang instead of failing with a circuit breaker error.

Enhanced optimizer rules to prefer index lookups over table scans in more cases, following up on fixes from 5.2.7.

Fixed incorrect row count or SQLParseException when dropping a non‑existent table with a crate schema prefix, e.g., DROP TABLE IF EXISTS crate.doc.non_existent_table .

Improved timestamp subtraction output to match PostgreSQL behavior, returning larger units up to days (e.g., PT40H15M becomes P1DT16H15M ).

Enhanced error messages for the date_bin scalar function when the first argument of the INTERVAL type includes month or year units.

Added a workaround allowing insertion of a non‑array value into a column dynamically created as an empty array, converting empty arrays to null on query.

Fixed AssertionError when referencing a previously defined relation without an explicit join condition, e.g., a cross join followed by an inner join.

Fixed issue where default expressions for GEO_SHAPE columns were ignored during writes.

Resolved race condition when accessing multiple S3 repositories with different settings, affecting sys.snapshots queries.