[
https://issues.apache.org/jira/browse/HADOOP-18752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727884#comment-17727884
]
ASF GitHub Bot commented on HADOOP-18752:
-----------------------------------------
ayushtkn commented on PR #5689:
URL: https://github.com/apache/hadoop/pull/5689#issuecomment-1569931307
yep, it is like that, lot of discussions and tickets around this, example:
[HDFS-13505](https://issues.apache.org/jira/browse/HDFS-13505), this is also
marked as incompatible and was pushed only to trunk. This comment also says the
same thing
(https://issues.apache.org/jira/browse/HDFS-13505?focusedCommentId=16854777&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16854777)
may be the reason is like if someone had a use case like he explicitly
wanted the conf to be "delete" for whatever reasons and the default value was
also "delete", he didn't configure it considering the default value, now if you
change it to "keep", that guy who explicitly wanted the value to be delete, he
has to change and have to configure it to "delete" to preserve his old
behaviour.
Not against this change, just telling the generic stuff around config
defaults, what I have read or know about the compat :-)
> Change fs.s3a.directory.marker.retention to "keep"
> --------------------------------------------------
>
> Key: HADOOP-18752
> URL: https://issues.apache.org/jira/browse/HADOOP-18752
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.5
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
>
> Change the default value of "fs.s3a.directory.marker.retention" to keep;
> update docs to match.
> maybe include with HADOOP-17802 so we don't blow up with fewer markers being
> created.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
