-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for TTL #35
Comments
@thomasd3 do you still have a need for it? Would you consider submitting a PR?
The creation lifecycle will receive some love in #43; Perhaps providing a At item level, I suspect that it can be specified by providing a field with the well-known name on your record without any code changes, but there may be some rough edges (again, if you or anyone has specific ideas or requirements, please feel free to jump in) |
@bartelink we've totally dropped the use of DynamoDB in our system, so I haven't touched that system in many months now. |
Thanks for the update - that's no problem With the way the Verify/Initialize/Provision APIs in #43 now expose an optional
Therefore I have updated that PR to close this one - let me know if you disagree @samritchie If anyone encounters any requirements not served, please feel free to discuss here and/or raise a new specific issue with more details on the exact needs. |
I'd expect TTL to be defined using an attribute on the appropriate record field, this is more consistent with the way we define GSIs etc. It’s going to involve some work at the pickle layer as it needs to be stored as epoch time rather than the string we convert |
I'll reopen this one pending a reasonable design. As I see it the options are:
|
Any plans to implement the TimeToLive feature of DynamoDB?
The text was updated successfully, but these errors were encountered: