mtovmassian commented on issue #20896:
URL: https://github.com/apache/superset/issues/20896#issuecomment-2009258149
I made the same observation with Superset v3.1.0. Whereas my cache
configuration is well set, when I inspect the key/value pairs stored in redis I
got only:
```shell
127.0.0.1:6379> keys *
1) "_kombu.binding.celery"
2) "_kombu.binding.celery.pidbox"
3) "_kombu.binding.celeryev"
```
Then I understand that there are actually two databases:
```shell
127.0.0.1:6379> info keyspace
# Keyspace
db0:keys=3,expires=0,avg_ttl=0
db1:keys=16,expires=16,avg_ttl=84395431
```
And If I select the second `db`, I find the expected Superset key/value
pairs:
```shell
127.0.0.1:6379> select 1
OK
127.0.0.1:6379[1]> keys *
1)
"superset_explore_cachesRY7u3miuZUUW-YxMgUfcyec8dVfMfp0lNmEfMc-j5hckiQkPUHHS-hzEEsfHqcj"
2)
"superset_filter_cache2;lwT4VFo4S-24ljI2ALt-jt3BYSxTFlP9Z67HaMnZ2KS9mSztblVoM3FFujHTXkBc"
3)
"superset_explore_cache432b454caa649faa0133735bd34cab457c4f5f528d4b50beead61d32000d75bcd0640386a780b2498ce757c29a5322589e5f7f511cc391ee9cc5781c55afed73;3;8;30;table"
...
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
