Skip to content
SoftClient4ES Logo SoftClient4ES

Metabase

Metabase cannot connect to SoftClient4ES today, and the blocker is on Metabase’s side.

Metabase connects only through drivers its team maintains. There is no generic JDBC database type — no menu entry where you supply a JDBC URL and a driver JAR. Anything not on Metabase’s own list requires a community driver plugin, which is a piece of software somebody has to write, build and distribute; none exists for SoftClient4ES.

(Checked against a running Metabase instance and against Metabase’s own connection documentation, 2026-08-31 and 2026-09-01.)

What this means for you

There is no configuration, no URL and no JAR placement that makes this work. Earlier versions of this page described adding SoftClient4ES as a “generic JDBC database”; that is not a Metabase feature and the instructions could not have worked.

What to use instead

If you need a self-hosted, open-source BI front end over Elasticsearch today:

  • Apache Superset — connects over Arrow Flight SQL, has a dedicated dialect, and is the closest substitute for a Metabase workload. This is the recommended path.
  • DBeaver — for SQL exploration and ad-hoc analysis over JDBC or Arrow Flight SQL.
  • Grafana — for dashboards, over Arrow Flight SQL.

All three run the cross-index JOIN that Elasticsearch cannot do natively — see the Cross-Index JOIN walkthrough.

Could this change?

Only if Metabase adds a generic JDBC database type, or if a SoftClient4ES community driver plugin is written. Neither is something a licence or a configuration change unlocks. If Metabase support matters to your evaluation, open an issue — that is how we count who needs it.

License

The JDBC driver and the Arrow Flight SQL server are licensed under the Elastic License 2.0 — free to use, not open source.