[
https://issues.apache.org/jira/browse/KAFKA-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson updated KAFKA-8453:
-----------------------------------
Description: The Metadata response may contain the following
partition-level error codes: LEADER_NOT_AVAILABLE, REPLICA_NOT_AVAILABLE, and
LISTENER_NOT_FOUND. The AdminClient at the moment does not appear to be
checking these error codes. This seems mostly harmless in the case of
LEADER_NOT_AVAILABLE and REPLICA_NOT_AVAILABLE, but potentially we should raise
an error in the case of LISTENER_NOT_FOUND since the result would otherwise be
misleading. (was: The Metadata response may contain the following error codes:
LEADER_NOT_AVAILABLE, REPLICA_NOT_AVAILABLE, and LISTENER_NOT_FOUND. The
AdminClient at the moment does not appear to be checking these error codes.
This seems mostly harmless in the case of LEADER_NOT_AVAILABLE and
REPLICA_NOT_AVAILABLE, but potentially we should raise an error in the case of
LISTENER_NOT_FOUND since the result would otherwise be misleading.)
> AdminClient describeTopic should handle partition level errors
> --------------------------------------------------------------
>
> Key: KAFKA-8453
> URL: https://issues.apache.org/jira/browse/KAFKA-8453
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Priority: Major
>
> The Metadata response may contain the following partition-level error codes:
> LEADER_NOT_AVAILABLE, REPLICA_NOT_AVAILABLE, and LISTENER_NOT_FOUND. The
> AdminClient at the moment does not appear to be checking these error codes.
> This seems mostly harmless in the case of LEADER_NOT_AVAILABLE and
> REPLICA_NOT_AVAILABLE, but potentially we should raise an error in the case
> of LISTENER_NOT_FOUND since the result would otherwise be misleading.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
