Release 383 (1 Jun 2022)
warning
This release has a regression that may cause queries to fail.
General
- Introduce
json_exists,json_query, andjson_valueJSON functions. (#9081) - Add AWS IAM role support for exchange spooling on S3. (#12444)
- Improve query performance by reducing worker-to-worker communication overhead. (#11289)
- Improve performance and reduce memory usage of queries that contain aggregations. (#12336)
- Improve performance of correlated queries involving distinct aggregations. (#12564)
Web UI
- Clarify format of cumulative user memory on query details page. (#12596)
Accumulo connector
- Fail creating a new table if a table comment is specified. Previously, the comment was ignored. (#12452)
BigQuery connector
- Fail creating a new table if a table comment or a column comment is specified. Previously, the comment was ignored. (#12452, #12574)
Cassandra connector
- Fail creating a new table if a table comment or a column comment is specified. Previously, the comment was ignored. (#12452, #12574)
ClickHouse connector
- Fix incorrect results for certain aggregation queries when aggregations are pushed down to the underlying database. (#12598)
Delta Lake connector
- Add support for table comments during table creation.. (#12452)
- Fix incorrect
table already existserror caused by a client timeout when creating a new table. (#12300) - Fail creating a new table if a column comment is specified. Previously, the comment was ignored. (#12574)
Iceberg connector
- Add support for v2 tables for the
optimizetable procedure. (#12351) - Rename
hive.target-max-file-sizetoiceberg.target-max-file-sizeandhive.delete-schema-locations-fallbacktoiceberg.delete-schema-locations-fallback. (#12330)
Kudu connector
- Fail creating a new table if a table comment or a column comment is specified. Previously, the comment was ignored. (#12452, #12574)
MariaDB connector
- Fix incorrect results for certain queries involving aggregations that are pushed down to the underlying database. (#12598)
- Fail creating a new table if a column comment is specified. Previously, the comment was ignored. (#12574)
Memory connector
- Fail creating a new table if a table comment or a column comment is specified. Previously, the comment was ignored. (#12452, #12574)
MySQL connector
- Fix incorrect results for certain aggregation queries when aggregations are pushed down to the underlying database. (#12598)
- Fail creating a new table if a column comment is specified. Previously, the comment was ignored. (#12574)
Oracle connector
- Fail creating a new table if a table comment or a column comment is specified. Previously, the comment was ignored. (#12452, #12574)
- Fix incorrect results for certain aggregation queries when aggregations are pushed down to the underlying database. (#12598)
Phoenix connector
- Fail creating a new table if a table comment or a column comment is specified. Previously, the comment was ignored. (#12452, #12574)
PostgreSQL connector
- Fail creating a new table if a table comment or a column comment is specified. Previously, the comment was ignored. (#12452, #12574)
- Fix incorrect results for certain aggregation queries when aggregations are pushed down to the underlying database. (#12598)
Raptor connector
- Fail creating a new table if a table comment or a column comment is specified. Previously, the comment was ignored. (#12452, #12574)
Redshift connector
- Fail creating a new table if a table comment or a column comment is specified. Previously, the comment was ignored. (#12452, #12574)
SingleStore (MemSQL) connector
- Fail creating a new table if a table comment or a column comment is specified. Previously, the comment was ignored. (#12452, #12574)
- Fix incorrect results for certain aggregation queries when aggregations are pushed down to the underlying database. (#12598)
SQL Server connector
- Fail creating a new table if a table comment or a column comment is specified. Previously, the comment was ignored. (#12452, #12574)
- Fix incorrect results for certain aggregation queries when aggregations are pushed down to the underlying database. (#12598)
SPI
- Allow limiting access to functions based on whether they are scalar, aggregation, window, or table functions. (#12544)