[
https://issues.apache.org/jira/browse/KAFKA-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203322#comment-14203322
]
Vivek Madani commented on KAFKA-1737:
-------------------------------------
Faced this issue while using the AdminUtils in our CreateTopic wrapper as well.
I did went over the AdminUtils.scala and can submit a patch to set the
ZkStringSerializer on the passed ZkClient instance - only issue is that there
is no way to know whether setSerializer was called on the ZkClient instance by
the caller (there does not seem to be a getter in ZkClient for serializer). If
we set this to ZkStringSerializer we may override if it was already set to
something else. If that is acceptable, I can go ahead and submit the patch.
I am new to both Kafka and Zookeeper code, so I may have missed out something.
> Document required ZkSerializer for ZkClient used with AdminUtils
> ----------------------------------------------------------------
>
> Key: KAFKA-1737
> URL: https://issues.apache.org/jira/browse/KAFKA-1737
> Project: Kafka
> Issue Type: Improvement
> Components: tools
> Affects Versions: 0.8.1.1
> Reporter: Stevo Slavic
> Priority: Minor
>
> {{ZkClient}} instances passed to {{AdminUtils}} calls must have
> {{kafka.utils.ZKStringSerializer}} set as {{ZkSerializer}}. Otherwise
> commands executed via {{AdminUtils}} may not be seen/recognizable to broker,
> producer or consumer. E.g. producer (with auto topic creation turned off)
> will not be able to send messages to a topic created via {{AdminUtils}}, it
> will throw {{UnknownTopicOrPartitionException}}.
> Please consider at least documenting this requirement in {{AdminUtils}}
> scaladoc.
> For more info see [related discussion on Kafka user mailing
> list|http://mail-archives.apache.org/mod_mbox/kafka-users/201410.mbox/%3CCAAUywg-oihNiXuQRYeS%3D8Z3ymsmEHo6ghLs%3Dru4nbm%2BdHVz6TA%40mail.gmail.com%3E].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
