Version 6.4.3 - Unreleased

Note

In development. 6.4.3 isn’t released yet. These are the release notes for the upcoming release.

Note

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

We recommend that you upgrade to the latest 6.3 release before moving to 6.4.3.

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

Fixes

  • Fixed an issue that could cause partitions of tables to be excluded from a query if the WHERE clause contained a complex expression nesting an IS NULL clause.

  • Fixed a NullPointerException that could happen if using an aggregation function as window function with a FILTER clause on a column containing NULL values.

  • Fixed an issue that could lead to an OutOfMemoryError when running a query with aggregations under memory pressure.

  • Fixed a NullPointerException that could happen if using an aggregation function as window function with RANGE..FOLLOWING on a column containing NULL values.

  • Fixed an issue that caused a string_agg aggregation to fail with IndexOutOfBoundsException error when used as a part of a window function with windows of size 1, for example ROWS BETWEEN CURRENT ROW AND CURRENT ROW

  • Fixed an issue that caused a SUM aggregation to return wrong results when used as part of a window function and a not null value being last in one window and next window having only NULL-s. An Example:

    select sum(x) OVER (ROWS BETWEEN CURRENT ROW AND CURRENT ROW)
from (
  select 10
  union all
  select null
) tbl (x);

  • Fixed an issue that could lead to a memory leak if nodes within the cluster were temporarily not reachable.

  • Fixed incorrect results in window function when using RANGE <offset> FOLLOWING/PRECEDING with ORDER BY <column> DESC.