Version 3.1.3

    Note

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

    We recommend that you upgrade to the latest 3.0 release before moving to 3.1.3.

    If you want to perform a rolling upgrade, your current CrateDB version number must be at least . Any upgrade from a version prior to this will require a full restart upgrade.

    Warning

    Tables that were created prior to upgrading to CrateDB 2.x will not function with 3.1 and must be recreated before moving to 3.1.x.

    Before upgrading, you should .

    • Updated the Admin UI to 1.10.4 which includes the following fixes:

      • Fixed an issue that caused the cluster and node checks to not be refreshed when clicking on the refresh icon.

      • Fixed the navigation component to allow opening URLs in new tabs.

    • Fixed a race condition that could allow the creation of partitions with a different schema than other partitions within the same partitioned table.

    • Removed the conf_location hdfs repository parameter as it is no longer used.

    • Fixed a memory leak in the MQTT ingest service.

    • Fixed a memory leak that could occur with clients connecting via PostgreSQL protocol and invoking read queries with statements containing expressions that would fail (such as 1 / 0).

    • Fixed an issue in the PostgreSQL wire protocol that could result in nodes crashing with if clients queried very large tables without specifying the fetch size.

    • Fixed an issue that caused missing privilege errors if table aliases were used.