dbt-labs / dbt-labs/dbt

DuckDB bugbash: external materialization and upstream registration flow

Open
#14,516 1 comment 0 reactions 0 assignees View on GitHub
adapter:duckdb area:adapters engine:v2 status:has-repro
Dominant language
Rust
Stars
13.8k
Forks
2.6k
Avg merge
21h 31m
Merged PRs (30d)
56

Description

## Goal
Compare dbt Core `dbt-duckdb` vs dbt Fusion DuckDB behavior for external materialization workflows.

## Experiment
Cover:
- writing Parquet output via external materialization
- a partitioned output case
- re-reading upstream external models, including `register_upstream_external_models()`-style flow where applicable

## Why this matters
External materialization is one of the adapter's distinctive workflow features.

## Success criteria
- Equivalent external model workflows operate in both engines, or
- a minimal repro isolates the Fusion gap

## Notes
Exclude static-analysis / `SQL_understanding` concerns from scope.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.