Skip to content
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

Dynamodb TTL and expiration of old events #43

Open
noah-goodrich opened this issue Jul 11, 2018 · 1 comment
Open

Dynamodb TTL and expiration of old events #43

noah-goodrich opened this issue Jul 11, 2018 · 1 comment

Comments

@noah-goodrich
Copy link

In researching solutions for clearing old data out of the LeoEvent and LeoStream dynamodb tables, I came across the TTL feature. According to the AWS DynamoDB docs I've read, the TTL feature expects the timestamp to represent the number of seconds from the Unix epoch.

However, looking at the ttl and timestamp columns on the LeoEvent and LeoStream tables, it appears that the values are being stored in milliseconds instead.

I am looking for solutions to expire out old test data from dynamodb and this seems like the best bet. What is needed to fix both the LeoEvent and LeoStream tables so we could reliably use this feature?

@roaringdev
Copy link
Contributor

This is indeed a bug, we will get that fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants