Using DSE Search/Solr

A brief description and illustration of DSE Search.

When you update a table using CQL, the Solr document is updated. Re-indexing occurs automatically after an update.

Writes are durable. A Solr API client writes data to Cassandra first, and then Cassandra updates indexes. All writes to a replica node are recorded both in memory and in a commit log before they are acknowledged as a success. If a crash or server failure occurs before the memory tables are flushed to disk, the commit log is replayed on restart to recover any lost writes.

The commit log replaces the Solr updatelog, which is not supported in DSE Search/Solr. Consequently, features that require the updateLog are not supported:

Atomic updates
Real-time get
Versioning and optimistic concurrency

If you still want to use the update log, configure the updateLog in the solrconfig.xml using the force="true" attribute.

DataStax, Titan, and TitanDB are registered trademark of DataStax, Inc. and its subsidiaries in the United States and/or other countries.

Apache Cassandra, Apache, Tomcat, Lucene, Solr, Hadoop, Spark, TinkerPop, and Cassandra are trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.