DBeaver

The open-source tool DBeaver Community is a powerful SQL editor and universal database tool. It is installed as a local application on your workstation. You can use DBeaver with the JDBC driver to access e6data clusters.

Requirements

• Users of the e6data cluster must use DBeaver 23.3.3 or newer.

• Install the latest e6data jdbc driver.

Connection

Get the necessary connection information for your cluster:

• JDBC URL

• Username

• Password (Personal Access Token)

Connection string for Direct Connectivity Endpoint

Syntax of the JDBC URL required to establish a DBeaver connection with the e6data cluster when connecting using the earlier method:

jdbc:e6data://<host>:<port>/database=<database_name>&catalog=<catalog_name>

Connection string for TLS Connectivity Endpoint

Please refer to the syntax of the JDBC URL required to establish a DBeaver connection with the e6data cluster when connecting via endpoints:

jdbc:e6data://<host_name>:<port>/database=<database_name>&catalog=<catalog_name>&secure=true&cluster-uuid=<cluster_uuid>

Use the following steps to prepare DBeaver to access your cluster:

1. Obtain the necessary connection information for your cluster.

2. Navigate to the database section and proceed to the driver manager.

3. Create a new driver by clicking the "New" button.

4. Provide a suitable driver name.

5. Go to the "Libraries" section and add the e6data JDBC driver by clicking "Add File."

6. Click on "Find class" to proceed.

1. Go back to settings to ensure the class name is available in the provided field and create the driver.

2. Your newly created driver will be available in the database connection.

3. Navigate to the Database section and select the new database connection.

4. Now search for the same driver in the new database connection.

1. Select that driver and proceed to the next step.

2. Add the JDBC URL, username, and password, and test the connection.

JDBC Driver Class name

io.e6.jdbc.driver.E6Driver

TLS/HTTPS

e6data utilizes globally trusted certificates, ensuring that the host and port provided by the connection dialogue are adequate. Any e6data cluster necessitating authentication must also employ TLS/HTTPS. If adhering to globally trusted certificate best practices, utilize the cluster’s HTTPS URL in the connection string as detailed in the aforementioned steps.