mdenison opened a new issue, #38605:
URL: https://github.com/apache/superset/issues/38605
### Bug description
When using S3Cache as the Cache Backend for `DATA_CACHE_CONFIG` the Cache
Timeout is not respected when charts are fetched. Neither the
`CACHE_DEFAULT_TIMEOUT` of 86400 is used nor if I configure a Cache Timeout on
Dataset level.
Below is the response when I set the Cache Timeout to 10 seconds.
```{
"result": [
{
"cache_key": "0ccc532b072680aeb65955c39ca75392",
"cached_dttm": "2026-03-12T14:55:45",
"cache_timeout": 10,
"applied_template_filters": [],
"annotation_data": {},
"error": null,
"is_cached": true,
......
```
### Screenshots/recordings
Users sees that the Data was cached a longer time then what the Cache
Timeout is:
<img width="670" height="120" alt="Image"
src="https://github.com/user-attachments/assets/6dccddc3-2e22-4d1c-8059-2e5b839d9169";
/>
Also the Cached Data still resides on S3:
<img width="884" height="57" alt="Image"
src="https://github.com/user-attachments/assets/d790def2-1214-494c-8c86-6c7bc380497d";
/>
### Superset version
6.0.0
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
Users started reporting this once we migrated from 5.0.0 to 6.0.0. Also
still an issue with 6.0.1rc1.
If anyone maybe knows why this is happening, I would be happy to know.
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [x] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
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]
