[HDFS-13109] Support fully qualified hdfs path in EZ commands

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.1.0, 2.10.0, 2.9.1, 2.8.4, 3.0.3
• Component/s: hdfs
• Hadoop Flags: Reviewed
• Assignee: Hanisha Koneru
• Reporter: Hanisha Koneru
• Created: 06/Feb/18 01:15
• Updated: 05/Apr/18 20:15
• Resolved: 07/Mar/18 03:36

Description

When creating an Encryption Zone, if the fully qualified path is specified in the path argument, it throws the following error.

~$ 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?

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.

Issue Links

• duplicates: HDFS-12586 EZ createZone returns IllegalArgumentException when using protocol in path