[
https://issues.apache.org/jira/browse/KAFKA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255709#comment-14255709
]
Andrii Biletskyi commented on KAFKA-1817:
-----------------------------------------
Can you please elaborate on the issue?
I checked this on 0.8.2 branch:
Called from code AdminUtils.createTopic(zkClient, "my_topic", 7, 1)
And I see
ls /brokers/topics/my_topic1752385998/partitions
[3, 2, 1, 0, 6, 5, 4]
Is perfectly created, same as when called from kafka-topics.sh...
What exactly is the problem, steps to reproduce?
> 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
> 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)
