[
https://issues.apache.org/jira/browse/HADOOP-18878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066666#comment-18066666
]
ASF GitHub Bot commented on HADOOP-18878:
-----------------------------------------
ajfabbri opened a new pull request, #8353:
URL: https://github.com/apache/hadoop/pull/8353
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
From HADOOP-18878:
> the fs.s3a.multipart.purge option has been in for a long time, to help
avoid running up costs from incomplete uploads, especially during testing.
>
> but
>
> adds overhead on startup (list + delete)
> dangerous if one client has a very short lifespan; all active s3a
committer jobs will be broken
> obsoleted by s3 lifecycle rules
> and "hadoop s3guard uploads" cli.
> proposed: deprecate for the next release, delete after.
### How was this patch tested?
s3a integration tests run against localstack S3.
### For code changes:
- [x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [x] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [na] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [na ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
### AI Tooling
If an AI tool was used:
- [na ] The PR includes the phrase "Contains content generated by <tool>"
where <tool> is the name of the AI tool used.
- [x] My use of AI contributions follows the ASF legal policy
https://www.apache.org/legal/generative-tooling.html
> remove/deprecate fs.s3a.multipart.purge
> ---------------------------------------
>
> Key: HADOOP-18878
> URL: https://issues.apache.org/jira/browse/HADOOP-18878
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.6
> Reporter: Steve Loughran
> Assignee: Aaron Fabbri
> Priority: Major
>
> the fs.s3a.multipart.purge option has been in for a long time, to help avoid
> running up costs from incomplete uploads, especially during testing.
> but
> * adds overhead on startup (list + delete)
> * dangerous if one client has a very short lifespan; all active s3a committer
> jobs will be broken
> * obsoleted by s3 lifecycle rules
> * and "hadoop s3guard uploads" cli.
> proposed: deprecate for the next release, delete after.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
