GitHub user dosubot[bot] added a comment to the discussion: Not able to run any SQL query on SQL lab
<!-- Answer --> Since impersonation is disabled and queries work in your terminal but not in Superset, the issue is likely with Superset’s connection configuration or environment. Here are the most common causes and next steps: - **Driver compatibility**: Superset requires `sqlalchemy==1.4.54`, but the latest StarRocks adapter needs SQLAlchemy v2, which can cause authentication or query execution errors. Make sure you’re using `starrocks==1.0.6` for the driver in your Superset environment to avoid this conflict [source](https://github.com/apache/superset/issues/33544). - **Connection string and SSL settings**: Double-check that your Superset connection string matches the one you use in your terminal, including any SSL or root certificate options. In Superset, these should be set either in the SQLAlchemy URI or in the Extra JSON as `engine_params.connect_args` (for example: `{"engine_params": {"connect_args": {"sslmode": "require", "sslrootcert": "/path/to/cert.pem"}}}`) [source](https://github.com/apache/superset/blob/master/docs/docs/configuration/databases.mdx). - **Endpoint configuration**: If Superset is pointed at a read-only StarRocks endpoint or proxy, even SELECT queries can fail with authentication or permission errors. Make sure the endpoint allows reads and matches what you use in your terminal [source](https://github.com/apache/superset/discussions/33915#discussioncomment-13580929). - **Environment-specific issues**: If you’re running Superset in Kubernetes or with Helm, missing Redis password configuration can cause authentication errors in SQL Lab, even if the database credentials are correct. Check your Helm chart’s `values.yaml` for Redis password settings if applicable [source](https://github.com/apache/superset/issues/22773). If you share your Superset connection string, Extra JSON, and the exact driver versions, I can help spot any mismatches. Also, check Superset and StarRocks logs for more detailed error messages—they often pinpoint where authentication is failing. <!-- 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/5e0f65a2-4b12-4be0-ba07-4c41687b43bd?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5e0f65a2-4b12-4be0-ba07-4c41687b43bd?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5e0f65a2-4b12-4be0-ba07-4c41687b43bd?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5e0f65a2-4b12-4be0-ba07-4c41687b43bd?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5e0f65a2-4b12-4be0-ba07-4c41687b43bd?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5e0f65a2-4b12-4be0-ba07-4c41687b43bd?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5e0f65a2-4b12-4be0-ba07-4c41687b43bd?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Since%20impersonation%20is%20disabled%20and%20queries%20work%20in%20your%20terminal%20but%20not%20in%20Superset%2C%20the%20issue%20is%20likely%20with%20Superset%E2%80%99s%20connection%20configuration%20or%20environment.%20Here%20are%20the%20most%20common%20causes%20and%20next%20steps%3A%0A%0A-%20%2A%2ADriver%20compatibility%2A%2A%3A%20Superset%20requires%20%60sqlalchemy%3D%3D1.4.54%60%2C%20but%20the%20latest%20StarRocks%20adapter%20needs%20SQLAlchemy%20v2%2C%20which%20can%20cause%20authentication%20or%20query%20execution%20errors.%20Make%20sure%20you%E2%80%99re%20using%20%60starrocks%3D%3D1.0.6%60%20for%20the%20driver%20in%20your%20Superset%20environment%20to%20avoid%20this%20conflict%20%5Bsource%5D%28https%3A//github.com/apache/superset/issues/33544% 29.%0A-%20%2A%2AConnection%20string%20and%20SSL%20settings%2A%2A%3A%20Double-check%20that%20your%20Superset%20connection%20string%20matches%20the%20one%20you%20use%20in%20your%20terminal%2C%20including%20any%20SSL%20or%20root%20certificate%20options.%20In%20Superset%2C%20these%20should%20be%20set%20either%20in%20the%20SQLAlchemy%20URI%20or%20in%20the%20Extra%20JSON%20as%20%60engine_params.connect_args%60%20%28for%20example%3A%20%60%7B%22engine_params%22%3A%20%7B%22connect_args%22%3A%20%7B%22sslmode%22%3A%20%22require%22%2C%20%22sslrootcert%22%3A%20%22/path/to/cert.pem%22%7D%7D%7D%60%29%20%5Bsource%5D%28https%3A//github.com/apache/superset/blob/master/docs/docs/configuration/databases.mdx%29.%0A-%20%2A%2AEndpoint%20configuration%2A%2A%3A%20If%20Superset%20is%20pointed%20at%20a%20read-only%20StarRocks%20endpoint%20or%20proxy%2C%20even%20SELECT%20queries%20can%20fail%20with%20authentication%20or%20permission%20errors.%20Make%20sure%20the%20endpoint%20allows%20reads%20and%20matches%20wh at%20you%20use%20in%20your%20terminal%20%5Bsource%5D%28https%3A//github.com/apache/superset/discussions/33915%23discussioncomment-13580929%29.%0A-%20%2A%2AEnvironment-specific%20issues%2A%2A%3A%20If%20you%E2%80%99re%20running%20Superset%20in%20Kubernetes%20or%20with%20Helm%2C%20missing%20Redis%20password%20configuration%20can%20cause%20authentication%20errors%20in%20SQL%20Lab%2C%20even%20if%20the%20database%20credentials%20are%20correct.%20Check%20your%20Helm%20chart%E2%80%99s%20%60values.yaml%60%20for%20Redis%20password%20settings%20if%20applicable%20%5Bsource%5D%28https%3A//github.com/apache/superset/issues/22773%29.%0A%0AIf%20you%20share%20your%20Superset%20connection%20string%2C%20Extra%20JSON%2C%20and%20the%20exact%20driver%20versions%2C%20I%20can%20help%20spot%20any%20mismatches.%20Also%2C%20check%20Superset%20and%20StarRocks%20logs%20for%20more%20detailed%20error%20messages%E2%80%94they%20often%20pinpoint%20where%20authentication%20is%20failing.) [](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/36482) GitHub link: https://github.com/apache/superset/discussions/36710#discussioncomment-15281602 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
