[
https://issues.apache.org/jira/browse/HADOOP-19256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876076#comment-17876076
]
Viraj Jasani commented on HADOOP-19256:
---------------------------------------
{quote}we already use conditional headers in read operations, using version or
etag of a file to ensure that every GET in an input stream either always picks
up the same file version (versioned option) or just etag validation (default)
{quote}
Steve, i agree that we have the changeDetectionPolicy
(fs.s3a.change.detection.source), but it is still generic config and the config
name does not say that it is used by getObject only, correct? i was thinking
about having API level header as s3afs config but now i think whatever the
header value we want to use for conditional writes, we want to use it for all
APIs: getObject, headObject and copyObject headers rather than only for select
ones.
Even in that case, does it still make sense to have a config that can take
multiple key-value pairs like i mentioned above? because as per the docs,
multiple headers can also be provided e.g. If-Match and If-Unmodified-Since.
> Support S3 Conditional Writes
> -----------------------------
>
> Key: HADOOP-19256
> URL: https://issues.apache.org/jira/browse/HADOOP-19256
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Ahmar Suhail
> Priority: Major
>
> S3 Conditional Write (Put-if-absent) capability is now generally available -
> [https://aws.amazon.com/about-aws/whats-new/2024/08/amazon-s3-conditional-writes/]
>
> S3A should allow passing in this put-if-absent header to prevent over writing
> of files.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
