Skip to content

FEATURE PREVIEW: Add Actor State TTL support #849

Open

Description

@JoshVanL

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.

Activity

  1. added this to the v1.10 milestone on May 15, 2023
  2. changed the title [-]Add Actor State TTL support[/-] [+]FEATURE PREVIEW: Add Actor State TTL support[/+] on May 25, 2023
  3. JoshVanL commented on May 25, 2023

    @JoshVanL
    MemberAuthor

    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.

  4. modified the milestones: v1.10, v1.11 on Oct 3, 2023
  5. modified the milestones: v1.11, v1.12 on Feb 8, 2024
  6. modified the milestones: v1.12, v1.13 on Jul 23, 2024
  7. 12 remaining items

  8. moved this from In review to Done in v1.16 Release Tracking Boardon Apr 1, 2025
  9. reopened this on Apr 1, 2025
  10. cicoyle commented on Apr 1, 2025

    @cicoyle
    Contributor

    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.

  11. WhitWaldo commented on Apr 1, 2025

    @WhitWaldo

    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.

    Hmm... Something must have bugged out somewhere as I don't recall intentionally closing this. Absolutely let's reopen it.

  12. moved this from Backlog to In progress in v1.16 Release Tracking Boardon Apr 2, 2025
  13. modified the milestones: v1.15, v1.16 on Aug 20, 2025
  14. modified the milestones: v1.17, v1.20 on Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions