[
https://issues.apache.org/jira/browse/KAFKA-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659017#comment-14659017
]
ASF GitHub Bot commented on KAFKA-2393:
---------------------------------------
GitHub user granthenke opened a pull request:
https://github.com/apache/kafka/pull/117
KAFKA-2393: Correctly Handle InvalidTopicException in KafkaApis.getTo…
…picMetadata()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/granthenke/kafka invalid-topic
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/117.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #117
----
commit 0abda5fffe7cb7cda585941e4909be304ad011f6
Author: Grant Henke <granthe...@gmail.com>
Date: 2015-08-05T21:45:25Z
KAFKA-2393: Correctly Handle InvalidTopicException in
KafkaApis.getTopicMetadata()
----
> 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)
