Tells the consumer that the message contains a key mutation.
The request:
- Must have extras
- Must have key
- May have value
Extra looks like:
Byte/ 0 | 1 | 2 | 3 |
/ | | | |
|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|
+---------------+---------------+---------------+---------------+
0| by_seqo |
| |
+---------------+---------------+---------------+---------------+
8| rev seqno |
| |
+---------------+---------------+---------------+---------------+
16| flags |
+---------------+---------------+---------------+---------------+
20| expiration |
+---------------+---------------+---------------+---------------+
24| lock_time |
+---------------+---------------+---------------+---------------+
28| Metadata Size | NRU | clen |
+---------------+---------------+-------------------------------+
Total 31 bytes
The metadata is located after the items value. The size for the value is therefore bodylen - key length - metadata size - 31 (size of extra).
NRU is an internal field used by the server and may safely be ignored by other consumers.
The consumer should not send a reply to this command. The following example shows the breakdown of the message:
Byte/ 0 | 1 | 2 | 3 |
/ | | | |
|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|
+---------------+---------------+---------------+---------------+
0| 0x80 | 0x57 | 0x00 | 0x05 |
+---------------+---------------+---------------+---------------+
4| 0x1f | 0x00 | 0x02 | 0x10 |
+---------------+---------------+---------------+---------------+
8| 0x00 | 0x00 | 0x00 | 0x29 |
+---------------+---------------+---------------+---------------+
12| 0x00 | 0x00 | 0x12 | 0x10 |
+---------------+---------------+---------------+---------------+
16| 0x00 | 0x00 | 0x00 | 0x00 |
+---------------+---------------+---------------+---------------+
20| 0x00 | 0x00 | 0x00 | 0x00 |
+---------------+---------------+---------------+---------------+
24| 0x00 | 0x00 | 0x00 | 0x00 |
+---------------+---------------+---------------+---------------+
28| 0x00 | 0x00 | 0x00 | 0x04 |
+---------------+---------------+---------------+---------------+
32| 0x00 | 0x00 | 0x00 | 0x00 |
+---------------+---------------+---------------+---------------+
36| 0x00 | 0x00 | 0x00 | 0x01 |
+---------------+---------------+---------------+---------------+
40| 0x00 | 0x00 | 0x00 | 0x00 |
+---------------+---------------+---------------+---------------+
44| 0x00 | 0x00 | 0x00 | 0x00 |
+---------------+---------------+---------------+---------------+
48| 0x00 | 0x00 | 0x00 | 0x00 |
+---------------+---------------+---------------+---------------+
52| 0x00 | 0x00 | 0x00 | 0x68 ('h') |
+---------------+---------------+---------------+---------------+
56| 0x65 ('e') | 0x6c ('l') | 0x6c ('l') | 0x6f ('o') |
+---------------+---------------+---------------+---------------+
60| 0x77 ('w') | 0x6f ('o') | 0x72 ('r') | 0x6c ('l') |
+---------------+---------------+---------------+---------------+
64| 0x64 ('d') |
+---------------+
DCP_MUTATION command
Field (offset) (value)
Magic (0) : 0x80
Opcode (1) : 0x57
Key length (2,3) : 0x0005
Extra length (4) : 0x1f
Data type (5) : 0x00
Vbucket (6,7) : 0x0210
Total body (8-11) : 0x00000029
Opaque (12-15): 0x00001210
CAS (16-23): 0x0000000000000000
by seqno (24-31): 0x0000000000000004
rev seqno (32-39): 0x0000000000000001
flags (40-43): 0x00000000
expiration (44-47): 0x00000000
lock time (48-51): 0x00000000
nmeta (52-53): 0x0000
nru (54) : 0x00
Key (55-59): hello
Value (60-64): world
This message will not return a response unless an error occurs.
The datatype field of the DCP_MUTATION
describes the Value payload of the message
and not the datatype of the original document. This is important to consider when a
producer is opened with any combination of the no value or include xattr flags.
- Datatype bits
- DCP without the value or xattr flags - datatype will never contain XATTR, but could be a combination of 0, JSON. If the client has enabled compression, the SNAPPY datatype bit may also be present.
DCP_OPEN_NO_VALUE
- datatype will always be 0DCP_OPEN_NO_VALUE|DCP_OPEN_INCLUDE_XATTRS
- datatype will be 0 or XATTR. If the client has enabled compression, the SNAPPY datatype bit may also be present.DCP_OPEN_INCLUDE_XATTRS
- datatype could be many combinations. e.g. 0, XATTR or XATTR|JSON. If the client has enabled compression, the SNAPPY datatype bit may also be present.
See Document - Extended Attributes for details of the encoding scheme.
The extended meta data section is used to send extra meta data for a particular mutation. This section is at the very end, after the value. Its length will be set in the nmeta field.
If the DCP producer is collection enabled, all keys with be prefixed with the collection-ID of the document encoded as a 32-bit [unsigned LEB128(https://en.wikipedia.org/wiki/LEB128)] value. The key-length field will include the bytes used by the collection-ID.
PROTOCOL_BINARY_RESPONSE_KEY_ENOENT (0x01)
If a stream does not exist for the vbucket specfied on this connection.
PROTOCOL_BINARY_RESPONSE_EINVAL (0x04)
If data in this packet is malformed or incomplete then this error is returned.
PROTOCOL_BINARY_RESPONSE_ERANGE (0x22)
If the by sequence number is lower than the current by sequence number contained on the consumer. The by sequence number should always be greater than the one the consumer currently has so if the by sequence number in the mutation message is less than or equal to the by sequence number on the consumer this error is returned.
(Disconnect)
If this message is sent to a connection that is not a consumer.