You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TimestampOffset per slice can probably be stored in the background, or at least not in each saveOffset. It can be flushed on flush on size/time. After a restart we will see duplicates, which is fine, if storeSequenceNumbers is successful and storeTimestampOffsets fails or is performed later.
Also, we must group the batches, also the storeSequenceNumbers, into chunks that fit the DynamoDB batch limit.
The text was updated successfully, but these errors were encountered:
The TimestampOffset per slice can probably be stored in the background, or at least not in each saveOffset. It can be flushed on flush on size/time. After a restart we will see duplicates, which is fine, if storeSequenceNumbers is successful and storeTimestampOffsets fails or is performed later.
Also, we must group the batches, also the storeSequenceNumbers, into chunks that fit the DynamoDB batch limit.
The text was updated successfully, but these errors were encountered: