You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apache Calcite Avatica 1.18.0 includes a few dependency upgrades, minor fixes and a breaking change.
35
+
Please see below to determine how the breaking change will affect your project.
36
+
37
+
Compatibility: This release is tested
38
+
on Linux, macOS, Microsoft Windows;
39
+
using Oracle JDK 8, 9, 10, 11, 12, 13, 14;
40
+
using IBM Java 8;
41
+
Guava versions 14.0 to 29.0;
42
+
other software versions as specified in `gradle.properties`.
43
+
44
+
***Breaking changes***
35
45
*[<ahref="https://issues.apache.org/jira/browse/CALCITE-4503">CALCITE-4503</a>] Order of fields in records should follow that of the SQL types
36
46
37
47
`Meta#deduce(List<ColumnMetaData> columns, Class resultClazz)` now only derives the order of the fields from the list of provided column metadata `columns` when generating a record from the given Java class `resultClazz`, instead of relying on the field order provided by `Object#getFields()`, which is a JVM-dependent feature.
38
48
39
49
Before, the field names where not checked against the field names of the provided class. Now, if `resultClazz` is not null, the provided field names are expected to match existing fields in that class. If a column metadata has name `column`, and no public field in `resultClazz` with that name exists, the following exception is thrown:
0 commit comments