Mailing-List: contact kafka-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: kafka-dev@incubator.apache.org
Date: Mon, 11 Jun 2012 23:50:43 +0000 (UTC)
From: "Neha Narkhede (JIRA)" <jira@apache.org>
To: kafka-dev@incubator.apache.org
Message-ID: <921094637.4751.1339458643225.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Created] (KAFKA-364) Consumer re-design
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Neha Narkhede created KAFKA-364:
-----------------------------------

             Summary: Consumer re-design
                 Key: KAFKA-364
                 URL: https://issues.apache.org/jira/browse/KAFKA-364
             Project: Kafka
          Issue Type: New Feature
            Reporter: Neha Narkhede
            Assignee: Neha Narkhede


We've received quite a lot of feedback on the consumer side features over the past few months. Some of them are improvements to the current consumer design and some are simply new feature/API requests. I have attempted to write up the requirements that I've heard on this wiki -

https://cwiki.apache.org/confluence/display/KAFKA/Consumer+Client+Re-Design

This would involve some significant changes to the consumer APIs, so we would like to collect feedback on the proposal from our community. Since the list of changes is not small, we would like to understand if some features are preferred over others, and more importantly, if some features are not required at all. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira