[
https://issues.apache.org/jira/browse/KAFKA-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027357#comment-15027357
]
Andrew Winterman commented on KAFKA-2887:
-----------------------------------------
my only complaint with this approach is that it leaves people on 0.8 in a
lurch. If we make the configuration values for the broker more fine grained,
meaning have one configuration value for "creates topics on produce request"
and one for "creates topics on consume/metadata request" then that both
preserves api continuity (or are configuration values a part of the API?) and
solves the problem we're facing.
> 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)
