Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 80378200D19 for ; Fri, 6 Oct 2017 21:22:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7EB34160BDC; Fri, 6 Oct 2017 19:22:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C50D9160BDB for ; Fri, 6 Oct 2017 21:22:05 +0200 (CEST) Received: (qmail 10844 invoked by uid 500); 6 Oct 2017 19:22:04 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 10825 invoked by uid 99); 6 Oct 2017 19:22:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Oct 2017 19:22:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 34F0318112C for ; Fri, 6 Oct 2017 19:22:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id P6Lr7iqDk7jq for ; Fri, 6 Oct 2017 19:22:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id B700260DDF for ; Fri, 6 Oct 2017 19:22:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B742BE0F17 for ; Fri, 6 Oct 2017 19:22:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id EDBEA24360 for ; Fri, 6 Oct 2017 19:22:00 +0000 (UTC) Date: Fri, 6 Oct 2017 19:22:00 +0000 (UTC) From: "Gary Gregory (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (VFS-586) Add more ways to specify alternate HDFS configuration information MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 06 Oct 2017 19:22:06 -0000 [ https://issues.apache.org/jira/browse/VFS-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated VFS-586: ----------------------------- Fix Version/s: (was: 2.2) 2.2.1 > 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.2.1 > > Attachments: hdfs-config-2.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.4.14#64029)