hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9307) BufferedFSInputStream.read returns wrong results after certain seeks
Date Thu, 14 Feb 2013 10:22:13 GMT

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

Steve Loughran commented on HADOOP-9307:

Interesting. I saw some quirks with data read/writes talking to OpenStack swift, but felt
that was eventual consistency related, not buffering. If you look in {{FileSystemContractBaseTest}}
there's some updated code for creating test datasets and comparing byte arrays in files -that
comparison code could be teased out, and/or a new test added to the contract "if you seek(offset)
then readFully(bytes[]), you get the data at file[offset]...file[offset+bytes.length-1]"

Let me add that to my list of things we assume that a filesystem does.

> BufferedFSInputStream.read returns wrong results after certain seeks
> --------------------------------------------------------------------
>                 Key: HADOOP-9307
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9307
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 1.1.1, 2.0.2-alpha
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
> After certain sequences of seek/read, BufferedFSInputStream can silently return data
from the wrong part of the file. Further description in first comment below.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message