DSE Search versus open-source Apache Solr™

Because of its integration into DataStax Enterprise (DSE), differences exist between DSE Search and open-source Apache Solr™.

Capability Included in DSE Search Included in OSS Apache Solr Description

Capability	Included in DSE Search	Included in OSS Apache Solr	Description
Includes a database	Yes	No	For OSS, create an interface to add a database.
Indexes real-time data	Yes	No	Ingests real-time data and automatically indexes the data.
Provides an intuitive way to update data	Yes	No	CQL for loading and updating data.
Supports data distribution	Yes	Yes	Transparently distributes real-time, analytics, and search data to multiple nodes in a cluster. OSS Apache Solr requires using Apache ZooKeeper™.
Balances loads on nodes/shards	Yes	No	Unlike Solr and Solr Cloud, DSE Search loads can be efficiently rebalanced.
Spans indexes over multiple datacenters	Yes	No	A DSE cluster can have more than one datacenter for different types of nodes.
Makes durable updates to data	Yes	No	Updates are durable and written to the commit log for all updates.
Automatically reindexes search data	Yes	No	OSS requires the client to reingest everything to reindex data in Solr.
Upgrades of Apache Lucene™ preserve data	Yes	No	DataStax integrates Lucene upgrades periodically and data is preserved when you upgrade DSE.
Supports limiting queries by time	Yes	Yes	DSE Search supports the Solr `timeAllowed` parameter with the following differences: If `timeAllowed` is exceeded, an exception is thrown. If `timeAllowed` is exceeded and the `shards.tolerant` is set to `true`, the application returns the partial results collected so far. When partial results are returned, the CQL custom payload contains the `DSESearch.isPartialResults` key.
Supports `timeAllowed` queries with deep paging	Yes	No	OSS Solr does not support `timeAllowed` queries with deep paging.

Includes a database

Yes

For OSS, create an interface to add a database.

Indexes real-time data

Yes

Ingests real-time data and automatically indexes the data.

Provides an intuitive way to update data

Yes

CQL for loading and updating data.

Supports data distribution

Yes

Transparently distributes real-time, analytics, and search data to multiple nodes in a cluster.

OSS Apache Solr requires using Apache ZooKeeper™.

Balances loads on nodes/shards

Yes

Unlike Solr and Solr Cloud, DSE Search loads can be efficiently rebalanced.

Spans indexes over multiple datacenters

Yes

A DSE cluster can have more than one datacenter for different types of nodes.

Makes durable updates to data

Yes

Updates are durable and written to the commit log for all updates.

Automatically reindexes search data

Yes

OSS requires the client to reingest everything to reindex data in Solr.

Upgrades of Apache Lucene™ preserve data

Yes

DataStax integrates Lucene upgrades periodically and data is preserved when you upgrade DSE.

Supports limiting queries by time

Yes

DSE Search supports the Solr timeAllowed parameter with the following differences:

If timeAllowed is exceeded, an exception is thrown.
If timeAllowed is exceeded and the shards.tolerant is set to true, the application returns the partial results collected so far. When partial results are returned, the CQL custom payload contains the DSESearch.isPartialResults key.

Supports timeAllowed queries with deep paging

Yes

OSS Solr does not support timeAllowed queries with deep paging.

DSE Search versus open-source Apache Solr™

Was this helpful?

Give Feedback