influxdata/influxdb · error · MultiTenantExtractError

<transparent: OrgBucketMappingError>

Error message

<transparent: OrgBucketMappingError>

What it means

This is a transparent wrapper in iox_http's MultiTenantExtractError for OrgBucketMappingError. It occurs when parsing a write request in multi-tenant mode fails because the org and bucket from the HTTP request could not be mapped to a valid NamespaceName. The display output is entirely the inner error's message.

Solutions

1. Read the inner OrgBucketMappingError message to see which org/bucket failed.
2. Verify the request's org and bucket query parameters are present and well-formed.
3. Check that the bucket exists and its name maps to a valid NamespaceName.
4. Fix the client configuration (org/bucket) issuing the write.

Example fix

// before
let params = WriteParamsV2 { org: "".into(), bucket: "bad/bucket".into(), .. };
// after
let params = WriteParamsV2 { org: "my-org".into(), bucket: "my-bucket".into(), .. };

// Rust: pre-validate org/bucket before issuing a multi-tenant write
fn valid_org_bucket(org: &str, bucket: &str) -> bool {
    !org.is_empty() && !bucket.is_empty()
        && org.chars().all(|c| c.is_ascii_alphanumeric() || c == '-' || c == '_')
        && bucket.chars().all(|c| c.is_ascii_alphanumeric() || c == '-' || c == '_')
}

fn is_invalid_org_bucket(e: &MultiTenantExtractError) -> bool {
    matches!(e, MultiTenantExtractError::InvalidOrgAndBucket(_))
}

When it happens

Trigger: Handling a multi-tenant HTTP write request whose org/bucket identifiers cannot be converted into a reasonable namespace name (invalid characters, empty values).

Common situations: Clients sending writes to wrong or malformed org/bucket names; misconfigured SDK endpoints omitting org/bucket; URL-encoding issues.

Understand the failure class

Background: "invalid id" errors: invalid identifier format — why libraries reject IDs before lookup, and how to fix them — this error's family across 37 libraries.

Related errors

• <transparent: MultiTenantExtractError>
• <transparent: V2WriteParseError>
• not implemented
• <transparent: SingleTenantExtractError>
• Adding a new database would exceed limit of

AI-assisted analysis of influxdata/influxdb@06200ef96b (2026-09-19). Data as JSON: /api/errors/c1d45572c0b04863. Report an issue: GitHub.

Appendix: source

Thrown at core/iox_http/src/write/multi_tenant.rs:19

//! Parsing of HTTP requests that conform to the [V2 Write API] only.
//!
//! [V2 Write API]:
//!     https://docs.influxdata.com/influxdb/v2.6/api/#operation/PostWrite

use async_trait::async_trait;
use data_types::{NamespaceName, OrgBucketMappingError};
use iox_http_util::Request;

use super::{
    WriteParams, WriteParseError, WriteRequestUnifier,
    v2::{V2WriteParseError, WriteParamsV2},
};

/// Request parsing errors when operating in "single tenant" mode.
#[derive(Debug, thiserror::Error)]
pub enum MultiTenantExtractError {
    /// A failure to map a org & bucket to a reasonable [`NamespaceName`].
    #[error(transparent)]
    InvalidOrgAndBucket(#[from] OrgBucketMappingError),

    /// A [`WriteParamsV2`] failed to be parsed from the HTTP request.
    #[error(transparent)]
    ParseV2Request(#[from] V2WriteParseError),
}

/// Implement a by-ref conversion to avoid "moving" the inner errors when only
/// matching against the variants is necessary (the actual error content is
/// discarded, replaced with only a HTTP code)
impl From<&MultiTenantExtractError> for hyper::StatusCode {
    fn from(value: &MultiTenantExtractError) -> Self {
        // Exhaustively match the inner parser errors to ensure new additions
        // have to be explicitly mapped and are not accidentally mapped to a
        // "catch all" code.
        match value {
            MultiTenantExtractError::InvalidOrgAndBucket(_) => Self::BAD_REQUEST,
            MultiTenantExtractError::ParseV2Request(

View on GitHub (pinned to 06200ef96b)