Closed oliverjanik closed 4 years ago
Exceptions like ReqlOpFailedError
are built into the protocol. If the protocol doesn't provide an error code, the driver can't provide one either.
Try turning on protocol debugging, trace both exceptions over the wire, and see if you can detect anything different besides the error msg
string in both JSON responses.
If you can detect some other discriminator value (like an error code), re-open the issue and let me know and I'll take a look at adding it. IIRC, it is not possible with the current server protocol implementation.
Hope that helps, Brian
Too bad, I thought that might be the case. Thanks for detailed response.
If I'm not mistaken I can't tell the difference between
and
correct?
I'm looking into availability and it's worth retrying on the first error but not on the second one.
If exceptions had error codes or some other way of telling them apart (message text notwithstanding) that would enable me to write more granular retry policies.