Version 2.1.9

Released on 2017/11/08.

Note

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

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

Consult the upgrade notes for Version 2.1.0 when upgrading.

Warning

Before upgrading, you should back up your data.

Table of Contents

Changelog

Fixes

  • Fixed an issue that caused extra spaces to be added to the formatted console results in the Admin UI.

  • Fixed issue that caused NULL values to be displayed as empty objects in the console view of the Admin UI.

  • Fixed an issue that prevented the complete graceful shutdown of CrateDB node.

  • Fixed an issue that caused a NullPointerException for queries that use the IN or ANY operator on timestamp fields.

  • Improves resiliency of COPY FROM and INSERT FROM SUBQUERY statements when lot of new partitions will be created on demand.

  • Fixed a NullPointerException which could occur when joining four tables with a join condition which referred to fields from the leftmost relation.

  • Fixed a problem that caused WITHIN queries to return no or incorrect results.

  • Fixed the problem that stats.breaker.* settings were not applied to the correct circuit breaker.

  • Fixed an issue that caused an error Primary key value must not be NULL to be thrown when trying to insert rows in a table that has a generated column which is used both in PARTITION_BY and PRIMARY KEY.

  • The postgres wire protocol service can now be bound to IPv6 addresses as documented.

  • Fixed an issue that resulted in aliases overriding column names when a subselect is used and a column appears in the outer SELECT multiple times, without an alias and with alias or with multiple aliases. E.g.:

    1. SELECT a, a AS newcol FROM (SELECT a FROM t WHERE a > 1)
    2. SELECT a AS newcol1, a AS newcol2 FROM (SELECT a FROM t WHERE a > 1)