Skip to content

Custom JDBC Source Support

Okera provides the ability to specify custom JDBC drivers using the driver.jar.path and properties. Okera will try to download the JAR files on the fly for the first time from the valid driver.jar.path. This path/file, if in Amazon S3, should have appropriate IAM credentials allowing Okera to connect and download the file. For any other https:// path this file should be downloadable.

Note: This does not guarantee that Okera would support arbitrary JDBC drivers. The data type mapping can be undefined due to Okera not certifying those JDBC drivers. For example, Okera has certified that Oracle JDBC driver used as a custom driver is fully supported and documented for limitations and data type mapping.

Here is an example that adds a custom driver called mariadb:

  ''='<database to connect to>',
  ''='<schema to connect to, if required>',
For information on how Okera uses JDBC drivers, see JDBC Driver Use in Okera.