dosubot[bot] commented on issue #38605:
URL: https://github.com/apache/superset/issues/38605#issuecomment-4047909478

   <!-- Answer -->
   This appears to be a **known regression in Superset 6.0.0**. Another user 
reported the [same behavior in a recent 
discussion](https://github.com/apache/superset/discussions/38355) — cache 
timeout is being returned correctly in API responses but not actually enforced, 
causing stale data to persist.
   
   **Likely cause**: Between 5.0.0 and 6.0.0, cache handling was refactored in 
[PR #34654](https://github.com/apache/superset/pull/34654) to centralize the 
`-1` timeout logic (cache bypass). This may have inadvertently affected how 
positive timeout values are validated against `cached_dttm`.
   
   **Workarounds until a fix is available**:
   
   1. **Force refresh** via the UI context menu when needed
   2. **Enable cache key tracking** for programmatic invalidation:
      ```python
      STORE_CACHE_KEYS_IN_METADATA_DB = True
      ```
      Then use the `/api/v1/cachekey/invalidate` endpoint to clear stale 
entries.
   3. **Set S3 lifecycle policies** as a backup mechanism to delete objects 
after your intended TTL
   4. **Test with a different cache backend** (Redis/SimpleCache) to confirm 
whether this is S3-specific or affects all backends
   
   I'd recommend adding your configuration details to the [existing 
discussion](https://github.com/apache/superset/discussions/38355) to help 
maintainers reproduce and fix this.
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention 
[@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=brand-link).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/ffa044a8-351d-4c1c-a0b5-e719f622a018?feedback_type=great_response&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/ffa044a8-351d-4c1c-a0b5-e719f622a018?feedback_type=irrelevant_answer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/ffa044a8-351d-4c1c-a0b5-e719f622a018?feedback_type=incorrect_sources&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/ffa044a8-351d-4c1c-a0b5-e719f622a018?feedback_type=too_verbose&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-too_verbose)
 | [Hallucination](https://app.dosu.dev/response-feedback/ffa044a8-351d
 
-4c1c-a0b5-e719f622a018?feedback_type=hallucination&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/ffa044a8-351d-4c1c-a0b5-e719f622a018?feedback_type=bug_report&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/ffa044a8-351d-4c1c-a0b5-e719f622a018?feedback_type=other&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-other)</sup>
   
   [![Chat with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=chat-badge)&nbsp;[![Open
 in 
Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20appears%20to%20be%20a%20%2A%2Aknown%20regression%20in%20Superset%206.0.0%2A%2A.%20Another%20user%20reported%20the%20%5Bsame%20behavior%20in%20a%20recent%20discussion%5D%28https%3A//github.com/apache/superset/discussions/38355%29%20%E2%80%94%20cache%20timeout%20is%20being%20returned%20correctly%20in%20API%20responses%20but%20not%20actually%20enforced%2C%20causing%20stale%20data%20to%20persist.%0A%0A%2A%2ALikely%20cause%2A%2A%3A%20Between%205.0.0%20and%206.0.0%2C%20cache%20handling%20was%20refactored%20in%20%5BPR%20%2334654%5D%28https%3A//github.com/apache/superset/pull/34654%29%20to%20centralize%20the%20%60-1%60%20timeout%20logic%20%28cache%20bypass%29.%20This%20may%2
 
0have%20inadvertently%20affected%20how%20positive%20timeout%20values%20are%20validated%20against%20%60cached_dttm%60.%0A%0A%2A%2AWorkarounds%20until%20a%20fix%20is%20available%2A%2A%3A%0A%0A1.%20%2A%2AForce%20refresh%2A%2A%20via%20the%20UI%20context%20menu%20when%20needed%0A2.%20%2A%2AEnable%20cache%20key%20tracking%2A%2A%20for%20programmatic%20invalidation%3A%0A%20%20%20%60%60%60python%0A%20%20%20STORE_CACHE_KEYS_IN_METADATA_DB%20%3D%20True%0A%20%20%20%60%60%60%0A%20%20%20Then%20use%20the%20%60/api/v1/cachekey/invalidate%60%20endpoint%20to%20clear%20stale%20entries.%0A3.%20%2A%2ASet%20S3%20lifecycle%20policies%2A%2A%20as%20a%20backup%20mechanism%20to%20delete%20objects%20after%20your%20intended%20TTL%0A4.%20%2A%2ATest%20with%20a%20different%20cache%20backend%2A%2A%20%28Redis/SimpleCache%29%20to%20confirm%20whether%20this%20is%20S3-specific%20or%20affects%20all%20backends%0A%0AI%27d%20recommend%20adding%20your%20configuration%20details%20to%20the%20%5Bexisting%20discussion%5D%28http
 
s%3A//github.com/apache/superset/discussions/38355%29%20to%20help%20maintainers%20reproduce%20and%20fix%20this.)&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=join-discord)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/38605)


-- 
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]

Reply via email to