[ 
https://issues.apache.org/jira/browse/HDFS-14739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908876#comment-16908876
 ] 

xuzq commented on HDFS-14739:
-----------------------------

I'm sorry,  maybe I didn't express it clearly.

First, I add some mount table use the command like:

_./bin/hdfs dfsrouteradmin -add /mnt ns0 /mnt -owner mnt -group mnt_group -mode 
755_

 _./bin/hdfs dfsrouteradmin -add /mnt/test1 ns0 /mnt/test1 -owner mnt_test1 
-group mnt_test1_group -mode 755_

 _./bin/hdfs dfsrouteradmin -add /test1 ns1 /test1 -owner test1 -group test1 
-mode 755_

 

Second, use hadoop fs shell to LS (in order to do getListing rpc), like:

_./bin/hadoop fs -ls /mnt_

 

 

And the result of FsShell Ls does not match my expect.

 

> RBF: LS command for mount point shows wrong owner and permission information.
> -----------------------------------------------------------------------------
>
>                 Key: HDFS-14739
>                 URL: https://issues.apache.org/jira/browse/HDFS-14739
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: xuzq
>            Priority: Major
>
> ||source||target namespace||destination||owner||group||permission||
> |/mnt|ns0|/mnt|mnt|mnt_group|755|
> |/mnt/test1|ns1|/mnt/test1|mnt_test1|mnt_test1_group|755|
> |/test1|ns1|/test1|test1|test1_group|755|
> When do getListing("/mnt"), the owner of  */mnt/test1* should be *mnt_test1* 
> instead of *test1* in result.
>  
> And if the mount table as blew, we should support getListing("/mnt") instead 
> of throw IOException when dfs.federation.router.default.nameservice.enable is 
> false.
> ||source||target namespace||destination||owner||group||permission||
> |/mnt/test1|ns0|/mnt/test1|test1|test1|755|
> |/mnt/test2|ns1|/mnt/test2|test2|test2|755|
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to