[
https://issues.apache.org/jira/browse/KAFKA-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740859#comment-16740859
]
ASF GitHub Bot commented on KAFKA-7808:
---------------------------------------
cmccabe commented on pull request #6124: KAFKA-7808: AdminClient#describeTopics
should not throw InvalidTopicException if topic name is not found
URL: https://github.com/apache/kafka/pull/6124
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> AdminClient#describeTopics should not throw InvalidTopicException if topic
> name is not found
> --------------------------------------------------------------------------------------------
>
> Key: KAFKA-7808
> URL: https://issues.apache.org/jira/browse/KAFKA-7808
> Project: Kafka
> Issue Type: Bug
> Components: admin, core
> Reporter: Guozhang Wang
> Assignee: Lee Dongjin
> Priority: Major
>
> In AdminClient#describeTopics, we have the following logic:
> {code:java}
> if (!cluster.topics().contains(topicName)) {
> future.completeExceptionally(new
> InvalidTopicException("Topic " + topicName + " not found."));
> continue;
> }
> {code}
> However, {{InvalidTopicException}} is a non-retriable exception and is used
> to indicate that topic contains invalid chars or topic name is too long etc,
> and hence not correct to use. We should, instead, throw the retriable
> {{UnknownTopicOrPartitionException}} instead.
> We should make sure any callers on this logic should be cleaned up when
> fixing it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
