Version 2.0.7

    Note

    If you are upgrading a cluster, you must be running CrateDB Version 1.1.3 or higher before you upgrade to 2.0.7.

    If you want to perform a , your current CrateDB version number must be Version 2.0.0. If you want to upgrade from a version prior to this, the upgrade will introduce all of the breaking changes listed for , and will require a full restart upgrade.

    Consult the upgrade notes for when upgrading.

    Warning

    If you’re using CrateDB’s BLOB storage you should consult the Upgrade Notes.

    Due to a bug introduced in that can cause loss of BLOB data, it is necessary to perform a rolling upgrade if you’re running a version >= 2.0.0 and < 2.0.4 and using BLOB tables.

    Additionally, the number of replicas needs to be set to at least for all blob tables and you need to make sure that data is fully replicated before continuing.

    Only then you may upgrade one node after each other.

    Changelog

    Fixes

    • Fixed an issue where COPY FROM, INSERT-BY-SUBQUERY or bulk INSERT statements could not be killed when high pressure is put on data node thread pools.

    • Fixed an issue which caused an exception if is used on a statement that uses the ANY (array_expression) .

    • Fixed support for negate on null in conditional expressions.

    • Fixed support for setting write.wait_for_active_shards on a partitioned table.

    • Optimized the algorithm that determines the best ordering of the tables in a JOIN.

    • Fixed a regression causing incorrect results for queries with DISTINCT on scalar functions. E.g.:

    • Implemented constraint validation for nested object columns, which was previously ignored. E.g.:

      1. CREATE TABLE test (
      2.   stuff object(dynamic) AS (
      3.     level1 object(dynamic) AS (
      4.       level2 string not null
      5.     ) NOT NULL