DuckDB can write to an Iceberg catalog now, in an alpha

The interesting release of the month arrived in an alpha, which is where interesting releases usually arrive.

dbt Core's v2 alpha line added read-write Horizon and Unity catalog support for DuckDB, over Iceberg REST, on duckdb 1.5.4. The stable line, v1.12.0 on July 16, took the quieter half: a catalog_database override for catalog write integrations. Read the two together and the direction is legible. DuckDB stops being the engine you test models on and becomes an engine that writes tables something else will later read.

We have called the single-node renaissance real before, with one caveat: it ended where shared state began. The catalog is the shared state. Writing into a REST catalog other engines honor is the first credible answer to that caveat.

Temperature check. Alpha means alpha. Those same Horizon and Unity attachments were read-only in an earlier v2 alpha, and an interface that moves that far between June and July will move again. The distance between "DuckDB can write here" and "our pipeline writes here at three in the morning" is measured in credentials, retries and whoever ends up owning compaction.

Verdict: prototype on it this quarter, budget nothing on it. Ask again at v2 stable, and ask first what happens to a half-written commit.