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

Lei Yang updated HADOOP-18193:
------------------------------
    Description: 
Defining following client mount table config is not supported in  INodeTree and 
will throw FileAlreadyExistsException

fs.viewfs.mounttable.link./foo/bar=hdfs://nn1/foo/bar

fs.viewfs.mounttable.link./foo=hdfs://nn02/foo

 

INodeTree has 2 methods that need change to support nested mount points.

createLink(..)

resolve(..)

 

ViewFileSystem and ViewFs referes INodeTree.resolve(..) to resolve path to 
specific mount point. No changes are expected in both classes. 

  was:
Defining following client mount table config is not supported in  INodeTree and 
will throw FileAlreadyExistsException

fs.viewfs.mounttable.link./foo/bar=hdfs://nn1/foo/bar

fs.viewfs.mounttable.link./foo=hdfs://nn02/foo

 


> Support nested mount points in INodeTree
> ----------------------------------------
>
>                 Key: HADOOP-18193
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18193
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: viewfs
>    Affects Versions: 2.10.0
>            Reporter: Lei Yang
>            Priority: Major
>
> Defining following client mount table config is not supported in  INodeTree 
> and will throw FileAlreadyExistsException
> fs.viewfs.mounttable.link./foo/bar=hdfs://nn1/foo/bar
> fs.viewfs.mounttable.link./foo=hdfs://nn02/foo
>  
> INodeTree has 2 methods that need change to support nested mount points.
> createLink(..)
> resolve(..)
>  
> ViewFileSystem and ViewFs referes INodeTree.resolve(..) to resolve path to 
> specific mount point. No changes are expected in both classes. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

Reply via email to