Return-Path: X-Original-To: apmail-kafka-dev-archive@www.apache.org Delivered-To: apmail-kafka-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B4FC3E695 for ; Thu, 3 Jan 2013 19:48:12 +0000 (UTC) Received: (qmail 1779 invoked by uid 500); 3 Jan 2013 19:48:12 -0000 Delivered-To: apmail-kafka-dev-archive@kafka.apache.org Received: (qmail 1755 invoked by uid 500); 3 Jan 2013 19:48:12 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 1744 invoked by uid 99); 3 Jan 2013 19:48:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jan 2013 19:48:12 +0000 Date: Thu, 3 Jan 2013 19:48:12 +0000 (UTC) From: "David Arthur (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-657) Add an API to commit offsets MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543227#comment-13543227 ] David Arthur commented on KAFKA-657: ------------------------------------ We had talked about limiting the size of the metadata to 1k or something and making this configurable. My question is: where does this config belong, and how to get it into KafkaApis? Right now, I've added this config to KafkaConfig and have passed in the "config" variable from KafkaServer to KafkaApis. Also, for the offset payloads, I'm opting to store them as a JSON object in ZooKeeper: {"offset": 42, "metadata": "foo"} > 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 > Attachments: KAFKA-657v1.patch, KAFKA-657v2.patch, KAFKA-657v3.patch, KAFKA-657v4.patch, KAFKA-657v5.patch, KAFKA-657v6.patch, KAFKA-657v7.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