Storage-Attached Indexing (SAI) Overview

Storage-Attached Indexing (SAI) allow you create one or multiple secondary indexes on the same database table, with each SAI index based on any column. Exception: there is no need to define an SAI index based on a single-column partition key.

What is SAI?

Use Storage-Attached Indexing (SAI) to create multiple secondary indexes on the same table.

SAI quickstart

Follow the steps to get started quickly with Storage-Attached Indexing (SAI).

Create SAI indexes

Create SAI indexes on a table.

Drop SAI indexes

Drop SAI indexes from a table.

Examine SAI column index and query rules

Understand the columns on which you can define SAI indexes and run queries.

Configure SAI indexes

Learn which configuration settings may affect SAI indexing performance.

Monitor SAI indexes

Use these tools to monitor secondary indexes that were created with Storage-Attached Indexing (SAI).

SAI write path and read path

Describe the SAI write path and read path.


Frequently asked questions about Storage-Attached Indexing (SAI).

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,