You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2011/08/18 13:06:27 UTC

[jira] [Updated] (KAFKA-111) A bug in the iterator of the ByteBufferMessageSet returns incorrect offsets when it encounters a compressed empty message set

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

Neha Narkhede updated KAFKA-111:
--------------------------------

    Attachment: KAFKA-111.patch

This patch corrects the offset management in the deep iterator of the ByteBufferMessageSet, to handle the case of compressed empty message sets.

> A bug in the iterator of the ByteBufferMessageSet returns incorrect offsets when it encounters a compressed empty message set
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-111
>                 URL: https://issues.apache.org/jira/browse/KAFKA-111
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.7
>            Reporter: Neha Narkhede
>         Attachments: KAFKA-111.patch
>
>
> The deep iterator logic in the ByteBufferMessageSet returns incorrect offsets when it encounters empty compressed data. Ideally, it should be able to decompress the data, figure out that it is somehow empty, skip it and proceed to decoding rest of the data. To make this possible, the manner in which we update the offset to be returned by the iterator, needs to be tweaked.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira