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 "Ahmed Hussein (Jira)" <ji...@apache.org> on 2021/04/15 18:06:00 UTC
[jira] [Work started] (HDFS-15979) Move within EZ fails and cannot
remove nested EZs
[ https://issues.apache.org/jira/browse/HDFS-15979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on HDFS-15979 started by Ahmed Hussein.
--------------------------------------------
> Move within EZ fails and cannot remove nested EZs
> -------------------------------------------------
>
> Key: HDFS-15979
> URL: https://issues.apache.org/jira/browse/HDFS-15979
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: encryption, hdfs
> Reporter: Ahmed Hussein
> Assignee: Ahmed Hussein
> Priority: Major
>
> Moving between EZ directories should work fine if the EZ key for the directories is identical. If the key is name identical then no decrypt/re-encrypt is necessary.
> However, the rename operation checks more than the key name. It compares the inode number (unique identifier) of the source and dest dirs which will never be the same for 2 dirs resulting in the cited failure. Note it also incorrectly compares the key version.
> A related issue is if an ancestor of a EZ share the same key (ie. /projects/foo and /projects/foo/bar/blah both use same key), files also cannot be moved from the child to a parent dir, plus the child EZ cannot be removed even though it's now covered by the ancestor.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org