risingwavelabs/risingwave · error · SinkError::Connector

[transparent] (Connector: passthrough ConnectorError)

Error message

[transparent] (Connector: passthrough ConnectorError)

What it means

Transparent passthrough variant of SinkError: Connector(#[from] ConnectorError). It carries no own message; Display delegates to the inner ConnectorError. It exists so generic connector-layer failures can be converted into SinkError automatically via From and preserve the original error text.

Solutions

1. Inspect the transparently wrapped ConnectorError for the actual cause.
2. Fix the sink configuration or connector issue reported by the inner error.
3. If the inner error is transient, retrying the sink write may succeed.

When it happens

Trigger: Thrown at src/connector/src/sink/mod.rs:1220 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/f06660561dfb36f5. Report an issue: GitHub.

Appendix: source

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

    #[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)]
    Connector(
        #[from]
        #[backtrace]
        ConnectorError,
    ),
    #[error("Secret error: {0}")]
    Secret(
        #[from]
        #[backtrace]
        SecretError,
    ),
    #[error("Mongodb error: {0}")]
    Mongodb(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
    #[error("Redshift error: {0}")]

View on GitHub (pinned to 6469eb736d)