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 2021/03/11 15:11:00 UTC

[jira] [Updated] (HADOOP-17415) Use S3 content-range header to update length of an object during reads

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

Steve Loughran updated HADOOP-17415:
------------------------------------
    Parent: HADOOP-17566  (was: HADOOP-16829)

> 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
>            Priority: Major
>
> 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.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org