Planet NoSQL

In Couchbase, data is always partitioned using the   consistent hash   value of the document key into buckets, which are stored on the data nodes. Couchbase   Global Secondary Index (GSI)   abstracts the indexing operations and runs as a distinct service within the Couchbase data platform. When a single index can cover a whole type of documents, everything is good. But there are cases where you’d want to partition an index. Capacity : You want increased capacity because a single node is unable to hold a big index. Query-ability : You want to avoid rewriting the query to work with manual partitioning of the index using a partial index. Performance : Single index is unable to meet the SLA. To address this, Couchbase 5.5 introduces automatic hash partitioning of the index. You’re used to having bucket data hashed into multiple nodes. Index partitioning enables you to hash the index into multiple nodes as well. There is good symmetry. Creating the index is easy. Simply a...