architecture/secondary-index.html

architecture/secondary-index.html

Secondary indexes are on a non-primary key, which allows you to model one-to-many relationships. In Aerospike, secondary indexes are specified on a bin-by-bin basis (like RDBMS columns). This allows efficient updates and minimizes the amount of resources required to store indexes.

A data description (DDL) determines which bins and data types to index. Use the Aerospike tools or the API to dynamically create and remove indexes. This DDL (similar to RDBMS schema) is not used for data validation—even if a bin is in the DDL as indexed, that bin is optional. For an indexed bin, updating the record to include the bin updates the index.

Index entries are type checked i.e If you have a bin that stores user age, and the age value is stored as a string by one application and an integer by another application, an integer index excludes records containing string values stored in the indexed bin, while a string index excludes records with integer values stored in the indexed bin.

Read full article from architecture/secondary-index.html