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

Virajith Jalaparti commented on HDFS-15436:
-------------------------------------------

[~umamaheswararao]
bq. is there a case your configured cluster name is different than fs.defaultFS

No, in our case the configured cluster name is the same as fs.defaultFS. 
However, the scheme of the path used by an application may not match the scheme 
of fs.defaultFS. And this path doesn't have the authority. Hence, the current 
logic in {{FileSystem#get}} to use the cluster name of fs.defaultFS doesn't 
kick in.

Thanks for the review! Will address those shortly.

> Default mount table name used by ViewFileSystem should be configurable
> ----------------------------------------------------------------------
>
>                 Key: HDFS-15436
>                 URL: https://issues.apache.org/jira/browse/HDFS-15436
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: viewfs, viewfsOverloadScheme
>            Reporter: Virajith Jalaparti
>            Assignee: Virajith Jalaparti
>            Priority: Major
>
> Currently, if no authority is provided and the scheme of the Path is doesn't 
> match the scheme of the {{fs.defaultFS}} , the mount table used by 
> ViewFileSystem to resolve this path is {{default}}. 
> This breaks accesses to path like {{hdfs:///foo/bar}} (without any authority) 
> when the following configurations are used:
> (1) {{fs.defaultFS}} = {{viewfs://clustername/}} 
> (2) {{fs.hdfs.impl = 
> org.apache.hadoop.fs.viewfs.ViewFileSystemOverloadScheme}}
> This JIRA proposes to add a new configuration 
> {{fs.viewfs.mounttable.default.name.key}} which is used to get the name of 
> the cluster/mount table when the authority is missing in cases like the 
> above. If not set, the string {{default}} will be used as today.



--
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