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/26 18:57:35 UTC

[jira] [Commented] (KAFKA-412) deal with empty TopicData list in producer and fetch request

    [ https://issues.apache.org/jira/browse/KAFKA-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423228#comment-13423228 ] 

Neha Narkhede commented on KAFKA-412:
-------------------------------------

Can we change nRequestedPartitions to something like numPartitions ? 

Other than that, it looks good. 

+1
                
> deal with empty TopicData list in producer and fetch request
> ------------------------------------------------------------
>
>                 Key: KAFKA-412
>                 URL: https://issues.apache.org/jira/browse/KAFKA-412
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>             Fix For: 0.8
>
>         Attachments: kafka-412_v1.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Both producer and fetch request can pass in an empty list of TopicData. Instead of handling those requests through RequestPurgatory, we should just send a response with an empty list immediately.

--
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