Release 360-e LTS (16 Aug 2021)#

Starburst Enterprise platform (SEP) 360-e is the follow up release to the 359-e STS release and the 356-e LTS release.

This release is a long term support (LTS) release.

The 360-e release includes all improvements from the following Trino project releases:

It contains all improvements from the Starburst Enterprise releases since 356-e LTS:

Highlights since 356-e#

  • ARM64 and AWS Graviton support

  • Add support for Oracle and MySQL as backing RBDMS for Insights

Breaking changes since 356-e#

The breaking changes from 359-e for Hive connector name, Java version, and discovery URL apply.

The breaking change from 358-e for the JDBC driver applies.

As any release since 354-e, this release is based on Trino and the information in the migration guide needs to be taken into account.

360-e initial changes#

The following changes from 360-e.0, 360-e.1, and 360-e.2 are all part of the first public release.


  • Add integration with Apache Atlas.

  • Add new Starburst DynamoDB connector.

  • Starburst Insights

    • Add multiple tab support in Worksheet.

    • Extend date filters in Usage metrics.

    • Add estimated cost control in Usage metrics.

    • Extended usage metrics data with additional dimensions, like node environment, version, and instance id.

    • Add automatic upload of usage metrics data to Starburst


Delta Lake connector#

  • Improve read performance for Parquet files

  • Add ANALYZE support

  • Add support for table scan redirection

Hive connector#

  • Improve read performance for Parquet files

  • Improve effectiveness of dynamic filtering

Greenplum connector#

  • Fix incorrect incorrect pushdown of large dynamic filters as range predicates on char and varchar columns for JDBC connectors where the remote database is case-insensitive or follows a different sort ordering for letters from Trino

MySQL connector#

  • Add support for authentication with AWS IAM

PostgreSQL connector#

  • Add support for authentication with AWS IAM

Salesforce connector#

  • Expose Salesforce API usage and limits in system information

Teradata connector#

  • Fix queries failing with No nodes available to run query

360-e.3 changes (7 Sep 2021)#

  • Fix invalid result when two decimals are added together. This happened in certain queries where decimals had different precision.

  • Fix incorrect result when using the BigQuery TIME type.

  • Fix incorrect results for queries with a comparison between a VARCHAR column and a CHAR constant.

  • Fix query failure when inserting data into a Hive ACID table that is not explicitly bucketed.

  • Fix Sentry access control incorrectly assigning roles from the local system instead of LDAP.

  • Improve performance of updating Glue table statistics for partitioned tables.

  • Change default Glue statistics read/write parallelism from 1 to 5.

  • Stop writing the CData OEM key to server logs when the Salesforce connector is configured with an invalid connection URL.

  • Fix an “Overflow detected” error message when compressing incompressible data with ZSTD.

360-e.4 was skipped

360-e.5 changes (22 Sep 2021)#

  • Fix incorrect results of BigQuery parameterized NUMERIC type.

  • Fix locking of non-partitioned transactional tables.

  • Fix reading Delta Lake multipart checkpoints.

  • Support case insensitive name matching to BigQuery views.

  • Fix security vulnerability in Okta authentication.

360-e.6 changes (13 Oct 2021)#

  • UPDATE now supports subqueries in SET assignments.

  • Add support for deprecated BITPACKING encoding for nulls in Parquet flat readers.

  • Fix failure in WITH RECURSIVE CTE.

  • Fix infinte loop in optimizer.

  • Fix UPDATE with multiple identical values.

  • Fix failure for queries containing ORDER BY ... LIMIT when columns in the subquery are known to be constant.

  • Fix QueryResult returns empty results for retries.

  • Fix incorrect result for comparisons between zero-valued decimals.