Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
From: Roger Whitcomb <Roger.Whitcomb@actian.com>
To: Commons Developers List <dev@commons.apache.org>
Subject: RE: [VFS] Further changes to HDFS Provider for alternate
 configuration support
Thread-Topic: [VFS] Further changes to HDFS Provider for alternate
 configuration support
Thread-Index: AdEgtnK1dzsIHkIGQvWcMki7cKKqhQADZ9kAAFygrEA=
Date: Wed, 18 Nov 2015 19:24:47 +0000
Message-ID: 
 <SN1PR0601MB1565203ECE35AE26C4F24033E71C0@SN1PR0601MB1565.namprd06.prod.outlook.com>
References: 
 <CY1PR0601MB156301F4CF0B050588FF3799E71E0@CY1PR0601MB1563.namprd06.prod.outlook.com>
 <015801d120c4$128b4150$37a1c3f0$@comcast.net>
In-Reply-To: <015801d120c4$128b4150$37a1c3f0$@comcast.net>
Accept-Language: en-US
Content-Language: en-US
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Nov 2015 19:24:47.3263
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 20057ce9-1386-4770-8b04-e7824ef632be
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0601MB1565
X-MC-Unique: SHy701YoQTO6vks5dICd_A-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

I have opened issue https://issues.apache.org/jira/browse/VFS-586 with my p=
roposed patch attached, and these questions included in the issue.  Updated=
 the patch with some things I noticed after the initial post also.

Thanks,
~Roger

-----Original Message-----
From: dlmarion@comcast.net [mailto:dlmarion@comcast.net]=20
Sent: Monday, November 16, 2015 3:11 PM
To: 'Commons Developers List' <dev@commons.apache.org>
Subject: RE: [VFS] Further changes to HDFS Provider for alternate configura=
tion support

I don't see the patch. It might be stripped off by the mail server.

=20

From: Roger Whitcomb [mailto:Roger.Whitcomb@actian.com]
Sent: Monday, November 16, 2015 5:12 PM
To: Commons Developers List
Subject: [VFS] Further changes to HDFS Provider for alternate configuration=
 support

=20

Hi all,

                In trying to solve some customer issues we're having, mainl=
y to do with trying to browse HDFS files when the Name Node is configured f=
or High-Availability, I found I needed to make some more changes/additions =
to the VFS HDFS Provider.  I have attached a diff/patch file.  But, a coupl=
e of
questions:

.         This is a follow-on (basically) to my earlier patch for VFS-555,
should I open a new JIRA, or just reopen the existing one?

.         Since this actually changes an API (but which is not released
yet), is that an acceptable thing to do?

.         The new properties I have added to HdfsFileSystemConfigBuilder ar=
e
not actually symmetrical, so they don't fit the definition of a Java "prope=
rty", that is the setters are "setXXX" while the getters are "getXXXs"
(plural). The logic behind this is that the setters are called by user code=
, and each can be called multiple times.  The getters are only (meant to be=
) called by the HdfsFileSystem object (that is internally to the HdfsProvid=
er), and thus it is a lot easier to get all the settings at once than to ha=
ve to make multiple calls, with potentially iterators, etc.

.         Is this too big a change to fit in last-minute before the release
of VFS 2.1?

=20

Patch is attached.

=20

Thanks,

~Roger Whitcomb


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org