Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Message-ID: <794068487.1252193817504.JavaMail.jira@brutus>
Date: Sat, 5 Sep 2009 16:36:57 -0700 (PDT)
From: "Chris Douglas (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Subject: [jira] Reopened: (HADOOP-6196) sync(0); next() breaks SequenceFile
In-Reply-To: <1557218490.1250413814794.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:all-tabpanel ]

Chris Douglas reopened HADOOP-6196:
-----------------------------------


No patch fixing this issue has been integrated into 0.21, yet; a committer needs to review and approve the patch before it can be pushed to the repository and we can resolve the issue as "fixed." I'm reopening the issue and marking it "patch available" again.

Considering the pain of writing incompatible SequenceFiles, I'm leaning away from bumping the version and just going with the compatible change to the reader. If the modified Reader approach seems hackish or I'm overestimating the pain of bumping the version, I'm open to the alternate strategy, but unless we have formats that call sync(0) regularly it seems like a reasonable workaround.

> 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.  Patch w/ test attached, bumps VERSION from 6 to 7.

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