[
https://issues.apache.org/jira/browse/KAFKA-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549500#comment-13549500
]
ben fleis commented on KAFKA-689:
---------------------------------
Although it's not precisely the same, perhaps thinking about topic|partition as
a remote file open is a useful metaphor. An open() call is where you would set
normal open params (flush interval, O_CREAT, etc.), and stat() is where you get
broker and other real time updates. Of course, if create is explicit, where
does delete come into play?
@Jun - I don't see where in server.properties anything about topic creation
exists? And further, does an extra RPC matter if it's only during
setup/periodic?
> 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
