Starburst Enterprise Platform Support Clarification Regarding Trino Community Connectors

This notice clarifies Starburst’s stance on Trino community connector support in Starburst Enterprise Platform.

Summary:

• Trino Community Connectors are not supported by Starburst. They are supported via the Trino community
• You may request formal support of a Community Connector via your Account Team
  

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

While Starburst does not support the Community Connectors directly, they will remain accessible and usable within Starburst Enterprise for the foreseeable future. However, Starburst reserves the right to remove any Community Connector from our distribution if it causes stability or security issues on the platform.

We consider certain community plugins (AKA “connectors’)  important to the daily operation of the Starburst Enterprise Platform. The following plugins are supported by Starburst:

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