Release 433-e STS (12 Jan 2024)#

Starburst Enterprise platform (SEP) 433-e is the follow up release to the 429-e version. It includes all improvements from the following Trino releases:

This release is a short term support (STS) release.

Breaking changes#

  • This release includes some changes to how Ranger policies are evaluated that may require policy modifications. If you use Apache Ranger for role-based access control, read the migration guide.

  • This release removes RubiX, Apache Sentry, and Hive Alluxio from the Hive connector. If your existing deployment relies on these technologies and you wish to use the legacy Hive connector, contact Starburst Support for assistance.

  • The query.max-writer-tasks-count configuration property has been renamed to query.max-writer-task-count, and its corresponding session property max_writer_tasks_count renamed to max_writer_task_count. These properties must be renamed in your cluster configuration or the cluster fails to start.

  • The built-in access control REST API has been updated. Grants for functions are now created for all functions in a catalog (catalog.*), all functions in a catalog’s schema (catalog.schema.*), or for a specific function (catalog.schema.function). API requests that only describe the function name must be updated or validation fails with an error.

  • Older versions of the Trino CLI and JDBC driver now fail when attempting to run RESET/SET SESSION AUTHORIZATION statements. To use these statements, upgrade to the latest versions of these clients. As a best practice, always use the client version matching the SEP cluster version.

  • The hive.metastore-timeout catalog configuration property has been removed in favor of the hive.metastore.thrift.client.connect-timeout and properties. This property must be removed from your catalog configuration files to allow successful startup.

  • The experimental.late-materialization.enabled and configuration properties have been removed. These properties must be removed from your cluster configuration to allow successful cluster startup.


  • Added support for Java 21.

  • Added Principal and User/principal as filter attributes in Insights query overview and as general information under Insights query details query details.

  • Added support for keyboard shortcuts in the query editor.

  • Fixed an edge case where query history displayed incorrect results.


  • SCIM is now in general availability.

  • Added the ability to assign a SCIM user to a role from a drop-down menu from anywhere in the BIAC UI. Users no longer have to enter information manually.

  • Added support for configuring SAML 2.0 authentication to implement single sign-on (SSO) for SEP clusters.

  • Added support for using AWS Lake Formation alongside built-in access control as a public preview.

  • Added a new resource type in Ranger and BIAC that allows users to control access to system information.

  • Added support for CREATE FUNCTION, DROP FUNCTION, and SHOW FUNCTIONS SQL functions in BIAC and in Ranger.

  • Improved performance of certain database queries when using built-in access control.

  • Upgraded Ranger to 2.4.

  • Fixed bug where user session would not log out when the web-ui.authentication.type property is set to DELEGATED-PASSWORD in capital letters.

  • Fixed access control checks for ANALYZE queries when using AWS Lake Formation.

  • Fixed a BIAC UI issue that prevented “Allow role receiving grant to grant to others” from being applied to the public role.

BigQuery connector#

Hive connector#

Snowflake connector#

  • Added support for proxy configuration to the Snowflake parallel connector.

  • Fixed an issue where managed statistics would fail for tables with OBJECT type.

Starburst Stargate#

  • Fixed an issue which caused some queries to fail when using a Stargate connection to query a BigQuery catalog.