You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2012/07/18 22:17:35 UTC
[jira] [Updated] (KAFKA-352) Throw exception to client if it makes
a produce/consume request to a Kafka broker for a topic that hasn't been
created
[ https://issues.apache.org/jira/browse/KAFKA-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neha Narkhede updated KAFKA-352:
--------------------------------
Attachment: kafka-352-v1.patch
1. Improved error handling for produce, fetch, get offsets request to handle unknown topic error code
2. Topic metadata request error handling is fixed as part of KAFKA-350.
3. I understand that we have KAFKA-402 filed to go over all other error handling. This patch only handled unknown topics and unit tested it for all types of requests.
> Throw exception to client if it makes a produce/consume request to a Kafka broker for a topic that hasn't been created
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-352
> URL: https://issues.apache.org/jira/browse/KAFKA-352
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Attachments: kafka-352-v1.patch
>
>
> It will be good to inform the client if it makes a produce/consume request to a Kafka broker for a topic that hasn't been created. The exception should be something like UnknownTopicException that is descriptive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira