Can I connect Apache Cassandra to iDBQuery?

Not as a native connection — iDBQuery is built for SQL and relational data, and Cassandra is a wide-column NoSQL store. To analyse Cassandra data, export the relevant tables to CSV or expose them through an API, and iDBQuery will query that in plain language with cited answers.

iDBQuery natively connects to SQL databases, spreadsheets, files, documents, REST APIs, and SQL data warehouses. Apache Cassandra is a distributed wide-column NoSQL database with its own query language (CQL) and data model, so it isn't a native SQL connection — but you can still analyse Cassandra data with iDBQuery through a truthful, standard path.

Two common approaches:

  • Export to files — dump the relevant Cassandra tables to CSV (or Parquet) on a schedule, and point iDBQuery at those. It ingests them and you query in plain language.
  • Expose through an API — if a service already reads from Cassandra and returns JSON, connect iDBQuery to that REST API and it will treat the responses as a queryable source.

Either way, once the data is in iDBQuery's model you get the full experience: plain-language questions, generated SQL, charts and dashboards, and every figure cited back to its source.

A key benefit is that you can blend that Cassandra-derived data with your relational databases and spreadsheets in one live model — for example, joining Cassandra event exports with a Postgres customer table to answer a question neither could alone.

If your Cassandra data is truly central to reporting, the durable pattern is to land it in a SQL store or warehouse (many teams already do), which iDBQuery then connects to directly.

Updated 2026-06-22