Version 1.1.4¶
Released on 2017/06/02.
Note
If you are upgrading a cluster, you must be running CrateDB 0.57.0 or higher before you upgrade to 1.1.4.
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¶
Changes¶
Improved the resiliency of the retrieval of large results via HTTP. Queries are now aborted and result in an error if they consume too much memory.
Changed the
QueryStats
JMX MBean to deliver node-based values instead of cluster-based values.This makes it possible to spot performance discrepancies between nodes more easily.
Fixes¶
Fixed a
COPY FROM
issue that caused imports into tables with certain combinations ofPARTITIONED BY
,PRIMARY KEY
andGENERATED COLUMNS
to fail.Fixed an issue with algorithm that tries to reorder the joined tables using the optimum ordering. The issue caused an exception to be thrown when join conditions contain table(s) which are not part of the adjacent joined tables. E.g.:
SELECT * FROM t1 JOIN t2 JOIN t3 JOIN t4 ON t4.id = t2.id
Fixed an issue that led to
ArrayIndexOutOfBoundsException
onDISTINCT
orGROUP BY
queries on thesys.shards
table.Fixed an issue that could cause
sys.operations
entries to remain even after the operation has finished.Optimized the JMX
QueryStats
MBean to prevent it from putting too much load on the cluster.Fixed the calculation of the
OverallQueryAverageDuration
QueryStats
MBean.The internal
fetchSize
is now dynamic based on configured heap and has an upper bound to preventOutOfMemory
errors if a PostgreSQL client retrieves a large result set without setting afetchSize
, or setting afetchSize
which is too large.Fixed a race condition that could lead to
KILL (ALL)
causing queries to get stuck instead of interrupting them.Fix an issued that cause a
NullPointerException
when ordering by system columns.Fixed validation so that
SELECT DISTINCT
can be used only if there is noGROUP BY
present or if the set ofGROUP BY
expressions is the same as the setSELECT
expressions.Added validation that
ORDER BY
symbols are included in theSELECT
list whenDISTINCT
is used.