- 最新
- 投票最多
- 评论最多
Thank you for reaching out on re:Post.
Timestream update existing records in an idempotent manner as it would dedupe and accept the data, if sent with same value and version.
You can use the Version parameter in a WriteRecords[1] request to update data points. Timestream tracks a version number with each record. Version defaults to 1 when it's not specified for the record in the request. Timestream updates an existing record’s measure value along with its Version when it receives a write request with a higher Version number for that record. When it receives an update request where the measure value is the same as that of the existing record, Timestream still updates Version, if it is greater than the existing value of Version. You can update a data point as many times as desired, as long as the value of Version continuously increases.
[1] Refer more about upserts here : https://docs.aws.amazon.com/timestream/latest/developerguide/API_WriteRecords.html
Having said that, You can use this for Multi-measure records where there are multiple records with the same dimensions, timestamps, and measure names as long as the value of Version continuously increases.
Additionally, I would also like to mention that we already have a Feature Request in place for Timestream - SQL delete functionality. However, we currently do not have an ETA for the same. We appreciate the feedback and have already noted down your request for the same.
When you upset a multi-measure record do you have to write the entire measure over again, or can you upset just a single measurement within the multi-measure record and have it leave the rest ?