[
https://issues.apache.org/jira/browse/KAFKA-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5992.
--------------------------------
Resolution: Duplicate
Duplicate of KAFKA-5445.
> Better Java Documentation for AdminClient Exceptions
> ----------------------------------------------------
>
> Key: KAFKA-5992
> URL: https://issues.apache.org/jira/browse/KAFKA-5992
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.11.0.1
> Reporter: Stephane Maarek
>
> When invoking a describeTopics operation on a topic that does not exist, we
> get an InvalidTopicException as a RuntimeException.
> I believe this should be documented, and the API maybe changed:
> For example changing:
> {code:java}
> public DescribeTopicsResult describeTopics(Collection<String> topicNames)
> {
> {code}
> To:
> {code:java}
> public DescribeTopicsResult describeTopics(Collection<String> topicNames)
> throws InvalidTopicException
> {code}
> Additionally, in case multiple topics don't exist, only the first one will
> throw an error. This is really not scalable.
> Maybe the DescribeTopicsResult could have a Boolean "topicExists" ?
> Up for discussion
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
