You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2017/05/08 16:46:04 UTC

[jira] [Resolved] (KAFKA-4839) throw NoOffsetForPartitionException once for all assigned partitions from poll

     [ https://issues.apache.org/jira/browse/KAFKA-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson resolved KAFKA-4839.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.11.0.0

Issue resolved by pull request 2637
[https://github.com/apache/kafka/pull/2637]

> throw NoOffsetForPartitionException once for all assigned partitions from poll
> ------------------------------------------------------------------------------
>
>                 Key: KAFKA-4839
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4839
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients
>    Affects Versions: 0.10.2.0
>            Reporter: radai rosenblatt
>            Assignee: radai rosenblatt
>             Fix For: 0.11.0.0
>
>
> KafkaConsumer.poll() will currently throw NoOffsetForPartitionException if reset strategy is "none" and there are no defined offsets.
> problem is the exception will only be thrown for the 1st such partition encountered.
> since a single consumer can be the owner of thousands of partitions this results in a lot of exception that need to be caught and handled.
> its possible to throw the exception once for all such TopicPartitions without any user-visible API changes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)