Client overview #

Starburst lets you query all the connected data sources with the most widely used and best supported query language — standard SQL. You can even query multiple data sources with the same query. Simple queries, and these more complex federated queries all access the data right in the source. There is no need for ETL processes.

As a data consumer, you can use any supported client tool to connect to your Starburst Galaxy or Starburst Enterprise platform (SEP) cluster and execute your queries. Many tools allow you much more powerful usage than simply running custom written queries. You can create complex reports, charts, dashboards, and many other useful results.

Starburst client tools and drivers #

Use the following clients to query data in Starburst Galaxy or Starburst Enterprise platform (SEP):

The JDBC driver, ODBC driver, and the Python client allow you to connect with many other applications. Use the Trino command line interface (CLI) for shell scripts and manual execution using a terminal.

The following sections contain further information about connection details and configuration applicable to all client tools.

Basic connection information #

The details you need to connect to Starburst are independent of your preferred client tool. For a minimum connection without TLS, you need:

• URL of the Starburst cluster, including the port used.
• Credentials, typically username and password.

Ask your Starburst platform administrator for this information.

Let’s look at some examples:

A basic test installation on your local computer, using the default port and no TLS configuration:

• http://localhost:8080
• username can be a random string like your first name since no authorization is configured
• no password

The same basic test application running on a different server:

• http://starburst.example.com:8080
• random username string
• no password

Default ports #

The following table shows the default ports for a SEP cluster:

TLS connection information #

If you enable TLS for your coordinator, you typically use a load balancer or proxy. In this case, the default port is generally used, and the protocol changes to https:

• https://starburst.example.com
• random username string
• password

TLS is a requirement for authorization against a provider’s data, such as your site’s LDAP directory. In this case, you must use real credentials:

• https://starburst.example.com
• LDAP username
• LDAP password

If your client tool uses JDBC to connect, you must enable TLS support with the SSL=true parameter in the JDBC configuration for your client, as described in Enable JDBC TLS support.

Other authorization providers may require additional credentials. Support for other providers varies among client tools.

Determine cluster version #

The version of SEP running on the cluster determines compatibility of suitable clients. Specifically important is whether the cluster is using SEP 354-e or newer, or an older release prior to the rename of the open source project. Newer versions use the name Trino, while older releases up to 350-e use the Presto or PrestoSQL name.

You can determine the version of the cluster by asking your platform administrator, or with one of the following methods, depending on your access:

• Connect a client or browser to the v1/info REST endpoint. For example, connect to http://starburst.example.com:8080/v1/info.
• Connect a modern web browser to the cluster and log in to view the SEP Web UI. For example, connect to http://starburst.example.com:8080/ui. The version number is shown on the right side of the top row.
• Connect the SEP CLI and run the following query: select * from system.runtime.nodes;

General advice #

General advice for using clients is the following:

• For clusters running SEP version 350 or earlier, use version 350 of the client.
• For clusters running SEP version 350, you can use client version 350, 354 or newer to help with migration.
• For clusters running SEP versions 354 and later, use the same version of the client as the cluster or a newer client.

This applies for the CLI and JDBC driver. Some clients, such as ODBC driver, have separate versioning, and details are documented with the client. Other clients, including open source tools like DBeaver, use the Trino name for versions 354 or newer and PrestoSQL or Presto for older versions.

Examples:

Starburst Enterprise version 360-e LTS recommended clients:

• CLI 360
• JDBC driver 360
• DBeaver with Trino connection

Starburst Enterprise version 345-e LTS recommended clients:

• CLI 350
• JDBC driver 350
• DBeaver with PrestoSQL connection