Invalid protocol message is received by the server or by the client. Indicates communication error between the server and the driver.
Indicates that the number of operations passed to writeMany, putMany or deleteMany methods exceeds the system defined limit.
Indicates authorization error caused by problem with accessing user or application credentials. The reason for this error depends on what credential provider is used for the authorization. E.g. if file system credentials are used, this error may result if the credentials file is not found or not accessible.
Indicates a record version mismatch. REST operations only.
Indicates that an attempt has been made to evolve the schema of a a table more times than allowed by the system defined limit.
Operation is called with invalid argument value(s) or invalid options. This error code is also used if invalid configuration is passed to NoSQLClient constructor.
Indicates that a service is in incorrect state. Administrative intervention may be required.
The operation attempted to create an index for a table but the named index already exists.
Indicates that an attempt has been made to create more indexes on a table than the system defined limit.
The operation attempted to access a index that does not exist or is not in a visible state.
Indicates that an application does not have sufficient permission to perform an operation.
Indicates that an application presented an invalid authorization string in a request to the server. Whether this error is retryalble depends on the cause. If the error is due to access token expiration, it can be retried, in which case a fresh access token should be obtained before the retry. However if the retry results in the same error, then the cause is not access token expiration and the error is no longer retryable and should be returned to the application. This logic is implemented by default RetryHandler and default AuthorizationProvider.
Indicates that an attempt has been made to create a row with a primary key or index key size that exceeds the system defined limit.
Memory consumed by client-side query execution exceeded the limit set by maxMemoryMB, maxMemoryMB or default limit of 1 GB. To execute the query successfully you may need to increase this limit.
Indicates network error when trying to communicate with the service. Can be due to inability to connect (e.g. if the network or the service is down). Note that this is different from unsuccessful response from the service, which is indicated by SERVICE_ERROR.
This error happens when a non-data operation is throttled. This can happen if an application attempts too many control operations such as table creation, deletion, or similar methods. Such operations do not use throughput or capacity provisioned for a given table but they consume system resources and their use is limited.
This error is retryable but a large delay should be used in order to minimize the chance that a retry will also be throttled. This delay can be configured by controlOpBaseDelay property of the default RetryHandler.
Indicates that the requested operation is not supported. Some operations are supported for Cloud Service but not for On-Premise NoSQL Database (see ServiceType) and vice versa.
Indicates that the provisioned read throughput has been exceeded.
This error is retryable and will be retried by the driver's default RetryHandler. However, it is recommended that applications attempt to avoid throttling exceptions by rate limiting themselves to the degree possible.
Retries and behavior related to throttling can be managed by configuring retry handler and options in RetryConfig.
Indicates that the size of a request to the server exceeds the system defined limit.
Indicates that operation cannot be processed because the provided timeout interval is exceeded. If the operation is retryable, it is possible that it has been retried a number of times before the timeout occurs.
The operation attempted to create a resource but it already exists.
The operation attempted to access a resource that does not exist or is not in a visible state.
Indicates that authentication to kvstore failed either because authentication information was not provided or because authentication session has expired. The driver will automatically retry authentication.
Indicates that an attempt has been made to create a row with a size that exceeds the system defined limit.
Indicates that security information is not ready in the system. This error will occur as the system acquires security information and must be retried in order for authorization to work properly.
Indicates that there is an internal system problem. Most system problems are temporary, so this is a retryable error.
Indicates unsuccessful response from the service. Even though the client was able to communicate with the service, the service was not able to process client request and thus returned unsuccessful response. Additional information is provided in the error message. Note that this is different from inability to communicate with the service which is indicated by NETWORK_ERROR.
Indicates that the service is temporarily unavailable. This is retryable error.
Indicates that a table size limit has been exceeded by writing more data than the table can support. This error is not retryable because the conditions that lead to it being thrown, while potentially transient, typically require user intervention.
Indicates that a table operation failed because the table is in use or busy. Only one modification operation at a time is allowed on a table. This is a retryable error.
Indicates that an attempt has been made to create or modify a table using limits that exceed the maximum allowed for a single table.
The operation attempted to create a table but the named table already exists.
Indicates that an attempt has been made to create a number of tables that exceeds the system defined limit.
The operation attempted to access a table that does not exist or is not in a visible state.
Cloud service only. Indicates that an operation is attempted on a replicated table that is not yet fully initialized.
Indicates that an attempt has been made to create or modify a table using limits that cause the tenant's aggregate resources to exceed the maximum allowed for a tenant.
Indicates that the operation to obtain access token or other data from authorization server was unauthorized. See NoSQLAuthorizationError for more information on this error.
Indicates that a server error occured that is not classified by known error codes. Server response may still provide additional information.
Server received unknown or unsupported operation.
Indicates the client protocol version is not supported by the server, i.e. the client is newer than the server. The driver will try to decrement the protocol version, if possible, and try again. This error will result if the protocol version cannot be further decremented.
Indicates that the server does not support the current query protocol version, i.e. the client is using newer query version than the server. The driver will try to decrement the query version, if possible, and try again. This error will result if the query version cannot be further decremented.
Indicates that the provisioned write throughput has been exceeded.
This error is retryable and will be retried by the driver's default RetryHandler. However, it is recommended that applications attempt to avoid throttling exceptions by rate limiting themselves to the degree possible.
Retries and behavior related to throttling can be managed by configuring retry handler and options in RetryConfig.
Generated using TypeDoc
This enumeration lists error codes for different errors raised by the driver. Error codes constants also store additional information such as if the error is retryable. ErrorCode is used by NoSQLError and its subclasses. It is indicated below which errors are retryable.
See
Working With Tables