Records rejected after changing in memory store retention period

I just found out this is the expected behaviour according to this documentation.
https://docs.aws.amazon.com/timestream/latest/developerguide/storage.html

So basically the table needs to have the in memory storage retention period configured at creation time, otherwise old data won't be accepted.

Me too. I met this problem 2 months ago, currently, the only thing I can do is to re-create my Timestream database if I configured improper retention(I mean actual value is larger than set). I think this is a bug, according to the dev. document, this shouldn't happen.

Hi,
As pointed by the documentation link, this is the expected behavior of the system. If you do update the retention window, its a retroactive change. Essentially its a sliding window of time where on retention increase the time (retTime) upto which data is accepted is frozen, and it will again start moving forward once the (current time - retTime) is as per your newly defined value.
Are you looking into ingesting data across any arbitrary time, or into your magnetic tier window? Please reach out via AWS support so that we can track the feature ask.

Thanks,
Kanishka

Edited by: Kanishka-AWS on Apr 20, 2021 3:18 PM