[
https://issues.apache.org/jira/browse/HADOOP-11417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293495#comment-14293495
]
Steve Loughran commented on HADOOP-11417:
-----------------------------------------
looks like s3n, s3a and swift all fail here: either they check and reject, or
they hand off to HTTP to open at the offset, which then fails.
It would be nice to have a common solution. To complicate things, they will all
need to close their http input streams, so that future seeks don't get confused
as to where they are, so other bits of the code will have to check for this now
special state "streams closed at end of file", differentiating it from "streams
closed after close()"
> review filesystem seek logic, clarify/confirm spec, test & fix compliance
> -------------------------------------------------------------------------
>
> Key: HADOOP-11417
> URL: https://issues.apache.org/jira/browse/HADOOP-11417
> Project: Hadoop Common
> Issue Type: Task
> Components: fs, fs/s3, fs/swift
> Affects Versions: 2.6.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
>
> HADOOP-11270 implies there's a diff in the way HDFS seeks and the object
> stores on the action {{seek(len(file))}}
> # review what HDFS does, add contract test to exactly demonstrate HDFS
> behaviour.
> # ensure FS spec is consistent with this
> # test/audit all supported filesystems to verify consistent behaviour
> # fix where appropriate
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
