[ 
https://issues.apache.org/jira/browse/KAFKA-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548746#comment-13548746
 ] 

Jay Kreps commented on KAFKA-689:
---------------------------------

Well I think there are actually two problems.

The first is that it is mixing concerns in kind of a messy way. In some sense 
it would be the "get metadata or maybe create a new topic" api. So I would 
rather not enshrine that in the public API. I think it is okay the kind of 
hacky way it is now, and in the future we can add an api.

The second problem is that we need to move the per-topic config into zookeeper 
so that you can dynamically add topics with their own settings (flush interval, 
retention period, # of partitions, etc...there are like ten of these settings). 
This is discussed in KAFKA-554. Currently these are in the broker config, but 
that means bouncing the broker all the time which is a hassle. So we will need 
to include these in the api that creates topics. That makes it messier still 
since we would have all these properties mixed into the get_metadata call.

I agree that right now it is a lot of overhead to add an api, but I think we 
could fix that directly by making it easier to add apis. KAFKA-643 had one 
proposal for htis.
Since you just went through that it would be good to get your feedback on that 
proposal.
                
> 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

Reply via email to