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 Tue, 29 Jan 2013 00:23:13 GMT

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

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

I see. Actually the same issue is present in hadoop-consumer's use of builder.build(). Unit
tests look fine with patch v2.
                
> 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, kafka-738_v2.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