Elassandra
Elassandra embeds OpenSearch in Apache Cassandra so each node provides distributed storage and search.
What Elassandra is
Elassandra embeds OpenSearch in Apache Cassandra so each node provides distributed storage and search. Its maintained line targets Apache Cassandra 4.0.x, OpenSearch 1.3.x, and Java 11. An OpenSearch index maps to a Cassandra keyspace, while documents map to rows and indexed fields to columns or cells. Cassandra holds durable data; after a restart, Elassandra can replay that state and rebuild the local search view. Search requests can use the OpenSearch HTTP API or CQL, with standard OpenSearch-style responses. Schema can be created from an OpenSearch index or discovered from an existing Cassandra schema through OpenSearch mappings. Data placement follows Cassandra token ownership, and replication follows the keyspace settings. Deployment options include tarball, Debian package, RPM, Docker image, and Helm chart; integrations include OpenSearch plugins, OpenSearch Dashboards, and Spark. Elassandra requires the Murmur3 partitioner. Search indexing adds work to Cassandra writes, and immediate search visibility can increase write latency; synchronous refresh also adds cost. Its current line focuses on embedded OpenSearch, so advanced upstream features should be validated before production use.
Good
- Combines distributed storage and search in each node
- Search through OpenSearch HTTP API or CQL
- Offers tarball, package, Docker, and Helm deployments
- Open source and listed as free
Watch out
- Requires the Murmur3 partitioner
- Search indexing adds work to Cassandra writes
- Immediate search visibility can increase write latency
- Advanced upstream features need validation before production use
Who it suits
Elassandra suits teams seeking Cassandra-backed distributed storage with OpenSearch-compatible search interfaces. It is self-hosted and requires the Murmur3 partitioner.
Verdict
Elassandra connects Cassandra durability and distribution with OpenSearch-style search. Account for the partitioner requirement, write overhead, and search freshness trade-offs when assessing it.
The facts
Each one read from Elassandra's own pages, with the date it was checked.
What it does
- APIs
- Elassandra exposes Cassandra-backed documents through OpenSearch-compatible HTTP APIs and also supports searching through CQL.checked 3 Oct 2026
- Consistency limit
- Document version fields such as _version, _seq_no, and _primary_term are not globally authoritative conflict controls.checked 3 Oct 2026
- Current stack
- The maintained line targets Apache Cassandra 4.0.x, OpenSearch 1.3.x, and Java 11.checked 3 Oct 2026
- Data durability
- Cassandra is the durable storage layer, and Elassandra rebuilds the local search view from Cassandra state when needed.checked 3 Oct 2026
- Data model
- Elassandra maps OpenSearch indices to Cassandra keyspaces, documents to rows, and indexed fields to columns or cells.checked 3 Oct 2026
- Deployment
- The documentation lists tarball, Debian package, RPM, Docker image, and Helm chart installation options.checked 3 Oct 2026
- Deployment options
- The documentation lists tarball, Debian package, RPM, Docker image, and Helm chart installation options.checked 3 Oct 2026
- Durability
- Cassandra is the durable storage layer, and restart recovery replays Cassandra state and can rebuild the local search view.checked 3 Oct 2026
- Feature scope
- The current line focuses on embedded OpenSearch, and the documentation advises validating advanced upstream features before relying on them in production.checked 3 Oct 2026
- Index deletion limit
- Deleting an index removes search metadata and files but does not delete its backing Cassandra keyspace or table by default.checked 3 Oct 2026
- Integrations
- The documentation lists integration with OpenSearch plugins, OpenSearch Dashboards, and Spark.checked 3 Oct 2026
- Local resource guidance
- The quick start says each node usually needs around 1.5 GB to 2 GB of RAM for local demos.checked 3 Oct 2026
- Maintained stack
- The documented maintained line targets Apache Cassandra 4.0.x, OpenSearch 1.3.x, and Java 11.checked 3 Oct 2026
- Operational limit
- Elassandra requires the Murmur3 partitioner, and search indexing adds work to Cassandra writes, especially for complex documents.checked 3 Oct 2026
- Operational requirement
- Elassandra requires the Murmur3 partitioner.checked 3 Oct 2026
- Purpose
- Elassandra embeds OpenSearch inside Apache Cassandra so each node provides distributed storage and distributed search.checked 3 Oct 2026
- Refresh trade-off
- Immediate search visibility after a write trades off against write latency, and synchronous refresh adds cost.checked 3 Oct 2026
- Scaling
- Data placement follows Cassandra token ownership, and replica behavior follows Cassandra keyspace replication.checked 3 Oct 2026
- Schema workflows
- Elassandra supports creating Cassandra schema from an OpenSearch index or discovering an existing Cassandra schema through OpenSearch mappings.checked 3 Oct 2026
- Search freshness
- Refresh scheduling is separate from Cassandra replication, so immediate search visibility trades off against write latency.checked 3 Oct 2026
- Search interfaces
- Search requests can use the OpenSearch HTTP API or CQL, and Elassandra returns standard OpenSearch-style search responses.checked 3 Oct 2026
- What it does
- Elassandra embeds OpenSearch inside Apache Cassandra so each node serves distributed storage and distributed search.checked 3 Oct 2026
Where it runs
- Search and storage mapping
- An OpenSearch index maps to a Cassandra keyspace, and the current `_doc` model maps to a Cassandra table.checked 3 Oct 2026
Alternatives to Elassandra
- 1

Apache Cassandra
Free planOpen sourceWebAPILinuxmacOS7.7Free plan - 2
Apache HBase
Free planOpen sourceAPILinuxSelf-hosted7.1Free plan - 3

Google Cloud Bigtable
Free planWebAPI6.8From $0.03 a month - 4

Amazon Keyspaces
Free planWebAPI6.4Free plan - 5

Azure Cosmos DB for NoSQL
Free planAPISelf-hosted6.3Free plan - 6
Apache Accumulo
Free planAPILinuxSelf-hosted6.0Free plan
