Release 369-e STS (1 Feb 2022)#

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

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

Breaking changes#

You need to adjust your configuration for the following Trino changes:

  • Remove distinction between system and user memory. This simplifies cluster configuration. The configuration property query.max-total-memory-per-node is removed, query.max-memory-per-node should be used instead.

  • Remove unnecessary spilling configuration properties spill-order-by and spill-window-operator.

Known issues#

  • Dynamic filtering causes a performance regression due to the new execution policy default of phased. Affects all connectors with a defined connection-url catalog property to use a JDBC driver to connect to the data source. Change to the prior default with query.execution-policy=all-at-once. A fix for the regression is part of the upcoming 370-e release.


  • Skip pre-aggregate rule on non-sum aggregation with non-null default to avoid incorrect (NULL) result when data is present.


  • Add built-in access control as experimental feature.

  • Add Immuta access control as experimental feature.

Starburst Stargate#

  • Remove memory leak occurrences.

Delta Lake connector#

  • Add support for writing to Delta Lake table created by Databricks Runtime version 9.1. Some table features like Generated Columns are not supported.

  • Prevent data loss during DROP SCHEMA when the schema location contains files that are not part of existing tables.

  • Improve SELECT performance on partitioned tables after ALTER TABLE .. EXECUTE OPTIMIZE, by creating more optimal file sizes during the table optimization.

Salesforce connector#

  • Add support for OAuth 2.0 JWT authentication

SingleStore (MemSQL) connector#

  • Add support for Kerberos authentication

Teradata connector#

  • Fix writing incorrect date <= 1582-10-14