Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add Trino 397 release notes #14194

Merged
merged 1 commit into from Sep 21, 2022
Merged

Add Trino 397 release notes #14194

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/src/main/sphinx/release.rst
View file
Open in desktop
Expand Up @@ -10,6 +10,7 @@ Release notes
.. toctree::
:maxdepth: 1

release/release-397
release/release-396
release/release-395
release/release-394
Expand Down
57 changes: 57 additions & 0 deletions docs/src/main/sphinx/release/release-397.md
View file
Open in desktop
@@ -0,0 +1,57 @@
# Release 397 (21 Sep 2022)

## General

* Fix incorrect parsing of invalid values in cast from `varchar` to `timestamp`. ({issue}`14164`)
* Fix potential incorrect results for queries with a partitioned output which
doesn't depend on any column data. ({issue}`14168`)
* Fix `EXPLAIN (TYPE IO)` query failure for certain queries on empty tables. ({issue}`10398`)

## Security

* Add support for multiple recipients with JWT authentication. ({issue}`13442 `)
* Fix OAuth 2.0 token refresh causing JWT authentication failure. ({issue}`13575`)

## JDBC driver

* Fix potential memory leak when cancelling statements. ({issue}`14176`)
colebow marked this conversation as resolved.
Show resolved Hide resolved

## Delta Lake connector

* Rename the `parquet.experimental-optimized-writer.enabled` configuration
property and `experimental_parquet_optimized_writer_enabled` session property
colebow marked this conversation as resolved.
Show resolved Hide resolved
to `parquet.optimized-writer.enabled` and `parquet_optimized_writer_enabled`,
respectively. ({issue}`14137`)

## Hive connector

* Rename the `parquet.experimental-optimized-writer.enabled` configuration
property and `experimental_parquet_optimized_writer_enabled` session property
colebow marked this conversation as resolved.
Show resolved Hide resolved
to `parquet.optimized-writer.enabled` and `parquet_optimized_writer_enabled`,
respectively. ({issue}`14137`)
* Improve performance when querying JSON data and Hive S3 Select pushdown is
enabled. ({issue}`14040`)
* Improve planning performance when querying tables in the Glue catalog that
contain a large number of columns. ({issue}`14206`)
* Allow reading from a partitioned table after a column's data type was changed
from `decimal` to `varchar` or `string`. ({issue}`2817`)
* Fix query failure when reading from a Hive view and
`hive.hive-views.run-as-invoker` and `hive.hive-views.legacy-translation` are
both enabled. ({issue}`14077`)

## Iceberg connector

* Improve performance of queries that contain predicates involving `date_trunc`
with an `hour` unit on `date`, `timestamp`, or `timestamp with time zone`
partition columns. ({issue}`14161`)
* Improve performance of reads after a `DELETE` removes all rows from a file. ({issue}`14198`)
* Reduce query latency when using a Glue catalog for metadata. ({issue}`13875`)
* Fix materalized views temporarily appearing empty when a refresh is about to
complete. ({issue}`14145`)
* Fix potential table corruption when changing a table before committing to the
Hive metastore has completed. ({issue}`14118`)
Comment on lines +51 to +52
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To me, this wording doesn't convey the meaning.
It sounds like user "changing the table" could trigger the bug, while the triggering condition was e.g. network problems between Trino and HMS.

Any reason why the wording proposed in #14154 (comment) was not used here?
I checked PR comments of this PR (#14194), but didn't spot any related discussion that would explain this.


## SPI

* Replace `DictionaryBlock` constructors with a factory method. ({issue}`14092`)
* Replace `RunLengthEncodedBlock` constructors with a factory method. ({issue}`14092`)