Skip to main content

6 posts tagged with "secondary index"

View All Tags

· 11 min read
Neel Phadnis

(Source: Photo by Cameron Ballard on [Unsplash](https://unsplash.com/) ) Source: Photo by Cameron Ballard on Unsplash

The Collection Data Types (CDTs) in Aerospike are List and Map. They offer powerful capabilities to model and access your data for speed-at-scale. A major use of the CDTs is to store and process JSON documents efficiently. In the recent Aerospike Database 6.1 release, secondary index capabilities over the CDTs have been enhanced to make the CDTs even more useful and powerful for JSON documents in addition to other uses.

· 3 min read
Ronen Botzer

The soon-to-be-released Aerospike 5.7 includes the first milestone of a rewrite of Secondary Indexes. Among these new features are indexes which are 60% more memory efficient, faster queries, and a superior new garbage collection system. You can get a more comprehensive launch overview by reading the blog post Aerospike Database 5.7: Operational, Query, and Security Enhancements.

· 3 min read

Secondary indexes are on a non-primary key, which allows you to model one-to-many relationships. [https://www.aerospike.com/docs/architecture/secondary-index.html](https://www.aerospike.com/docs/architecture/secondary-index.html) Secondary indexes are on a non-primary key, which allows you to model one-to-many relationships. https://www.aerospike.com/docs/architecture/secondary-index.html

spring-data-aerospike supports creating secondary indexes in Aerospike out of the box.

There are two ways to accomplish this task:

  1. Using AerospikeTemplate createIndex method; or

  2. Using @Indexed annotation placed over the field in your entity.