[
https://issues.apache.org/jira/browse/HADOOP-9495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639654#comment-13639654
]
Steve Loughran commented on HADOOP-9495:
----------------------------------------
the seek past the EOF is actually a core feature of the unix {{fseek()}} and
windows equivalent. It is so that if you have a file open for writing, you can
seek somewhere past the end of a file and write to it. It may also be to deal
with shared access files, where there may not be data at a specific offset on
the {{seek()}}, but there is on the {{read()}}: checking at seek time is overly
pessimistic.
Because of that feature, the underlying local FS has that behaviour (though
ChecksumFs is stricter).
> Define behaviour of Seekable.seek(), write tests, fix all hadoop
> implementations for compliance
> -----------------------------------------------------------------------------------------------
>
> Key: HADOOP-9495
> URL: https://issues.apache.org/jira/browse/HADOOP-9495
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs
> Affects Versions: 1.2.0, 3.0.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
>
> {{Seekable.seek()}} seems a good starting point for specifying, testing and
> implementing FS API compliance: one method, relatively non-ambiguous
> semantics, easily assessed used in the Hadoop codebase. Specify and test it
> first
--
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
