Skip to content

Release notes

Trino Gateway 12 (7 Nov 2024)

Artifacts:

Changes:

  • Add support for parsing EXECUTE IMMEDIATE statements for routing. (#484)
  • Add support to set configuration values from environment variables. (#483)
  • Add support to include information about the cluster used for query processing to the response cookie. (#465)
  • Add support for configuring the startup command for Trino Gateway in the Helm chart with the command node. (#505)
  • ⚠ Breaking change: Require Java 23 for build and runtime. Use Java 23 as runtime in the container. (#486)
  • ⚠ Breaking change: Rename routing rule configuration blackListHeaders toexcludeHeaders. (#470)
  • Prevent request analyzer failures for some queries without a defined catalog. (#478)
  • Fix parsing failure and therefore routing problems for queries using WITH clauses. (#528)

More details and a list of all merged pull requests are available in the milestone 12 list.

Trino Gateway 11 (12 Sep 2024)

Artifacts:

Changes:

  • ⚠ Breaking change: Require Java 22 for build and runtime. (#441)
  • Add support for determining routing group in an external service. (#423)
  • Add an option to forward requests without adding X-Forwarded-* HTTP headers with the addXForwardedHeaders: false configuration in routing. (#417)
  • Add OpenMetrics endpoint to enable monitoring with Prometheus and compatible systems. (#429)
  • Add option to deactivate hostname verification for the certificate of the Trino clusters. (#436)
  • Add option to use additional paths as Trino client REST API endpoints. (#326)
  • Add timeout parameters for INFO_API and JDBC health checks. (#424)
  • Add support for specifying custom labels in the Helm chart commonLabels. (#448)
  • Enable routing for requests to kill query processing. (#427)
  • Fix routing functionality and query history issues caused by lowercase HTTP headers in HTTP/2 connections. (#450)
  • Fix failures when clients use HTTP/2. (#451)
  • Ensure that the user history dashboard displays the correct user name. (#370)
  • Fix incorrect routing of OAuth logout requests. (#455)

More details and a list of all merged pull requests are available in the milestone 11 list.

Trino Gateway 10 (24 Jul 2024)

Artifacts:

Changes:

  • ⚠ Breaking change: Remove support for Dropwizard and Jetty Proxy integration and usage. Add Airlift as the base application framework as used in Trino. This changes the supported Trino Gateway startup, configuration files, and relevant properties. Find details in the documentation, and specifically refer to the upgrade guide when migrating from older releases. (#41)
  • ⚠ Breaking change: Improve Helm chart reliability and adjust to new Airlift base framework. (#401)
  • Enable routing rules to use query and user details extracted from the HTTP request. (#325)
  • Add support for using an OIDC claim for authorization. (#322)
  • Improve OIDC spec compliance, and add state and nonce verification. (#348)
  • Allow null values for userName and source in the query history. (#381)
  • Show times in query distribution graph in UI in local time instead of UTC. (#369)
  • Fix problems with secrets, liveness, and readiness templates in Helm chart. (#348)
  • Fix cluster reordering issue in the cluster user interface. (#331)
  • Fix creation of new resource groups. (#379)

Trino Gateway 9 (8 May 2024)

Artifacts:

Changes:

  • Ensure inclusion of UI in JAR and container artifacts. (#337)

Trino Gateway 8 (6 May 2024)

Artifacts:

Changes:

  • Add support for configurable router policies. (#98)
  • Add a router policy based on query count per cluster. (#98)
  • Add a router policy for select paths based on cookie content. (#188)
  • Support configuring access permissions for UI pages. (#296)
  • Add Helm chart for Kubernetes deployments. (#87)
  • Require Java 21 for build and runtime. (#225)
  • Fix the userInfo resource to pass role information used by the API, so that the webapp authentication matches the API authentication. (#310)

Trino Gateway 7 (21 Mar 2024)

Artifacts:

Changes: * Replace user interface with a new modern UI. (#116) * Improve logging configurability. Users must update to the new logging configuration. (#260) * Improve Trino cluster health check performance and remove authentication requirement by using the v1/info endpoint. (#264) * Fix query id tracking based on request querystring parsing. (#265)

Details about all pull requests and issues

Trino Gateway 6 (16 Feb 2024)

Artifacts:

Changes:

  • Add Docker container build, publishing, and usage setup and instructions. (#86)

Details about all pull requests and issues

Trino Gateway 5 (24 Jan 2024)

Artifacts:

Changes:

  • Add support for OAuth 2 audience use. (#164)
  • Add quickstart scripts and documentation. (#110)
  • Add project logo. (#111)
  • Prevent ignoring HTTP header configuration. (#100)

Details about all merged pull requests

Trino Gateway 4 (30 Nov 2023)

Artifacts:

Changes:

  • Add support for configuring additional whitelisted URL paths. (#63)
  • Improve flexibility of user and group name matching for authorization. (#32)
  • Add support to use external URL for backend creation. (#76)
  • Enable configuration of HTTP header size. (#67)
  • Automatically set JDBC configuration parameter for TLS when connecting to clusters for monitoring. (#71)
  • Modernize application and remove potential for undiscovered bugs and security issues with update of many core dependencies. (#59)
  • Avoid failure when unhandled OIDC properties are present. (#69)
  • Prevent failures resulting from reloading and parsing rules file. (#5)

Details about all merged pull requests

Trino Gateway 3 (26 Sep 2023)

Artifacts:

Changes:

The first release of Trino Gateway is based on the Presto Gateway 1.9.5 codebase (#4) with these additions:

  • Add authentication and authorization with LDAP, OIDC and user list from config file. (#9)
  • Add support for user, admin and API roles. (#9)
  • Add healthcheck for Trino backends using JDBC. (#9)
  • Add TCP check for routing. (#9)
  • Add logic to route requests only to healthy backends. (#13)
  • Add PostgreSQL support for backend database. (#13)
  • Allow routing of /v1/node endpoint URL. (#27)
  • Filter logs for sensitive information. (#9)
  • Require Java 17 for build and runtime. (#16)
  • Deactivate clusters with zero workers. (#13)
  • Remove concurrency issue from repeated rules file loading. (#9)

Details about all merged pull requests

Breaking changes

Starting with Trino Gateway 10, release note entries include a ⚠ Breaking change: prefix to highlight any changes as potentially breaking changes. The following changes are considered and may require adjustments:

  • Removal or renaming of configuration properties that may prevent startup or require configuration changes.
  • Changes to default values for configuration properties that may significantly change the behavior of a system.
  • Updates to the requirements for external systems or software used with Trino Gateway.
  • Non-backwards compatible changes which may require router modules to be updated.
  • Otherwise significant changes that requires specific attention from teams managing a Trino Gateway deployment.