[
https://issues.apache.org/jira/browse/KAFKA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537108#comment-14537108
]
Andrey A commented on KAFKA-1817:
---------------------------------
Faced the same issue ({{org.apache.kafka:kafka_2.10:0.8.2.1}}). The workaround
is:
{code}
ZkClient zkClient = new ZkClient("localhost:2181", 10000, 10000,
ZKStringSerializer$.MODULE$);
{code}
(http://stackoverflow.com/questions/27036923/how-to-create-a-topic-in-kafka-through-java)
> AdminUtils.createTopic vs kafka-topics.sh --create with partitions
> ------------------------------------------------------------------
>
> Key: KAFKA-1817
> URL: https://issues.apache.org/jira/browse/KAFKA-1817
> Project: Kafka
> Issue Type: Sub-task
> Affects Versions: 0.8.2.0
> Environment: debian linux current version up to date
> Reporter: Jason Kania
> Fix For: 0.8.3
>
>
> When topics are created using AdminUtils.createTopic in code, no partitions
> folder is created The zookeeper shell shows this.
> ls /brokers/topics/foshizzle
> []
> However, when kafka-topics.sh --create is run, the partitions folder is
> created:
> ls /brokers/topics/foshizzle
> [partitions]
> The unfortunately useless error message "KeeperErrorCode = NoNode for
> /brokers/topics/periodicReading/partitions" makes it unclear what to do. When
> the topics are listed via kafka-topics.sh, they appear to have been created
> fine. It would be good if the exception was wrapped by Kafka to suggested
> looking in the zookeeper shell so a person didn't have to dig around to
> understand what the meaning of this path is...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
