[
https://issues.apache.org/jira/browse/HADOOP-17415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039023#comment-18039023
]
ASF GitHub Bot commented on HADOOP-17415:
-----------------------------------------
github-actions[bot] commented on PR #3939:
URL: https://github.com/apache/hadoop/pull/3939#issuecomment-3544466261
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> Use S3 content-range header to update length of an object during reads
> ----------------------------------------------------------------------
>
> Key: HADOOP-17415
> URL: https://issues.apache.org/jira/browse/HADOOP-17415
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Assignee: Monthon Klongklaew
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> As part of all the openFile work, knowing full length of an object allows for
> a HEAD to be skipped. But: code knowing only the splits don't know the final
> length of the file.
> If the content-range header is used, then as soon as a single GET is
> initiated against an object, if the field is returned then we can update the
> length of the S3A stream to its real/final length
> Also: when any input stream fails with an EOF exception, we can distinguish
> stream-interrupted from "no, too far"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
