Version 1.1.3¶
Released on 2017/05/09.
Note
If you are upgrading a cluster, you must be running CrateDB 0.57.0 or higher before you upgrade to 1.1.3.
If you want to perform a rolling upgrade, your current CrateDB version number must be Version 1.1.1 or higher. If you want to upgrade from a version prior to this, the upgrade will introduce all of the breaking changes listed for Version 1.1.0, and will require a full restart upgrade.
Warning
Before upgrading, you should back up your data.
Table of contents
Changelog¶
Fixes¶
Admin UI improvements.
Improved the accuracy of results if arithmetic operators (
+
,-
,*
, and/
) are used in expressions that contain only float-type values.Fixed
COPY FROM
to be able to copy data into a partitioned table with a generated column as both the primary key and a partition column.Fixed a
NullPointerException
which occurred when selectingrouting_hash_function
orversion
columns fromsys.shards
for blob tables.Fixed error thrown when applying filtering, ordering or limit on joins with more than 2 tables.
Fixed issue which lead to an object’s column policy being changed to the default
DYNAMIC
when adding a nested object column using theALTER TABLE
statement.Fixed an issue with
regexp_replace
: In some cases it used the third argument as flags parameter instead of the fourth argument.Improved error message when trying to update an element of an array.
Fixed a regression that lead to
ArrayIndexOutOfBoundsException
if aJOIN
query was made with a WHERE clause on partition columns.Fixed a
NullPointerException
which could occur if an attempt was made to usematch
on two different relations within an explicit join condition. This now raises a proper error stating that it’s not supported.Wrong results were returned from queries with more than one level of nested subselects.
ORDER BY
on joins caused incorrect order of values when having multiple non-distinct values on the left part of the join. NowORDER BY
is correctly applied.The usage of
DISTINCT
in a query with aGROUP BY
was producing wrong results and was changed to throwUnsupportedOperationException
. E.g.:SELECT DISTINCT col1 FROM t1 GROUP BY col2, col1
An error was thrown when using
ORDER BY COUNT(*)
onJOINS
. E.g.:SELECT COUNT(*) FROM t1, t2 ORDER BY 1