[
https://issues.apache.org/jira/browse/KAFKA-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15025546#comment-15025546
]
Andrew Winterman edited comment on KAFKA-2887 at 11/24/15 10:14 PM:
--------------------------------------------------------------------
Reopening because the auto.create.topics.enable configuration parameter also
controls whether or not a topic is created by attempts to produce to it. It
seems like producing is a write operation, while consuming or asking for
metadata is a read. I maintain that creating topics in response to read
operations is surprising.
was (Author: awinterman):
Reopening because the auto.create.topics.enable also controls whether or not a
topic is created by attempts to produce to it. It seems like producing is a
write operation, while consuming or asking for metadata is a read. I maintain
that creating topics in response to read operations is surprising.
> 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)
