[ https://issues.apache.org/jira/browse/KAFKA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145583#comment-13145583 ]
Jun Rao commented on KAFKA-196: ------------------------------- Thanks for the patch. Where is the limit 200 coming from? Is that the file name limit in most file systems? > Topic creation fails on large values > ------------------------------------ > > Key: KAFKA-196 > URL: https://issues.apache.org/jira/browse/KAFKA-196 > Project: Kafka > Issue Type: Bug > Components: core > Reporter: Pierre-Yves Ritschard > Attachments: > 0001-Set-a-hard-limit-on-topic-width-this-fixes-KAFKA-196.patch > > > Since topic logs are stored in a directory holding the topic's name, creation > of the directory might fail for large strings. > This is not a problem per-se but the exception thrown is rather cryptic and > hard to figure out for operations. > I propose fixing this temporarily with a hard limit of 200 chars for topic > names, it would also be possible to hash the topic name. > Another concern is that the exception raised stops the broker, effectively > creating a simple DoS vector, I'm concerned about how tests or wrong client > library usage can take down the whole broker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira