[
https://issues.apache.org/jira/browse/KAFKA-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182416#comment-15182416
]
Chi Hoang commented on KAFKA-3018:
----------------------------------
Coming back to this. Seems like the more appropriate design would be to split
server from core, and start moving code that will be shared by both client and
server to core. The suggestion to wait until the server rejects the topic
means we have to wait and have more complex interactions to get the true nature
of the problem. I would still prefer to have the failure occur the moment the
topic is referenced, and in this case, it is during instantiation of a
ProducerRecord. I'm also in favor of the server being the ultimate enforcer of
the topic name.
To save a few cycles, Topic can be a formal object which owns the validation,
and the ProducerRecord would take a Topic object instead of a String, so the
ProducerRecord constructor would not be responsible for validating the topic.
Splitting out another module would probably require a KIP, so I'm not going to
take another shot at this until we establish a direction.
> 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)
