You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Swapnil Ghike (JIRA)" <ji...@apache.org> on 2013/01/28 01:31:12 UTC

[jira] [Commented] (KAFKA-738) correlationId is not set in FetchRequest in AbstractFetcherThread

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

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

Probably because we create a new FetchRequestBuilder object in AbstractFetcherThread.doWork() and create the fetchRequest as 

val fetchRequest = fetchRequestBuilder.build() // this sets correlationId in fetchRequest to 0.


                
> 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
>            Priority: Blocker
>
> 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