Proper catching of errors like "readTs: 60534 less than minTs: 60535 for key"

[mehdiym]

What you wanted to do

I needed to catch those occasional and unpredictable errors and retry if they happen.

What you actually did

I parsed the error message and if it matched the error string, modulo the numbers, I ran the query again.

Why that wasn't great, with examples

Parsing an error string is :

• not efficient: It takes time to parse a string with a regexp matching
• not durable: The string message may change in the future

Any external references to support your case

This request has been discussed in that thread.

[manishrjain]

Following up on discussions with @srfrog in this direction, we could generate a unique string based code to reflect error; so it can be searched for by the user at their end, without us having to modify all our client libraries.

[mehdiym]

Thx for your answer.
It would indeed be better, more durable.
Do you mean an error message prefix?

[mehdiym]

Thx for your answer.
It would indeed be better, more durable.
Do you mean an error message prefix?

[manishrjain]

Closing this issue as a duplicate of #2646 .