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

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

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

   
   New trash policies, and a schema specific trash policy set by
   
   fs.SCHEMA.trash.policy.
   
   This lets clusters declare different policies for different stores
   in the same cluster.
   
   ResilientTrashPolicy: for abfs with rename failure resilience
   DeleteFilesTrashPolicy: for versioned s3 buckets; delete the files.
   
   
   ### How was this patch tested?
   
   what do you mean, tested?
   
   
   ### For code changes:
   
   - [ ] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] 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?
   
   




> ABFS: add resilient trash policy
> --------------------------------
>
>                 Key: HADOOP-18013
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18013
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/azure
>    Affects Versions: 3.3.2
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>
> Add a custom TrashPolicy for azure which
> * is patched in to the config automatically if "fs.trash.classname" is unset
> * checks the source for existing at all before trying anything
> * considers itself enabled even if the trash interval is 0
> * if interval is 0, just does a delete (issue: what about 90s timeouts)
> * downgrades exceptions/failures during rename. If anything is raised and the 
> source dir isn't there, all is good.



--
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