What causes "Dremio" in dbt-labs/dbt-core?

Use a supported adapter until Dremio column building lands.

Dremio

Error message

Dremio

What it means

A `todo!()` panic in `ColumnBuilder::build` (column_builder.rs:39) for the Dremio adapter. The dispatch table lacks a Dremio column-builder implementation, so converting query/Arrow schema into Column metadata with a Dremio adapter panics with the message 'Dremio'.

Source

Thrown at crates/dbt-adapter/src/column/column_builder.rs:39

    }

    pub fn build(&self, field: &FieldRef, type_ops: &dyn TypeOps) -> AdapterResult<Column> {
        use AdapterType::*;
        match self.adapter_type {
            Snowflake => Ok(Self::build_snowflake(field, type_ops)),
            Bigquery => Ok(Self::build_bigquery(field, type_ops)),
            Databricks | Spark => Ok(Self::build_databricks(field, type_ops)),
            Redshift => Ok(Self::build_redshift(field, type_ops)),
            Postgres | Salesforce | DuckDB | LakeCompute => {
                Ok(Self::build_postgres_like(field, type_ops))
            }
            Fabric => Ok(Self::build_fabric(field, type_ops)),
            ClickHouse => Self::build_clickhouse(field, type_ops),
            Exasol => Ok(Self::build_exasol(field, type_ops)),
            Starburst => todo!("Starburst"),
            Athena => todo!("Athena"),
            Trino => todo!("Trino"),
            Dremio => todo!("Dremio"),
            Oracle => todo!("Oracle"),
            Datafusion => todo!("Datafusion"),
        }
    }

    pub fn build_from_parts(
        &self,
        name: String,
        dtype: String,
        char_size: Option<u32>,
        numeric_precision: Option<u64>,
        numeric_scale: Option<u64>,
        mode: Option<BigqueryColumnMode>,
    ) -> Column {
        use AdapterType::*;
        match self.adapter_type {
            Postgres => Column::new(
                Postgres,

View on GitHub (pinned to 0267ce9170)

Solutions

Use a supported adapter until Dremio column building lands.
Implement the Dremio arm in column_builder.rs:39 (Dremio types are largely ANSI/Postgres-like; `build_postgres_like` is a starting point).
Map the arm to a clean error instead of a panic so pipelines can fail gracefully.

Example fix

// before
Dremio => todo!("Dremio"),
// after
Dremio => Ok(Self::build_postgres_like(field, type_ops)),

Defensive patterns

Strategy: type-guard

Validate before calling

if adapter == AdapterType::Dremio {
    return Err(anyhow!("Dremio column building is not implemented yet"));
}

Type guard

fn build_supported(t: AdapterType) -> bool {
    matches!(t, Postgres | Salesforce | DuckDB | LakeCompute | Fabric | ClickHouse | Exasol)
}

Try / catch

let res = std::panic::catch_unwind(AssertUnwindSafe(|| builder.build(field, type_ops)));
if let Err(_) = res { return Err(anyhow!("unsupported adapter for column building")); }

Prevention

Gate Dremio features on adapter support before running schema introspection
Contribute a Dremio arm (ANSI types map well to build_postgres_like)
Run a variant-sweep test for ColumnBuilder::build when adding adapters
Replace todo!() arms with typed errors as first hardening step

When it happens

Trigger: Calling ColumnBuilder::build via schema_to_columns, get_column_schema_from_query, or update_node_columns while the adapter is Dremio — e.g. catalog generation or result introspection on a Dremio connection.

Common situations: First run of docs generate or column-aware features against a Dremio adapter profile; also in adapter-coverage tests iterating over all AdapterType variants.

Related errors

AI-assisted analysis of dbt-labs/dbt-core@0267ce9170 (2026-09-07). Data as JSON: /api/errors/58e77642387831a6. Report an issue: GitHub.