dosubot[bot] commented on issue #36808: URL: https://github.com/apache/superset/issues/36808#issuecomment-3686032531
<!-- Answer --> This error is caused by how Superset handles errors during chart creation: when Explore tries to reflect table/column metadata for DuckDB, any failure in this process (such as a DBAPI or SQLAlchemy error) is misclassified as an authentication issue. The frontend then displays "Authentication required (Issue 1011)", even though DuckDB does not require authentication and the connection itself is valid. This is a misleading error message resulting from the error handling path, not an actual authentication problem. The underlying issue is a metadata reflection failure during chart creation, not a problem with your DuckDB connection or credentials. There is no existing bug report or fix specifically for this misleading error. The DuckDB engine spec in Superset only requires authentication for MotherDuck connections, not for standard DuckDB usage, so the error message does not reflect the real cause of the failure. Recent updates to DuckDB integration do not address this specific error case. If you need to work around this, check for any issues with table/view metadata or schema compatibility between DuckDB and Superset, as the failure is likely happening during metadata inspection. If you have logs or stack traces from Superset, they may help pinpoint the exact cause of the metadata reflection failure. For reference, see the [DuckDB engine spec code](https://github.com/apache/superset/blob/master/superset/db_engine_specs/duckdb.py) and the [chart creation/metadata inspection flow](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/databases/api.py#L677-L1086). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/afe9a97f-11bf-40fc-979f-b4237e129fe6?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/afe9a97f-11bf-40fc-979f-b4237e129fe6?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/afe9a97f-11bf-40fc-979f-b4237e129fe6?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/afe9a97f-11bf-40fc-979f-b4237e129fe6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/afe9a97f-11bf-40fc-979f-b4237e129fe6?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/afe9a97f-11bf-40fc-979f-b4237e129fe6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/afe9a97f-11bf-40fc-979f-b4237e129fe6?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=This%20error%20is%20caused%20by%20how%20Superset%20handles%20errors%20during%20chart%20creation%3A%20when%20Explore%20tries%20to%20reflect%20table/column%20metadata%20for%20DuckDB%2C%20any%20failure%20in%20this%20process%20%28such%20as%20a%20DBAPI%20or%20SQLAlchemy%20error%29%20is%20misclassified%20as%20an%20authentication%20issue.%20The%20frontend%20then%20displays%20%22Authentication%20required%20%28Issue%201011%29%22%2C%20even%20though%20DuckDB%20does%20not%20require%20authentication%20and%20the%20connection%20itself%20is%20valid.%20This%20is%20a%20misleading%20error%20message%20resulting%20from%20the%20error%20handling%20path%2C%20not%20an%20actual%20authentication%20problem.%20The%20underlying%20issue%20is%20a%20metadata%20reflection%20failure %20during%20chart%20creation%2C%20not%20a%20problem%20with%20your%20DuckDB%20connection%20or%20credentials.%20%0A%0AThere%20is%20no%20existing%20bug%20report%20or%20fix%20specifically%20for%20this%20misleading%20error.%20The%20DuckDB%20engine%20spec%20in%20Superset%20only%20requires%20authentication%20for%20MotherDuck%20connections%2C%20not%20for%20standard%20DuckDB%20usage%2C%20so%20the%20error%20message%20does%20not%20reflect%20the%20real%20cause%20of%20the%20failure.%20Recent%20updates%20to%20DuckDB%20integration%20do%20not%20address%20this%20specific%20error%20case.%20%0A%0AIf%20you%20need%20to%20work%20around%20this%2C%20check%20for%20any%20issues%20with%20table/view%20metadata%20or%20schema%20compatibility%20between%20DuckDB%20and%20Superset%2C%20as%20the%20failure%20is%20likely%20happening%20during%20metadata%20inspection.%20If%20you%20have%20logs%20or%20stack%20traces%20from%20Superset%2C%20they%20may%20help%20pinpoint%20the%20exact%20cause%20of%20the%20metadata%20reflection %20failure.%20%0A%0AFor%20reference%2C%20see%20the%20%5BDuckDB%20engine%20spec%20code%5D%28https%3A//github.com/apache/superset/blob/master/superset/db_engine_specs/duckdb.py%29%20and%20the%20%5Bchart%20creation/metadata%20inspection%20flow%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/databases/api.py%23L677-L1086%29.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36808) -- 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]
