Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 31 May 2016 17:27:12 +0000 (UTC)
From: "Illes S (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12973821.1464544786000.339676.1464715632977@Atlassian.JIRA>
In-Reply-To: <JIRA.12973821.1464544786000@Atlassian.JIRA>
References: <JIRA.12973821.1464544786000@Atlassian.JIRA> <JIRA.12973821.1464544786001@arcas>
Subject: [jira] [Updated] (HADOOP-13214) sync(0); next(); yields wrong
 key-values on block-compressed files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 31 May 2016 17:27:14 -0000


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

Illes S updated HADOOP-13214:
-----------------------------
    Attachment: HADOOP-13214.2.patch

Added unit tests for the issue being fixed.

> sync(0); next(); yields wrong key-values on block-compressed files
> ------------------------------------------------------------------
>
>                 Key: HADOOP-13214
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13214
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: io
>            Reporter: Illes S
>              Labels: easyfix, newbie
>         Attachments: HADOOP-13214.2.patch, HADOOP-13214.patch
>
>
> Calling {{sync(0); next(...);}} on a block-compressed {{SequenceFileReader}} that has already been used may not yield the key-values at the beginning, but those following the previous position. The issue is caused by {{sync(0)}} not releasing previously buffered keys and values. The issue was introduced by HADOOP-6196


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org