In previous superset versions, DATA_CACHE_CONFIG was deemed a security issue, because a user without read rights on the original data would we allowed to see the cached data.
Let's re-evaluate this to see whether this is still the case in Superset 3.0.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | brouberol | T353782 Decommission an-tool1010 | |||
| Resolved | brouberol | T347710 Migrate the Analytics Superset instances to our DSE Kubernetes cluster | |||
| Declined | brouberol | T358753 Re-evaluate data cache security issues, along with per user data caching |
Change 1007580 had a related patch set uploaded (by Brouberol; author: Brouberol):
[operations/deployment-charts@master] superset: allow usage of DATA_CACHE_STORAGE
Change 1007581 had a related patch set uploaded (by Brouberol; author: Brouberol):
[operations/deployment-charts@master] superset-next: enable data cache
Change 1007582 had a related patch set uploaded (by Brouberol; author: Brouberol):
[operations/deployment-charts@master] superset-next: enable per-user query cache
Change 1007580 merged by Brouberol:
[operations/deployment-charts@master] superset: allow usage of DATA_CACHE_CONFIG
Change 1007581 merged by Brouberol:
[operations/deployment-charts@master] superset-next: enable data cache
I think that this can be merged with (or into?) {T273850}
That was the original ticket where we attempted to enable caching, but then rolled back due to the security concerns.
Change 1007582 merged by Brouberol:
[operations/deployment-charts@master] superset-next: enable per-user query cache