[
https://issues.apache.org/jira/browse/KAFKA-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063131#comment-15063131
]
Mayuresh Gharat commented on KAFKA-2887:
----------------------------------------
[~hachikuji] just wanted to be sure what you meant by leaving the current
TopicMetadataRequest unchanged, is that it will not be creating the topic in
future. Am I right?
This is very important when we are dealing with deleting topics in a pipeline.
> TopicMetadataRequest creates topic if it does not exist
> -------------------------------------------------------
>
> Key: KAFKA-2887
> URL: https://issues.apache.org/jira/browse/KAFKA-2887
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 0.8.2.0
> Environment: Centos6, Java 1.7.0_75
> Reporter: Andrew Winterman
> Priority: Minor
>
> We wired up a probe http endpoint to make TopicMetadataRequests with a
> possible topic name. If no topic was found, we expected an empty response.
> However if we asked for the same topic twice, it would exist the second time!
> I think this is a bug because the purpose of the TopicMetadaRequest is to
> provide information about the cluster, not mutate it. I can provide example
> code if needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
