https://nanta-data.dev/en/tags/superset/Recent content in Superset on nanta - Data EngineeringHugo -- gohugo.ioen© 2026 nantaFri, 27 Feb 2026 00:00:00 +0000https://nanta-data.dev/en/posts/superset-user-reported-issues/Fri, 27 Feb 2026 00:00:00 +0000https://nanta-data.dev/en/posts/superset-user-reported-issues/Our data governance team reported six issues they found while using Superset. From a missing .png extension on Slack screenshots to a CSV download 500 error caused by PostgreSQL’s idle_in_transaction_session_timeout killing the metadata DB connection mid-download. The trickiest one required tracing through both Superset server logs and RDS error logs to discover that the error connection and the causal connection were different — the SSL error was on the metadata DB, not Redshift.https://nanta-data.dev/en/posts/bigquery-bi-integration/Fri, 27 Feb 2026 00:00:00 +0000https://nanta-data.dev/en/posts/bigquery-bi-integration/We integrated BigQuery with both Redash and Superset for per-user BI access. Redash had a known schema browsing limitation. Superset hit a much worse problem — queries executed successfully on BigQuery but results never came back, blocking indefinitely. The root cause: gunicorn’s gevent worker monkey-patches Python’s threading primitives, which deadlocks gRPC calls inside the BigQuery SDK. Switching the worker type to gthread resolved it. We contributed a docs fix upstream.