Database Reference
In-Depth Information
Error handling
As discussed in the previous section, DynamoDB responds with three kinds of status codes.
Response 200 means success; responses starting with 4 (400, 413, and so on) are client-side
errors caused by syntax error, and responses starting with 5 (500) are server-side errors,
caused because the provisioned throughput has been exceeded, the service is down, and so
on.
Along with this status code, every error has an error message too. For example, a request
with an invalid signature will result in a 400 error code, with the
com.amazon.coral.service#InvalidSignatureException
exception with
the error message
"The request signature we calculated does not match the signature
you provided. Check your AWS Secret Access Key and signing method. Consult the
service documentation for details."
.
Let's see what all the possible client-side errors are. There are only two client-side status er-
ror codes. These are 400 and 413. Out of these client-side errors, a few are timing errors
only. If we retry it, then it might work fine (without changing the parameters). Other errors
will always fail because of a syntax error, irrespective of how many times we retry.
