CrateDB is a distributed SQL database that makes it simple to store and analyze large amounts of machine data in real time. CrateDB offers the scalability and flexibility typically associated with NoSQL databases, and the smallest CrateDB clusters can easily ingest tens of thousands of records per second. These data can be queried in real time, temporarily, and in parallel across the entire cluster.

CrateDB 5.1.1 is officially released, and the updated content of this version is as follows:

Note: If you are upgrading a cluster, you must be running CrateDB 4.0.2 or later before upgrading to 5.1.1. It is officially recommended that you upgrade to the latest version 5.0 before upgrading to 5.1.1. Rolling upgrades from 5.0.x to 5.1.1 are supported. Before upgrading, you should back up your data.

Warning: Tables created prior to CrateDB 4.x will not work in 5.x and must be recreated before migrating to 5.xx.

repair

• fixed the blocking_id IN (SELECT ...)Problem matching records.
• Fixed an issue that could cause a class_cast_exception error when using ORDER BY on a column of type TEXT or VARCHAR.
• The logic of the parsing function was changed. Previously, it would first look for built-in functions for all patterns in the search path before looking for user-defined functions. It will now search builtins and UDFs for each schema, prioritizing UDFs earlier in the search path over builtins later in the search path.
• Fixed a bug that could cause theobjectpart of the columnbitIssue with columns returning encoded values.
• fixed when using array(subquery) When the subquery uses ORDER BY on a different column than the one returned, it causes problems with incorrect results being returned, ie:

SELECT array(SELECT country FROM sys.summits ORDER BY height DESC LIMIT 3)

• Fixed a bug that prevented definitions with the same name as a parent object in a tablebitcolumn problem. IE:

CREATE TABLE tbl (x OBJECT AS (x bit(1)))
                  ^            ^

• fixed usingpercentileaggregation can cause out of memory errors.
• Fixed using in objectbitTypes that could cause serialization errors.
• Fixed running on partitioned tableSELECT count(*) FROM tblmay causeIllegalIndexShardStateExceptionwrong question.
• Fixed a bug that caused inserts to requirePRIMARY KEYColumns, even though they are generated and their source columns are non-null by default, ie:

CREATE TABLE test (
  id INT NOT NULL PRIMARY KEY,
  created TIMESTAMP WITH TIME ZONE DEFAULT current_timestamp NOT NULL,
  month TIMESTAMP GENERATED ALWAYS AS date_trunc('month', created) PRIMARY KEY
);

INSERT INTO test(id) VALUES(1);

• Fixed an issue that could cause COPY FROM, INSERT INTO, UPDATE, and DELETE operations to get stuck under memory pressure.
• Fixed an issue that did not allow successful execution of queries with OFFSET greater than 0 but without LIMIT, namely:

SELECT * FROM test OFFSET 10
SELECT * FROM test LIMIT null OFFSET 10
SELECT * FROM test LIMIT ALL OFFSET 10

• fixes the cause ofcol IS NULLProblem with matching empty objects.
• Fixed a bug that caused ARRAY_COL = []Problem throwing an exception on OBJECT, GEO_SHAPE, IP, or BIT array element types.
• Fixed an issue that would cause queries that read values ​​of type BIT to return incorrect results if the query contained a WHERE clause k_col = ? condition.
• Fixed an issue that prevented NOT NULL constraints on GEO_SHAPE columns from showing up in SHOW CREATE TABLE statements.

For details, please refer to the update instructions.