Each user have each cache for chart?

[AnTapTanhCode]

I am testing warm_up cache, this is my config:

from flask_caching.backends.rediscache import RedisCache
# Superset specific config
ROW_LIMIT = 5000

# Flask App Builder configuration
# Your App secret key will be used for securely signing the session cookie
# and encrypting sensitive information on the database
# Make sure you are changing this key for your deployment with a strong key.
# Alternatively you can set it with `SUPERSET_SECRET_KEY` environment variable.
# You MUST set this for production environments or the server will refuse
# to start and you will see an error in the logs accordingly.
SECRET_KEY = 'oL58rZE2peSFU6j38N5a8ziyd8HTykQpfiyWaUPinsHIqFq7pdqGbiXu'

# The SQLAlchemy connection string to your database backend
# This connection defines the path to the database that stores your
# superset metadata (slices, connections, tables, dashboards, ...).
# Note that the connection information to connect to the datasources
# you want to explore are managed directly in the web UI
# The check_same_thread=false property ensures the sqlite client does not attempt
# to enforce single-threaded access, which may be problematic in some edge cases
#SQLALCHEMY_DATABASE_URI = 'postgresql+psycopg2://postgres:postgres@localhost/superset'
# Flask-WTF flag for CSRF
WTF_CSRF_ENABLED = True
# A CSRF token that expires in 1 year
WTF_CSRF_TIME_LIMIT = 60 * 60 * 24 * 365
WEBDRIVER_BASEURL = "http://localhost:8088/"
WEBDRIVER_BASEURL_USER_FRIENDLY = "http://localhost:8088"

CACHE_CONFIG = {
    "CACHE_TYPE": "RedisCache",
    "CACHE_DEFAULT_TIMEOUT": 86400,
    "CACHE_KEY_PREFIX": "superset_",
    'CACHE_REDIS_URL': 'redis://localhost:6379/1'
}

DATA_CACHE_CONFIG = {
    'CACHE_TYPE': 'RedisCache',
    'CACHE_DEFAULT_TIMEOUT': 60,  
    'CACHE_KEY_PREFIX': 'superset_chart_',
    'CACHE_REDIS_URL': 'redis://localhost:6379/2'
}

FILTER_STATE_CACHE_CONFIG = {
    'CACHE_TYPE': 'RedisCache',
    'CACHE_DEFAULT_TIMEOUT': 86400,
    'CACHE_KEY_PREFIX': 'superset_filter_',
    'CACHE_REDIS_URL': 'redis://localhost:6379/4'
}

EXPLORE_FORM_DATA_CACHE_CONFIG = {
    'CACHE_TYPE': 'RedisCache',
    'CACHE_DEFAULT_TIMEOUT': 120,
    'CACHE_KEY_PREFIX': 'superset_explore_',
    'CACHE_REDIS_URL': 'redis://localhost:6379/5'
}

RESULTS_BACKEND = {
		'CACHE_TYPE': 'RedisCache',
    'CACHE_DEFAULT_TIMEOUT': 120,
    'CACHE_KEY_PREFIX': 'superset_query_'
     'CACHE_REDIS_URL': 'redis://localhost:6379/3'
}
ALERT_REPORTS_NOTIFICATION_DRY_RUN = True

class CeleryConfig:
    broker_url = 'redis://localhost:6379/0'
    imports = (
        "superset.sql_lab",
        "superset.tasks.scheduler",
        "superset.tasks.thumbnails",
        "superset.tasks.cache",
    )
    result_backend = 'redis://localhost:6379/6'
    worker_prefetch_multiplier = 10
    task_acks_late = True
    task_annotations = {
        "sql_lab.get_sql_results": {
	            "rate_limit": "100/s",
        },
    }
    beat_schedule = {
        "cache-warmup-hourly": {
        "task": "cache-warmup",
        "schedule": crontab(minute='*', hour='*'),  
        "kwargs": {"strategy_name": "dummy"}, 
        },
    }
    

CELERY_CONFIG = CeleryConfig


# Set this API key to enable Mapbox visualizationsa
MAPBOX_API_KEY = ''

it working and created one key in redis for chart( id = 21). After i loggin by admin account and superset user cache. But when i use user alpha( have role Alpha) superset does not use an existing cache but create another cache.
Is it a bug or feature?

[dosubot[bot]]

Superset's behavior of creating separate cache entries for different users is not a bug; it's a feature. This is controlled by feature flags such as CACHE_QUERY_BY_USER and CACHE_IMPERSONATION. When these flags are enabled, Superset differentiates cache keys based on the user, meaning that different users will have separate cache entries even for the same query or chart.

1. CACHE_QUERY_BY_USER: When enabled, this feature flag ensures that cache keys are unique to each user. This means that if two users request the same chart, they will have different cache entries.

2. CACHE_IMPERSONATION: This flag, when enabled, also differentiates cache keys based on the user, but only if the database has impersonate_user set to True.

In your case, it seems that the cache is being differentiated by user, which is why a new cache entry is created when a different user accesses the chart. You can check if these feature flags are enabled in your Superset configuration to confirm this behavior ^[1].

To continue talking to Dosu, mention @dosu.