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

Mikhail Erofeev commented on HDFS-12292:
----------------------------------------

Thanks [~msingh] for looking into this jira and for pointing to this issue, I 
noticed only timeout in TestHDFSCLI message.
I fixed tests as you suggested, but now I am worried that the documentation in 
HdfsQuotaAdminGuide.md is not exactly precise, because the current exception 
will throw "File does not exist" instead of "Directory does not exist" as 
stated in the text. Moreover, depending on hdfs://test or /test, different 
exception texts will be sent, depending on which step it will fail. 
I think that the current solution is ok as the exception is precise enough at 
this level of abstraction. The method is used not only for quota commands, so 
not only dirs should be presented. And there should be an exception at this 
common level, as DfsAdmin commands operate only with existing files/dirs.
Please correct me if I am wrong, I am new to Hadoop contribution.

> Federation: Support viewfs:// schema path for DfsAdmin commands
> ---------------------------------------------------------------
>
>                 Key: HDFS-12292
>                 URL: https://issues.apache.org/jira/browse/HDFS-12292
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: federation
>            Reporter: Mikhail Erofeev
>            Assignee: Mikhail Erofeev
>         Attachments: HDFS-12292-002.patch, HDFS-12292-003.patch, 
> HDFS-12292.patch
>
>
> Motivation:
> As of now, clients need to specify a nameservice when a cluster is federated, 
> otherwise, the exception is fired:
> {code}
> hdfs dfsadmin -setQuota 10 viewfs://vfs-root/user/uname
> setQuota: FileSystem viewfs://vfs-root/ is not an HDFS file system
> # with fs.defaultFS = viewfs://vfs-root/
> hdfs dfsadmin -setQuota 10 vfs-root/user/uname
> setQuota: FileSystem viewfs://vfs-root/ is not an HDFS file system
> # works fine thanks to https://issues.apache.org/jira/browse/HDFS-11432
> hdfs dfsadmin -setQuota 10 hdfs://users-fs/user/uname
> {code}
> This creates inconvenience, inability to rely on fs.defaultFS and forces to 
> create client-side mappings for management scripts
> Implementation:
> PathData that is passed to commands should be resolved to its actual 
> FileSystem
> Result:
> ViewFS will be resolved to the actual HDFS file system



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to