Building and maintaining secondary indexes

All secondary indexes (2i, SAI, and SASI) are built in the background automatically, without blocking reads or writes. Client-maintained tables as indexes must be created manually. For example, if the age column had been indexed by creating a table such as cyclist_by_age, your client application would have to populate the table with data from the cyclist_name table that uses id as the primary key.

To perform a hot rebuild of an index, use the nodetool rebuild_index command.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000,