[
https://issues.apache.org/jira/browse/KAFKA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265042#comment-14265042
]
Dana Powers commented on KAFKA-1634:
------------------------------------
possibly related to this JIRA: KAFKA-1841 . The timestamp field itself was not
in the released api version 0 and if it is to be included in 0.8.2 (this JIRA
suggests it is, but to be removed in 0.8.3 ?) then I think it will need to be
versioned.
> Improve semantics of timestamp in OffsetCommitRequests and update
> documentation
> -------------------------------------------------------------------------------
>
> Key: KAFKA-1634
> URL: https://issues.apache.org/jira/browse/KAFKA-1634
> Project: Kafka
> Issue Type: Bug
> Reporter: Neha Narkhede
> Assignee: Guozhang Wang
> Priority: Blocker
> Fix For: 0.8.3
>
> Attachments: KAFKA-1634.patch, KAFKA-1634_2014-11-06_15:35:46.patch,
> KAFKA-1634_2014-11-07_16:54:33.patch, KAFKA-1634_2014-11-17_17:42:44.patch,
> KAFKA-1634_2014-11-21_14:00:34.patch, KAFKA-1634_2014-12-01_11:44:35.patch,
> KAFKA-1634_2014-12-01_18:03:12.patch
>
>
> 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)
