risingwavelabs/risingwave · error · SinkError

DynamoDB error

Error message

DynamoDB error: {0}

What it means

Sentinel variant of the SinkError enum in src/connector/src/sink/mod.rs that wraps any anyhow error originating from the DynamoDB sink connector. It is a generic wrapper raised wherever DynamoDB-specific operations (table writes, credential/token handling) fail; the inner error carries the actual cause.

Solutions

1. Inspect the wrapped anyhow error for the underlying DynamoDB SDK failure (throttling, provisioning, credentials, serialization).
2. Check AWS credentials/region configuration and IAM permissions on the target table.
3. Retry transient throttling errors; verify table capacity or use on-demand mode.

When it happens

Trigger: Thrown at src/connector/src/sink/mod.rs:1202 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of risingwavelabs/risingwave@6469eb736d (2026-09-11). Data as JSON: /api/errors/c909ec2e799dbf95. Report an issue: GitHub.

Appendix: source

Thrown at src/connector/src/sink/mod.rs:1202

    #[error("Pulsar error: {0}")]
    Pulsar(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
    #[error(transparent)]
    Internal(
        #[from]
        #[backtrace]
        anyhow::Error,
    ),
    #[error("BigQuery error: {0}")]
    BigQuery(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
    #[error("DynamoDB error: {0}")]
    DynamoDb(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
    #[error("SQL Server error: {0}")]
    SqlServer(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
    #[error("Postgres error: {0}")]
    Postgres(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
    #[error(transparent)]

View on GitHub (pinned to 6469eb736d)