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 2020/02/14 13:01:00 UTC
[jira] [Updated] (HADOOP-16202) S3A openFile() operation to support
explicit versionID, etag parameters
[ https://issues.apache.org/jira/browse/HADOOP-16202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-16202:
------------------------------------
Parent Issue: HADOOP-16829 (was: HADOOP-15620)
> S3A openFile() operation to support explicit versionID, etag parameters
> -----------------------------------------------------------------------
>
> Key: HADOOP-16202
> URL: https://issues.apache.org/jira/browse/HADOOP-16202
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Priority: Major
>
> The {{openFile()}} builder API lets us add new options when reading a file
> Proposed: allowing applications to explicitly demand on. If we explicitly add the values in the S3A filestatus & located filestatus (maybe even: checksum?), then you can list a directory and. knowing those values, explicitly ask for that version of file.
> {code}
> org.apache.fs.s3a.open.versionid + versionID
> org.apache.fs.s3a.open.etag + etag
> {code}
> setting both will be an error.
--
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