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.

472-e STS (17 Apr 2025)#

  • The following HTTP client property prefixes have been renamed:

    • workerInfo to worker-info

    • memoryManager to memory-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-headers

    • hive.metastore.http.client.authentication.type

    • hive.metastore.http.client.bearer-token

    • hive.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 fetchSize in the JDBC connection URL. You must remove fetchSize from your connection-url property and use the db2.fetch-size property 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_generation session property and the optimizer.optimize-hash-generation configuration 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.host to hive.metastore.unity.host

    • delta.metastore.unity.catalog-name to hive.metastore.unity.catalog-name

    • delta.metastore.unity.access-token to hive.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.