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
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: