You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Stephane Maarek (JIRA)" <ji...@apache.org> on 2017/09/29 04:25:00 UTC

[jira] [Created] (KAFKA-5992) Better Java Documentation for AdminClient Exceptions

Stephane Maarek created KAFKA-5992:
--------------------------------------

             Summary: 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)