[jira] [Updated] (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:all-tabpanel ] Jun Rao updated KAFKA-738: -- Resolution: Fixed Fix Version/s: 0.8 Status: Resolved (was: Patch Available) Thanks for the review. Committed to 0.8. 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 Fix For: 0.8 Attachments: kafka-738.patch, kafka-738.patch, kafka-738_v2.patch, kafka-738_v3.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
[jira] [Updated] (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:all-tabpanel ] Jun Rao updated KAFKA-738: -- Attachment: kafka-738.patch Attach a patch. Yes, we have to create a new FetchRequestBuilder every time, since some of the old values need to be cleared. 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 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
