You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 03:19:04 UTC
Re: [D] ducklake support [superset]
GitHub user dosubot[bot] edited a comment on the discussion: ducklake support
<!-- Greeting -->
Hi @dridk! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
Superset does not have native, explicit support for the DuckLake format, but you can likely query DuckLake tables from Superset if DuckDB itself can access them. Superset connects to DuckDB using its DuckDB connector, which passes SQL queries directly to DuckDB. If you have set up DuckLake in DuckDB (by installing the DuckLake extension and attaching the catalog), Superset should be able to query any tables that DuckDB exposes, including those managed by DuckLake, as long as the underlying DuckDB SQLAlchemy dialect supports it. There is no special handling or abstraction for DuckLake in Superset—everything depends on DuckDB's capabilities and configuration [[source](https://github.com/apache/superset/blob/fc13a0fde5b775f6734a0280742f44ddc2acdadb/superset/db_engine_specs/duckdb.py)].
For authentication to the DuckLake metastore: this depends on the backend you use for the DuckLake catalog (e.g., DuckDB, PostgreSQL, SQLite, MySQL). Superset manages authentication to DuckDB via the SQLAlchemy URI, which can include parameters like access tokens (for example, when connecting to MotherDuck, a DuckDB cloud service). For other backends, you would use the appropriate SQLAlchemy connection string for that database, including any required credentials [[source](https://github.com/apache/superset/blob/fc13a0fde5b775f6734a0280742f44ddc2acdadb/superset/db_engine_specs/README.md)].
There are no existing issues or documentation in Superset specifically about DuckLake support. If DuckDB can see and query your DuckLake tables, Superset should be able to as well, but you may need to manage authentication and catalog setup outside of Superset and ensure your DuckDB connection string is correct.
If you run into issues, they are likely to be related to the DuckDB SQLAlchemy dialect or the specifics of your DuckLake catalog backend, not Superset itself.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=f98b0e55-1e36-4a59-ae27-02af43bcbf81) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33666#discussioncomment-13348410
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org