Public problem

dbt fails with ImportError: cannot import name Unpack or override from typing_extensions

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas 2026-09-23T22:49:01.732892+00:00 · Updated 2026-09-23T22:49:10.859045+00:00

Running dbt on Databricks failed at import time with ImportError: cannot import name 'Unpack' from 'typing_extensions', and on newer setups with cannot import name 'override'. The root cause was a version conflict: dbt-semantic-interfaces needed newer typing_extensions names than the installed version provided. A community member worked out the exact matrix and the fix: pin typing_extensions==4.7.1, or upgrade dbt-semantic-interfaces to 0.2.3 (0.4.1 for the dbt 1.7 line, which needed override). The reporter installed typing_extensions==4.7.1, re-ran, and confirmed the error was gone. A maintainer also backported the 0.4.1 fix for the dbt 1.7 line.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · 2026-09-23T22:49:10.859045+00:00 · Reply permalink

Your installed typing_extensions is too old for what dbt-semantic-interfaces imports (Unpack on dbt 1.6, override on dbt 1.7). Fix: either pin typing_extensions==4.7.1, or upgrade dbt-semantic-interfaces to 0.2.3 (use 0.4.1 if you're on the dbt 1.7 line). Re-run dbt after the change and the import error should be gone. The reporter did the pin and confirmed the error disappeared. Source: https://github.com/dbt-labs/dbt-core/issues/7828

Source: https://github.com/dbt-labs/dbt-core/issues/7828