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

[jira] [Resolved] (KAFKA-5078) PartitionRecords.fetchRecords(...) should defer exception to the next call if iterator has already moved across any valid record

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

Jiangjie Qin resolved KAFKA-5078.
---------------------------------
    Resolution: Fixed

> PartitionRecords.fetchRecords(...) should defer exception to the next call if iterator has already moved across any valid record
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-5078
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5078
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Dong Lin
>            Assignee: Dong Lin
>             Fix For: 0.11.0.0
>
>
> Suppose there are two valid records followed by one invalid records in the FetchResponse.PartitionData(). As of current implementation, PartitionRecords.fetchRecords(...) will throw exception without returning the two valid records. The next call to PartitionRecords.fetchRecords(...) will not return that two valid records either because the iterator has already moved across them.
> We can fix this problem by deferring exception to the next call of PartitionRecords.fetchRecords(...) if iterator has already moved across any valid record.



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