[
https://issues.apache.org/jira/browse/KAFKA-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-495:
--------------------------------
Attachment: kafka-v0.8-v4.patch
Uploading kafka-v0.8-v4.patch.
This patch allows only ASCII alphanumeric chars, underscore and dash in the
topic names. Also since we are arguing that the hard constraints set by us are
not going to be challenged in likely usages, I have also hardcoded topic name
length to have a max value of 255 since it's very difficult to exceed this
length as well.
> Handle topic names with "/" on Kafka server
> -------------------------------------------
>
> Key: KAFKA-495
> URL: https://issues.apache.org/jira/browse/KAFKA-495
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.7, 0.8
> Reporter: Neha Narkhede
> Assignee: Swapnil Ghike
> Labels: bugs
> Fix For: 0.8, 0.7.1
>
> Attachments: kafka-495-v0.8.patch, kafka-495-v0.8-v2.patch,
> kafka-495-v0.8-v3.patch, kafka-495-v1.patch, kafka-495-v2.patch,
> kafka-495-v3.patch, kafka-495-v4.patch, kafka-v0.8-v4.patch
>
>
> If a producer publishes data to topic "foo/foo", the Kafka server ends up
> creating an invalid directory structure on the server. This corrupts the
> zookeeper data structure for the topic - /brokers/topics/foo/foo. This leads
> to rebalancing failures on the consumer as well as errors on the zookeeper
> based producer.
> We need to harden the invalid topic handling on the Kafka server side to
> avoid this.
--
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
