kv,sql: replica command errors bubble up as-is to SQL clients #49868
Labels
A-error-handling
Error messages, error propagations/annotations
A-kv-client
Relating to the KV client and the KV interface.
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
S-3-ux-surprise
Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
T-kv
KV Team
T-sql-queries
SQL Queries Team
Projects
Found in #49513, a KV error went through all the layers and popped up in the client unadulterated:
The present issue is not about investigating the cause of the error and instead focuses on the communication of this error throughout CockroachDB.
There are a couple of problems with this situation:
The way forward would be to address this in SQL by:
%+v
in the log fileerrors.Handled()
)cc @andreimatei if you have suggestions as to how/where to do this? Perhaps the error could be summarized by txncoordsender before it comes into SQL?
cc @asubiotto @jordanlewis for triage.
Jira issue: CRDB-4177
The text was updated successfully, but these errors were encountered: