[
https://issues.apache.org/jira/browse/KAFKA-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026076#comment-15026076
]
Jason Gustafson commented on KAFKA-2887:
----------------------------------------
There is probably wide agreement that auto-creation of topics on metadata
requests is not a good idea. However, the problem with adding a flag to the
topic metadata request is that future versions would have to continue to
support it. Seems that leaves unneeded baggage in the request API, especially
if the plan is ultimately to deprecate this feature. Since 0.9 has already been
cut, my own preference for the next release would be to finish the CreateTopic
request in KIP-4, disable auto-creation by default, and leave the metadata
request unchanged. Then hopefully in a future release, we could remove
auto-creation entirely.
> 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)
