Starburst Enterprise Platform support updates about Trino community connectors

This notice clarifies Starburst’s stance on Trino community connector support in Starburst Enterprise Platform and provides detailed information about upcoming changes to ensure our customers understand and are well-prepared for the transition.

Summary:

• Trino Community Connectors are not supported by Starburst. They are supported via the Trino community
• Shortly after the 2024 Q1 Long Term Support release, Community Connectors will be removed from the distribution but will still be available for download and use
• You may request formal support of a Community Connector via your Technical Account Manager or Solution Architect

Clarification on Support for Community Connectors

Starburst does not formally support “Community Connectors.” These connectors, created by the Trino Community, are included in the Starburst distribution but have not undergone Starburst’s testing or enhancement processes. The following Connectors are Community-Based:

• Accumulo
• Atop
• Black Hole
• Cassandra
• ClickHouse 
• Druid
• Elasticsearch
• Google Sheets
• Hudi *
• Ignite
• JMX
• Kinesis
• Kudu *
• Local file
• MariaDB
• Memory
• Phoenix
• Pinot 
• Prometheus
• Redis
• System
• Thrift
• TPCDS
• TPCH

* On roadmap for formal support

Utilizing Community Connectors with Starburst

To maintain a high standard of security and reliability, we will remove Community Connectors from our core distribution after the release of the 2024 Q1 Long Term Support (LTS) distribution. While we will not support these connectors directly, they will remain accessible and usable with Starburst Enterprise. Community connectors will be available for download via the Trino project’s Maven repository, and we will provide direct links to them in our documentation, ensuring you can access them as needed.

We consider certain community plugins (AKA “connectors’)  important to the daily operation of the Starburst Enterprise Platform. The following plugins will continue to be included with Starburst moving forward:

• Black Hole
• JMX
• Memory
• System
• TPCDS
• TPCH

Requesting Formal Support for a Community Connector

We understand the importance of certain Community Connectors to your operations. Therefore, we have established a process for a Community Connector to be “promoted” to fully supported status that involves rigorous testing and due diligence by our engineering team. If you wish to request formal support for a specific Community Connector, please reach out to your Starburst Technical Account Manager or Solution Architect. We will evaluate these requests in collaboration with our Engineering, Product, and Support teams to ensure alignment and clarity for all stakeholders.