coreyoconnor on v1.3.0
coreyoconnor on master
Prep 1.3.0 (#115) * prep for 1… (compare)
persistAll
method is supposed to be atomic for the whole batch. Currently, the journal implementation works around the fact that a batch write is not atomic in DynamoDB with the idx
and cnt
attributes. Has anyone looked into using TransactWriteItems
to guarantee this atomicity?
Hi folks,
I have been exploring a solution to have dynamo items TTL configured at the table level (journal and snapshot). #99
I read the contributing guide afterwards and realised that a discussing is advised before pull request. :grimacing:
In a nutshell, we would have some optional configuration for journal and snapshot tables to specify the TTL:
my-dynamodb-journal { // also available for snapshots tables
dynamodb-item-ttl-config {
field-name = "expiresAt" // in the AWS UI, we need to set the field name https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/time-to-live-ttl-how-to.html
ttl = 30d
}
}
With this configuration, it would add a field "expiresAt" for each journal item inserted with value now + 30d
.
What do you think about this approach?
rO0ABXNyAD9jb20uY2Fwb25lLmJhbmsuYWN0b3JzLlBlcnNpc3RlbnRCYW5rQWNjb3VudCRCYW5rQWNjb3VudENyZWF0ZWQrGoMniq0AywIAAUwAC2JhbmtBY2NvdW50dAA6TGNvbS9jYXBvbmUvYmFuay9hY3RvcnMvUGVyc2lzdGVudEJhbmtBY2NvdW50JEJhbmtBY2NvdW50O3hwc3IAOGNvbS5jYXBvbmUuYmFuay5hY3RvcnMuUGVyc2lzdGVudEJhbmtBY2NvdW50JEJhbmtBY2NvdW5011CikshX3ysCAAREAAdiYWxhbmNlTAAIY3VycmVuY3l0ABJMamF2YS9sYW5nL1N0cmluZztMAAJpZHEAfgAETAAEdXNlcnEAfgAEeHBAj0AAAAAAAHQAA0VVUnQAJDM5M2M2NmRiLTJhYmItNDEwNS04NWUyLWMwZjc3MzExMDNlM3QAB3JjYXJkaW4=
\