[
https://issues.apache.org/jira/browse/KAFKA-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-495:
--------------------------------
Attachment: kafka-495-v0.8-v2.patch
- After discussing with Jun, inserted topic validation in createTopic() instead
of LogManager in 0.8.
- Created a singleton Topic in Utils/Topic.scala, topicNameValidators in
KafkaConfig and CreateTopicCommand default to the maxNameLen in this singleton.
The value at both these locations can be overridden.
- The check in LogManager.createLog is not necessary anymore because the topic
would be validated by then, removed this check.
- Added a new unit test in test/utils for topic validation.
- Tested this change with bin/kafka-create-topic.sh for fun.
- Opened KAKFA-505 to deal with the TopicMetaDataResponse errorcode.
> 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-v1.patch, kafka-495-v2.patch, kafka-495-v3.patch, kafka-495-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
