You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2014/09/20 21:03:34 UTC

[jira] [Commented] (KAFKA-1634) Update protocol wiki to reflect the new offset management feature

    [ https://issues.apache.org/jira/browse/KAFKA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14142161#comment-14142161 ] 

Neha Narkhede commented on KAFKA-1634:
--------------------------------------

[~junrao], that explanation is actually pretty unintuitive. So seems like this is something that needs to be fixed. The client shouldn't need to specify a timestamp for an offset commit. Unless I'm missing something that it is designed for. [~jjkoshy], any idea?

> 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: Joel Koshy
>            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)