Jay Kreps 2013-01-03, 21:02
David Arthur 2013-01-03, 19:48
Jay Kreps 2013-01-04, 00:32
Jay Kreps 2013-01-04, 17:38
[ https://issues.apache.org/jira/browse/KAFKA-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544370#comment-13544370 ]
Jay Kreps commented on KAFKA-657:
I updated the property name. Normally I am against commenting out code since it is in version control anyway, but in this case those tests are actually useful and not in version control so probably makes sense to leave them.
> Add an API to commit offsets
> Key: KAFKA-657
> URL: https://issues.apache.org/jira/browse/KAFKA-657
> Project: Kafka
> Issue Type: New Feature
> Reporter: Jay Kreps
> Labels: project
> Fix For: 0.8.1
> Attachments: KAFKA-657v1.patch, KAFKA-657v2.patch, KAFKA-657v3.patch, KAFKA-657v4.patch, KAFKA-657v5.patch, KAFKA-657v6.patch, KAFKA-657v7.patch, KAFKA-657v8.patch
> Currently the consumer directly writes their offsets to zookeeper. Two problems with this: (1) This is a poor use of zookeeper, and we need to replace it with a more scalable offset store, and (2) it makes it hard to carry over to clients in other languages. A first step towards accomplishing that is to add a proper Kafka API for committing offsets. The initial version of this would just write to zookeeper as we do today, but in the future we would then have the option of changing this.
> This api likely needs to take a sequence of consumer-group/topic/partition/offset entries and commit them all.
> It would be good to do a wiki design on how this would work and consensus on that first.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Neha Narkhede 2013-01-04, 21:16
Joel Koshy 2013-01-02, 20:44
Jay Kreps 2013-01-02, 23:50
David Arthur 2012-12-20, 15:07
Jay Kreps 2012-12-20, 21:25
Neha Narkhede 2012-12-24, 00:52