Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
muralikrishnankh opened this issue Aug 29, 2022 · 6 comments
Labels
#bug Bug report

Comments

@muralikrishnankh
Copy link

muralikrishnankh commented Aug 29, 2022

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 muralikrishnankh added the #bug Bug report label Aug 29, 2022
@michalmalus
Copy link

Is there any update to this issue?

@Shazad-khan
Copy link

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

@billcrook
Copy link

billcrook commented Sep 29, 2023

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

@unnyns-307
Copy link

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

@rusackas
Copy link
Member

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.

@ka-weihe
Copy link
Contributor

ka-weihe commented Jun 18, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

7 participants