[
https://issues.apache.org/jira/browse/KAFKA-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182433#comment-15182433
]
Chi Hoang commented on KAFKA-3018:
----------------------------------
The server is already correctly validating the topic name, and the message
coming from the server is also pretty clear. The problem described in this
ticket revolve around how the client handles it.
[~granthenke]'s original suggestion was to move the topic validation to the
common client code, and I thought it was sensible and would have made things
simpler. However, that meant that core would continue to depend on client, and
that part was not so sensible to me. I don't know the history behind making
core dependent on client - git blame shows that KAFKA-1237 introduced this
relationship - so if we want to maintain this dependency chain, I would go back
to Grant's original suggestion and move the logic to clients-->common. I have
enough context to make that change and push a new pr.
> Kafka producer hangs on producer.close() call if the producer topic contains
> single quotes in the topic name
> ------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-3018
> URL: https://issues.apache.org/jira/browse/KAFKA-3018
> Project: Kafka
> Issue Type: Bug
> Components: producer
> Affects Versions: 0.8.2.0
> Reporter: kanav anand
> Assignee: Jun Rao
>
> While creating topics with quotes in the name throws a exception but if you
> try to close a producer configured with a topic name with quotes the producer
> hangs.
> It can be easily replicated and verified by setting topic.name for a producer
> with a string containing single quotes in it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
