clients > Gather connection information

Gather connection information #

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:

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

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:

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

Note: When connecting to Starburst Galaxy, some tools require the / between the username and role value to be URL encoded with %2F. A username in the form username@example.com/accountadmin must be entered as username@example.com%2Faccountadmin.

Default ports #

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

Port	Connection type
8080	Direct to coordinator, no security enabled
8443	Direct to TLS-enabled coordinator
80	Connect through load balancer or proxy server
443	TLS-enabled load balancer or proxy server

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 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:

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.

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 #

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.

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

Note: If you encounter an error message on connection stating “Session properties cannot be overridden once a transaction is active”, enable Auto commit or the equivalent setting in your client. Refer to your client’s documentation for information on where to configure this setting.

Is the information on this page helpful?

Yes

Skip

Gather connection information