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

Fix for expiration of records in DynamoDB #47

Closed
wants to merge 1 commit into from

Conversation

lefthand
Copy link

@lefthand lefthand commented Jun 5, 2020

Description of changes:

The timestamp provided was in milliseconds, so the expiration date was
set for sometime around the year 52000. I'm cutting off the last three digits to get it into a format that DynamoDB expects

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The timestamp provide was in milliseconds, so the expiration date was
set for sometime around the year 52000.

Also a couple updates to the README
@apianeta503
Copy link

Any updates on this pull request? Leaving millisecond epoch times in the table causes inconsistencies when DynamoDB runs the TTL delete item background operation. The DynamoDB scanner background process compares the epoch times in seconds.

@gsingh04
Copy link
Member

gsingh04 commented Oct 4, 2021

Thank you for reporting this issue.

We have added it to our backlog items. It will be addressed with the next release of the solution.

@abewub
Copy link
Member

abewub commented Jan 9, 2024

Included in #178.

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

Successfully merging this pull request may close these issues.

4 participants