Skip to main content
The JDBC gateway runs queries through vendor JDBC drivers when Planasonix does not ship a first-class connector for your engine. You upload approved driver JARs, define connection URLs, and use SQL nodes against the gateway-managed pools.

​
JDBC gateway concept

Instead of embedding drivers in every worker, the gateway:
  • Hosts driver isolation per database type and version
  • Pools connections with configurable limits
  • Translates Planasonix SQL requests into JDBC calls your database understands
  • Surfaces errors back to pipeline logs with JDBC SQLState context
Admins operate the gateway cluster; analysts reference connections the admin published.
Prefer first-class connectors when available—they include tuned pagination, metadata discovery, and CDC hooks the generic JDBC path may lack.

​
Supported databases

The JDBC path supports many engines when you supply a compatible driver. Common enterprise examples include:
EngineNotes
TeradataUse official JDBC; respect session limits on shared appliances
Apache HiveConnect to HiveServer2; watch metastore latency on wide scans
Apache DruidJDBC exposes SQL; complex ingest still uses native batch tooling
ExasolHigh-performance analytics; tune fetch size for wide rows
Netezza (PureData)Verify supported driver generation for your appliance firmware
FireboltUse Firebolt JDBC; align warehouse scaling with burst workloads
Exact support depends on driver licensing—your legal team must approve redistribution if drivers are not publicly downloadable.

​
Driver upload

1

Obtain the JAR

Download from the vendor or your internal artifact repository; verify checksums.
2

Upload in admin console

Navigate to Connectors → JDBC gateway → Drivers and upload with a descriptive label (teradata-17.20-jdbc4).
3

Create a connection template

Supply JDBC URL pattern, default properties, and credential mapping.
4

Test connectivity

Run SELECT 1 from a privileged admin account, then validate least-privilege service accounts for pipelines.
Mismatched driver and database versions cause opaque protocol errors—pin versions in change management.

​
Operational guidance

Open firewall rules from gateway hosts to database listeners; avoid NAT ambiguity with multi-subnet clusters.
Store passwords and keytabs in your vault; rotate on the same schedule as native DB users.
Tune fetch size and parallel readers based on DBA guidance; JDBC defaults are rarely optimal for ETL throughput.

Connections overview

How credentials and networking fit together.

SQL assistance

Author JDBC-backed SQL with Copilot help.