Return-Path: X-Original-To: apmail-incubator-kafka-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-kafka-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5A091DA88 for ; Tue, 4 Sep 2012 22:53:08 +0000 (UTC) Received: (qmail 67725 invoked by uid 500); 4 Sep 2012 22:53:08 -0000 Delivered-To: apmail-incubator-kafka-dev-archive@incubator.apache.org Received: (qmail 67690 invoked by uid 500); 4 Sep 2012 22:53:08 -0000 Mailing-List: contact kafka-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: kafka-dev@incubator.apache.org Delivered-To: mailing list kafka-dev@incubator.apache.org Received: (qmail 67681 invoked by uid 99); 4 Sep 2012 22:53:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2012 22:53:08 +0000 Date: Wed, 5 Sep 2012 09:53:07 +1100 (NCT) From: "Swapnil Ghike (JIRA)" To: kafka-dev@incubator.apache.org Message-ID: <285315660.35414.1346799188001.JavaMail.jiratomcat@arcas> In-Reply-To: <1999046075.26131.1346462827717.JavaMail.jiratomcat@arcas> Subject: [jira] [Assigned] (KAFKA-495) Handle topic names with "/" on Kafka server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Ghike reassigned KAFKA-495: ----------------------------------- Assignee: Swapnil Ghike > 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 > > 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