-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DynamoDB: DuplicateKeyException after resuming CDC #301
Comments
a) We will look into the resume logic if we can spot any bugs. |
a) Relating to that comment, cratedb-toolkit/cratedb_toolkit/io/processor/kinesis_lambda.py Lines 106 to 110 in db67cd1
and how error handling is taking place, cratedb-toolkit/cratedb_toolkit/io/processor/kinesis_lambda.py Lines 142 to 154 in db67cd1
I guess the regular modus operandi for a Lambda that receives events from a Kinesis stream is that if the Lambda fails for whatever reason, recent events will be re-delivered. If it's multiple records, it is probably normal that some of them may be redundant, because they have been relayed to CrateDB successfully already. b) I guess using ON CONFLICT IGNORE/UPDATE instead will be the right choice. |
About
Problem
/cc @dfeokti
The text was updated successfully, but these errors were encountered: