[
https://issues.apache.org/jira/browse/KAFKA-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548748#comment-13548748
]
Jun Rao commented on KAFKA-689:
-------------------------------
Currently, auto-creation is a broker-side flag. Basically, the broker controls
whether a topic can be created automatically or not. This is likely useful for
admin. The getMetadata API implicitly implies auto-creation, subject to the
server side config. This is probably a bit hacky. It does save one extra RPC.
We can think a bit more if adding a separate create topic API is a better
strategy.
> Can't append to a topic/partition that does not already exist
> -------------------------------------------------------------
>
> Key: KAFKA-689
> URL: https://issues.apache.org/jira/browse/KAFKA-689
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 0.8
> Reporter: David Arthur
> Attachments: kafka.log, produce-payload.bin
>
>
> With a totally fresh Kafka (empty logs dir and empty ZK), if I send a
> ProduceRequest for a new topic, Kafka responds with
> "kafka.common.UnknownTopicOrPartitionException: Topic test partition 0
> doesn't exist on 0". This is when sending a ProduceRequest over the network
> (from Python, in this case).
> If I use the console producer it works fine (topic and partition get
> created). If I then send the same payload from before over the network, it
> works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
