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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2013/07/09 19:13:49 UTC

[jira] [Updated] (HADOOP-9713) FSDataInputStream.readFully doesn't work on filesystems without seek -even when the offset==getPos

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

Steve Loughran updated HADOOP-9713:
-----------------------------------

          Component/s: fs
    Affects Version/s: 1.3.0
                       2.1.0-beta
                       3.0.0
    
> FSDataInputStream.readFully doesn't work on filesystems without seek -even when the offset==getPos
> --------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9713
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9713
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 3.0.0, 2.1.0-beta, 1.3.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> {{FSDataInputStream.readFully(offset,data)}} doesn't work even if the offset==the current location -because it always seeks to the offset and seeks back. No seek => Exception.
> We could optimise {{FSDataInputStream.readFully(offset,data)}} to eliminate the seeks on these operations -which would have tangible benefits for those filesystems where seek is expensive (remote blobstores). It would also let you use readFully against filesystems without seeks, provided you are only reading from the current location.

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