You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Roger Whitcomb (JIRA)" <ji...@apache.org> on 2015/01/08 18:23:34 UTC

[jira] [Commented] (VFS-555) Add ability to specify alternate HDFS configuration file

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

Roger Whitcomb commented on VFS-555:
------------------------------------

Since I'm an Apache committer, I propose to commit this change within a few days unless objections are raised.  Thanks for opening up Commons to all committers!

> Add ability to specify alternate HDFS configuration file
> --------------------------------------------------------
>
>                 Key: VFS-555
>                 URL: https://issues.apache.org/jira/browse/VFS-555
>             Project: Commons VFS
>          Issue Type: Improvement
>    Affects Versions: 2.1
>         Environment: All
>            Reporter: Roger Whitcomb
>            Priority: Minor
>             Fix For: 2.1
>
>         Attachments: VFS-555.patch
>
>
> We need to access HDFS on an AWS installation from outside the AWS firewall.  The technique is described here:  http://rainerpeter.wordpress.com/2014/02/12/connect-to-hdfs-running-in-ec2-using-public-ip-addresses/
> In order to do this we need to set the "dfs.client.use.datanode.hostname=true" in an alternate configuration file set after the default configuration is loaded.
> I propose to add a property "configName" to HdfsFileSystemConfigBuilder, and then code in HdfsFileSystem to get the value of the property and set it in the Configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)