 | ResponseStatus Enumeration |
The response status for binary Memcached and Couchbase operations.
Namespace: Couchbase.Core.IO.Operations
Assembly: Couchbase.NetClient (in Couchbase.NetClient.dll) Version: 3.0.0-local-202004010202+047adc0837bfc29c0b8cce4322194a09afd8ea18
SyntaxC#
public enum ResponseStatus
Members| Member name | Value | Description | |
|---|---|---|---|
| None | -1 | Indicates that the enum has not been set. | |
| UnknownError | -2 | An unknown error occured. Please check logs for more details. | |
| Failure | -3 | An Error occured and more details can be found in the operation message. | |
| Success | 0 | The operation was successful | |
| KeyNotFound | 1 | The key does not exist in the database | |
| KeyExists | 2 | The key exists in the database. | |
| ValueTooLarge | 3 | The value of the object stored was too large. | |
| InvalidArguments | 4 | The arguments of the operation were invalid. | |
| ItemNotStored | 5 | The item could not be stored in the database | |
| IncrDecrOnNonNumericValue | 6 | The increment operation was called on a non-numeric value | |
| VBucketBelongsToAnotherServer | 7 |
The VBucket the operation was attempted on, no longer belongs to the server.
Remarks This is a common during rebalancing after adding or removing a node or during a failover. | |
| BucketNotConnected | 8 | Not connected to a bucket. | |
| Locked | 9 | The requested resource is locked. | |
| AuthStale | 31 | The authentication context is stale. You should reauthenticate | |
| AuthenticationError | 32 | The connection to Couchbase could not be authenticated. | |
| AuthenticationContinue | 33 |
During SASL authentication, another step (or more) must be made before authentication is complete.
Remarks This is a system-level response status. | |
| InvalidRange | 34 | The value was outside of supported range. | |
| Rollback | 35 | Roll back to an earlier version of the vbucket UUID (_currently_ only used by DCP for agreeing on selecting a starting point) | |
| Eaccess | 36 | No access (could be opcode, value, bucket etc) | |
| NotInitialized | 37 | The Couchbase cluster is currently initializing this node, and the Cluster manager has not yet granted all users access to the cluster. | |
| UnknownCommand | 129 | The server received an unknown command from a client. | |
| OutOfMemory | 130 | The server is temporarily out of memory. | |
| NotSupported | 131 | The operation is not supported. | |
| InternalError | 132 | An internal error has occured. | |
| Busy | 133 | The server was too busy to complete the operation. | |
| TemporaryFailure | 134 | A temporary error has occured in the server. | |
| ClientFailure | 409 | A client error has occured before the operation could be sent to the server. | |
| OperationTimeout | 512 | The operation exceeded the specified OperationTimeout configured for the client instance. | |
| NoReplicasFound | 768 | Returned when the client cannot locate a replica within the cluster map config for a replica read. This would happen if a bucket was not configured to have replicas; if you encounter this error check to make sure you have indeed configured replicas on your bucket. | |
| NodeUnavailable | 1024 | The node or service that the key has been mapped to is offline or cannot be reached. | |
| TransportFailure | 1280 | Indicates that a transport layer failure occured while the client was sending or receiving data. | |
| DocumentMutationLost | 1536 | Document Mutation lost during a hard failover. | |
| DocumentMutationDetected | 1537 | A document mutation was detected on the document being observed. | |
| SubDocPathNotFound | 192 | Subdocument error indicating the path inside the JSON is invalid. | |
| SubDocPathMismatch | 193 | Subdocument error indicating one of the path components was denoting a wrong type (eg. trying to access an array index in an entry that isn't an array). Also for arithmetic operations when the value of the path is not a number. | |
| SubDocPathInvalid | 194 | Subdocument error indicating that the path provided is invalid. For operations requiring an array index, this is returned if the last component of that path isn't an array. Similarly for operations requiring a dictionary, if the last component isn't a dictionary but eg. an array index. | |
| SubDocPathTooBig | 195 | Subdocument error indicating that the path is too large (ie. the string is too long) or too deep (more that 32 components). | |
| SubDocDocTooDeep | 196 | Subdocument error indicating that the target document's level of JSON nesting is too deep to be processed by the subdoc service. | |
| SubDocCannotInsert | 197 | Subdocument error indicating that the target document is not flagged or recognized as JSON. | |
| SubDocDocNotJson | 198 | Subdocument error indicating that, for arithmetic subdoc operations, the existing number is already too large. | |
| SubDocNumRange | 199 | Subdocument error indicating that for arithmetic subdoc operations, the operation will make the value too large. | |
| SubDocDeltaRange | 200 | Subdocument error indicating that for arithmetic subdoc operations, the operation will make the value too large. | |
| SubDocPathExists | 201 | Subdocument error indicating that the last component of the path already exist despite the mutation operation expecting it not to exist (the mutation was expecting to create only the last part of the path and store the fragment there). | |
| SubDocValueTooDeep | 202 | Subdocument error indicating that, in a multi-specification, an invalid combination of commands were specified, including the case where too many paths were specified. | |
| SubDocInvalidCombo | 203 | Subdocument error indicating that, in a multi-specification, an invalid combination of commands were specified, including the case where too many paths were specified. | |
| SubDocMultiPathFailure | 204 | Subdocument error indicating that, in a multi-specification, one or more commands failed to execute on a document which exists (ie. the key was valid). | |
| SubDocXattrInvalidFlagCombo | 206 | Subdocument error indicating the flag combination for an XATTR operation was invalid. | |
| SubDocXattrInvalidKeyCombo | 207 | Subdocument error indicating the key combination for an XATTR opeation was invalid. | |
| SubdocXattrUnknownMacro | 208 | The server has no knowledge of the requested macro | |
| SubdocXattrUnknownVattr | 209 | The server has no knowledge of the requested virtual xattr | |
| SubdocXattrCantModifyVattr | 210 | Virtual xattrs can't be modified | |
| SubdocMultiPathFailureDeleted | 211 | [For multi-path commands only] Specified key was found as a Deleted document, but one or more path operations failed. Examine the individual lookup_result (MULTI_LOOKUP) mutation_result (MULTI_MUTATION) structures for details. | |
| SubdocInvalidXattrOrder | 212 | According to the spec all xattr commands should come first, followed by the commands for the document body | |
| UnknownCollection | 136 | Collection does not exist. | |
| DurabilityInvalidLevel | 160 | Invalid request. Returned if an invalid durability level is specified. | |
| DurabilityImpossible | 161 | Valid request, but given durability requirements are impossible to achieve - because insufficient configured replicas are connected. Assuming level=majority and C=number of configured nodes, durability becomes impossible if floor((C + 1) / 2) nodes or greater are offline. | |
| SyncWriteInProgress | 162 | Returned if an attempt is made to mutate a key which already has a SyncWrite pending. Transient, the client would typically retry (possibly with backoff). Similar to ELOCKED. | |
| SyncWriteAmbiguous | 163 | The SyncWrite request has not completed in the specified time and has ambiguous result - it may Succeed or Fail; but the final value is not yet known. |
See Also