From ee470de367e275a07bd4a41b12e25ce7645b709e Mon Sep 17 00:00:00 2001 From: Pierre-Yves Ritschard Date: Mon, 7 Nov 2011 10:07:08 +0100 Subject: [PATCH] Set a hard limit on topic width, this fixes KAFKA-196 --- core/src/main/scala/kafka/log/LogManager.scala | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/core/src/main/scala/kafka/log/LogManager.scala b/core/src/main/scala/kafka/log/LogManager.scala index 5bde936..80762b6 100644 --- a/core/src/main/scala/kafka/log/LogManager.scala +++ b/core/src/main/scala/kafka/log/LogManager.scala @@ -163,6 +163,8 @@ private[kafka] class LogManager(val config: KafkaConfig, awaitStartup if (topic.length <= 0) throw new InvalidTopicException("topic name can't be empty") + if (topic.length >= 200) + throw new InvalidTopicException("topic name too long") if (partition < 0 || partition >= topicPartitionsMap.getOrElse(topic, numPartitions)) { logger.warn("Wrong partition " + partition + " valid partitions (0," + (topicPartitionsMap.getOrElse(topic, numPartitions) - 1) + ")") -- 1.7.7.2