AWS - DynamoDB
A developer set TTL attribute with timestamps in milliseconds instead of seconds. What issue will this cause?
A developer set TTL attribute with timestamps in milliseconds instead of seconds. What issue will this cause?
medium📝 Debug Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Understand TTL timestamp format
TTL expects epoch time in seconds, not milliseconds.Step 2: Effect of using milliseconds
Milliseconds timestamps are much larger, so DynamoDB sees them as far future dates, preventing expiry.Final Answer:
Items will not expire because timestamps are too large -> Option DQuick Check:
TTL timestamps must be in seconds [OK]
Quick Trick: TTL timestamps must be in seconds, not milliseconds [OK]
Common Mistakes:
MISTAKES- Using milliseconds instead of seconds
- Expecting immediate expiry with wrong units
- Assuming DynamoDB throws errors for wrong timestamp
Master "DynamoDB" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes