[
https://issues.apache.org/jira/browse/KAFKA-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739246#comment-14739246
]
Ewen Cheslack-Postava commented on KAFKA-2500:
----------------------------------------------
[~hachikuji] The only drawback to pushing it to the next release is that in the
meantime people end up having to write some awkward and error-prone code to
achieve the same thing. See, e.g., what I've done in a patch for Copycat for
offset storage (and will also need the same for config storage I think):
https://github.com/apache/kafka/pull/202/files#diff-9fc968ba381156d12e5c645336ccf9f1R209
Since you actually have to seek and poll to get the info unless you issue the
request yourself, you could potentially leave yourself in a bad state if
something goes wrong (e.g. if you fail to properly seek back to your previous
position).
> Make logEndOffset available in the 0.8.3 Consumer
> -------------------------------------------------
>
> Key: KAFKA-2500
> URL: https://issues.apache.org/jira/browse/KAFKA-2500
> Project: Kafka
> Issue Type: Sub-task
> Components: consumer
> Affects Versions: 0.8.3
> Reporter: Will Funnell
> Assignee: Jason Gustafson
> Priority: Critical
> Fix For: 0.8.3
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
