[KAFKA-2500] Expose fetch response high watermark in ConsumerRecords

• Type: Sub-task
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 0.9.0.0
• Component/s: consumer
• Assignee: Jason Gustafson
• Reporter: Will Funnell
• Created: 01/Sep/15 20:50
• Updated: 24/Jan/17 05:42

Description

Originally created in the old consumer here: https://issues.apache.org/jira/browse/KAFKA-1977

The requirement is to create a snapshot from the Kafka topic but NOT do continual reads after that point. For example you might be creating a backup of the data to a file.

This ticket covers the addition of the functionality to the new consumer.

In order to achieve that, a recommended solution by Joel Koshy and Jay Kreps was to expose the high watermark, as maxEndOffset, from the FetchResponse object through to each MessageAndMetadata object in order to be aware when the consumer has reached the end of each partition.
The submitted patch achieves this by adding the maxEndOffset to the PartitionTopicInfo, which is updated when a new message arrives in the ConsumerFetcherThread and then exposed in MessageAndMetadata.
See here for discussion:
http://search-hadoop.com/m/4TaT4TpJy71

Issue Links

• relates to: KAFKA-1977 Make logEndOffset available in the Zookeeper consumer