You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add first class API support for Actor State TTL dapr/dapr#5899
A dedicated function to Actor State should be created. Psudo code: func (key string, value string, ttl duration). It should be made clear in the SDK documentation/comments that users should always use this function, unless they have specifically created some kind of Actor State clean up out of band of Dapr or don't have an issue with the Actor State store keep state and grow "forever".
Please see the go-sdk for implementation reference.
UPDATE: Due to the nature of the current implementation of write through caching of actor state and the unavailability of the real TTL expire time of state keys, SDKs will have an inconsistent view of the world when it has a cold cache and the state store has TTL keys. The TTL functionality has been put behind a feature gate in daprd. See dapr/dapr#6400 for more details. This feature is expected to be moved to GA in 1.12.
Activity
[-]Add Actor State TTL support[/-][+]FEATURE PREVIEW: Add Actor State TTL support[/+]JoshVanL commentedon May 25, 2023
UPDATE: Due to the nature of the current implementation of write through caching of actor state and the unavailability of the real TTL expire time of state keys, SDKs will have an inconsistent view of the world when it has a cold cache and the state store has TTL keys. The TTL functionality has been put behind a feature gate in daprd. See dapr/dapr#6400 for more details. This feature is expected to be moved to GA in 1.12.
cicoyle commentedon Jun 19, 2024
Inspiration can be derived from this PR adding ttl to actor reminder and timer that was not completed
12 remaining items
cicoyle commentedon Apr 1, 2025
Hey @WhitWaldo - the PR is not merged yet, its on my TODO for this upcoming release to fix it up. I think this issue should stay open.
WhitWaldo commentedon Apr 1, 2025
Hmm... Something must have bugged out somewhere as I don't recall intentionally closing this. Absolutely let's reopen it.