Add Trino 454 release notes

docs/src/main/sphinx/admin/fault-tolerant-execution.md

@@ -124,16 +124,11 @@ configuration properties have their default values changed to follow best
 practices for a fault-tolerant cluster. However, this automatic change does not
 affect clusters that have these properties manually configured. If you have
 any of the following properties configured in the `config.properties` file on
-a cluster with a `TASK` retry policy, it is strongly recommended to make the
-following changes:
-
-- Set the `task.low-memory-killer.policy`
-  {doc}`query management property </admin/properties-query-management>` to
-  `total-reservation-on-blocked-nodes`, or queries may
-  need to be manually killed if the cluster runs out of memory.
-- Set the `query.low-memory-killer.delay`
-  {doc}`query management property </admin/properties-query-management>` to
-  `0s` so the cluster immediately unblocks nodes that run out of memory.
+a cluster with a `TASK` retry policy, it is strongly recommended to set the
+`task.low-memory-killer.policy`
+{doc}`query management property </admin/properties-query-management>` to
+`total-reservation-on-blocked-nodes`, or queries may need to be manually killed
+if the cluster runs out of memory.
 
 :::{note}
 A `TASK` retry policy is best suited for large batch queries, but this

docs/src/main/sphinx/admin/properties-query-management.md

@@ -109,15 +109,6 @@ memory availability. Supports the following values:
 Only applies for queries with task level retries enabled (`retry-policy=TASK`)
 :::
 
-## `query.low-memory-killer.delay`
-
-- **Type:** {ref}`prop-type-duration`
-- **Default value:** `30s`
-
-The amount of time a query is allowed to recover between running out of memory
-and being killed, if `query.low-memory-killer.policy` or
-`task.low-memory-killer.policy` is set to value different from `none`.
-
 ## `query.max-execution-time`
 
 - **Type:** {ref}`prop-type-duration`

docs/src/main/sphinx/release.md

@@ -6,6 +6,7 @@
 ```{toctree}
 :maxdepth: 1
 
+release/release-454
 release/release-453
 release/release-452
 release/release-451

docs/src/main/sphinx/release/release-454.md

@@ -0,0 +1,100 @@
+# Release 454 (15 Aug 2024)
+
+## General
+
+* Add support for retrieving lightweight query information from the `/v1/query`
+  endpoint with the `pruned` query parameter. ({issue}`20843`)
+* Add support for providing configuration for a secrets provider in a
+  `secrets.toml` file in the main Trino configuration directory. ({issue}`22633`)
+* Add support for an event listener plugin that publishes events to Kafka. ({issue}`22426`)
+* Add temporary support for restoring unsafe pushdown behavior removed in
+  version 445. This can be enabled with the `optimizer.allow-unsafe-pushdown`
+  configuration property. When this mode is enabled, certain queries containing
+  expressions that may fail for some inputs may fail at runtime. ({issue}`22987`)
+* Improve performance of queries with multiple aggregations involving
+  `DISTINCT`. ({issue}`22355`)
+* {{breaking}} Improve query concurrency when memory is low by removing the
+  `query.low-memory-killer.delay` configuration property. ({issue}`22936`)
+* Avoid retrying failed filesystem operations when they will always fail. ({issue}`22678`)
+* Fix failure for queries involving {func}`json_parse` and a cast to `array`,
+  `map`, or `row`. ({issue}`22840`)
+* Fix query failure when file-based network topology is configured with the
+  `node-scheduler.network-topology.file` configuration property. ({issue}`18793`)
+
+## Web UI
+
+* Add information about which tables and routines have been referenced by a
+  query. ({issue}`20843`)
+
+## JDBC driver
+
+* Add support for the `NO_GENERATED_KEYS` option in the
+  `Connection.prepareStatement` method. ({issue}`22100`)
+* Fix the Trino username incorrectly defaulting to the name of the user running
+  the Trino process when no username is specified. ({issue}`22901`)
+
+## BigQuery connector
+
+* Add support for the `execute` procedure. ({issue}`22692`)
+
+## Delta Lake connector
+
+* Add S3 security mapping for the native S3 filesystem. ({issue}`22559`)
+* Add support for writing
+  [deletion vectors](https://docs.delta.io/latest/delta-deletion-vectors.html). ({issue}`17063`)
+* Improve performance by caching table metadata to the metastore. ({issue}`21463`)
+* {{breaking}} Rename metastore OpenTelemetry attributes from `trino.hive.*` to
+  `trino.metastore.*`. ({issue}`22866`)
+
+## Hive connector
+
+* Add support for using the `hive.metastore-refresh-interval` configuration
+  property when using Glue v2 Hive metastore. ({issue}`22706`)
+* Add S3 security mapping for the native S3 filesystem. ({issue}`22559`)
+* {{breaking}} Rename metastore OpenTelemetry attributes from `trino.hive.*` to
+  `trino.metastore.*`. ({issue}`22866`)
+* Add support for adjusting UTC-adjusted `INT64` timestamps to the timezone
+  specified in the `hive.parquet.time-zone` property when reading Parquet files. ({issue}`22577`)
+* Fix potential query failure caused by incorrect bucket column validation. ({issue}`22261`)
+* Fix error when reading `INT96` timestamps in Parquet files generated by AWS
+  Wrangler. ({issue}`22854`)
+
+## Hudi connector
+
+* Add S3 security mapping for the native S3 filesystem. ({issue}`22559`)
+* {{breaking}} Rename metastore OpenTelemetry attributes from `trino.hive.*` to
+  `trino.metastore.*`. ({issue}`22866`)
+
+## Iceberg connector
+
+* Add S3 security mapping for the native S3 filesystem. ({issue}`22559`)
+* Add support for changing a column's type from `tinyint` or `smallint` to
+  `integer`. ({issue}`19971`)
+* Improve query planning performance by caching Iceberg metadata files on the
+  coordinator. This behavior can be disabled by setting the new
+  `iceberg.metadata-cache.enabled` configuration property to `false`. ({issue}`22739`)
+* {{breaking}} Rename metastore OpenTelemetry attributes from `trino.hive.*` to
+  `trino.metastore.*`. ({issue}`22866`)
+
+## Memory connector
+
+* Fix incorrect results after truncating tables. ({issue}`22665`)
+
+## Oracle connector
+
+* Add support for specifying the JDBC fetch size with the `oracle.fetch-size`
+  configuration property. ({issue}`22670`)
+
+## PostgreSQL connector
+
+* Add support for specifying the JDBC fetch size with the
+  `postgresql.fetch-size` configuration property. ({issue}`22670`)
+* Improve performance when using the `euclidean_distance` and `cosine_distance`
+  functions on `vector` types. ({issue}`22618`)
+* Improve performance when a query contains `-dot_product` projections. ({issue}`23015`)
+* Fix failure when a user-defined type name contains uppercase characters. ({issue}`22848`)
+
+## Redshift connector
+
+* Add support for specifying the JDBC fetch size with the `redshift.fetch-size`
+  configuration property. ({issue}`22670`)