[
https://issues.apache.org/jira/browse/HDDS-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDDS-3574:
--------------------------------
Target Version/s: 0.6.0
Labels: Triaged pull-request-available (was:
pull-request-available)
> Implement ofs://: Override getTrashRoot
> ---------------------------------------
>
> Key: HDDS-3574
> URL: https://issues.apache.org/jira/browse/HDDS-3574
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
> Labels: Triaged, pull-request-available
>
> [~pifta] found if we delete file with Hadoop shell, namely {{hadoop fs -rm}},
> without {{-skipTrash}} option, the operation would fail in OFS due to the
> client is renaming the file to {{/user/<username>/.Trash/}} because renaming
> across different buckets is not allowed in Ozone. (Unless the file happens to
> be under {{/user/<username>/}}, apparently.)
> We could override {{getTrashRoot()}} in {{BasicOzoneFileSystem}} to a dir
> under the same bucket to mitigate the problem. Thanks [~umamaheswararao] for
> the suggestion.
> This raises one more problem though: We need to implement trash clean up on
> OM. Opened HDDS-3575 for this.
> CC [~arp] [~bharat]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
