GitHub user Thustepsforward created a discussion: Superset Dev Image Not Exposing ECharts via API + Issues Connecting to Trino in Superset 5.0
I’m using the Superset development Docker image and trying to programmatically build charts (e.g., a simple bar chart) using the Superset API. However, every time I create a chart via the API, Superset only exposes the deprecated legacy chart types, not the modern ECharts ones. The UI shows all the correct ECharts visualizations, but the backend in the dev image does not—because ECharts appears to exist only in the frontend, not the backend. As a result, attempts to list available chart types or create charts result in 404 errors or Superset referencing the old charts, since the backend doesn’t know about ECharts in dev mode. I’d like to confirm whether this is expected behavior with the dev image, whether there’s a supported backend API that exposes the frontend chart registry? Additionally, I’m also experiencing issues connecting to Trino when using Superset 5.0.0. Since this requires the sqlalchemy-trino driver, I tried installing that inside the Superset container usi ng pip. It seems that Superset 5.0 uses a prebuilt Python environment inside that container. When I ran pip install commands, the packages installed to a different Python environment than the one Superset uses. Because of this, Superset didn't recognize the Trino driver, not allowing Superset and Trino to connect. Has anyone had success with this? I would appreciate your help! GitHub link: https://github.com/apache/superset/discussions/36434 ---- 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]
