[
https://issues.apache.org/jira/browse/HADOOP-19256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881799#comment-17881799
]
ASF GitHub Bot commented on HADOOP-19256:
-----------------------------------------
steveloughran commented on PR #7011:
URL: https://github.com/apache/hadoop/pull/7011#issuecomment-2351041617
@shameersss1 exactly. which means that fs.create(path, false).close() is
equivalent to other filesystems, though
```
st = fs.create(path, false)
st.write("I think I have exclusive access")
st.close()
```
is not quite the same as the failure is on line 3, not line 1. But the
overall behaviour holds: if the write completes then you created the file and
nobody has overwritten it.
file rename would be equivalent; dir rename not though.
Been distracted by this. something about "latest SDKs keep telling us off
for using the SDK" which is complicating my life and makes we really reluctant
to pick up a new SDK unless we are sure it fixes some longstanding issues. I
don't see why everyone is working on features when significant bugs exist and
every upgrade causes regressions in behaviour.
> S3A: 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
> Labels: pull-request-available
>
> 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]
