Can I connect Elasticsearch or OpenSearch to iDBQuery?

iDBQuery natively connects to SQL databases, spreadsheets, files, documents, REST APIs, and SQL data warehouses. Elasticsearch and OpenSearch are distributed search and document engines built for full-text search and log analytics, so they aren't a native SQL connection — but you can still bring their data into iDBQuery honestly.

Two practical paths:

• Use their REST API — Elasticsearch and OpenSearch expose HTTP APIs (including SQL-style query endpoints). Connect iDBQuery to that API as a REST source and it will treat the responses as a queryable dataset.
• Export to files — snapshot or export the indices you care about to CSV or JSON, and point iDBQuery at those.

After that, you get the full iDBQuery experience: ask in plain language, iDBQuery writes the query, and every figure is cited back to its source.

The advantage is unification. Log or event data from Elasticsearch can be blended with your relational databases and spreadsheets in one live model — for instance, joining error-log counts from Elasticsearch with a customer table in Postgres to see which accounts are hitting the most issues.

For heavy, ongoing reporting, teams often route Elasticsearch data into a SQL store or warehouse; iDBQuery connects to that directly and gives you cited, plain-language analytics over it.