You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Illes S (JIRA)" <ji...@apache.org> on 2016/05/29 18:17:12 UTC

[jira] [Commented] (HADOOP-13214) sync(0); next(); yields wrong key-values on block-compressed files

    [ https://issues.apache.org/jira/browse/HADOOP-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306016#comment-15306016 ] 

Illes S commented on HADOOP-13214:
----------------------------------

A workaround until the issue is fixed:
{code:java}
reader.sync(0);
reader.seek(reader.getPosition()); // drops buffered key-values without doing I/O
reader.next(...); // yields key-values from the beginning of the file
{code}

> 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.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