Skip to main content

DBeaver

IOMETE warehouse JDBC endpoints are compatible with Hive JDBC drivers. But due to recent SSL issues, we have released a fixed version of the driver. If you wish to use the JDBC driver must download it from our GitHub repository and include it as a library in their project.

Download the Driver​

Visit our GitHub repository iomete-artifacts and download the latest version of the Hive JDBC driver hive-jdbc-3.1.3-standalone.jar.

Using JDBC driver for DBeaver connection​

  1. Open DBeaver and navigate to the Database menu.
  2. Click on Driver Manager.
    Driver Manager | IOMETEDriver Manager | IOMETE
  3. Click on New to add a new driver.
  4. Set Driver Name as IOMETE and Driver Type Hive.
  5. Switch to the Libraries tab and click on Add File.
  6. Select the downloaded hive-jdbc-3.1.3-standalone.jar file and then in the Driver class section click Find Class (if it won't work try saving the newly created driver and edit again).
    Add File | IOMETEAdd File | IOMETE
  7. Switch back to Setting tab and make sure that driver class name are filled correctly. (Should be done automatically)
    Driver Settings | IOMETEDriver Settings | IOMETE
  8. Click OK to save the driver.

Connection settings​

In order to connect to the IOMETE lakehouse using newly created driver, click on New Database Connection and select the IOMETE driver from the list.
You can find the connection details in the IOMETE Console by navigating to the necessary lakehouse and switching to the Connections tab (Select JDBC option).

Fill the connection details as in the example image below.

Connection Settings | IOMETEConnection Settings | IOMETE
note

For the password field, you should use the Access Token key generated in the IOMETE Console.

After successfully connecting to the lakehouse, in the Database Navigator you can see the list of tables and views available in the lakehouse as in the screenshot below.

Database Navigator | IOMETEDatabase Navigator | IOMETE

Known issues​

Below is a list of known issues you may encounter when using DBeaver with the IOMETE JDBC driver. These issues are on our roadmap and will be addressed in future releases.

Schema Selection Error

When selecting an active schema from the top menu, DBeaver may throw an error indicating that the schema is not found.

Selecting Active Schema | IOMETESelecting Active Schema | IOMETE
Schema not found error | IOMETESchema not found error | IOMETE

There are two ways to workaround this issue:

  1. Use the USE statement to switch between schemas.
  2. Using fully qualified table names, e.g. catalog_name.schema_name.table_name.
Approaches | IOMETEApproaches | IOMETE
DBeaver Fully Qualified Table Names

Currently, DBeaver does not include catalog in the fully qualified table names. This may cause issues when querying tables from different catalogs. Especially when working with Database Navigator, when you copy or drag tables to the SQL editor, DBeaver does not include the catalog name which cause the query to fail with TABLE_NOT_FOUND error.

Similarly, you can workaround this issue by:

  1. Using the USE statement to switch when working with catalogs.
  2. Using fully qualified table names, e.g. catalog_name.schema_name.table_name.
Approaches | IOMETEApproaches | IOMETE

ON THIS PAGE