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 "Hanisha Koneru (JIRA)" <ji...@apache.org> on 2018/02/13 20:22:00 UTC
[jira] [Commented] (HDFS-13109) Support fully qualified hdfs path
in EZ commands
[ https://issues.apache.org/jira/browse/HDFS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362993#comment-16362993 ]
Hanisha Koneru commented on HDFS-13109:
---------------------------------------
Thanks for the review, [~xyao].
Uploaded patch v02 with a unit test and fixed checkstyle.
> Support fully qualified hdfs path in EZ commands
> ------------------------------------------------
>
> Key: HDFS-13109
> URL: https://issues.apache.org/jira/browse/HDFS-13109
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Priority: Major
> Attachments: HDFS-13109.001.patch, HDFS-13109.002.patch
>
>
> When creating an Encryption Zone, if the fully qualified path is specified in the path argument, it throws the following error.
> {code:java}
> ~$ hdfs crypto -createZone -keyName mykey1 -path hdfs://ns1/zone1
> IllegalArgumentException: hdfs://ns1/zone1 is not the root of an encryption zone. Do you mean /zone1?
> ~$ hdfs crypto -createZone -keyName mykey1 -path "hdfs://namenode:9000/zone2"
> IllegalArgumentException: hdfs://namenode:9000/zone2 is not the root of an encryption zone. Do you mean /zone2?
> {code}
> The EZ creation succeeds as the path is resolved in DFS#createEncryptionZone(). But while creating the Trash directory, the path is not resolved and it throws the above error.
> A fully qualified path should be supported by {{crypto}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org