[
https://issues.apache.org/jira/browse/KAFKA-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064110#comment-15064110
]
Jens Rantil commented on KAFKA-3007:
------------------------------------
> Is this on the dev mailing list? If so, please can you share a link archived
> discussion on this thread.
Aarti gupta: Here's a link to the first message in the user mailing list
thread:
http://mail-archives.apache.org/mod_mbox/kafka-users/201512.mbox/%3CCAL%2BArfWNfkpymkNDuf6UJ06CJJ63XC1bPHeT4TSYXKjSsOpu-Q%40mail.gmail.com%3E
> This could either be a second argument to poll() or a configuration option.
I proposed using a configuration option as that could open up more
optimizations on startup instead of during runtime.
> new Consumer should expose mechanism to fetch single message,
> consumer.poll(timeout, maxMessageLimit)
> -----------------------------------------------------------------------------------------------------
>
> 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)
