[ https://issues.apache.org/jira/browse/HDFS-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Erofeev updated HDFS-12292: ----------------------------------- Description: 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 was: 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 > Federation: Support viewfs:// schema path for DfsAmdin 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 > > 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