[
https://issues.apache.org/jira/browse/HDDS-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17244444#comment-17244444
]
Marton Elek commented on HDDS-3367:
-----------------------------------
One more question: Based on the design doc, I see that "Extend
KeyDeletingService in Ozone" has more pros with fewer cons compared with
"Reusing Hadoop Trash Emptier".
Based on my limited understanding it means that we don't need to use
OzoneFileSystem at OM side. But code seems to use FileSystem interface on the
OM side which seems to be a heaviweght implementation.
Can you please share more information about the motivation?
> Trash Support for Ozone FileSystem
> ----------------------------------
>
> Key: HDDS-3367
> URL: https://issues.apache.org/jira/browse/HDDS-3367
> Project: Hadoop Distributed Data Store
> Issue Type: New Feature
> Components: Ozone Filesystem
> Affects Versions: 1.0.0
> Reporter: Sadanand Shenoy
> Assignee: Sadanand Shenoy
> Priority: Blocker
> Attachments: OzoneFilesystemTrashImplementation.pdf,
> OzoneFsTrash.patch
>
>
> The aim of this jira to add the trash feature capability in ozone that will
> help prevent accidental deletion of files and directories. When a file gets
> deleted in Ozone, the file is not immediately expelled from Ozone but will be
> moved to trash. Similarly as in HDFS, to immediately delete a file, a
> skipTrash option will be provided. The jira also aims to integrate the Ozone
> FS Trash to the Trash API developed as a part of HDDS-2416.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
