Release 427-e STS (16 Oct 2023)#

Starburst Enterprise platform (SEP) 427-e is the follow up release to the 426-e version. It includes all improvements from the Trino 427 release.

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

Breaking changes#

The updated base Docker image for SEP no longer includes curl, vi, nano, sed, awk, grep, and other popular command line tools. Starburst recommends using an init container with a base image that includes your needed command line tools. Guidance on using init containers and selecting suitable base images can be found in our init container documentation.
A new autoConfigure property was added to the Starburst Warp Speed Helm chart which defaults to false. Starburst Warp Speed deployments on AKS and GKE upgrading from 426-e that have already been reconfigured to use the filesystem instead of privileged mode must set this property to true or the filesystem is not created. Review and follow the considerations for your platform in the Starburst Warp Speed documentation.
SEP 427-e uses a base system image that does not contain a system-wide trust store. Trusted, self-signed certificates must now be added to the Java distribution CA certificates located under $JAVA_HOME/lib/security/cacerts.

Updated base Docker image for SEP to Red Hat UBI9 micro.
Added support for PyStarburst.
Added the insights.query-history.store-query-plan configuration property to control whether query plans are stored by the Backend service.
Fixed an issue causing errors to occur when loading query reports for queries with no defined source.

Added support for write operations on AWS Lake Formation resource links.
Added the ability for all users to access the system.metadata schema when using BIAC and Apache Ranger.
Improved an error message when there are multiple BIAC column masks present on a column.
Improved performance of filtering catalogs, schemas, tables and columns in BIAC.
Fixed an issue when querying with a resource link pointing to a Glue database in a Lake Formation-secured catalog.
Fixed an issue with BIAC where attempting to create an access policy for a catalog session property, the resulting policy will include the catalog name twice.
Fixed an issue with JavaScript policy evaluation in Apache Ranger and Privacera.

Added support for partitioned_by, bucketed_by, bucket_count, and sorted_by table properties when Iceberg is used as the catalog for materialized view storage with the materialized-views.storage-catalog catalog configuration property.