kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neha Narkhede (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-738) correlationId is not set in FetchRequest in AbstractFetcherThread
Date Tue, 29 Jan 2013 00:29:12 GMT

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

Neha Narkhede commented on KAFKA-738:

We don't use the builder pattern the way it is supposed to be used. The builder is created
once, setting the required values and calling build() happens multiple times. In our case,
this is complicated because we maintain some state in the request map, but this can easily
be resolved by providing a resetBuilder() API. That way, it will work for SimpleConsumer and
high level consumer
> 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

View raw message