JDBC driver #
The Java Database Connectivity (JDBC) driver enables any application supporting a JDBC driver to connect to Starburst clusters. The application can then issue SQL queries and receive results.
Typically the applications are JVM-based, or support JDBC driver usage with a different mechanism. Using an applications with the JDBC driver generally follows the same steps.
Connection information #
Configure the driver #
Adding the JDBC driver to your application varies for each application.
Some applications, such as DBeaver, automatically download and configure the driver, or include it by default and no action is necessary.
Many applications, however, require you to download the driver and place it in a directory that varies for each application. Refer to the documentation of your client application for the necessary details.
The JDBC driver needs to be compatible with the version of the cluster you are connecting to.
Download the JDBC driver #
You can request the CLI for a specific version from Starburst Support.
Alternatively, to gain access to SEP archives, visit the Starburst website and click either the Get Started or Start Free buttons.
This opens a dialog that prompts for your name, email address, and location. Fill out the form using a valid email address, then click Free Download.
Click on the link to the Downloads page in the resulting email. It is organized into Long-Term and Short-Term Support sections.
Download a specific version of the CLI, based on your cluster version:
- Version 350, if your cluster version is older than 350
- Same or newer version than the cluster for versions 350, 354 and newer
You can also download the JDBC driver binary straight from the link in the reference documentation:
Use the version selector in the documentation for different releases, or contact |support|.
Create the connection to the cluster #
With a configured driver you can now configure a connections to a cluster. Typically you only need the connection information. Other details such as the JDBC URL are automatically configured in many applications, or can be seen and updated in an user interface dialog.
The main parameters are the driver classname, which is typically preconfigured by your client driver integration, the JDBC URL and the credentials from the needed connection information.
Driver version 350 and older:
- JDBC URL:
Driver version 354 and newer:
- JDBC URL:
If your application does not include these out of the box, check the reference documentation for the JDBC driver for the correct values and other supported parameters.
Start querying #
The configured connection, can now be opened and you can start running queries.
For example, if you application allows you to write and run queries you can see what catalogs are available:
Many applications provide a user interface to see the list of catalogs, schema, tables and much more.
Next steps #
Now you can take advantage of the features of your application, and potentially learning more about the SQL support in Starburst.
Is the information on this page helpful?