[
https://issues.apache.org/jira/browse/HDFS-15979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323602#comment-17323602
]
Ahmed Hussein commented on HDFS-15979:
--------------------------------------
The test failures are not related to the changes. Those three tests have
related opened Jiras and they were failing for some time.
The changes were contributed by [~daryn] and we have our internal clusters
running on those changes with hadoop-2.8 and hadoop-2.10.
I made some modifications in order to handle the conflict since our internal
branch has a feature that is not merged yet into the community (HDFS-13009).
I always struggle with the decision of providing patches Vs PR because
reviewers have different preferences.
Since [~weichiu] Is watching this jira (he prefers PRs as far as I remember), I
am going to post a PR addressing the checkstyle warnings.
> 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
> Attachments: HDFS-15979.001.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
