influxdata/influxdb · error · PluginError

invalid database

Error message

invalid database {0}

What it means

PluginError::InvalidDatabase, a validation variant raised when a processing-engine plugin operation is given a database name/id that does not resolve to a real database — e.g. testing or installing a WAL plugin against a nonexistent database.

Solutions

1. Confirm the database name exists before running plugin test/install operations
2. Check for typos or case sensitivity in the database name
3. Create the database first if the plugin targets a new one

When it happens

Trigger: Thrown at influxdb3_processing_engine/src/plugins.rs:35 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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

Appendix: source

Thrown at influxdb3_processing_engine/src/plugins.rs:35

    write::WriteAccumulator,
};
use influxdb3_types::{
    DatabaseName,
    http::{WalPluginTestRequest, WalPluginTestResponse},
};
use influxdb3_write::{Precision, write_buffer};
use iox_time::{Time, TimeProvider};
use observability_deps::tracing::error;
use std::{fmt::Debug, path::PathBuf, str::FromStr, sync::Arc};
use tokio_util::sync::CancellationToken;

use anyhow::{Context, anyhow};
use parking_lot::Mutex;
use thiserror::Error;

#[derive(Debug, Error)]
pub enum PluginError {
    #[error("invalid database {0}")]
    InvalidDatabase(String),

    #[error("couldn't find db")]
    MissingDb,

    #[error(transparent)]
    PyError(#[from] pyo3::PyErr),

    #[error(transparent)]
    WriteBufferError(#[from] write_buffer::Error),

    #[error(transparent)]
    AnyhowError(#[from] anyhow::Error),

    #[error("reading plugin file: {0}")]
    ReadPluginError(#[from] std::io::Error),

    #[error("error executing plugin: {0}")]

View on GitHub (pinned to 06200ef96b)