forked from crate/crate
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathCHANGES.txt
77 lines (55 loc) · 2.96 KB
/
CHANGES.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
==================
Unreleased Changes
==================
This file collects *unreleased* changes only.
For release notes, see:
https://crate.io/docs/reference/en/latest/release_notes/index.html
For developers: changes should be recorded here (using RST syntax) as you are
developing CrateDB. When a new release is being cut, changes will be moved to
the appropriate section of the docs.
Breaking Changes
================
- Dropped support for tables that have been created with CrateDB prior to
version 2.0. Tables which require upgrading are indicated in the cluster
checks, including visually shown in the Admin UI, if running the latest 2.2
or 2.3 release. The upgrade of tables needs to happen before updating CrateDB
to this version. This can be done by exporting the data with ``COPY TO`` and
importing it into a new table with ``COPY FROM``. Alternatively you can use
``INSERT`` with query.
- Data paths as defined in ``path.data`` must not contain the cluster name as a
folder. Data paths which are not compatible with this version are indicated
in the node checks, including visually shown in the Admin UI, if running the
latest 2.2 or 2.3 release.
- The ``bootstrap.seccomp`` setting that controls system call filters has been
replaced in favour of ``bootstrap.system_call_filter``.
- The ``error_trace`` GET parameter of the HTTP endpoint only allows ``true``
and ``false`` in lower case. Other values are not allowed any more and will
result in a parsing exception.
- Store level throttling settings (``indices.store.throttle.*``) have been
removed.
- The gateway recovery table setting ``recovery.initial_shards`` has been
removed. Nodes will recover their unassigned local primary shards
immediatelly after restart.
Changes
=======
- CrateDB is now based on Elasticsearch 6.0.1 and Lucene 7.0.1.
- Added new ``cluster.routing.allocation.disk.watermark.flood_stage`` setting,
that controls at which disk usage indices should become read-only to prevent
running out of disk space.
- Added new tokenizers ``simple_pattern`` and ``simple_pattern_split`` which
allow to tokenize text for the fulltext index by a regular expression pattern.
- Changed ``BEGIN`` and ``SET SESSION`` to no longer require ``DQL``
permissions on the ``CLUSTER`` level.
- Implemented a `Ready` node status JMX metric expressing if the node is ready
for processing SQL statements.
Fixes
=====
- Fixed a regression which caused ``IS NOT NULL`` predicates on columns of type
``array(object)`` to not match correctly.
- Fixed an issue that caused the ``percentile`` aggregation to fail if an array
containing a single item was passed as ``fractions``.
- Fixed an issue which resulted in an exception when a routing column was
compared against a sub-query inside a ``WHERE`` clause.
- Fixed a performance regression resulting in a table scan instead of a NO-MATCH
if a sub-query used inside a ``WHERE`` clause returns no result
(https://github.com/crate/crate/issues/6773).