[
https://issues.apache.org/jira/browse/HDDS-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076670#comment-17076670
]
Matthew Sharp commented on HDDS-2416:
-------------------------------------
[~shashikant] one of the early assumptions with this feature was to enable
trash by bucket. With that approach it was an opt in or out model, so there
were no discussions around having a skipTrash option as part of this. If a
bucket was enabled you checked the existing deleted keys table to find the keys
and if it wasn't enabled you didn't worry about it. This also worked nicely
with GDPR, forcing buckets to be one or the other to ensure data was really
deleted.
With that, one of the items to decide on is if we even want a skipTrash option?
We are planning to have a way for users to empty trash (separate command) to
help minimize overhead of retaining large deletes, in addition to the
configurable recovery window where it would get purged automatically. It feels
like the empty-trash and skipTrash overlap a bit though.
> Ozone Trash Feature
> -------------------
>
> Key: HDDS-2416
> URL: https://issues.apache.org/jira/browse/HDDS-2416
> Project: Hadoop Distributed Data Store
> Issue Type: New Feature
> Reporter: Matthew Sharp
> Assignee: Matthew Sharp
> Priority: Minor
> Attachments: Ozone_Trash_Feature.docx
>
>
> This Jira is a proposal to add a new feature to Ozone that provides a user
> with the ability to recover keys that may have been deleted accidentally.
> This would be similar to the HDFS trash feature.
>
> The attached document outlines the proposal and considerations for this
> feature.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
