Package com.couchbase.client.core.error
package com.couchbase.client.core.error
-
ClassDescriptionThrown if a resource is already permanently terminated and tried to be used afterwards.This is a special case of the timeout exception, signaling that the timeout happened with an ambiguous cause.There was a problem fulfilling the analytics request.Every exception that has to do with authentication problems should either instantiate or subclass from this type.Exception raised if during config load the bucket is not found (think: http 404).Exception raised if during config load the bucket is found, but not deemed ready yet.Indicates an optimistic locking failure.The query failed to compile.This is an internal exception the user should never see; The SDK should translate it to some other exception before presenting it to the user.The parent class for all exceptions created by this SDK (or clients using it).The queried dataset is not found on the server.Raised when provided content could not be successfully decoded.This exception is raised when the server fails to execute a DML query.Indicates an operation failed because the key already exists.Thrown when the server reports a temporary failure that is very likely to be lock-related (like an already locked key or a bad cas used for unlock).Indicates an operation failed because the key does not exist.Thrown when the server reports the document is already locked - generally raised when an unlocking operation is being performed.Indicates an operation completed but no successful document was retrievable.Naming TBD! The synchronous replication durability work can return an ambiguous error (or we timeout waiting for the response, which is effectively the same).The given durability requirements are currently impossible to achieve, as not enough configured replicas are currently available.This exception is raised when a durability level has been requested that is not available on the server.Returned if an attempt is made to mutate a key which already has a durable write pending.The requested key has a SyncWrite which is being re-committed.Raised when provided content could not be successfully encoded.A numeric error code and associated human-readable error message.Raised if the eventing function failed to compile on the server.Raised if the eventing function is currently deployed.Raised if the source and metadata keyspace are the same.Raised if the eventing function is not bootstrapped at the time of request.Raised if the eventing function is not deployed.Raised if the eventing function is not found.Exception which states that the feature is not available for the bucket.Exception thrown if global configs are supported but the server tells the client that there is currently non available.Indicates an operation failed because there has been an issue with the query planner or similar.Indicates an operation failed because there has been an internal error in the server.Indicates the analytics server job queue is fullGeneric exception that captures all meter-related errors.Raised when a requested subdoc operation does not exist.Indicates an operation failed because parsing of the input returned with an error.Indicates an operation failed because there has been an issue with the query planner.Indicates an operation failed because there has been an issue with query prepared statements.Deprecated.The SDK never throws this exception.This error is raised if the operation failed due to hitting a quota-limit on the server side.This is an internal exception used to signal exceptional states in the range scan orchestrator.This error is raised if the operation failed due to hitting a rate-limit on the server side.Used to signal that the seed node used for an operation is outdated and might need to be refreshed.Thrown when Couchbase Server returns with an Out of Memory error.Exception which states that the service is not available for the bucket.Internal optimisation to avoid the cost of completableFuture.completeExceptionally() creating a CompletionException (including expensive stack creation).Thrown when the server reports a temporary failure.The
TimeoutExceptionsignals that an operation timed out before it could be completed.Raised if more SDK instances are created than allowed in configuration.Generic exception that captures all tracer-related errors.This is a special case of the timeout exception, signaling that the timeout happened with no ambiguous cause.Thrown when the request is too big for some reason.There was a problem fulfilling the view request.