# Data sources
# Supported data sources
- AWS Athena
- AWS Redshift
- Databricks
- Denodo
- Dremio
- Google BigQuery
- H2
- MariaDB
- Microsoft SQL Server
- MySQL
- Oracle
- PostgreSQL
- Presto
- Snowflake
- Trino
# JDBC drivers
JDBC drivers are required for Ontopic Suite to establish connections with the supported data sources.
# Docker-compose
Before running Ontopic Suite, you can include the JDBC drivers in the folder jdbc or you can edit the location of your folder in the .env file adding a variable as:
JDBC_ROOT_DIR=./jdbc
JDBC drivers included in Ontopic Suite (v2026.1.0) are:
| Data source | JDBC driver file |
|---|---|
| Dremio | dremio-jdbc-driver-26.0.5-202509091642240013-f5051a07.jar |
| SQL Server | mssql-jdbc-13.2.1.jre11.jar |
| PostgreSQL | postgresql-42.7.9.jar |
| Snowflake | snowflake-jdbc-4.0.0.jar |
| Databricks | DatabricksJDBC42.jar (3.1.1) |
| H2 | h2-2.4.240.jar |
| MariaDB | mariadb-java-client-3.5.5.jar |
| Oracle | ojdbc11.jar (23.26.1.0.0) |
| Athena | AthenaJDBC42-2.2.2.1000.jar |
| Redshift | redshift-jdbc42-2.2.2.jar |
| Presto | presto-jdbc-0.296.jar |
| Trino | trino-jdbc-479.jar |
The MySQL JDBC Driver is supported but is not included in this distribution due to licensing restrictions. The MySQL JDBC Driver is licensed under the GNU General Public License (GPL) v2. Similarly, the Denodo JDBC Driver is not included in this distribution as it is proprietary.
BigQuery is also supported, but conflicting with the Dremio driver. To use BigQuery you should add the drivers in the folder jdbc and remove the conflicting Dremio JDBC driver.
Restart Ontopic Suite if it is already running.
# Kubernetes
Kubernetes includes the same JDBC drivers as the Docker-compose distribution (see table above).
# Custom JDBC drivers
Load additional JDBC drivers from an external Git repository to use drivers not included by default (such as MySQL, Denodo, or BigQuery) or to specify particular driver versions.
Configure the jdbcExternal section in your Helm values.yaml file:
ontopic-server:
jdbcExternal:
enabled: true
replaceExistingDrivers: false
sourceRepository: <repository_url>
sourceFolder: <folder_path>
Configuration parameters:
enabled: Set totrueto load drivers from the external repositoryreplaceExistingDrivers: Controls how external drivers are integratedfalse(default): External drivers are added alongside built-in driverstrue: External drivers replace all built-in drivers. Important: When enabled, your repository must include PostgreSQL and H2 drivers, as these are required for Ontopic Suite to function
sourceRepository: Git repository URL containing the JDBC driverssourceFolder: Path to the folder within the repository that contains the JDBC jar files
Authentication
If your Git repository requires authentication, create a Kubernetes secret containing your SSH deploy key:
kubectl create secret generic jdbc-private-key \
--from-file=jdbc-private-key=./secrets/jdbc-private-key
After updating the configuration, stop and start Ontopic Suite to apply the changes.
# Windows Desktop
Update of the JDBC drivers should be done when the application is not running.
# How to access the local folder of Ontopic Suite
The App is installed in C:\Program Files\OntopicSuite and contains app-specific settings and downloaded software updates.
# Add a new JDBC driver
Add it to the existing JDBC drivers directory at C:\Program Files\OntopicSuite\resources\app.asar.unpacked\src\electron\app\process-server\app\jdbc.
# Use a different directory for JDBC drivers
If you want to use your own directory for JDBC drivers, edit or create a .env file in %AppData%/OntopicSuite.
Update the environment variable JDBC_ROOT_DIR with the full path of the JDBC driver folder of your choice.
Example:
JDBC_ROOT_DIR=C:\OntopicSuite\jdbc
# AWS Marketplace
- Connect on SSH, go to the folder
/etc/ontopic-suite/jdbc. - Add your JDBC jar file (e.g. using
scp) and remove any conflicting driver, if present. - Restart Ontopic Suite with the command
systemctl restart ontopic-suite.service.