The details you need to connect to Starburst are independent of your preferred client tool. This topic contains information about connection details and configuration applicable to all client tools.
For a minimum connection without TLS, you need:
Ask your Starburst platform administrator for this information.
For example, a basic test installation on your local computer, using the default port and no TLS configuration:
The same basic test application running on a different server:
/ between the username and role value to be URL encoded with
%2F. A username in the form
email@example.com/accountadmin must be
The following table shows the default ports for a SEP cluster:
|Direct to coordinator, no security enabled
|Direct to TLS-enabled coordinator
|Connect through load balancer or proxy server
|TLS-enabled load balancer or proxy server
If you enable TLS for your coordinator, you typically use a load balancer or
proxy. In this case, the default port is used, and the protocol changes to
TLS is a requirement for authorization against a provider’s data, such as your site’s LDAP directory:
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.
The version of SEP running on the cluster determines compatibility of suitable clients.
Determine the version of the cluster by asking your platform administrator, or with one of the following methods, depending on your access:
v1/info REST endpoint. For example,
http://starburst.example.com:8080/ui. The version
number is shown on the right side of the top row.
select * from system.runtime.nodes;
You must 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.
Starburst Enterprise version 360-e LTS recommended clients:
Starburst Enterprise version 345-e LTS recommended clients:
Is the information on this page helpful?