Enum aws_sdk_dynamodb::error::UpdateGlobalTableSettingsErrorKind

#[non_exhaustive]
pub enum UpdateGlobalTableSettingsErrorKind {
    GlobalTableNotFoundException(GlobalTableNotFoundException),
    IndexNotFoundException(IndexNotFoundException),
    InternalServerError(InternalServerError),
    InvalidEndpointException(InvalidEndpointException),
    LimitExceededException(LimitExceededException),
    ReplicaNotFoundException(ReplicaNotFoundException),
    ResourceInUseException(ResourceInUseException),
    Unhandled(Unhandled),
}

Types of errors that can occur for the UpdateGlobalTableSettings operation.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

GlobalTableNotFoundException(GlobalTableNotFoundException)

The specified global table does not exist.

IndexNotFoundException(IndexNotFoundException)

The operation tried to access a nonexistent index.

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.

ReplicaNotFoundException(ReplicaNotFoundException)

The specified replica is no longer part of the global table.

ResourceInUseException(ResourceInUseException)

The operation conflicts with the resource's availability. For example, you attempted to recreate an existing table, or tried to delete a table currently in the CREATING state.

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.

Trait Implementations

impl Debug for UpdateGlobalTableSettingsErrorKind

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.