[
https://issues.apache.org/jira/browse/KAFKA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151279#comment-14151279
]
Jun Rao commented on KAFKA-1634:
--------------------------------
Another use case is the following. It may not make sense to retain an offset
longer than the data retention time. So, if data is kept for only 7 days, a
consumer client may want to set timestamp to be now + 7 days to preserve the
offset as long as it's still valid.
Joel probably can comment on the general use cases more.
> Update protocol wiki to reflect the new offset management feature
> -----------------------------------------------------------------
>
> Key: KAFKA-1634
> URL: https://issues.apache.org/jira/browse/KAFKA-1634
> Project: Kafka
> Issue Type: Bug
> Reporter: Neha Narkhede
> Assignee: Jun Rao
> Priority: Blocker
> Fix For: 0.8.2
>
>
> From the mailing list -
> following up on this -- I think the online API docs for OffsetCommitRequest
> still incorrectly refer to client-side timestamps:
> https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-OffsetCommitRequest
> Wasn't that removed and now always handled server-side now? Would one of
> the devs mind updating the API spec wiki?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
