'what will happen when DynamoDB ttl is set as epoch timestamp in millisecond?

As per this documentation https://aws.amazon.com/premiumsupport/knowledge-center/ttl-dynamodb/ , the ttl must be set in seconds. but what will happen to the data if the ttl has been set incorrectly as ms while saving to dynamodb?

we have 5 months of data in dynamodb where ttl has been set incorrectly as 13 digit epoch timestamp(ms). Any inputs is much appreciated, Thanks in advance.



Solution 1:[1]

DynamoDB has no built-in support for mass updates.

If I were in this situation, I would have written a script that i ran locally that queries the entire table and updates the TTL attribute to its correct value.

If the dataset is too large for that, I'd do it using lambdas and a queue instead (i.e. post the query results and the LastEvaluatedKey to the queue and process that accordingly in a lambda).

Solution 2:[2]

You need to fill in the option for Select year. So either enter a placeholder (depending on your text field component) or add a menuitem like this: <MenuItem value={"Select year"}>{"Select year"}</MenuItem> To render the value for "Select year".

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 August Lilleaas
Solution 2 Domino987