[ 
https://issues.apache.org/jira/browse/HADOOP-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek Das updated HADOOP-17032:
----------------------------------
    Description: 
In case the viefs mount table is configured in a way where multiple child mount 
points are pointing to different file systems, the getContentSummary or 
getStatus don't return the expected result

mount link /a/b/ → hdfs://nn1/a/b
 mount link /a/d/ → [file:///nn2/c/d]

b has two files and d has 1 file. So getContentSummary on / should return 3 
files.

It also fails for the following scenario:

 

  was:
In case the viefs mount table is configured in a way where multiple child mount 
points are pointing to different file systems, the getContentSummary or 
getStatus don't return the expected result

mount link /a/b/ → hdfs://nn1/a/b
 mount link /a/d/ → [file:///nn2/c/d]

b has two files and d has 1 file. So getContentSummary on / should return 3 
files.


> Handle a internal dir in viewfs having multiple children mount points 
> pointing to different filesystems
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-17032
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17032
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs, viewfs
>            Reporter: Abhishek Das
>            Priority: Major
>
> In case the viefs mount table is configured in a way where multiple child 
> mount points are pointing to different file systems, the getContentSummary or 
> getStatus don't return the expected result
> mount link /a/b/ → hdfs://nn1/a/b
>  mount link /a/d/ → [file:///nn2/c/d]
> b has two files and d has 1 file. So getContentSummary on / should return 3 
> files.
> It also fails for the following scenario:
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to