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 "Vinayakumar B (Jira)" <ji...@apache.org> on 2019/09/03 05:37:00 UTC
[jira] [Commented] (HDFS-12212) Options.Rename.To_TRASH is
considered even when Options.Rename.NONE is specified
[ https://issues.apache.org/jira/browse/HDFS-12212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921176#comment-16921176 ]
Vinayakumar B commented on HDFS-12212:
--------------------------------------
thanks [~ayushtkn] for review and commit.
[~hanishakoneru] and [~jojochuang] for reviews.
> Options.Rename.To_TRASH is considered even when Options.Rename.NONE is specified
> --------------------------------------------------------------------------------
>
> Key: HDFS-12212
> URL: https://issues.apache.org/jira/browse/HDFS-12212
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.9.0, 2.7.4, 3.0.0-alpha1, 2.8.2
> Reporter: Vinayakumar B
> Assignee: Vinayakumar B
> Priority: Major
> Fix For: 3.3.0, 3.2.1, 3.1.4
>
> Attachments: HDFS-12212-01.patch
>
>
> HDFS-8312 introduced {{Options.Rename.TO_TRASH}} to differentiate the movement to trash and other renames for permission checks.
> When Options.Rename.NONE is passed also TO_TRASH is considered for rename and wrong permissions are checked for rename.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org