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

Manoj Govindassamy commented on HADOOP-13055:
---------------------------------------------

[~andrew.wang],

HADOOP-14136 has requested for DefaultFS to fallback whenever the mounts are 
not resolvable. Kind of Hierarchical Mount FS support for ViewFS but only at 
the root level. This does bring in whole new set of cases to consider for all 
other supported FS operations on ViewFS, but I am going to investigate on what 
it takes to get fallback DefaultFS for ViewFS. Would your concern on this jira 
HADOOP-13055 and the patch be addressed if we can club this in with the fix for 
HADOOP-14136 ? Please share your thoughts. 

> Implement linkMergeSlash for ViewFileSystem
> -------------------------------------------
>
>                 Key: HADOOP-13055
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13055
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: fs, viewfs
>            Reporter: Zhe Zhang
>            Assignee: Manoj Govindassamy
>         Attachments: HADOOP-13055.00.patch, HADOOP-13055.01.patch, 
> HADOOP-13055.02.patch, HADOOP-13055.03.patch, HADOOP-13055.04.patch
>
>
> In a multi-cluster environment it is sometimes useful to operate on the root 
> / slash directory of an HDFS cluster. E.g., list all top level directories. 
> Quoting the comment in {{ViewFs}}:
> {code}
>  *   A special case of the merge mount is where mount table's root is merged
>  *   with the root (slash) of another file system:
>  *   <ul>
>  *   <li>    fs.viewfs.mounttable.default.linkMergeSlash=hdfs://nn99/
>  *   </ul>
>  *   In this cases the root of the mount table is merged with the root of
>  *            <b>hdfs://nn99/ </b> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to