You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Grant Henke (JIRA)" <ji...@apache.org> on 2015/07/31 18:31:04 UTC

[jira] [Commented] (KAFKA-2393) Correctly Handle InvalidTopicException in KafkaApis.getTopicMetadata()

    [ https://issues.apache.org/jira/browse/KAFKA-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649438#comment-14649438 ] 

Grant Henke commented on KAFKA-2393:
------------------------------------

Makes this scenario more likely to occur.

> Correctly Handle InvalidTopicException in KafkaApis.getTopicMetadata()
> ----------------------------------------------------------------------
>
>                 Key: KAFKA-2393
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2393
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.2.1
>            Reporter: Grant Henke
>            Assignee: Grant Henke
>
> It seems that in KafkaApis.getTopicMetadata(), we need to handle InvalidTopicException explicitly when calling AdminUtils.createTopic (by returning the corresponding error code for that topic). Otherwise, we may not be able to get the metadata for other valid topics. This seems to be an existing problem, but KAFKA-2337 makes InvalidTopicException more likely to happen. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)