[
https://issues.apache.org/jira/browse/KAFKA-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062904#comment-15062904
]
aarti gupta commented on KAFKA-3007:
------------------------------------
Is this on the dev mailing list? If so, please can you share a link archived
discussion on this thread.
( search on the archives, did not reveal the specific archived conversation)
Trying to understand the reason for the long poll to - not currently include
this control, (i.e. why the pollOnce method is private) , and how other users
are overcoming this in the current version of the client.
We could have a large number of messages backed up, and fetching all messages
in memory for all clients of all topics, is not feasible. (which makes this a
road blocker in migrating to the new client)
> new Consumer should expose mechanism to fetch single message
> -------------------------------------------------------------
>
> Key: KAFKA-3007
> URL: https://issues.apache.org/jira/browse/KAFKA-3007
> Project: Kafka
> Issue Type: Improvement
> Components: consumer
> Affects Versions: 0.9.0.0
> Reporter: aarti gupta
> Assignee: Neha Narkhede
>
> Currently, the consumer.poll(timeout)
> returns all messages that have not been acked since the last fetch
> The only way to process a single message, is to throw away all but the first
> message in the list
> This would mean we are required to fetch all messages into memory, and this
> coupled with the client being not thread-safe, (i.e. we cannot use a
> different thread to ack messages, makes it hard to consume messages when the
> order of message arrival is important, and a large number of messages are
> pending to be consumed)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
