[
https://issues.apache.org/jira/browse/HADOOP-19256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885003#comment-17885003
]
ASF GitHub Bot commented on HADOOP-19256:
-----------------------------------------
steveloughran commented on PR #7011:
URL: https://github.com/apache/hadoop/pull/7011#issuecomment-2376887483
@diljotgrewal except in the special case of "massive merge conflict
requiring a rebase", can you just use merge commits once we are in the review
phase. Github lets me review changes happened since my last review -but it
cannot do this with forced pushes. This makes my life harder and reduces the
frequency of me actually looking at patches.
I will review later
> 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]