[
https://issues.apache.org/jira/browse/HADOOP-9985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776216#comment-13776216
]
Steve Loughran commented on HADOOP-9985:
----------------------------------------
Lohit, I can see why just changing the default FS parameter isn't enough -if
you want to support inputs across clusters then you may need explicit source
and dest URLs. Though if your code is using hdfs://// that's a very much
"default" reference that is deprecated in 2.x (what if the default FS isn't
HDFS?)
did you try just subverting `hdfs.fs.impl` to point to the viewfs
implementation, or didn't that work due to viewfs being fussy about the URIs
and/or you also wanting to use HDFS locally?
Otherwise, the general best practise is "don't have hard code URIs in your
scripts", though that is easier said than done if you have a lot of existing
scripts.
Can you stick up your new FS for us to look at?
> HDFS Compatible ViewFileSystem
> ------------------------------
>
> Key: HADOOP-9985
> URL: https://issues.apache.org/jira/browse/HADOOP-9985
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Lohit Vijayarenu
> Fix For: 2.0.6-alpha
>
>
> There are multiple scripts and projects like pig, hive, elephantbird refer to
> HDFS URI as hdfs://namenodehostport/ or hdfs:/// . In federated namespace
> this causes problem because supported scheme for federation is viewfs:// . We
> will have to force all users to change their scripts/programs to be able to
> access federated cluster.
> It would be great if thee was a way to map viewfs scheme to hdfs scheme
> without exposing it to users. Opening this JIRA to get inputs from people who
> have thought about this in their clusters.
> In our clusters we ended up created another class
> HDFSCompatibleViewFileSystem which hijacks both hdfs.fs.impl and
> viewfs.fs.impl and passes down filesystem calls to ViewFileSystem. Is there
> any suggested approach other than this?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
