[
https://issues.apache.org/jira/browse/KAFKA-15866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans resolved KAFKA-15866.
------------------------------------
Fix Version/s: 3.7.0
(was: 3.8.0)
Assignee: (was: Lan Ding)
Resolution: Fixed
> Refactor OffsetFetchRequestState Error handling to be more consistent with
> OffsetCommitRequestState
> ---------------------------------------------------------------------------------------------------
>
> Key: KAFKA-15866
> URL: https://issues.apache.org/jira/browse/KAFKA-15866
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer
> Reporter: Philip Nee
> Priority: Minor
> Labels: consumer-threading-refactor
> Fix For: 3.7.0
>
>
> The current OffsetFetchRequestState error handling uses nested if-else, which
> is quite different, stylistically, to the OffsetCommitRequestState using a
> switch statment. The latter is a bit more readable so we should refactor the
> error handling using the same style to improve readability.
>
> A minor point: Some of the error handling seems inconsistent with the commit.
> The logic was from the current implementation, so we should also review all
> the error handling. For example: somehow the current logic doesn't mark the
> coordinator unavailable when receiving COORDINATOR_NOT_AVAILABLE
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
