[
https://issues.apache.org/jira/browse/VFS-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009441#comment-15009441
]
Roger Whitcomb commented on VFS-586:
------------------------------------
Some questions I had about this:
* This changes my earlier fix to rename "getConfigName" to "getConfigNames",
which now returns an array of String, instead of a single String. But since
2.1 is not released yet, is this acceptable? Also, this method is really only
meant to be called from inside HdfsFileSystem anyway, maybe it doesn't matter.
* Second, related question: now these are not real POJO "properties" since the
setter methods are named "setXXX" while the getter methods are "getXXXs"
(plural), with non-compatible return values (String vs. String[], Path vs.
Path[], etc.) Is this acceptable?
* Is this too big a change considering 2.1 was/is just about to be released?
Thanks.
> Add more ways to specify alternate HDFS configuration information
> -----------------------------------------------------------------
>
> Key: VFS-586
> URL: https://issues.apache.org/jira/browse/VFS-586
> Project: Commons VFS
> Issue Type: Improvement
> Affects Versions: 2.1
> Environment: All
> Reporter: Roger Whitcomb
> Priority: Minor
> Fix For: 2.1
>
> Attachments: hdfs-config.diffs
>
>
> In trying to resolve some customer issues we were experiencing, it was
> necessary to specify some alternate HDFS configuration information from some
> places other than resources in the current classpath, plus needing to specify
> multiple configurations (such as a local copy of "core-site.xml" and
> "hdfs-site.xml"). To accomplish this I have proposed some changes to
> HdfsFileSystemConfigBuilder.java and HdfsFileSystem.java to be able to
> specify alternate configurations from all the possible sources (as defined in
> org.apache.hadoop.fs.Configuration), namely from a named resource, from a
> local file Path, from an InputStream and from another Configuration object.
> For resource names and local files, multiple entries are allowed so that
> multiple configuration files can be specified as needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
