Elasticsearch
Connect QoreDB to Elasticsearch over HTTP or HTTPS. Multiple authentication modes, a dedicated search editor, SQL mode and result streaming.
QoreDB ships a native Elasticsearch driver that talks to the cluster over HTTP (port 9200) or HTTPS. Like every other engine, it plugs into the standard DriverRegistry, so the schema browser, results grid, exports and notebooks all work the same way — with two query surfaces tailored to Elasticsearch: a search editor for the Query DSL and a SQL mode for relational-style queries.
Quick connect
Pick the Elasticsearch engine and enter the cluster address. The default port is 9200.
http://USER:PASSWORD@HOST:9200
https://USER:PASSWORD@HOST:9200
Elastic Cloud deployments are exposed over HTTPS. Paste the endpoint URL from the Elastic Cloud console and choose the authentication mode that matches your deployment.
Connection fields
| Field | Required | Notes |
|---|---|---|
| Host | Yes | Hostname or IP. Cloud endpoint for Elastic Cloud. |
| Port | Yes | 9200 by default. |
| TLS | Optional | Enable for HTTPS. Uses Rustls under the hood; no system OpenSSL required. |
| CA cert | Optional | Custom CA certificate for clusters with a private or self-signed authority. |
Authentication modes
The driver supports several authentication modes, selectable in the connection modal:
- None — for a local cluster started without security.
- Basic auth — username and password (stored encrypted in the vault).
- API key — an Elasticsearch API key, sent as the
Authorization: ApiKey …header. - Bearer token — a bearer token for token-based or service-account auth.
Search editor and SQL mode
Elasticsearch exposes two query surfaces in QoreDB:
- Search editor — write Query DSL against an index (
_searchrequests) with the results rendered in the grid. Best for full-text search, aggregations and anything that isn't easily expressed in SQL. - SQL mode — run
SELECTstatements through Elasticsearch's SQL API. Convenient for tabular exploration and for reusing SQL muscle memory across engines.
Large result sets are streamed into the grid as they arrive rather than buffered whole, so a broad query starts rendering rows immediately.
Query safety
Read operations (searches, SQL SELECT, _cat and index introspection) run freely. Operations that mutate or administer the cluster — index creation/deletion, document writes, _reindex, cluster settings — are gated by QoreDB's universal safety net: read-only mode and environment guards (dev/staging/prod) apply exactly as they do on PostgreSQL or MySQL.
Common issues
Where to go next
- OpenSearch for the API-compatible fork
- Driver limitations for the per-engine quirks
- Connection URLs for the accepted URL schemes
Stay updated on new releases
Subscribe to get product releases, new drivers notifications, and technical tutorials.