Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <345167619.1252655517470.JavaMail.jira@brutus>
Date: Fri, 11 Sep 2009 00:51:57 -0700 (PDT)
From: "Hudson (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6196) sync(0); next() breaks SequenceFile
In-Reply-To: <1782929485.1250413814845.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HADOOP-6196:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #27 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk-Commit/27/])
    . Fix a bug in SequenceFile.Reader where syncing within the header
would cause the reader to read the sync marker as a record. Contributed by Jay Booth


> sync(0); next() breaks SequenceFile
> -----------------------------------
>
>                 Key: HADOOP-6196
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6196
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Jay Booth
>            Assignee: Jay Booth
>             Fix For: 0.21.0
>
>         Attachments: C6196-0.patch, C6196-test.patch, hadoop-6196-multipatch.txt, sync-bug.patch
>
>
> Currently, the end of the SequenceFile header is a sync block that isn't prefaced with SYNC_ESCAPE.  This means that sync(0) followed by next() fails.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.