[
https://issues.apache.org/jira/browse/CASSGO-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066807#comment-18066807
]
João Reis edited comment on CASSGO-113 at 3/19/26 2:45 PM:
-----------------------------------------------------------
Hmm since the driver doesn't wrap errors then we have to assume that some users
might be directly type asserting so we can't change this in a minor release but
we should take a look at this when we start working on v3 (hopefully not
anytime soon).
For this particular patch, I think we should have distinct types for each error
code but I'm not against adding just these 2 on this patch and logging a ticket
to add the remaining ones later.
was (Author: JIRAUSER306784):
Hmm since the driver doesn't wrap errors then we have to assume that some users
might be directly type asserting so we can't change this in a minor release but
we should take a look at this when we start working on v3 (hopefully not
anytime soon).
I think we should have distinct types for each error code but I'm not against
adding just these 2 on this patch and logging a ticket to add the remaining
ones later.
> Add dedicated error types for Overloaded and Bootstrapping errors
> -----------------------------------------------------------------
>
> Key: CASSGO-113
> URL: https://issues.apache.org/jira/browse/CASSGO-113
> Project: Apache Cassandra Go driver
> Issue Type: Improvement
> Components: Core
> Reporter: Paolo Elefante
> Priority: Normal
>
> h2. Problem
> ErrCodeOverloaded (0x1001) and ErrCodeBootstrapping (0x1002) are currently
> parsed as generic errorFrame instances.
> This prevents applications from handling these error conditions in a
> type-safe way, forcing them to rely on error message inspection or
> error code matching.
> h2. Use Case
> Some applications and wrapper libraries need to distinguish these server
> error conditions in a type-safe way, for example to implement custom
> retry, backoff, observability, or request classification logic.
> At the moment, ErrCodeOverloaded and ErrCodeBootstrapping are exposed as
> generic errorFrame values, which makes them inconsistent with other
> server errors that already have dedicated request error types.
> h2. Proposal
> Introduce dedicated error types:
> - RequestErrOverloaded
> - RequestErrBootstrapping
> These should follow the same pattern as existing error types such as:
> - RequestErrUnavailable
> - RequestErrWriteTimeout
> - RequestErrReadTimeout
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
