You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Manikumar (JIRA)" <ji...@apache.org> on 2017/09/08 16:33:00 UTC

[jira] [Resolved] (KAFKA-1817) AdminUtils.createTopic vs kafka-topics.sh --create with partitions

     [ https://issues.apache.org/jira/browse/KAFKA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manikumar resolved KAFKA-1817.
------------------------------
    Resolution: Fixed

Fixed in  KAFKA-1737

> 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
>
> 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.4.14#64029)