Sub-Document Operations
Sub-Document operations can be used to efficiently access and change parts of documents.
Sub-Document operations may be quicker and more network-efficient than full-document operations such as upsert, replace and get because they only transmit the accessed sections of the document over the network.
Sub-Document operations are also atomic, in that if one Sub-Document mutation fails then all will, allowing safe modifications to documents with built-in concurrency control.
Sub-Documents
You can atomically and efficiently update and retrieve parts of a document. These parts are called Sub-Documents. While full-document retrievals retrieve the entire document and full document updates require sending the entire document, Sub-Document retrievals only retrieve relevant parts of a document and Sub-Document updates only require sending the updated portions of a document.
You should use Sub-Document operations when you are modifying only portions of a document, and full-document operations when the contents of a document is to change significantly.
| The Sub-Document operations described on this page are for Key-Value requests only: they are not related to Sub-Document SQL++ queries. |
In order to use Sub-Document operations you need to specify a path indicating the location of the Sub-Document. The path follows SQL++ syntax. Considering the document:
{
"name": "Douglas Reynholm",
"email": "douglas@reynholmindustries.com",
"addresses": {
"billing": {
"line1": "123 Any Street",
"line2": "Anytown",
"country": "United Kingdom"
},
"delivery": {
"line1": "123 Any Street",
"line2": "Anytown",
"country": "United Kingdom"
}
},
"purchases": {
"complete": [
339, 976, 442, 666
],
"abandoned": [
157, 42, 999
]
}
}The paths name, addresses.billing.country and purchases.complete[0] are all valid paths.
Retrieving
The lookupIn operations query the document for certain path(s); these path(s) are then returned. You have a choice of actually retrieving the document path using the get Sub-Document operation, or simply querying the existence of the path using the exists Sub-Document operation. The latter saves even more bandwidth by not retrieving the contents of the path if it is not needed.
The examples use the following imports:
#include <couchbase/cluster.hxx>
#include <couchbase/fmt/cas.hxx>
#include <couchbase/fmt/error.hxx>
#include <fmt/format.h>
#include <tao/json/value.hpp>
#include <iostream>auto [err, result] = collection
.lookup_in(
"customer123",
couchbase::lookup_in_specs{
couchbase::lookup_in_specs::get("addresses.delivery.country"),
}
)
.get();
if (err) {
fmt::println("Error: {}", err);
} else {
auto country = result.template content_as<std::string>(0);
fmt::println("Country: {}", country);
}auto [err, result] = collection
.lookup_in(
"customer123",
couchbase::lookup_in_specs{
couchbase::lookup_in_specs::exists("addresses.delivery.does_not_exist"),
}
)
.get();
if (err) {
fmt::println("Error: {}", err);
} else {
fmt::println("Does the field exist? {}", result.exists(0));
}Multiple operations can be combined, and this can be most neatly done with a for-comprehension:
auto [err, result] = collection
.lookup_in(
"customer123",
couchbase::lookup_in_specs{
couchbase::lookup_in_specs::get("addresses.delivery.country"),
couchbase::lookup_in_specs::exists("addresses.delivery.does_not_exist"),
}
)
.get();
if (err) {
fmt::println("Error: {}", err);
} else {
fmt::println("Country: {}, Exists: {}", result.content_as<std::string>(0), result.exists(1));
}Choosing an API
The C++ SDK provides two async APIs for all operations. There’s the one returning std::future you’ve already seen, as well as a callback-based variant:
collection.lookup_in(
"customer123",
couchbase::lookup_in_specs{
couchbase::lookup_in_specs::get("addresses.delivery.country"),
},
{},
[](auto err, auto result) {
if (err) {
fmt::println("Error: {}", err);
} else {
auto country = result.template content_as<std::string>(0);
fmt::println("Country: {}", country);
}
}
);Mutating
Mutation operations modify one or more paths in the document. The simplest of these operations is upsert, which, similar to the fulldoc-level upsert, will either modify the value of an existing path or create it if it does not exist:
auto [err, result] = collection
.mutate_in(
"customer123",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::upsert("email", "dougr86@hotmail.com"),
}
)
.get();
if (err) {
fmt::println("Error: {}", err);
} else {
fmt::println("Success! (CAS: {})", result.cas());
}Likewise, the insert operation will only add the new value to the path if it does not exist:
auto [err, result] = collection
.mutate_in(
"customer123",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::insert("email", "dougr86@hotmail.com"),
}
)
.get();
if (err.ec() == couchbase::errc::key_value::path_exists) {
fmt::println("Error, path already exists");
} else if (err) {
fmt::println("Error: {}", err);
} else {
fmt::println("Unexpected success...");
}Dictionary values can also be replaced or removed, and you may combine any number of mutation operations within the same general mutateIn API. Here’s an example of one which replaces one path and removes another.
auto [err, result] = collection
.mutate_in(
"customer123",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::remove("addresses.billing"),
couchbase::mutate_in_specs::replace("email", "dougr96@hotmail.com"),
}
)
.get();
// Note: for brevity, checking the result will be skipped in subsequent examples, but
mutate_in is an atomic operation. If any single operation fails, then the entire document is left unchanged.
|
Supported Types
Mutation operations can take primitives (String, Int, etc.), along with any type for which an Encodable can be
found. This includes the built-in JSON library (JsonObject and JsonArray), many type from third-party JSON libraries,
and Scala case classes.
See the Data Operations page for more details.
Array Append and Prepend
The array_prepend and array_append operations are true array prepend and append operations.
Unlike fulldoc append/prepend operations (which simply concatenate bytes to the existing value), array_append and array_prepend are JSON-aware:
auto [err, result] = collection
.mutate_in(
"customer123",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::array_append("purchases.complete", 777),
}
)
.get();
// purchases.complete is now [339, 976, 442, 666, 777]auto [err, result] = collection
.mutate_in(
"customer123",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::array_prepend("purchases.complete", 18),
}
)
.get();
// purchases.abandoned is now [18, 157, 49, 999]If your document only needs to contain an array, you do not have to create a top-level object wrapper to contain it. Simply initialize the document with an empty array and then use the empty path for subsequent Sub-Document array operations:
auto [err1, result1] = collection.upsert("my_array", tao::json::empty_array).get();
auto [err2, result2] = collection
.mutate_in(
"my_array",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::array_append("", "some element"),
}
)
.get();
// the document my_array is now ["some element"]If you wish to create an array if it does not exist and also push elements to it within the same operation you may use the create_path option:
auto [err, result] = collection
.mutate_in(
"some_doc",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::array_append("some.array", "hello world").create_path(),
}
)
.get();Arrays as Unique Sets
Limited support also exists for treating arrays like unique sets, using the array_add_unique command.
This will do a check to determine if the given value exists or not before actually adding the item to the array:
auto [err1, result1] =
collection
.mutate_in("customer123", couchbase::mutate_in_specs{ couchbase::mutate_in_specs::array_add_unique("purchases.complete", 95) })
.get();
// Just for demo, a production app should check the result properly
assert(!err1);
auto [err2, result2] = collection
.mutate_in(
"customer123",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::array_add_unique("purchases.complete", 95),
}
)
.get();
if (err2.ec() == couchbase::errc::key_value::path_exists) {
fmt::println("Error, path already exists");
} else if (err2) {
fmt::println("Error: {}", err2);
} else {
fmt::println("Unexpected success...");
}Note that currently the array_add_unique will fail with a couchbase::errc::key_value::path_mismatch error code if the array contains JSON objects, or arrays.
The array_add_unique operation will also fail with couchbase::errc::key_value::value_invalid if the value to be added is one of those types as well.
Note that the actual position of the new element is undefined, and that the array is not ordered.
Array Insertion
New elements can also be inserted into an array.
While append will place a new item at the end of an array and prepend will place it at the beginning, insert allows an element to be inserted at a specific position.
The position is indicated by the last path component, which should be an array index.
For example, to insert "cruel" as the second element in the array ["Hello", "world"], the code would look like:
auto [err, result] = collection
.mutate_in(
"some_doc",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::array_insert("foo.bar[1]", "cruel"),
}
)
.get();Note that the array must already exist and that the index must be valid (i.e. it must not point to an element which is out of bounds).
Counters and Numeric Fields
Counter operations allow the manipulation of a numeric value inside a document. These operations are logically similar to the increment and decrement full-document operations:
auto [err, result] = collection
.mutate_in(
"some_doc",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::increment("logins", 1),
}
)
.get();
if (err) {
fmt::println("Error: {}", err);
} else {
auto count = result.content_as<std::int32_t>(0);
fmt::println("After increment, counter is {}", count);
}The increment and decrement operations perform simple arithmetic against a numeric value. The updated value is returned.
auto [err1, result1] = collection.upsert("player432", tao::json::value{ { "gold", 1000 } }).get();
assert(!err1);
auto [err2, result2] = collection
.mutate_in(
"player432",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::decrement("gold", 150),
}
)
.get();
if (err2) {
fmt::println("Error: {}", err2);
} else {
auto count = result2.content_as<std::int32_t>(0);
fmt::println("After decrement, counter is {}", count);
}The existing value for counter operations must be within range of a 64 bit signed integer. If the value does not exist, the operation will create it (and its parents, if createPath is enabled).
Note that there are several differences as compared to the full-document counter operations:
-
Sub-Document counters have a range of -9223372036854775807 to 9223372036854775807, whereas full-document counters have a range of 0 to 18446744073709551615
-
Sub-Document counter operations protect against overflow and underflow, returning an error if the operation would exceed the range. Full-document counters will use normal C semantics for overflow (in which the overflow value is carried over above 0), and will silently fail on underflow, setting the value to 0 instead.
-
Sub-Document counter operations can operate on any numeric value within a document, while full-document counter operations require a specially formatted counter document with only the counter value.
Executing Multiple Operations
Multiple Sub-Document operations can be executed at once on the same document, allowing you to retrieve or modify several Sub-Documents at once. When multiple operations are submitted within the context of a single lookupIn or mutateIn command, the server will execute all the operations with the same version of the document.
| Unlike batched operations which is simply a way of sending multiple individual operations efficiently on the network, multiple Sub-Document operations are formed into a single command packet, which is then executed atomically on the server. You can submit up to 16 operations at a time. |
When submitting multiple mutation operations within a single mutateIn command, those operations are considered to be part of a single transaction: if any of the mutation operations fail, the server will logically roll-back any other mutation operations performed within the mutateIn, even if those commands would have been successful had another command not failed.
When submitting multiple retrieval operations within a single lookupIn command, the status of each command does not affect any other command. This means that it is possible for some retrieval operations to succeed and others to fail. While their statuses are independent of each other, you should note that operations submitted within a single lookupIn are all executed against the same version of the document.
Creating Paths
Sub-Document mutation operations such as upsert or insert will fail if the immediate parent is not present in the document. Consider:
{
"level_0": {
"level_1": {
"level_2": {
"level_3": {
"some_field": "some_value"
}
}
}
}
}Looking at the some_field field (which is really level_0.level_1.level_2.level_3.some_field), its immediate parent is level_3.
If we were to attempt to insert another field, level_0.level_1.level_2.level_3.another_field, it would succeed because the immediate parent is present.
However if we were to attempt to insert to level_1.level_2.foo.bar it would fail, because level_1.level_2.foo (which would be the immediate parent) does not exist.
Attempting to perform such an operation would result in a Path Not Found error.
By default the automatic creation of parents is disabled, as a simple typo in application code can result in a rather confusing document structure.
Sometimes it is necessary to have the server create the hierarchy however.
In this case, the create_path option may be used.
auto [err, result] = collection
.mutate_in(
"customer123",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::upsert(
"level_0.level_1.foo.bar.phone",
tao::json::value{
{ "num", "311-555-0101" },
{ "ext", 16 },
}
)
.create_path(),
}
)
.get();Reading Sub-Documents From Replicas
Couchbase Server 7.6 and later support Sub-Doc lookup from replicas. With 7.6.2 onwards supporting reading from preferred Server Group.
The collection.lookup_in_any_replica() method returns the first response — from active or replica:
auto [err, result] = collection
.lookup_in_any_replica(
"customer123",
couchbase::lookup_in_specs{
couchbase::lookup_in_specs::get("addresses.delivery.country"),
}
)
.get();
if (err) {
fmt::println("Err: {}", err);
} else {
auto country = result.template content_as<std::string>(0);
auto is_replica = result.is_replica();
fmt::println("Country: {} Is replica: {}", country, is_replica);
}The collection.lookup_in_all_replicas() method fetches all available replicas (and the active copy), and returns all responses:
auto [err, result] = collection
.lookup_in_all_replicas(
"customer123",
couchbase::lookup_in_specs{
couchbase::lookup_in_specs::get("addresses.delivery.country"),
}
)
.get();
if (err) {
fmt::println("Err: {}", err);
} else {
for (const auto& replica : result) {
auto country = replica.template content_as<std::string>(0);
auto is_replica = replica.is_replica();
fmt::println("Country: {} Is replica: {}", country, is_replica);
}
}Concurrent Modifications
Concurrent Sub-Document operations on different parts of a document will not conflict. For example the following two blocks can execute concurrently without any risk of conflict:
auto future1 = collection.mutate_in(
"customer123",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::array_append("purchases.complete", 99),
}
);
auto future2 = collection.mutate_in(
"customer123",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::array_append("purchases.abandoned", 101),
}
);
future1.get();
future2.get();Even when modifying the same part of the document, operations will not necessarily conflict. For example, two concurrent arrayAppend operations to the same array will both succeed, never overwriting the other.
So in some cases the application will not need to supply a CAS value to protect against concurrent modifications.
If CAS is required then it can be provided like this:
auto [err1, result1] = collection.get("player432").get();
assert(!err1);
auto [err2, result2] = collection
.mutate_in(
"player432",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::decrement("gold", 150),
},
couchbase::mutate_in_options().cas(result1.cas())
)
.get();Durability
Couchbase’s traditional durability, using persist_to and replicate_to, is
still available, particularly for talking to Couchbase Server 6.0 and earlier:
auto [err, result] = collection
.mutate_in(
"key",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::insert("name", "andy"),
},
couchbase::mutate_in_options().durability(couchbase::persist_to::one, couchbase::replicate_to::one)
)
.get();In Couchbase Server 6.5 and up, this is built upon with Durable Writes, which uses the concept of majority to indicate the number of configured Data Service nodes to which commitment is required:
auto [err, result] = collection
.mutate_in(
"key",
couchbase::mutate_in_specs{
couchbase::mutate_in_specs::insert("name", "andy"),
},
couchbase::mutate_in_options().durability(couchbase::durability_level::majority)
)
.get();Error Handling
Sub-Document operations have their own set of error codes.
When programming with Sub-Document, be prepared for any of the full-document error codes (such as couchbase::errc::key_value::document_not_found) as well as
special Sub-Document errors which are received when certain constraints are not satisfied.
Some of the error codes include (all under the couchbase::errc::key_value namespace):
-
path_not_found: When retrieving a path, this means the path does not exist in the document. When inserting or upserting a path, this means the immediate parent does not exist. -
path_exists: In the context of an insert, it means the given path already exists. In the context of arrayAddUnique, it means the given value already exists. -
path_mismatch: This means the path may exist in the document, but that there is a type conflict between the path in the document and the path in the command. Consider the document:{ "tags": ["reno", "nevada", "west", "sierra"] }The path
tags.sierrais a mismatch, sincetagsis actually an array, while the path assumes it is a JSON object (dictionary). -
document_not_json: This means you are attempting to modify a binary document using Sub-Document operations. -
path_invalid: This means the path is invalid for the command. Certain commands such as arrayInsert expect array elements as their final component, while others such as upsert and insert expect dictionary (object) keys.
Path Syntax
Path syntax largely follows SQL++ conventions: A path is divided into components, with each component referencing a specific level in a document hierarchy.
Components are separated by dots (.) in the case where the element left of the dot is a dictionary, or by brackets ([n]) where the element left of the bracket is an array and n is the index within the array.
As a special extension, you can indicate the last element of an array by using an index of -1, for example to get the last element of the array in the document
{"some":{"array":[1,2,3,4,5,6,7,8,9,0]}}Use some.array[-1] as the path, which will return the element 0.
Each path component must conform as a JSON string, as if it were surrounded by quotes, and any character in the path which may invalidate it as a JSON string must be escaped by a backslash (\).
In other words, the path component must match exactly the path inside the document itself.
For example:
{"literal\"quote": {"array": []}}must be referenced as literal\"quote.array.
If the path also has special path characters (i.e. a dot or brackets) it may be escaped using SQL++ escapes. Considering the document
{"literal[]bracket": {"literal.dot": true}}A path such as `literal[]bracket`.`literal.dot`. You can use double-backticks (``) to reference a literal backtick.
If you need to combine both JSON and path-syntax literals you can do so by escaping the component from any JSON string characters (e.g.
a quote or backslash) and then encapsulating it in backticks (`path`).
| Currently, paths cannot exceed 1024 characters, and cannot be more than 32 levels deep. |
Extended Attributes
Extended Attributes (also known as XATTRs), built upon the Sub-Document API, allow developers to define application-specific metadata that will only be visible to those applications that request it or attempt to modify it. This might be, for example, meta-data specific to a programming framework that should be hidden by default from other frameworks or libraries, or possibly from other versions of the same framework. They are not intended for use in general applications, and data stored there cannot be accessed easily by some Couchbase services, such as Search.