[
https://issues.apache.org/jira/browse/HADOOP-17639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324914#comment-17324914
]
Steve Loughran commented on HADOOP-17639:
-----------------------------------------
no objection to the web ui, but not the CLI.
HADOOP-11553 was a big piece of work to give scripts stability. [~aw] put a lot
of effort in and if there's some incompatible change then he, amongst others,
will be unhappy.
In the cloud land, having trash itself is somewhat superfluous given that the
stores themselves
* AWS S3: https://docs.aws.amazon.com/AmazonS3/latest/userguide/Versioning.html
* azure wasb (not yet abfs):
https://docs.microsoft.com/en-us/azure/storage/blobs/versioning-overview
* Google GCS: https://cloud.google.com/storage/docs/object-versioning
see also HADOOP-15575, which argues for letting filesystems disable trash when
they know that they have versioned file access and there's no need to (slowly)
rename anything.
> Restrict the "-skipTrash" param for accidentally deletes data
> -------------------------------------------------------------
>
> Key: HADOOP-17639
> URL: https://issues.apache.org/jira/browse/HADOOP-17639
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Bhavik Patel
> Priority: Major
>
> Suppose the user tries to delete the data from CLI with the "-skipTrash"
> param but by mistake, he deleted a couple of directories but actually, that
> directory user want to retain then their is no way to retrieve the delete
> data.
> It will be good to have a confirm message like: "Skip the trash for the
> hdfs:///dri1/file.txt files? (Y or N)" ro we can completely disable the
> "-skipTrash" param.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
