[
https://issues.apache.org/jira/browse/KAFKA-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463259#comment-13463259
]
Swapnil Ghike commented on KAFKA-495:
-------------------------------------
Reopening this issue because of additional constraints imposed due to jmx mbean
Object naming spec and our own highwatermark handling.
JMX Mbean naming spec is tedious to implement. The full rules are at
http://docs.oracle.com/javase/7/docs/api/javax/management/ObjectName.html. The
easy way to make sure that we don't break any rule is to ban the characters
colon (:), asterisk (*), question mark (?), comma (,), equals (=), quote ("),
backslash (\), newline ('\n'). There does not seem to be any restrictions on
single quote ('), period (.) and the rest.
For Highwatermark handling, we need to ban whitespaces [ \t\r\n\f].
> 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
>
>
> 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
