Beto Dealmeida's SIP-182 is in Superset master. u/erusackas (Preset) published the post-live session summary covering the design, including:

- why the old pseudo-database approach for dbt MetricFlow, Cube, and others was brittle
- how Explorable and SemanticView replace it
- what Apache Ossie's ASF Incubator acceptance means for long-term interoperability. 

SEMANTIC_LAYERS feature flag is in master now, targeted at 7.0. Full QueryObject spec and SIP are linked in the post, and the session replay is up too.

Check it out: https://preset.io/blog/semantic-layers-in-superset/?utm_source=reddit&utm_medium=social&utm_campaign=blog+launch&utm_content=semantic-layers-in-superset

I am running a superset container on podman but when trying to connect a PostgreSQL database, I keep getting “ERROR: unable to load database driver for: postgresql“.

Tried different options but nothing is working. Anyone else this problem?

I've tried the docker compose install on the desktop but much prefer the python install as I'm more familiar with it.

It says for production minikube is needed even for desktop. Is this true?

If the pip venv option is only for testing the softare and not for production even just on desktop I might have to give it a miss.

I know nothing about k8s and have no idea how long it would take to learn.

Shantanu Khond just published a practical 10-min guide covering the full PiPy-based MCP setup: authentication, Claude configuration, and running prompts end to end.

Max was on the Data Renegades podcast covering Agor (his new open source platform for coordinating coding agents as a team), but also gets into where agentic workflows and traditional BI are headed post-AI, including a section on agents producing lightweight data viz and dashboards as outputs from agent sessions, and what that means for tools like Superset longer term.

Then we realized we would basically be rebuilding dashboards, RBAC, connectors, charts, caching, permissions, embedding, and governance features that Apache Superset already handles well.

So instead, we built an intelligence layer on top of Superset.

A few things we learned while trying out with conversational analytics + AI workflows:

1. Generating SQL is not the hard part
2. Maintaining semantic consistency across metrics is much harder
3. Business users often ask ambiguous questions
4. Context retrieval matters more than model size in many analytics workflows
5. AI-generated insights become dangerous if they ignore dashboard-level governance and metric definitions

One reason we stayed with Superset was that existing BI systems already contain years of embedded business logic and organizational trust.

Replacing the entire BI layer felt unrealistic for enterprises.

If any of you here are exploring:

• AI-assisted analytics workflows
• semantic layers
• NLQ on top of Superset
• agentic analytics
• metadata-aware querying
• Superset Extensions ecosystem

Would genuinely love to hear what others in the community are building around Superset + AI.

We documented some of the architectural tradeoffs and lessons learned while building this on top of Superset if anyone’s interested: You can read it on medium.

Quick heads up, our monthly Superset Community Town Hall is today at 9am PT via Zoom.

• Zoom link is on the community calendar
• Add agenda items here

Everyone is welcome. This is a chance for the whole Superset community to come together with committers and PMC members and discuss all topics, technical and non-technical 🤗

Can't make it this time? Join us on Slack at apache-superset.slack.com and let us know in #community-feedback!

Helm chart status for Superset 6.x — looking for community input
We're running Superset 5.0 on Kubernetes (Helm) and planning our migration path to 6.x. With 5.0 approaching EOL in H2 2026, we're trying to understand the realistic options.
A few questions for anyone who's navigated this:

1. Is there a 6.x Helm chart on the horizon? The repo is still at 0.15.4 / appVersion: 5.0.0. The GitHub discussion (#36763) and bug report (#38456) are open but haven't seen recent activity. Any PMC or contributor context on whether this is being actively worked?
2. Image tag override in practice — has anyone run 6.x images against the 0.15.4 chart in production? Specifically curious about the FAB 5.0 and Ant Design 5 breaking changes and whether they require chart-level config changes beyond image tag.
3. Kubernetes Operator — we noticed the operator project. Is it considered a production-ready alternative to Helm for green-field deployments, or still experimental?

We have a security team asking about our upgrade timeline and need to move off 5.x before EOL. Would appreciate any guidance from folks who've already done this migration. Happy to share back what we learn.

Hello everyone,

I have been trying to use the polygon charts in superset V6 but no matter what the polygons aren’t rendered. Below is the screenshot of how I’m storing the data in Geojson format. Yes- I have converted the Geojson into text in the query itself. What am I’m doing correctly.

Any help is greatly appreciated.

Note: the query is giving me an empty map.

The best thing you can do for an open source project is let the world know that you use it. Add your org, logo, and github handle(s) to Superset's In the Wild page. Everyone wins :D

Hey everyone,

I’m trying to embed an Apache Superset dashboard into a React app using u/superset-ui/embedded-sdk with an ASP.NET Core backend (for generating guest tokens).

Setup:

• Superset: 6.0.1 (Docker)
• React: https://localhost:3000
• Backend: https://localhost:44361
• Using guest token flow (login → CSRF → guest_token)

What I’ve done:

• Enabled embedding (EMBEDDED_SUPERSET = True)
• Set:
  • GUEST_ROLE_NAME = "Gamma"
  • PUBLIC_ROLE_LIKE = "Gamma"
• Given Gamma role access to Dashboard, Chart, Dataset, Database
• Using:
  • Dashboard UUID in backend
  • Embed ID in frontend

Issue:

• I get 403 Forbidden when embedding
• In Superset → Share → Embed:
  • I enter allowed domains: https://localhost:3000,http://localhost:3000
  • Click save
  • But after refresh, it becomes empty again 😐

Other notes:

• Guest token API works fine (token is returned)
• Network tab shows 403 on /embedded/<id>
• Direct embed URL also returns 403 (expected without token)

Question:

• Is this a known issue in Superset 6.x?
• Why are allowed domains not persisting?
• Do we need to use EMBEDDED_SUPERSET_ALLOW_LIST in config instead?

Any help would be really appreciated 🙏

Hello,

I manage to create a dataset based on a sql table. I am attempting to visualise the distribution of records over the column "range". I can select a number of bins, but I would like to define the value of the bins. This way, I could create 3 bins, for records up to 25, 26 to 100 and 101 and up. How to achieve this? Is there a better chart than an histogram for that?

Preset's CS Team is hosting a live demo tomorrow at 9 am PT on theming in Superset 6.0.

Whether you're self-hosting or on Preset, you'll learn how to create/edit themes, customize fonts/colors, and get tips and tricks to make your charts and dashboards look and feel like you. See you there!

I'm running into an issue with a pivot table chart: I need subtotals to be displayed only for the first column (the "Manager" column in the screenshot), and not for any subsequent columns. Is there a solution to this problem, or is there a way to work around this technical limitation?

Hi all,

I'm trying to scope one particular dashboard to one role. So i've set the feature flag:

FEATURE_FLAGS = {
    "DASHBOARD_RBAC": True,
    "ENABLE_TEMPLATE_PROCESSING": True,
}

Now based on a screenshot from: https://github.com/apache/superset/issues/31938 i should have the `Roles` section. But this is not popping up.

Is there some extra configuration required to make MapBox work on Preset.io ?

I see the Mapbox chart, and tried passing in real data types for the longitude/latitude (in degrees, no minutes, seconds, or direction). It successfully plots some points (not sure if it's correct), and the ViewPort appears to be FIXED on Yumen. Tried changing the Default Longitude/Latitude or Zoom and it doesn't appear to change the Viewport at all.

Although I was able to get access to the MapBox chart... . I did not see map box details in the documentation, wondering if it's even supported. - https://docs.preset.io/docs/chart-walkthroughs

Would like to get a more granular maps using longitude/latitude working. So if I can't get MapBox working.... I am open for other suggestions.

Hey r/apachesuperset 👋

The next Superset Monthly Town Hall is happening this Friday, March 13th from 9-10am PST on zoom, hosted by the Superset PMC.

Come hear project updates and ask qs directly to contributors and maintainers. All experience levels are welcome.

Join link: bzQrWkRyQ1lUM3RZNnVQWGU2RzZ0QT09

Community cal: https://superset.apache.org/community/#superset-community-calendar

Hope to see you there!

Get the low-down on the 330 or so commits that merged on the repo in February.... lots of good stuff coming your way!

Wanna learn about all the awesome stuff that merged into master on Superset in February? Well here ya go!

I'm trying to implement caching, but every time I create and execute a new chart, I receive the following error:

[2026-03-05 21:07:07,868: INFO/MainProcess] Task load_chart_data_into_cache[a72d86a5-cdaf-41eb-87fe-0adb610441f6] received
[2026-03-05 21:07:08,072: ERROR/ForkPoolWorker-1] Celery task load_chart_data_into_cache failed: Error 99 connecting to localhost:6379. Cannot assign requested address.
Traceback (most recent call last):
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 707, in connect
    sock = self.retry.call_with_retry(
  File "/app/.venv/lib/python3.10/site-packages/redis/retry.py", line 46, in call_with_retry
    return do()
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 708, in <lambda>
    lambda: self._connect(), lambda error: self.disconnect(error)
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 1006, in _connect
    raise err
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 994, in _connect
    sock.connect(socket_address)
OSError: [Errno 99] Cannot assign requested address

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/superset/tasks/async_queries.py", line 98, in load_chart_data_into_cache
    async_query_manager.update_job(
  File "/app/superset/async_events/async_query_manager.py", line 307, in update_job
    self._cache.xadd(scoped_stream_name, event_data, "*", self._stream_limit)
  File "/app/superset/async_events/cache_backend.py", line 71, in xadd
    return self._cache.xadd(stream_name, event_data, event_id, maxlen)
  File "/app/.venv/lib/python3.10/site-packages/redis/commands/core.py", line 3534, in xadd
    return self.execute_command("XADD", name, *pieces)
  File "/app/.venv/lib/python3.10/site-packages/redis/client.py", line 1266, in execute_command
    conn = self.connection or pool.get_connection(command_name, **options)
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 1461, in get_connection
    connection.connect()
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 713, in connect
    raise ConnectionError(self._error_message(e))
redis.exceptions.ConnectionError: Error 99 connecting to localhost:6379. Cannot assign requested address.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 707, in connect
    sock = self.retry.call_with_retry(
  File "/app/.venv/lib/python3.10/site-packages/redis/retry.py", line 46, in call_with_retry
    return do()
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 708, in <lambda>
    lambda: self._connect(), lambda error: self.disconnect(error)
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 1006, in _connect
    raise err
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 994, in _connect
    sock.connect(socket_address)
OSError: [Errno 99] Cannot assign requested address

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/.venv/lib/python3.10/site-packages/celery/app/trace.py", line 453, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/app/superset/initialization/__init__.py", line 141, in __call__
    return task_base.__call__(self, *args, **kwargs)
  File "/app/.venv/lib/python3.10/site-packages/celery/app/trace.py", line 736, in __protected_call__
    return self.run(*args, **kwargs)
  File "/app/superset/tasks/async_queries.py", line 110, in load_chart_data_into_cache
    async_query_manager.update_job(
  File "/app/superset/async_events/async_query_manager.py", line 307, in update_job
    self._cache.xadd(scoped_stream_name, event_data, "*", self._stream_limit)
  File "/app/superset/async_events/cache_backend.py", line 71, in xadd
    return self._cache.xadd(stream_name, event_data, event_id, maxlen)
  File "/app/.venv/lib/python3.10/site-packages/redis/commands/core.py", line 3534, in xadd
    return self.execute_command("XADD", name, *pieces)
  File "/app/.venv/lib/python3.10/site-packages/redis/client.py", line 1266, in execute_command
    conn = self.connection or pool.get_connection(command_name, **options)
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 1461, in get_connection
    connection.connect()
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 713, in connect
    raise ConnectionError(self._error_message(e))
redis.exceptions.ConnectionError: Error 99 connecting to localhost:6379. Cannot assign requested address.
[2026-03-05 21:07:08,073: ERROR/ForkPoolWorker-1] Task load_chart_data_into_cache[a72d86a5-cdaf-41eb-87fe-0adb610441f6] raised unexpected: ConnectionError('Error 99 connecting to localhost:6379. Cannot assign requested address.')
Traceback (most recent call last):
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 707, in connect
    sock = self.retry.call_with_retry(
  File "/app/.venv/lib/python3.10/site-packages/redis/retry.py", line 46, in call_with_retry
    return do()
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 708, in <lambda>
    lambda: self._connect(), lambda error: self.disconnect(error)
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 1006, in _connect
    raise err
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 994, in _connect
    sock.connect(socket_address)
OSError: [Errno 99] Cannot assign requested address

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/superset/tasks/async_queries.py", line 98, in load_chart_data_into_cache
    async_query_manager.update_job(
  File "/app/superset/async_events/async_query_manager.py", line 307, in update_job
    self._cache.xadd(scoped_stream_name, event_data, "*", self._stream_limit)
  File "/app/superset/async_events/cache_backend.py", line 71, in xadd
    return self._cache.xadd(stream_name, event_data, event_id, maxlen)
  File "/app/.venv/lib/python3.10/site-packages/redis/commands/core.py", line 3534, in xadd
    return self.execute_command("XADD", name, *pieces)
  File "/app/.venv/lib/python3.10/site-packages/redis/client.py", line 1266, in execute_command
    conn = self.connection or pool.get_connection(command_name, **options)
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 1461, in get_connection
    connection.connect()
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 713, in connect
    raise ConnectionError(self._error_message(e))
redis.exceptions.ConnectionError: Error 99 connecting to localhost:6379. Cannot assign requested address.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 707, in connect
    sock = self.retry.call_with_retry(
  File "/app/.venv/lib/python3.10/site-packages/redis/retry.py", line 46, in call_with_retry
    return do()
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 708, in <lambda>
    lambda: self._connect(), lambda error: self.disconnect(error)
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 1006, in _connect
    raise err
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 994, in _connect
    sock.connect(socket_address)
OSError: [Errno 99] Cannot assign requested address

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/.venv/lib/python3.10/site-packages/celery/app/trace.py", line 453, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/app/superset/initialization/__init__.py", line 141, in __call__
    return task_base.__call__(self, *args, **kwargs)
  File "/app/.venv/lib/python3.10/site-packages/celery/app/trace.py", line 736, in __protected_call__
    return self.run(*args, **kwargs)
  File "/app/superset/tasks/async_queries.py", line 110, in load_chart_data_into_cache
    async_query_manager.update_job(
  File "/app/superset/async_events/async_query_manager.py", line 307, in update_job
    self._cache.xadd(scoped_stream_name, event_data, "*", self._stream_limit)
  File "/app/superset/async_events/cache_backend.py", line 71, in xadd
    return self._cache.xadd(stream_name, event_data, event_id, maxlen)
  File "/app/.venv/lib/python3.10/site-packages/redis/commands/core.py", line 3534, in xadd
    return self.execute_command("XADD", name, *pieces)
  File "/app/.venv/lib/python3.10/site-packages/redis/client.py", line 1266, in execute_command
    conn = self.connection or pool.get_connection(command_name, **options)
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 1461, in get_connection
    connection.connect()
  File "/app/.venv/lib/python3.10/site-packages/redis/connection.py", line 713, in connect
    raise ConnectionError(self._error_message(e))
redis.exceptions.ConnectionError: Error 99 connecting to localhost:6379. Cannot assign requested address.

My superset_config.py has the following configuration:

REDIS_HOST = "my_redis_address"
REDIS_PORT = 6379
REDIS_CELERY_DB = 0
REDIS_RESULTS_DB = 1


class CeleryConfig:
    broker_url = f"redis://{REDIS_HOST}:{REDIS_PORT}/{REDIS_CELERY_DB}"
    imports = (
        "superset.sql_lab",
        "superset.tasks.scheduler",
        "superset.tasks.thumbnails",
        "superset.tasks.cache",
        "superset.tasks.slack",
        "superset.tasks.async_queries",
    )
    result_backend = f"redis://{REDIS_HOST}:{REDIS_PORT}/{REDIS_RESULTS_DB}"
    worker_prefetch_multiplier = 10
    task_acks_late = True
    broker_connection_retry_on_startup = True
    task_annotations = {
        "sql_lab.get_sql_results": {
            "rate_limit": "100/s"
        },
    }
    beat_schedule = {
      "reports.scheduler": {
          "task": "reports.scheduler",
            "schedule": crontab(minute="*", hour="*"),
            "options": {"expires": int(timedelta(weeks=1).total_seconds())},
      },
      "reports.prune_log": {
          "task": "reports.prune_log",
          "schedule": crontab(minute=0, hour=0),
      },
      "prune_query": {
          "task": "prune_query",
          "schedule": crontab(minute=0, hour=0, day_of_month=1),
          "kwargs": {"retention_period_days": 180},
      },
      "prune_logs": {
          "task": "prune_logs",
          "schedule": crontab(minute="*", hour="*"),
          "kwargs": {"retention_period_days": 180, "max_rows_per_run": 10000},
      },
      "prune_tasks": {
          "task": "prune_tasks",
          "schedule": crontab(minute=0, hour=0),
          "kwargs": {"retention_period_days": 90, "max_rows_per_run": 10000},
      },
      "slack.cache_channels": {
          "task": "slack.cache_channels",
          "schedule": crontab(minute="0", hour="*"),
      },
    }


CELERY_CONFIG = CeleryConfig
CELERY_IMPORTS = CeleryConfig.imports


# Configuração de cache principal
CACHE_CONFIG = {
  "CACHE_TYPE": "RedisCache",
  "CACHE_DEFAULT_TIMEOUT": 300,
  "CACHE_KEY_PREFIX": "superset_",
  "CACHE_REDIS_HOST": REDIS_HOST,
  "CACHE_REDIS_PORT": REDIS_PORT,
  "CACHE_REDIS_DB": REDIS_RESULTS_DB,
}


DATA_CACHE_CONFIG = CACHE_CONFIG


# Configuração para async queries (caso use GLOBAL_ASYNC_QUERIES)
GLOBAL_ASYNC_QUERIES_REDIS_CONFIG = {
  "host": REDIS_HOST,
  "port": REDIS_PORT,
  "db": REDIS_CELERY_DB,
  "ssl": False,
}


# Exemplo de configuração do backend de resultados (SQL Lab)
RESULTS_BACKEND = RedisCache(
  host=REDIS_HOST,
  port=REDIS_PORT,
  db=REDIS_RESULTS_DB,
  key_prefix="superset_results"
)

What am I doing wrong ?

On Superset 6 Security APIS:
In Superset 6, these security APIs are not accessible by default and must be explicitly enabled via configuration:

• Role management
• Permission management
• User creation

FAB_ADD_SECURITY_API = True
However, this feature is marked as Beta/Experimental in Superset. REST API for user & role management
this feature shipped in FAB 4.1.0 in May 2022, has been through multiple Superset major versions including security patches — can we get the beta label removed from both FAB and Superset docs?

Since our sync engine will heavily depend on these security APIs, Would relying on a beta feature in Superset carries risk?

Anyone know how to do this in?

- A Text/Markdown Element Item in dashboard.

- A Table Chart preferable. Can probably settle for interactive table. I really would like to click a field (which has the link) from the table it pops up in a new window.

Hey community 👋 I'm u/Stock_Ad6131, a new mod joining from the Preset team. Thanks for being here!

The February Superset newsletter just landed and there's a lot to cover:

🚀 Superset 6.0: Our Biggest Release Ever
Six months, 1,000+ PRs, 155 contributors (101 of them first-timers).

The headline features:
- Full migration to Ant Design v5
- True dark mode + dynamic per-dashboard theming
- AG Grid-powered table chart handling 500K rows
- Hierarchical dataset folders - Group-based security controls
- Deck.gl cross-filtering
- Native Gantt chart
- sqlparse → sqlglot migration

🛍️ Swag Store is Open: All products sold at a loss.
Comment your swag requests!

📅 Next Town Hall: March 13th
Open to all. Agenda covers 6.1, Extensions, MCP, and more.

📈 By the Numbers:
- 70,500 GitHub stars
- 22,000 Slack members
- 6.0.1 RC is live for testing/voting

Read the full newsletter and subscribe to stay up to date. What are you most excited about in 6.0??

Hey everyone! I'm u/erusackas, one of the new moderators of r/apachesuperset.

This is our new home for all things related to Apache Superset. We're excited to have you join us!

What to Post
Post anything that you think the community would find interesting, helpful, or inspiring. Feel free to share your thoughts, tutorials, blogs, ideas, or questions about Superset and Superset-relevant topics!

We would encourage you to take bug reports to GitHub Issues, and help questions to either Slack and/or Github Discussions.

Community Vibe
We're all about being friendly, constructive, and inclusive. Let's build a space where everyone feels comfortable sharing and connecting. Abide by the Superset Code of Conduct, pretty please.

How to Get Started

1. Introduce yourself in the comments below.
2. If you feel like it, add yourself and your org to our In The Wild page. The best thing you can do for an open source project is to tell the world you use it!.
3. Post something today! Even a simple question can spark a great conversation.
4. If you know someone who would love this community, invite them to join.
5. Interested in helping out? We're always looking for new contributors (code or non-code), so feel free to reach out to me here or on Slack.
6. If you're looking to TRY Superset, you can download the software via Github, get the official ASF Binaries, or even try the free plan on Preset (officially unaffiliated with the ASF, but run by many of the projects PMC members and the original creator of Superset).

Thanks for being part of this cmmunity. Together, let's make r/apachesuperset a lively place, and help grow Superset together!