SEP breaking changes#

This page compiles all of the breaking changes introduced in each Starburst Enterprise platform (SEP) LTS release. When upgrading between SEP releases, refer to this page to address all breaking changes listed between the two.

462-e LTS (27 November 2024)#

  • Legacy file system support for all catalogs has been disabled by default. You must activate the desired file system support with fs.native-azure.enabled,fs.native-gcs.enabled, fs.native-s3.enabled, or fs.hadoop.enabled in each catalog. Use the migration guides for Azure Storage, Google Cloud Storage, and S3 to assist if you have not switched from legacy support.

  • Starburst Helm charts are no longer accessible through the ChartMuseum API. Instead, use the OCI API.

  • Secrets configuration provider setup has been updated to use secrets.toml files. The configuration-provider.config-files property is no longer supported. You must update your configuration to use secrets.toml files.

  • The query.low-memory-killer.delay configuration property has been removed. You must remove this property or the cluster fails to start.

  • The following changes have been made to Ranger access control:

    The ranger-system-access-control value for access-control.name has been deprecated and renamed to legacy-ranger-system-access-control.

    The hive-based-ranger-system-access-control access control option has been renamed to hive-based-ranger.

    The ranger value for the hive.security and delta.security catalog configuration properties has been deprecated and renamed to hive.security=deprecated-ranger and delta.security=deprecated-ranger respectively.

    It is recommended that you migrate to the new configuration in anticipation of the removal of the deprecated properties.

  • The CFT property S3PinToCurrentRegion is no longer supported.

  • The following connectors have been removed:

    • Local file

    • Atop

    • Raptor

  • The snowflake.database configuration property is now required if snowflake.database-prefix-for-schema.enabled is set to false, which is the default value. You must update existing Snowflake catalog configurations or the cluster fails to start.

  • The Glue V2 REST interface is now used by default, which does not support the following configuration properties:

    • hive.metastore-cache.cache-partitions

    • hive.metastore-cache.cache-missing

    • hive.metastore-cache.cache-missing-partitions

    • hive.metastore-cache.cache-missing-stats

    To continue using these properties, the old implementation can be temporarily restored by setting the hive.metastore catalog configuration property to glue-v1.

453-e LTS (30 Aug 2024)#

  • SEP now requires JDK 22 to run.

  • The following configuration properties and catalog configuration properties have been removed. These properties must be removed from all configurations or the cluster fails to start:

    • delta.max-initial-splits

    • delta.max-initial-split-size

    • legacy.materialized-view-grace-period

  • The PARTITION_COLUMN and PARTITION_VALUE arguments for the flush_metadata_cache procedure of the Hive connector have been renamed to PARTITION_COLUMNS and PARTITION_VALUES, respectively. The old argument names no longer work.

  • The BigQuery connector now enables Arrow serializaion by default, which requires a JVM configuration. You must either add --add-opens=java.base/java.nio=ALL-UNNAMED to your jvm.config or set the bigquery.arrow-serialization.enabled catalog configuration property to false in your BigQuery catalog configurations.

  • Phoenix versions 5.1.x and earlier are no longer supported by the Phoenix connector.

  • The Warp Speed REST API is no longer enabled by default. To enable the Warp Speed REST API, set warp-speed.config.extensions.enabled=true.

  • Warp Speed custom warmup rules are no longer stored in an external RDBMS. Warmup rules are now saved in object storage in a location specified in warp-speed.objectstore.store.path. In order to allow an existing warmup configuration to continue uninterrupted, you must export any existing rules from the external database and import them to object storage, then update your catalog configuration with the object store path.

  • The optimizer.mark-distinct-strategy and optimizer.optimize-mixed-distinct-aggregations configuration properties have been removed and are replaced by optimizer.distinct-aggregations-strategy.

  • The bigquery.parallelism configuration property has been removed as scan parallelism is now enabled by default on the BigQuery connector.

  • The hive.experimental.schema-discovery.enabled catalog configuration property has been removed as schema discovery is enabled by default. You must remove this property from the cluster configuration or SEP fails to start.

  • The privacera-starburst plugin has been removed, so access.control=privacera-starburst is an invalid configuration that must be removed from your cluster.

443-e LTS (31 May 2024)#

  • As of SEP 438-e, Starburst Warp Speed uses a new file system caching mechanism. To use Starburst Warp Speed, you must add the --enable-preview flag to your jvm.config configuration. Additionally, the following catalog configuration properties have been removed:

    • warp-speed.workerdb.db.path

    • warp-speed.file-system-reserve-percentage

    • warp-speed.call-home.enable

    You must remove these configuration properties from your cluster configuration or the cluster fails to start.

  • The Elasticsearch connector no longer supports Elasticsearch version 6.x or OpenSearch 1.x. Update Elasticsearch to version 7.x or 8.x to continue using the connector. To connect to OpenSearch, use the OpenSearch connector.

  • SEP now requires JDK 21 to run. See the Java runtime environment requirements for more information.

  • The hive.cache.enabled configuration property has been deprecated in favor of fs.cache.enabled. Remove and replace the deprecated property from all Hive catalog configurations.

  • The legacy value for hive.security has been removed, the new default value is allow-all. See Authorization for more information.

  • The following Hive authorization configuration properties have been removed. These properties must be removed from all configurations or the cluster does not start:

    • hive.allow-drop-table

    • hive.allow-rename-table

    • hive.allow-add-column

    • hive.allow-drop-column

    • hive.allow-rename-column

    • hive.allow-comment-table

    • hive.allow-comment-column

  • Removed the service-database.connection-pool.enabled configuration property from the cache service. You must remove this configuration property or the cluster fails to start.

  • The cache service now supports the same authentication methods as the SEP backend service database. As part of this change, the following cache service configuration properties have changed and must be updated in your configuration:

    • service-database.user to insights.jdbc.user.

    • service-database.password to insights.jdbc.password.

    • service-database.jdbc-url to insights.jdbc.url.

    • service-database.connection-pool.max-size to insights.jdbc.connection-pool.max-size.

    • service-database.connection-pool.idle-timeout to insights.jdbc.connection-pool.idle-timeout.

    Read more about the requirements for the cache service storage in the documentation.

  • If you are using MySQL as the externally-managed database for the cache service, you must append the parameter sessionVariables=sql_mode=ANSI to the connection string you use in the insights.jdbc.url property or the cluster fails to start.

  • This release removes the snowflake_distributed connector. You must remove or migrate existing Snowflake catalogs that use the distributed connector to the parallel connector or the cluster fails to start.

  • If you are using Oracle as the externally-managed database for the Backend service and upgrading to this version from SEP version 435-e or earlier, you must take additional steps prior to upgrading SEP. Contact Starburst Support for assistance.

  • Removed the defunct *.http-client.max-connection configuration properties. These properties must be removed from your configuration or the cluster does not start.

435-e LTS (29 Feb 2024)#

  • 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 hive.metastore.thrift.client.read-timeout properties. This property must be removed from your catalog configuration files to allow successful startup.

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

  • This release introduces some security fixes in Trino that restrict users’ ability to create new Iceberg materialized views with Glue while using the iceberg.security=system catalog configuration setting. Querying new Iceberg materialized views that fit this criteria fail and return a Materialized view does not have an owner error. See Using BIAC with Iceberg materialized views for steps to mitigate this issue.

  • The optimizer.mark-distinct-strategy configuration property has been removed. You must remove this property from the cluster configuration in favor of the optimizer.distinct-aggregations-strategy configuration property or the cluster fails to start.

  • The internal-communication.shared-secret, managed-statistics.http-client.key-store-path, and managed-statistics.http-client.key-store-password catalog configuration properties are no longer required to enable managed statistics for a catalog. You must remove these properties from your catalog configuration files or the cluster fails to start. The internal-communication.shared-secret property is still valid as a general configuration property and can remain in non-catalog configuration files.

  • This release removed support for registering external tables with CREATE TABLE and the location table property. Use the register_table procedure instead. The delta.legacy-create-table-with-existing-location.enabled configuration property and corresponding legacy_create_table_with_existing_location_enabled session property are removed as well.

429-e LTS (29 Nov 2023)#

  • The SEP backend service has been updated to require PostgreSQL 12.0+ when using PostgreSQL as the underlying RDBMS.

  • TIMESTAMP type mapping between MySQL and Trino is no longer TIMESTAMP to TIMESTAMP. The new conversion is MySQL TIMESTAMP to Trino TIMESTAMP WITH TIMEZONE. Depending on the query, mapping from MySQL TIMESTAMP to Trino TIMESTAMP may result in an error message.

  • Privileged access to the attached storage on nodes is no longer required for Starburst Warp Speed cluster configuration in Helm deployments. Existing cluster configurations must be updated, with EKS deployments requiring the addition of a boostrap script. Review and follow the considerations for your platform in the Starburst Warp Speed documentation.

  • The deprecated.hive.metastore.glue-read-properties-based-column-statistics Hive Metastore configuration property and underlying functionality has been removed. You must remove this configuration property or the cluster fails to start.

  • 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 migration guide for detailed instructions for your cloud platform.

  • 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.

  • The legacy parse-decimal-literals-as-double configuration property has been removed. Clusters that use this property must have it removed from configuration or the cluster does not start.

  • The following deprecated task writer configuration properties have been removed:

    • task.writer-count, replaced by prop-task-min-writer-count.

    • task.partitioned-writer-count, replaced by prop-task-max-writer-count.

    • task.scale-writers.max-writer-count, replaced by prop-task-max-writer-count.

    • writer-min-size, replaced by writer-scaling-min-data-processed.

    You must remove these properties from the cluster configuration and replace them with these replacement properties, or the cluster does not start.

  • The Snowflake distributed connector is now deprecated and is planned to be removed in a future SEP release, in favor of the improved Snowflake parallel connector. Existing catalogs that use the Snowflake distributed connector must be migrated to the Snowflake parallel connector.

  • The RPM package service daemon script is now deprecated and is planned to be removed in a future SEP release. Configurations that rely on this script must be updated to use the systemctl daemon script instead.

  • As of the 429-e release, privileges allowing execution of table functions such as query must be qualified with a schema. Privileges for table function execution that are still not qualified with a schema result in an Access Denied error.

  • The legacy Parquet reader has been removed from the Hive, Hudi, Delta Lake, and Iceberg connectors. The parquet.optimized-reader.enabled and parquet.optimized-nested-reader.enabled catalog configuration properties must be removed from your catalog configurations or the cluster does not start.

  • The legacy Hive readers and writers are removed in Trino, as well as other deprecated features. The following catalog configuration properties and their respective session properties have been removed:

    • *.native-reader.enabled and *_native_reader_enabled

    • *.native-writer.enabled and *_native_writer_enabled

    • hive.s3select* and s3_select_pushdown_enabled

    • hive.optimize-symlink-listing and optimize_symlink_listing

    You must remove these properties from your catalog configurations or the cluster does not start.

  • Trino 429 removed differntiation between function types in File-based access control rules. Any rules that have been reliant on function type must be updated accordingly.

423-e LTS (31 Aug 2023)#

  • Removed legacy Teradata query pass-through in favor of the query table function. The deprecated.teradata.query-pass-through.enabled property must be removed from the cluster configuration or the cluster does not start. Instead of legacy pass-through, use the query function.

  • The Trino S3 file system class was renamed from io.trino.plugin.hive.s3.TrinoS3FileSystem to io.trino.hdfs.s3.TrinoS3FileSystem. If you are using Ranger Audit to S3, update the property value in ranger-audit.xml.

  • On a cluster with built-in access control, the sysadmin role is no longer assumed automatically when querying views in DEFINER mode whose owner has the sysadmin role. For views that are no longer accessible due to this change, the privileges of the view owner must be adjusted to grant access to the underlying tables.

  • The preferredWritePartitioningMinNumberOfPartitions cache service configuration property and underlying functionality has been removed. You must remove this configuration property or table scan redirection fails.

  • The following configuration properties and command line options have been removed from the cache service and the cache service CLI:

    • The unpartitioned.writer-count, unpartitioned.scale-writers, unpartitioned.writer-min-size, partitioned.use-preferred-write-partitioning, partitioned.writer-count, partitioned.scale-writers, and partitioned.writer-min-size configuration properties have been removed from the cache service. You must remove these configuration properties or the cluster fails to start.

    • The --use-server-import-config, --use-preferred-write-partitioning, --writer-count, --scale-writers, and --writer-min-size command line options have been removed from the cache service CLI.

    • The defaultUnpartitionedImportConfig, defaultPartitionedImportConfig, importConfig in elements of rules, and incrementalImportConfig in elements of rules properties are no longer recognized in the rules.json file.

  • The following changes have been made to the LDAP group provider configuration properties related to caching:

    • The ldap.cache-ttl property has been renamed to ldap.cache.ttl. You must update your configuration settings to reflect this change.

    • The ldap.negative-cache-ttl property has been removed. You must remove this property or the cluster fails to start. Negative entries are now cached as normal entries.

  • URL extraction functions have been updated to reject invalid URIs rather than returning NULL. Queries that rely on these functions returning NULL must be updated accordingly.

  • The optimizer.use-mark-distinct configuration property has been removed. You must remove this property from cluster configuration in favor of the optimizer.mark-distinct-strategy property or the cluster fails to start.

  • The parquet.optimized-writer.enabled and parquet.optimized-writer.validation-percentage configuration properties have been removed. You must remove these properties or the cluster fails to start.

413-e LTS (30 May 2023)#

  • SEP now disallows setting access-control.name=starburst as an access control system when built-in access control is not enabled on the coordinator. If this property is configured in an access control properties file but starburst.access-control.enabled is not set to true in config.properties on the coordinator node, the cluster fails to start.

  • Upgrades to this release involve an automated migration in the backend service database. If the cluster fails to start with an error message Migration of schema "public" to version "413.2 - Category" failed, contact Starburst Support for assistance.

  • SEP configuration validation now verifies that there is no combination of insecure and secure authentication types between the web-ui.authentication.type and http-server.authentication.type configuration properties. If this validation fails, the cluster fails to start and a descriptive error message appears. It is strongly recommended to fix this misconfiguration by setting both configuration properties to secure authentication types. You may also disable configuration validation by setting starburst.config-validation.enabled=false in your config.properties file.

  • The http-server.authentication.oauth2.groups-field property was renamed to deprecated.http-server.authentication.oauth2.groups-field. You must update the property name, or the cluster fails to start.

  • The accelerated Parquet reader was removed, and replaced with an improved implementation in Trino. The catalog configuration properties iceberg.accelerated-parquet-reader.enabled, hive.accelerated-parquet-reader.enabled, and delta.accelerated-parquet-reader.enabled, and the related catalog session properties are deprecated and must be removed from catalog configurations or the cluster does not start. The new implemenetation is enabled by default, see Parquet format configuration properties for details applicable to all object storage connectors.

  • The following connector names have been removed and must be changed to allow successful cluster starts:

    • hive-hadoop2 to hive

    • memsql to singlestore

  • The following connector names have been changed. The old connector names continue to work but it is strongly recommended to change catalog configurations to the new names:

    • delta-lake to delta_lake

    • generic-jdbc to generic_jdbc

    • sap-hana to sap_hana

    • snowflake-jdbc to snowflake_jdbc

    • snowflake-distributed to snowflake_distributed

    • teradata-direct to teradata_direct

    • warp-speed to warp_speed

  • This release introduced a Trino bug that causes some INSERT INTO ... SELECT statements to fail with an “invalid offset” exception when exchange data compression is enabled as part of a Fault-tolerant execution configuration. For a temporary workaround, set the exchange.compression-enabled configuration property to false.

  • The fault_tolerant_execution_target_task_input_size and fault_tolerant_execution_target_task_split_count configuration properties for Fault-tolerant execution are deprecated and must be removed from the config.properties file or the cluster does not start.

407-e LTS (28 Feb 2023)#

  • SEP configuration validation now checks for catalog security misconfigurations that may cause security issues. If built-in access control is in use but a catalog is configured with the hive.security or delta.security configuration properties set to a value other than starburst, the cluster fails to start. The same failure occurs if the iceberg.security catalog configuration property is set to a value other than system. It is strongly recommended to fix this misconfiguration by setting all hive.security and delta.security properties to starburst and iceberg.security properties to system, but you may also disable configuration validation by setting starburst.config-validation.enabled=false in your config.properties file.

  • Built-in access control audit log now uses an improved backend schema for log storage. Existing log entries stored in the old schema are not automatically migrated to the new storage, so those older entries do not appear in the audit logs upon upgrading to this version of SEP.

  • The new SEP release requires usage of Trino Python client version 0.317 or newer.

  • The deprecated event-logger listener has been removed, and any SEP cluster configuration that uses this listener now fails to start. To resolve this, remove the event-listener.name=event-logger configuration property from any event-listener.properties configuration files.

  • If you use the Teradata direct connector, you must update the table operator. WARNING: This update is not backward-compatible. If you have multiple environments, such as a developement cluster, any cluster on a release before SEP 406-e is no longer able to connect to Teradata using the direct connector.

402-e LTS (17 Nov 2022)#

  • Users of third-party RBAC tools such as Apache Ranger and Immuta require access to several schemas in the system catalog. You must create a policy that includes system.metadata, system.jdbc, and system.runtime. Built-in access control users are unaffected, as this is handled for you.

  • The hive.metastore.glue.read-properties-based-column-statistics catalog configuration property is now deprecated, as the current configuration is considered legacy and may be removed in a future release. Existing configurations that use this property must either remove it or rename the property to deprecated.hive.metastore.glue.read-properties-based-column-statistics or the cluster does not start.

  • Trino release 401 includes a change to file-based access control which changes the default behavior of SEP with respect to table function security. From Trino 401 and later, access to table functions is allowed by default. In Trino 400 and earlier, access is denied by default. To mitigate unwanted access, you must add a function rule to deny the TABLE function type.

  • The teradata.parallelism-type catalog configuration property has been deprecated and its functionality replaced with the newer teradata.connections_count catalog configuration property. If a catalog is configured with this deprecated property, the cluster fails to start.

  • Cloudera Distributed Hadoop (CDH) version 5.x is no longer supported by the Starburst Hive connector. You must upgrade to CDH version 6.x or higher to continue querying the Cloudera Data Platform.

393-e LTS (31 Aug 2022)#

  • SEP requires Java 17 as runtime version. The scope of the necessary changes varies on your deployment method and usage of SEP, including connectors, authentication type, security integrations and other components. Thoroughly review the dedicated migration guide to determine necessary steps.

  • Renamed the optimizer.join_partitioned_build_min_row_count configuration property to optimizer.join-partitioned-build-min-row-count, which no longer accepts negative values.

  • Remove support for Kubernetes 1.18.

  • Remove support for MapR-based Hive metastore as well as the MapR filesystem.

  • The release adds a new target catalog parameter to the cloneDataProduct endpoint of the data products API. This new parameter is mandatory, which breaks existing configurations that use this endpoint.

  • If you enable snowflake.database-prefix-for-schema.enabled, any existing queries must be updated to replace schema in the fully-qualified name with "database.schema" in double-quotes. Failure to do so results in an error when the query is run.

  • The optimizer.enable-starburst-optimizer-rules property is now defunct and must be removed from config.properties if configured. Failure to do so results in the cluster failing to start. Extended Starburst optimizer properties are now enabled on all clusters.

  • The catalogname.wait-for-dynamic-filters catalog property is now defunct, and must be removed from your catalog properties files to avoid the cluster failing to start. JDBC-based connectors wait for dynamic filters collection by default. The catalogname.dynamic-filtering.wait-timeout property can be used to change the default behavior.

  • The JMX table containing metrics related to dynamic filtering for JDBC based connectors is now jmx.current."io.trino.plugin.jdbc:name=catalogname,type=dynamicfilteringstats".

  • Validation was added to data products to ensure that dataset names are SQL compliant. Datasets with an invalid name do not refresh until the name is updated to be SQL compliant.

  • The teradata.query-pass-through.enabled catalog configuration property is now deprecated, as the current configuration is considered legacy and may be removed in a future release. Existing configurations that use this property must either remove it or rename the property to deprecated.teradata.query-pass-through.enabled or the cluster does not start.

  • The http-server.authentication.oauth2.auth-url, http-server.authentication.oauth2.jwks-url, and http-server.authentication.oauth2.token-url authentication properties are deprecated.

380-e LTS (23 May 2022)#

  • The SQL Server connector now enables TLS and certificate verification by default between the cluster and SQL Server, causing potential failures for catalogs that use the connector.

  • The ldap.ssl-trust-certificate configuration property for an LDAP password authenticator has been deprecated in favor of ldap.ssl.keystore.path and ldap.ssl.truststore.path for two-way TLS with an LDAP authentication server. Clusters that use the deprecated property in their LDAP password authenticator should migrate to the new properties as soon as possible.

  • Data products title length is now limited to 40 characters. Any existing data products with titles longer than 40 characters must be deleted and recreated.

  • Require value for the shared secret configuration for internal communication when any authentication is enabled.

  • The insights.authorized-users and insights.authorized-groups configuration properties are deprecated in favor of starburst.access-control.authorized-users and starburst.access-control.authorized-groups, respectively. These starburst. configuration properties also use a comma-separated list value, instead of a pipe-delineated list like the deprecated insights. properties. For more information, see Insights general configuration properties.

  • There are new format requirements for role names using built-in access controls. Role names with spaces must be replaced. Role names can have up to 64 characters, but can only contain lowercase Latin letters, digits, and underlines.

370-e LTS (17 Feb 2022)#

364-e LTS (16 Nov 2021)#

No breaking changes since the previous LTS release.

360-e LTS (16 Aug 2021)#

356-e LTS (10 May 2021)#

This release is the first LTS release based on Trino.

All breaking changes from 354-e and the tips from the migration guide apply.

350-e LTS (3 Feb 2021)#

  • Require a minimum Java version of 11.0.7 to mitigate Java issue JDK-8206955.

  • Redshift connector changed to use the Redshift JDBC driver, users need to update the connection-url in all catalog files

  • Use consistent NaN behavior for least(), greatest(), array_min(), array_max(), min(), max(), min_by(), and max_by(). NaN is only returned when it is the only value, except for null which are ignored for aggregation functions.

  • Remove configuration properties arrayagg.implementation, multimapagg.implementation, and histogram.implementation.

  • Removed legacy Kubernetes operator, replaced by the Helm-based Kubernetes support since 338-e

345-e LTS (11 Nov 2020)#

338-e LTS (20 Jul 2020)#

332-e LTS (14 Apr 2020)#

  • The internal cluster communication in earlier Starburst Enterprise Presto supports using Kerberos for authentication. This functionality has been removed in favor of automatically securing internal cluster communication. Find more details in Secure internal communication.

  • The Starburst BigQuery connector is replaced by the open source BigQuery connector contributed by the community. The new connector is more feature-rich and performant. Users of the old connector need to change their catalog files to adapt to the usage of the new connector and its configuration properties, documented in BigQuery connector.

  • The usage of users and groups in resource groups as selector rule properties and used for catalog rules as part of the built-in system access controls is deprecated. Replace any usage with lists and regular expressions in the user and group fields. For example, change users: ["abc", "def", "xyz"] to user:  "abc|def|xyz".

  • The DECODE function has been removed from the Oracle functions plugin. Users can change their SQL statements to achieve the same behavior with the use of a CASE statement.

  • The Starburst Secrets support using a Java keystore file containing any secrets is deprecated and replaced with the secrets support from Presto. More information can be found in Secrets.

  • The query audit feature changed to use a different configuration file and properties.

  • Configuration of the path to the license for Starburst Enterprise Presto changed to use a default path. As a result, the license.path property has been removed entirely.

  • Ranger-based audit as available in prior releases is included from 332-e.2 onwards only

  • Regular Kerberos support as as Kerberos and password authentication pass passthrough for the Teradata and Teradata Parallel Direct connectors it as available in prior releases is not included, but planned for a future patch version

  • Various configuration and property changes related to Kerberos configuration in general and specifically Kerberos credential pass-through