SEP STS breaking changes#
This page compiles the breaking changes introduced in Starburst Enterprise platform (SEP) STS release 471-e and higher. When upgrading between SEP releases, refer to this page to address all breaking changes listed between the two.
479-e STS (13 Feb 2026)#
Starburst data catalog only uses the
catalog.default.location.urias the database location when the database’scatalogidmatches the value you configure incatalog.default.catalog.id. If yourcatalogiddoes not matchcatalog.default.catalog.id, you must either specify alocationUriwhen creating databases or specify a location for each table explicitly, or queries against those tables fail.As of SEP 479-e, integration with Apache Ranger Admin 2.0.0 is no longer supported. You must upgrade your Ranger Admin deployment to version 2.1.0 or higher to continue using Ranger-based authorization.
Starburst Warp Speed now requires local SSD storage on the coordinator in addition to the existing local SSDs on worker nodes. You must provision local SSD storage on the coordinator before upgrading.
The following Starburst Warp Speed features are removed:
Fast warmup
Warmup rules
Index and cache resiliency
Associated properties for configuring these features are removed:
warp-speed.config.store.typewarp-speed.store.pathwarp-speed.objectstore.*warp-speed.local-store.pathwarp-speed.enable.import-exportwarp-speed.use-http-server-portwarp-speed.call-home.*
You must remove these properties from your configuration or the cluster fails to start.
The following Delta Lake Unity Catalog managed table configuration properties have been renamed:
hive.metastore.unity.catalog-owned-table-enabledtohive.metastore.unity.catalog-managed-table-enableddelta.feature.catalogOwned-previewtodelta.feature.catalogManaged
Update existing configurations to use the new property names.
The query editor Run and troubleshoot configuration property
troubleshooting.anonymized-query-planhas been removed. Remove this property from your configuration before upgrading.
478-e STS (8 Dec 2025)#
As of SEP 478-e, the default implementation of the
ConnectorFactory#getSecuritySensitivePropertyNamemethod is abstract. This method identifies configuration properties that may contain security-sensitive information so the engine can mask their values. Custom connectors must provide their own implementation. This change affects only customers who maintain custom plugins.
472-e STS (17 Apr 2025)#
The following HTTP client property prefixes have been renamed:
workerInfotoworker-infomemoryManagertomemory-manager
If you use these properties in your configuration files, the old names are no longer recognized. Update your configurations to use the new names to avoid unexpected behavior.
The following Hive metastore HTTP client properties have been removed:
hive.metastore.http.client.additional-headershive.metastore.http.client.authentication.typehive.metastore.http.client.bearer-tokenhive.metastore.http.client.read-timeout
If your current configuration includes any of these properties, update your configuration to remove them. If left in place, you may experience connection and authentication issues when interacting with the Hive metastore.
The Db2 connector no longer supports setting
fetchSizein the JDBC connection URL. You must removefetchSizefrom yourconnection-urlproperty and use thedb2.fetch-sizeproperty instead.
471-e STS (1 Apr 2025)#
The minimum required Java runtime for the JDBC driver and CLI has been updated to Java 11. If you are using an earlier version, you must upgrade to Java 11 or later.
The
optimize_hash_generationsession property and theoptimizer.optimize-hash-generationconfiguration option have been removed. You must remove these properties from your configuration or the cluster fails to start.The following Unity catalog metastore configuration properties have been renamed in the Delta Lake connector:
delta.metastore.unity.hosttohive.metastore.unity.hostdelta.metastore.unity.catalog-nametohive.metastore.unity.catalog-namedelta.metastore.unity.access-tokentohive.metastore.unity.token
Update these properties in your catalog configuration file or the cluster fails to start.
The Kinesis connector has been removed. Update your dependencies and configurations to use an alternative connector.