/
3.2.6.rst
66 lines (43 loc) · 2.16 KB
/
3.2.6.rst
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
.. _version_3.2.6:
=============
Version 3.2.6
=============
Released on 2019/03/25.
.. NOTE::
If you are upgrading a cluster, you must be running CrateDB 2.0.4 or higher
before you upgrade to 3.2.6.
We recommend that you upgrade to the latest 3.1 release before moving to
3.2.6.
If you want to perform a `rolling upgrade`_, your current CrateDB version
number must be at least :ref:`version_3.2.0`. Any upgrade from a version
prior to this will require a `full restart upgrade`_.
When restarting, CrateDB will migrate indexes to a newer format. Depending
on the amount of data, this may delay node start-up time.
Please consult the :ref:`version_3.0.0_upgrade_notes` before upgrading.
.. WARNING::
Tables that were created prior to upgrading to CrateDB 2.x will not
function with 3.2 and must be recreated before moving to 3.2.x.
You can recreate tables using ``COPY TO`` and ``COPY FROM`` while running a
2.x release into a new table, or by `inserting the data into a new table`_.
Before upgrading, you should `back up your data`_.
.. _rolling upgrade: https://crate.io/docs/crate/howtos/en/latest/admin/rolling-upgrade.html
.. _full restart upgrade: https://crate.io/docs/crate/howtos/en/latest/admin/full-restart-upgrade.html
.. _back up your data: https://crate.io/docs/crate/reference/en/latest/admin/snapshots.html
.. _inserting the data into a new table: https://crate.io/docs/crate/reference/en/latest/admin/system-information.html#tables-need-to-be-recreated
.. rubric:: Table of contents
.. contents::
:local:
Changelog
=========
Fixes
-----
- Fixed an issue which caused an ``IndexOutOfBoundsException`` when a
:ref:`window function <window-functions>` with an ordered window was selected
in a ``JOIN`` statement.
- Fixed an issue which caused a ``NullPointerException`` when executing a
window function over an ordered window which contained null values under the
ordered column.
- Fixed an issue which causes :ref:`subselect <gloss-subquery>` queries with
certain ``ORDER BY`` constructs to fail.
- Fixed circuit breaker memory accounting of window functions to prevent *Out
Of Memory* exceptions.