risingwavelabs/risingwave · error · MetaError

Invalid parameter: {0}

Error message

Invalid parameter: {0}

What it means

A caller passed a parameter that is invalid, malformed, or fails validation in a meta service API. The `#[message]` String carries the specific reason. Generic guard-rail error for bad inputs to meta RPCs and management operations.

Source

Thrown at src/meta/src/error.rs:72

        #[from]
        #[backtrace]
        HummockError,
    ),

    #[error(transparent)]
    RpcError(
        #[from]
        #[backtrace]
        RpcError,
    ),

    #[error("{0}")]
    PermissionDenied(String),

    #[error("Invalid worker: {0}, {1}")]
    InvalidWorker(WorkerId, String),

    #[error("Invalid parameter: {0}")]
    InvalidParameter(#[message] String),

    // Used for catalog errors.
    #[error("{0} id not found: {1}")]
    #[construct(skip)]
    CatalogIdNotFound(&'static str, String),

    #[error("table_fragment does not exist: id={0}")]
    FragmentNotFound(FragmentId),

    #[error("{0} named {1} already exists{under_creation}", under_creation = (.2).map(|_| " and is still being created").unwrap_or(""))]
    Duplicated(
        &'static str,
        String,
        // if under creation, take streaming job id, otherwise None
        Option<JobId>,
    ),

View on GitHub (pinned to 6469eb736d)

Solutions

1. Read the message payload to see which parameter failed and why.
2. Validate the parameter against RisingWave requirements (length, format, allowed values) before calling.
3. Correct the client/tool that produced the bad parameter.
4. Upgrade if the parameter was valid under a different RisingWave version but the accepted range changed.

Example fix

// before
meta_client.set_system_param("barrier_interval_ms", "not-a-number").await?; // InvalidParameter
// after
meta_client.set_system_param("barrier_interval_ms", "1000").await?;

fn validate_param(name: &str, value: &str) -> Result<(), String> {
    if value.is_empty() { return Err(format!("{} must be non-empty", name)); }
    Ok(())
}

match meta_result {
    Err(MetaError::InvalidParameter(msg)) => { eprintln!("bad parameter: {msg}"); /* fix input */ }
    other => other?,
}

When it happens

Trigger: Calling meta service methods (DDL wrappers, system parameter setters, scale/worker management APIs) with empty strings, out-of-range values, or malformed identifiers.

Common situations: Mistyped connection/property strings in CREATE SOURCE/SINK, invalid worker-group or parallelism values passed to scale APIs, empty parameter in admin tooling.

Understand the failure class

Background: "Must be a positive integer", "Invalid value", "Unsupported": the invalid-argument-value error family, when a library rejects the value you pass — this error's family across 35 libraries.

Related errors

• Invalid parameter {name}: {reason}
• since_timestamp is not before the committed epoch of upstrea
• since_timestamp is too new for upstream table {}: requested
• value {:?} out of range, expect {:?}
• value {:?} out of range, expect {:?}

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