#[non_exhaustive]
pub enum RestoreTableFromBackupErrorKind {
BackupInUseException(BackupInUseException),
BackupNotFoundException(BackupNotFoundException),
InternalServerError(InternalServerError),
InvalidEndpointException(InvalidEndpointException),
LimitExceededException(LimitExceededException),
TableAlreadyExistsException(TableAlreadyExistsException),
TableInUseException(TableInUseException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the RestoreTableFromBackup
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
BackupInUseException(BackupInUseException)
There is another ongoing conflicting backup control plane operation on the table. The backup is either being created, deleted or restored to a table.
BackupNotFoundException(BackupNotFoundException)
Backup not found for the given BackupARN.
InternalServerError(InternalServerError)
An error occurred on the server side.
InvalidEndpointException(InvalidEndpointException)
LimitExceededException(LimitExceededException)
There is no limit to the number of daily on-demand backups that can be taken.
Up to 500 simultaneous table operations are allowed per account. These operations include CreateTable
, UpdateTable
, DeleteTable
,UpdateTimeToLive
, RestoreTableFromBackup
, and RestoreTableToPointInTime
.
The only exception is when you are creating a table with one or more secondary indexes. You can have up to 250 such requests running at a time; however, if the table or index specifications are complex, DynamoDB might temporarily reduce the number of concurrent operations.
There is a soft account quota of 2,500 tables.
TableAlreadyExistsException(TableAlreadyExistsException)
A target table with the specified name already exists.
TableInUseException(TableInUseException)
A target table with the specified name is either being created or deleted.
Unhandled(Unhandled)
An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code).
When logging an error from the SDK, it is recommended that you either wrap the error in
DisplayErrorContext
, use another
error reporter library that visits the error’s cause/source chain, or call
Error::source
for more details about the underlying cause.