superset
superset copied to clipboard
Native filters doesn't update their cached values after Refresh Dashboard
The Native filters doesn't update their cached values after Refresh Dashboard even though the data is updated in the Database. The Native filters seems to be getting refreshed but the data doesn't get updated.
How to reproduce the bug
- Install any version of Superset
- Add some data to the connected Database. I have connected to Clickhouse DB.
- Open Superset.
- The Native filters will have the added values
- Add some more data to the DB
- Click Refresh Dashboard on the Dashboard
Expected results
The Native Filters data should get updated as per latest data.
Actual results
The Native filter data doesn't get refreshed
Screenshots
Clicking the Refresh Dashboard:

GIF indicating the Native filters getting refreshed after clicking Refresh Dashboard

Environment
(please complete the following information):
-
browser type and version: Microsoft Edge Version 104.0.1293.63 (Official build) (64-bit)
-
superset version: Tried in both 1.4.0 and 2.0.0
-
any feature flags active:
FEATURE_FLAGS = { "ENABLE_TEMPLATE_PROCESSING": True, "ALERT_REPORTS": True }
-
Cache setting:
Tried with default cache setting and redis cache. For redis, the following settings were used: CACHE_CONFIG = { 'CACHE_TYPE': 'RedisCache', 'CACHE_REDIS_URL': f"redis://{env('REDIS_HOST')}:{env('REDIS_PORT')}/0", 'CACHE_DEFAULT_TIMEOUT': 10,
'CACHE_KEY_PREFIX': 'superset_filter_'} FILTER_STATE_CACHE_CONFIG = CACHE_CONFIG
Is there any update to this issue?
This issue has been fixed already please check this issue and close.
@Shazad-khan in which version is this fixed? I am experiencing the issue on 2.1.1.
Hi, I'm experiencing this issue in 2.1.1 too. @Shazad-khan is this fixed in V.3.0.0?
I'm not sure if this is still an issue in current versions of Superset (3.x). If it is, we can re-open this, or feel free to open a new issue with updated context and a reproducible case using example data. We're no longer supporting Superset 2.x or prior, and it's been a while since this thread saw any activity, so I'm closing this as stale.
@rusackas This is still an issue in Superset 4.0.1. Can you open the issue again?
Looks like this should have been closed when https://github.com/apache/superset/pull/29291 was merged. Holler if I'm mistaken and we can reopen it (again) :)