/
5.0.1.rst
98 lines (65 loc) · 3.34 KB
/
5.0.1.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
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
.. _version_5.0.1:
=============
Version 5.0.1
=============
Released on 2022-09-06.
.. NOTE::
If you are upgrading a cluster, you must be running CrateDB 4.0.2 or higher
before you upgrade to 5.0.1.
We recommend that you upgrade to the latest 4.8 release before moving to
5.0.1.
A rolling upgrade from 4.8.x to 5.0.1 is supported.
Before upgrading, you should `back up your data`_.
.. WARNING::
Tables that were created before CrateDB 4.x will not function with 5.x
and must be recreated before moving to 5.x.x.
You can recreate tables using ``COPY TO`` and ``COPY FROM`` or by
`inserting the data into a new table`_.
.. _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:
See the :ref:`version_5.0.0` release notes for a full list of changes in the
5.0 series.
Fixes
=====
- Fixed a regression introduced in CrateDB ``4.3.0`` causing an
``IndexOutOfBoundsException`` when applying aggregations on literals.
Example::
SELECT SUM(10) FROM test HAVING COUNT(1) > 0
- Fixed an issue, preventing users from defining a constraint on a generated
column, when creating a table or when adding a generated column. Example::
CREATE TABLE test(
col1 INT,
col2 INT GENERATED ALWAYS AS col1*2 CHECK (col2 > 0)
)
- Fixed an issue causing ``IndexOutOfBoundsException`` to be thrown when using
``LEFT``/``RIGHT`` or ``FULL`` ``OUTER JOIN`` and one of the tables (or
sub-selects) joined has 0 rows.
- Updated the bundled JDK from 18.0.1+10 to 18.0.2+9.
- Fixed a race condition that could cause a ``INSERT INTO`` operation to get
stuck.
- Fixed an issue that could cause queries with ``objectColumn = ?`` expressions
to fail if the object contains inner arrays.
- Fixed a ``NullPointerException`` when using a ``IS NULL`` expression on an
object column that just had a child column added.
- Fixed an issue that caused ``array_upper`` and ``array_lower`` scalar
functions return wrong results on multidimensional arrays.
- Fixed exposure of the correct version a partitioned table was created on at
the ``information_schema.tables.version.created`` column for newly created
partitioned tables. This won't fix it for existing tables as the version
information the table was created with was not stored and such is not
known. The issue doesn't affect the version exposed for individual partitions.
- Fixed a column positions issue that caused an ``INSERT`` or any other
statements that adds columns dynamically to throw an exception.
- Updated the Admin UI to version 1.22.2. It includes a fix for a rendering
issue causing jumping behavior on selected views in view list.
- Fixed ``UPDATE``, ``INSERT`` and ``COPY FROM`` to preserve the implied column
order when columns are added.
- Fixed casts of strings to the ``DATE`` type, any possible time parts
of a timestamp formatted will be ignored instead of raising a cast error.
- Fixed casts of numeric and timestamp values to the ``DATE`` type, any time
values weren't removed from the returning epoch in milliseconds.
- Fixed an issue causing error when adding a check constraint to a nested
object sub column.