kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Swapnil Ghike (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-738) correlationId is not set in FetchRequest in AbstractFetcherThread
Date Mon, 28 Jan 2013 23:17:13 GMT

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

Swapnil Ghike commented on KAFKA-738:
-------------------------------------

With this patch, all fetchRequests in SimpleConsumerShell will have correlationId = 0. This
will happen in a bunch of unit tests too.
A solution could be to use the same fetchRequestBuilder in AbstractFetcherThread, but clear
its old values every time in doWork(). This way we can make sure that a fetchRequestBuilder
can increment its own correlationId with every call to build().
                
> correlationId is not set in FetchRequest in AbstractFetcherThread
> -----------------------------------------------------------------
>
>                 Key: KAFKA-738
>                 URL: https://issues.apache.org/jira/browse/KAFKA-738
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>            Priority: Blocker
>              Labels: p2
>         Attachments: kafka-738.patch
>
>
> correlationId is always 0 in FetchRequest in AbstractFetcherThread.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message