eschutho commented on PR #35294: URL: https://github.com/apache/superset/pull/35294#issuecomment-3340561201
## Why Pin DuckDB to <0.11? During testing of showtime ephemeral environments, we discovered that newer DuckDB versions (1.3.x) cause connection failures with the error: ``` [SQL: unhashable type: '_duckdb.typing.DuckDBPyType'] ``` ### Root Cause The DuckDB core library versions ≥1.0 introduced type system changes that are incompatible with Superset's DuckDB integration code. The error occurs when trying to establish any DuckDB connection (even basic `:memory:` connections). ### Testing ✅ **Confirmed working**: `duckdb==0.10.2` + `duckdb-engine>=0.17.0` ❌ **Confirmed broken**: `duckdb==1.3.2` + `duckdb-engine>=0.17.0` ### Version Constraint Rationale - **`duckdb>=0.10.2,<0.11`**: Stay within the 0.10.x series that we've tested and confirmed works - **`duckdb-engine>=0.17.0`**: Keep the current driver version (no issues with newer driver) This matches the approach used in the `motherduck` configuration which also pins `duckdb==0.10.2` to avoid these compatibility issues. Once Superset's DuckDB integration is updated to work with DuckDB 1.x+, we can relax this constraint. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
