[ 
https://issues.apache.org/jira/browse/HADOOP-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882689#comment-17882689
 ] 

ASF GitHub Bot commented on HADOOP-19278:
-----------------------------------------

steveloughran opened a new pull request, #7052:
URL: https://github.com/apache/hadoop/pull/7052

   
   - Removes a lot of code and testing
   - Lines up for pushing more code down into S3AStore (but does not do this)
   
   
   ### How was this patch tested?
   
   - Marker tool tests all failing.
   
   ### 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?
   - [ ] 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)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> S3A: remove option to deletel directory markers
> -----------------------------------------------
>
>                 Key: HADOOP-19278
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19278
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/s3
>    Affects Versions: 3.4.1
>            Reporter: Steve Loughran
>            Priority: Major
>
> We've supported directory marker retention since HADOOP-13230 went in.
> and switch to making it the default in HADOOP-18752
> nobody has ever complained about this.
> proposed: cut directory marker deletion entirely.
> this will
> * simplify our code
> * cut down on test options



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to