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:05:36 UTC
Re: [D] Superset Dev Image Not Exposing ECharts via API + Issues Connecting to Trino in Superset 5.0 [superset]
GitHub user dosubot[bot] edited a comment on the discussion: Superset Dev Image Not Exposing ECharts via API + Issues Connecting to Trino in Superset 5.0
<!-- Greeting -->
Hi @Thustepsforward! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
This is expected behavior with the Superset dev Docker image: when running in dev mode, the backend API does not expose modern ECharts chart types—only legacy ones—because the frontend build is skipped and ECharts exist only in the frontend registry, not the backend. There is currently no backend API that exposes the frontend chart registry, so programmatic chart creation via the API is limited to legacy chart types in this setup. See [this explanation](https://github.com/apache/superset/pull/30021) for details.
For connecting to Trino in Superset 5.0.0, you need to install the sqlalchemy-trino driver in the Python virtual environment used by Superset, which is located at `/app/.venv`. Running pip install outside this environment (e.g., using the system pip) will not work. Instead, run `/app/.venv/bin/pip install sqlalchemy-trino` inside the container, or use `uv pip install sqlalchemy-trino`. For persistent installs, extend the Superset image with a Dockerfile that runs the correct pip install command, or override the container command in docker-compose to install the driver before starting Superset. More details and examples are available [here](https://github.com/apache/superset/issues/33691#issuecomment-2940584591) and [here](https://github.com/apache/superset/issues/34557).
Once installed in the correct environment, Superset will recognize the Trino driver and it should appear as an option in the UI, unless it is excluded by the backend denylist configuration.
<!-- 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).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-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=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=5997cf15-3d8c-4aa1-9e15-9b1686eebbfe) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-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=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/36434#discussioncomment-15165739
----
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