[
https://issues.apache.org/jira/browse/HADOOP-17639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327248#comment-17327248
]
Viraj Jasani commented on HADOOP-17639:
---------------------------------------
Sounds good, I think yes it makes sense to continue supporting commands without
breaking arguments.
For this particular case, now I feel that *fs.trash.interval* at server side
should not be that required. And it should be all upto the client to utilize
this remove command. How about we introduce "*-useTrash*" as new command line
argument? That way, rm command will always have a choice to either use
"*-useTrash*" or "*-skipTrash*" without having to worry about whether server
has set trash interval > 0. Any thoughts?
> 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]
