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 ReturnValuesOnConditionCheckFailure is suppose in case of error to return the document present on dynamo. It's the case when we are using dynamo but not with this dax driver.
Here the difference when I use dynamo and dax in the output:
### DAX
➜ aws-dax-go git:(master) ✗ go run ./cmd/play
2024/10/11 15:00:50 item map[] <<<<<<<<<<<<<<<<< NOTHING HERE
2024/10/11 15:00:50 ConditionalCheckFailedException: The conditional request failed
{
RespMetadata: {
StatusCode: 400,
RequestID: "963TTCKR0P0SJ91BL1CO4SB3P7VV4KQNSO5AEMVJF66Q9ASUAAJG"
},
Message_: "The conditional request failed"
}
exit status 1
### DYNAMO
➜ aws-dax-go git:(master) ✗ go run ./cmd/play2
2024/10/11 15:00:57 item map[_id:{ <<<<<<<<<<<<<<<<<<<<< EXISTING DOCUMENT HERE
S: "test"
} test:{
S: "init"
} version:{
N: "0"
}]
2024/10/11 15:00:57 ConditionalCheckFailedException: The conditional request failed
{
RespMetadata: {
StatusCode: 400,
RequestID: "H7JR8TK2M7J3NQKI4363IJ3KCBVV4KQNSO5AEMVJF66Q9ASUAAJG"
},
Item: {
_id: {
S: "test"
},
version: {
N: "0"
},
test: {
S: "init"
}
},
Message_: "The conditional request failed"
}
exit status 1
The text was updated successfully, but these errors were encountered:
Hi,
This option is excellent and reduce cost on a highly concurrent update environment.
https://aws.amazon.com/blogs/database/handle-conditional-write-errors-in-high-concurrency-scenarios-with-amazon-dynamodb/
Here an short exemple:
The ReturnValuesOnConditionCheckFailure is suppose in case of error to return the document present on dynamo. It's the case when we are using dynamo but not with this dax driver.
Here the difference when I use dynamo and dax in the output:
The text was updated successfully, but these errors were encountered: