A newer version of this documentation is available.

View Latest

Data Structures

    You can use complex data structures such as dictionaries and lists in Couchbase. These data structures may be manipulated with basic operations without retrieving and storing the entire document.

    Data structures in Couchbase are similar in concept to data structures in Go:

    • Map is like a Go map, and is a key-value structure, where a value is accessed by using a key string.

    • List is like a Go slice and is a sequential data structure. Values can be placed in the beginning or end of a list, and can be accessed using numeric indexes.

    • Set is a wrapper over a list which provides the ability to handle unique values.

    These data structures are stored as JSON documents in Couchbase, and can therefore be accessed using N1QL, Full Text Search, and normal key-value operations. Data structures can also be manipulated using the traditional sub-document and full-document KV APIs.

    Using the data structures API may help your application in two ways:

    • Simplicity: Data structures provide high level operations by which you can deal with documents as if they were container data structures. Adding an item to a dictionary is expressed as MapAdd, rather than retrieving the entire document, modifying it locally, and then saving it back to the server.

    • Efficiency: Data structure operations do not transfer the entire document across the network. Only the relevant data is exchanged between client and server, allowing for less network overhead and lower latency.

    Creating a Data Structure

    Data structures can be created implicitly by specifying true for the createMap option of the operation. For example, to add an item to a map, specify the document ID of the map itself (i.e. the ID which uniquely identifies the map in the server), the key within the map, and the value to store under the key:

    bucket.MapAdd("map_id", "name", "Mark Nunberg", true)

    Likewise, to create a list, specify the document ID and the value to add:

    bucket.ListPush("list_id", "hello", true)

    Note that the createList parameter will not overwrite an existing document with the same name if it already exists. It is therefore always safe to use, unless your application creates data structures independently.

    Data structures can be explicitly created and reset using full-document methods, and initialized with its JSON equivalent. To create a new empty list or set, use bucket.Upsert("list_id", []string{}). To create an empty map, use bucket.Upsert("map_id", make(map[string]string)).

    Accessing Data Structures

    Data structures can be accessed using their appropriate methods.

    var value string
    cas, err := bucket.ListGet('list_id', 0, &value)
    fmt.Printf("%s", value)
    // Prints 'hello'
    var value string
    cas, err := bucket.MapGet("map_id", "name", &value)
    fmt.Printf("%s", value)
    // Prints 'Mark Nunberg'

    Here is a list of common operations:

    Table 1. Data Structure Operations


    Remove a key from a map.

    cas, err := bucket.MapRemove("map_id", "some_key")


    Get an item from a map.

    var value interface{}
    cas, err := bucket.MapGet("map_id", "some_key", &value)


    Add an item to the end of a list.

    cas, err := bucket.ListPush("list_id", "some_value", false)


    Add an item to the beginning of a list.

    cas, err := bucket.ListShift("list_id", "some_value", false)


    Get an item from a list by its index.

    var value interface{}
    cas, err := bucket.ListGet("list_id", 1, &value)


    Add an item to a set, if the item does not yet exist in the set.

    cas, err := bucket.SetAdd("list_id", "some_value", false)

    Note that a set is just a list. You can retrieve the entire set by simply using a full-document get operation:

    var value []string
    cas, err := bucket.Get("list_id", &value)
    Currently, using the Go SDK you can only store values which are implicitly comparable in Go, this include strings, numbers and booleans.


    Remove an item from a set, if it exists. An exception is not thrown if the item does not exist. You can determine if an item existed or not by the return value. If the item did not exist beforehand, None is returned.

    cas, err := bucket.SetRemove("list_id", "some_value")

    MapSize, ListSize, SetSize

    These methods get the length of the data structure. For maps, this is the number of key-value pairs inside the map. For lists, and sets, this is the number of elements in the structure.

    size, cas, err := bucket.ListSize("list_id")

    Note that there are only two basic types: map and list. Types such as set are merely derivatives of list.

    Data Structures and Key-Value APIs

    Data structures can be accessed using key-value APIs as well. In fact, the data structure API is actually a client-side wrapper around the key-value and sub-document API. Most of the data structure APIs wrap the sub-document API directly. Therefore, for example, the MapSet can be implemented as follows:

    func (b *Bucket) MapSet(key, path string, value interface{}, createMap bool) (Cas, error) {
    	frag, err := b.MutateIn(key, 0, 0).Upsert(path, value, false).Execute()
    	return frag.Cas, err

    Some data structure operations are compound operations. This means that they do not correspond to a single server-side operation. For example, SetRemove does not exist on the server. In order to implement SetRemove, it would require an implementation like so:

    func (b *Bucket) SetRemove(key string, value interface{}) (Cas, error) {
    	var setContents []interface{}
    	cas, err := b.Get(key, &setContents)
    	if err != nil {
    		return 0, err
    	foundItem := false
    	var newSetContents []interface{}
    	for _, item := range setContents {
    		if item == value {
    			foundItem = true
    		} else {
    			newSetContents = append(newSetContents, value)
    	if !foundItem {
    		return 0, ErrRangeError
    	return b.Replace(key, newSetContents, cas, 0)

    In the example above, the entire document is fetched and the index of the value is retrieved. If the value exists, the index of the value is removed at the server side.

    Because the data structure API is just a wrapper around the various key-value APIs, you are free to switch between them in your application code.