superset icon indicating copy to clipboard operation
superset copied to clipboard

Native filters doesn't update their cached values after Refresh Dashboard

Open muralikrishnankh opened this issue 3 years ago • 6 comments

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

  1. Install any version of Superset
  2. Add some data to the connected Database. I have connected to Clickhouse DB.
  3. Open Superset.
  4. The Native filters will have the added values
  5. Add some more data to the DB
  6. 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: image

GIF indicating the Native filters getting refreshed after clicking Refresh Dashboard image

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

muralikrishnankh avatar Aug 29 '22 10:08 muralikrishnankh

Is there any update to this issue?

michalmalus avatar Mar 07 '23 14:03 michalmalus

This issue has been fixed already please check this issue and close.

Shazad-khan avatar Mar 16 '23 14:03 Shazad-khan

@Shazad-khan in which version is this fixed? I am experiencing the issue on 2.1.1.

billcrook avatar Sep 29 '23 20:09 billcrook

Hi, I'm experiencing this issue in 2.1.1 too. @Shazad-khan is this fixed in V.3.0.0?

unnyns-307 avatar Oct 04 '23 04:10 unnyns-307

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 avatar Mar 19 '24 22:03 rusackas

@rusackas This is still an issue in Superset 4.0.1. Can you open the issue again?

ka-weihe avatar Jun 18 '24 07:06 ka-weihe

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) :)

rusackas avatar Mar 19 '25 21:03 rusackas