You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Shilun Fan (Jira)" <ji...@apache.org> on 2024/01/04 07:47:00 UTC

[jira] [Commented] (HDFS-11091) Implement a getTrashRoot that does not fall-back

    [ https://issues.apache.org/jira/browse/HDFS-11091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802528#comment-17802528 ] 

Shilun Fan commented on HDFS-11091:
-----------------------------------

Bulk update: moved all 3.4.0 non-blocker issues, please move back if it is a blocker. Retarget 3.5.0.

> Implement a getTrashRoot that does not fall-back
> ------------------------------------------------
>
>                 Key: HDFS-11091
>                 URL: https://issues.apache.org/jira/browse/HDFS-11091
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 2.8.0
>            Reporter: Xiao Chen
>            Assignee: Yuanbo Liu
>            Priority: Major
>
> From HDFS-10756's [discussion|https://issues.apache.org/jira/browse/HDFS-10756?focusedCommentId=15623755&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15623755]:
> {{getTrashRoot}} is supposed to return the trash dir considering encryption zone. But if there's an error encountered (e.g. access control exception), it falls back to the default trash dir.
> Although there is a warning message about this, it is still a somewhat surprising behavior. The fall back was added by HDFS-9799 for compatibility reasons. This jira is to propose we add a getTrashRoot that throws, which will actually be more user-friendly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org