[ https://issues.apache.org/jira/browse/HDFS-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379573#comment-16379573 ]
Hanisha Koneru commented on HDFS-13114: --------------------------------------- [~xyao], yes, the ListZonesCommand and ListReencryptionStatusCommand work as expected with the -fs command (without the fix too). > CryptoAdmin#ReencryptZoneCommand should resolve Namespace info from path > ------------------------------------------------------------------------ > > Key: HDFS-13114 > URL: https://issues.apache.org/jira/browse/HDFS-13114 > Project: Hadoop HDFS > Issue Type: Bug > Components: encryption, hdfs > Reporter: Hanisha Koneru > Assignee: Hanisha Koneru > Priority: Major > Attachments: HDFS-13114.001.patch > > > The {{crypto -reencryptZone <action> -path <zone>}} command takes in a path > argument. But when creating {{HdfsAdmin}} object, it takes the defaultFs > instead of resolving from the path. This causes the following exception if > the authority component in path does not match the authority of default Fs. > {code:java} > $ hdfs crypto -reencryptZone -start -path hdfs://mycluster-node-1:8020/zone1 > IllegalArgumentException: Wrong FS: hdfs://mycluster-node-1:8020/zone1, > expected: hdfs://ns1{code} > {code:java} > $ hdfs crypto -reencryptZone -start -path hdfs://ns2/zone2 > IllegalArgumentException: Wrong FS: hdfs://ns2/zone2, expected: > hdfs://ns1{code} -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org